Page 2 of 4
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sun Jul 26, 2020 2:37 am
by ispyisail
@stevencox
I'm not sure where to start...............
I have a C7 v2 running 1.12.x and its rock solid.
In my opinion your shouldn't but running 1.13.x at this stage in the development cycle for production networks.
I would go back to 1.12.x then talk to us about your problems.
I suspect your problem are not with Gargoyle. Going to 1.13.x is not going to help find these problems.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Tue Jul 28, 2020 12:30 pm
by Cezary
wordpr3ss wrote: ↑Sat Jun 20, 2020 1:39 pm
When configured as a repeater, right after reboot, I lost UI access (only get a purpleish background after login), before I can ssh to get some log, it would disappear from network (wifi interface is still active though).
sorry that i don't have a log.
My user reported something like this, but I can't get him to report a bug.
Code: Select all
Mon Jul 13 21:08:22 2020 kern.info kernel: [ 60.225967] do_page_fault(): sending SIGSEGV to gargoyle_header for invalid read access from 00000000
Mon Jul 13 21:08:22 2020 kern.info kernel: [ 60.235193] epc = 77f87014 in libc.so[77f13000+98000]
Mon Jul 13 21:08:22 2020 kern.info kernel: [ 60.240254] ra = 004026c5 in gargoyle_header_footer[400000+6000]
Mon Jul 13 21:08:22 2020 daemon.err uhttpd[4757]: Segmentation fault
See
https://eko.one.pl/forum/viewtopic.php? ... 26#p241726
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Tue Jul 28, 2020 6:29 pm
by Lantis
Is this only happening in repeater mode? I haven't seen this.
Need more information on what is causing it.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Wed Jul 29, 2020 12:32 am
by Cezary
No, probably in normal "router" mode. It doesn't happen with me either.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sat Aug 01, 2020 3:05 am
by Lantis
I pushed a fix which solves that bug when being used in repeater. I think it fixes all cases, but it might happen when using usb 3g/4g type connectivity as well.
I spent a while hunting this bug down. There's a great guide on what format a good bug report should be in here:
https://github.com/ericpaulbishop/gargo ... rting-bugs
Ultimately this leads to me finding the bug faster, and everyone getting a fix faster.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Fri Aug 07, 2020 2:16 pm
by wbennett88
Hi all,
Very new to Gargoyle and just wanted to know what is the difference between the Lantis builds and the regular Gargoyle builds?
Thanks!
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Fri Aug 07, 2020 7:15 pm
by Lantis
About 18 months of improvements and new features.
New releases are infrequent. These builds fill some of the gap and allow testing of new functionality.
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sat Aug 08, 2020 3:45 pm
by wbennett88
Lantis wrote: ↑Fri Aug 07, 2020 7:15 pm
About 18 months of improvements and new features.
New releases are infrequent. These builds fill some of the gap and allow testing of new functionality.
Thanks for the response and all that you do for the project Lantis! It's good to be here! Cheers!
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sat Aug 08, 2020 4:20 pm
by wbennett88
So, I upgraded my Archer C7 v2 to the Lantis Ath79 using the sysupgrade file. The router seems to functioning normally but I have a problem. I can get to the login page and type in my password but once logged in all I get is a blank page with the same background I had on my login page. Is it possible that the theme I was using with 1.12 was/is not compatible with the newer version? If so, is there a way to correct this using ssh?
Re: 1.13.x with IPv6 Test Build - 20200619
Posted: Sat Aug 08, 2020 7:57 pm
by ispyisail
wbennett88 wrote: ↑Sat Aug 08, 2020 4:20 pm
So, I upgraded my Archer C7 v2 to the Lantis Ath79 using the sysupgrade file. The router seems to functioning normally but I have a problem. I can get to the login page and type in my password but once logged in all I get is a blank page with the same background I had on my login page. Is it possible that the theme I was using with 1.12 was/is not compatible with the newer version? If so, is there a way to correct this using ssh?
You upgraded using a backup file or ticked preserve setting?
If so just reset your router