Version 1.13.0 : Based on OpenWrt 19.07.8

The latest news about Gargoyle

Moderator: Moderators

ispyisail
Moderator
Posts: 5033
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ispyisail »

What happens to IPv6 when you force DNS to a specific provider?

I to scared to play with this feature anymore. I specified a DNS provider and that was when my router crashed big time.

Lantis
Moderator
Posts: 6394
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by Lantis »

DNS is setup to work with both ipv4 and ipv6.
I don't think the force has been changed to suit though, and would only force ipv4. Ipv6 would sail on through uninterrupted.
I have mine set to use Cloudflare, for example.

I'm not seeing any issues on my end sorry. I ran it in production for 2 years.
That router sounds like it is having serious issues. Have you tried putting a different one into play?
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

pythonic
Posts: 155
Joined: Mon Mar 11, 2019 5:47 am
Location: Australia

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by pythonic »

ViBE wrote:
Mon Jun 20, 2022 10:24 am
pythonic wrote:
Fri Jun 03, 2022 8:14 am
The GL-MT300N-V2 (Mango), if that's what you have, is supported by my MT76x8 experimental build.
i can't do a comprehensive test but did what i can. overall it looks good. BUT now i noticed an issue. if i connect it via cable to my main router it cannot get IP for some reason.
Hmmm... I don't recall whether I tested that configuration (was more interested in using my Mango with a 4G dongle). Will give this a look when I get some time off in a 3-4 weeks, when I also hope to update the build to the latest 19.07 sources - thanks for the report.

ViBE
Posts: 188
Joined: Sun Apr 19, 2015 6:58 pm

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ViBE »

pythonic wrote:
Tue Jun 21, 2022 7:10 am
ViBE wrote:
Mon Jun 20, 2022 10:24 am
pythonic wrote:
Fri Jun 03, 2022 8:14 am
The GL-MT300N-V2 (Mango), if that's what you have, is supported by my MT76x8 experimental build.
i can't do a comprehensive test but did what i can. overall it looks good. BUT now i noticed an issue. if i connect it via cable to my main router it cannot get IP for some reason.
Hmmm... I don't recall whether I tested that configuration (was more interested in using my Mango with a 4G dongle). Will give this a look when I get some time off in a 3-4 weeks, when I also hope to update the build to the latest 19.07 sources - thanks for the report.
with 4G modems no such issues. it connects. that's why i didn't notice this issue before, cause mainly i bought it for travelling. but i started to test via cable and i have no success with this one. i have an AR300 too which has the original GL firmware. it connects instantly so my main router operates well. kinda MTK based issue i guess. thank's for your work.

ispyisail
Moderator
Posts: 5033
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ispyisail »

That router sounds like it is having serious issues. Have you tried putting a different one into play?
I think this is a good conclusion

I was starting to think the same thing, the more I think about this, the more I think its true.

Thank you, as always

ViBE
Posts: 188
Joined: Sun Apr 19, 2015 6:58 pm

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ViBE »

as a part of my home network rebuild/update is to format my network storage for several reasons. after formatting with Gargoyle i have to edit the swap. but before i do it i checked the partitions and fdisk -l gave me a strange output:

Code: Select all

Disk /dev/sdb: 5.47 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: PURZ-85ZUFY1    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E7842045-6289-4157-A5D3-32BAD783F0C8

Device           Start         End     Sectors  Size Type
/dev/sdb1         2048 11603834716 11603832669  5.4T VMware Virsto
/dev/sdb2  11603834880 11721045134   117210255 55.9G VMware Virtual SAN
the filesystem is detected as VMware filesystem. why? and why is it read-only on PC? is this normal?

ejlviking
Posts: 13
Joined: Mon Jun 20, 2016 4:59 pm

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ejlviking »

Hi,
I'm running 1.12 and looking to upgrade to 1.13 on my TPLINK WDR3600 , but I do not find the ar71xx version. I only see the ath79 for WDR3600.

Is the ar71xx not supported or still in test mode?

Thanks!

Lantis
Moderator
Posts: 6394
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by Lantis »

Introduced ath79 target (successor to ar71xx) and moved all images from ar71xx to ath79 where support was available (NOTE: use ath79 images where possible, all images will be ath79 in future releases)
Hope that helps.
Do not preserve settings between the two.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

ejlviking
Posts: 13
Joined: Mon Jun 20, 2016 4:59 pm

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ejlviking »

Lantis wrote:
Wed Jun 29, 2022 6:27 pm
Introduced ath79 target (successor to ar71xx) and moved all images from ar71xx to ath79 where support was available (NOTE: use ath79 images where possible, all images will be ath79 in future releases)
Hope that helps.
Do not preserve settings between the two.
Perfect!
Thanks.

ViBE
Posts: 188
Joined: Sun Apr 19, 2015 6:58 pm

Re: Version 1.13.0 : Based on OpenWrt 19.07.8

Post by ViBE »

ViBE wrote:
Wed Jun 29, 2022 6:31 am
as a part of my home network rebuild/update is to format my network storage for several reasons. after formatting with Gargoyle i have to edit the swap. but before i do it i checked the partitions and fdisk -l gave me a strange output:

Code: Select all

Disk /dev/sdb: 5.47 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: PURZ-85ZUFY1    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E7842045-6289-4157-A5D3-32BAD783F0C8

Device           Start         End     Sectors  Size Type
/dev/sdb1         2048 11603834716 11603832669  5.4T VMware Virsto
/dev/sdb2  11603834880 11721045134   117210255 55.9G VMware Virtual SAN
the filesystem is detected as VMware filesystem. why? and why is it read-only on PC? is this normal?
any ideas..?

Post Reply