Page 3 of 4
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sat Aug 08, 2020 9:37 pm
by Lantis
Don't preserve settings from 1.12 to 1.13.
Addtionally if you are using wireless bridge config, you should wait for the next build where I fixed an error causing the exact symptom you are describing.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sun Aug 09, 2020 5:40 pm
by wbennett88
Lantis wrote: ↑Sat Aug 08, 2020 9:37 pm
Don't preserve settings from 1.12 to 1.13.
Addtionally if you are using wireless bridge config, you should wait for the next build where I fixed an error causing the exact symptom you are describing.
Attempting to preserve settings was probably what caused my problem. I tried resetting the router and reflashing the firmware but the problem persisted. I was able to go back to 1.12 and reconfigure and all is good. I am using the router as a gateway with DHCP turned off, a static address and my main router for DNS. (Dumb AP)
If there is nothing in this setup that prevents me from upgrading to 1.13 I hope to try again tomorrow without preserving settings.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sun Aug 09, 2020 6:43 pm
by Lantis
If you have it in a configuration that doesn't have WAN, you will have trouble.
Your description doesn't really match what I would call Dumb AP, so I am not certain you will be affected.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Mon Aug 10, 2020 8:07 am
by wbennett88
Sorry, forgot to mention that I have Wan disabled.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Mon Aug 10, 2020 12:04 pm
by wbennett88
OKay, I reflashed 1.13 and this time I did not preserve settings. I was able to setup the router as a "DumbAP". Setup as Gateway, I disabled the wan and DHCP, gave it a static IP and put the main router as the DNS.
The router seems to be operating just fine but I am still having the same GUI problems. I can get to the login page but once logged in the GUI disappears and I just see the purple background. I don't have any GUI issues with 1.12.
Any suggestions?
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Mon Aug 10, 2020 6:01 pm
by Lantis
It is the same issue as already described. You can build from the latest code or wait for someone else to do so for you
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Mon Aug 10, 2020 6:54 pm
by wbennett88
Lantis wrote: ↑Mon Aug 10, 2020 6:01 pm
It is the same issue as already described. You can build from the latest code or wait for someone else to do so for you
Thanks Lantis, I will wait for your next build.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sun Aug 23, 2020 7:06 pm
by wordpr3ss
Thanks a lot for fixing the "BSOD" problem
I tried
1.13.0.x gargoyle-ispy 2020-August-17 19, still having trouble with repeater mode (Model:NETGEAR WNDRMACv2):
I can't access anything if I connected to the repeater wifi. I won't get an ip assigned by the AP dhcp. I can't access anything even if I manually set an ip/gateway in AP's subnet.
However I can ssh into the the repeater through its relay IP (10.0.0.6) from the AP,and I checked the routes, looked fine, and the repeater itself can reach the AP/internet.
Not sure how to debug further. I don't have ipv6 setup but not sure if or how to determine that's the problem.
I wish I could debug more, but my skill here is limited
couldn't make the image work here.
https://ibb.co/ggbTS0H
https://ibb.co/646kk9X
Thanks again for the gargoyle build!
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sun Aug 23, 2020 8:50 pm
by Lantis
Is your upstream AP also Gargoyle? If so, ensure that "Enforce DHCP Assignments" is disabled.
Other than that, your settings look OK.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Mon Aug 24, 2020 12:42 am
by wordpr3ss
Thanks for looking into it.
The upstream AP is ddwrt (no openwrt supported due to tainted kernel, i guess).
The exact setup works for gargoyle 1.12.
If it's just dhcp, manually setting up IP should work, but it didn't. So I suspect it's something more.
Lantis wrote: ↑Sun Aug 23, 2020 8:50 pm
Is your upstream AP also Gargoyle? If so, ensure that "Enforce DHCP Assignments" is disabled.
Other than that, your settings look OK.