gargoyle 1.5.11 wired network issue

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
coits
Posts: 118
Joined: Thu Sep 19, 2013 1:58 am
Location: canada

gargoyle 1.5.11 wired network issue

Post by coits »

Hi All,

I have installed gargoyle 1.5.11 firmware on buffalo ag300h and wifi 2.4 and 5 Ghz are working fine. but, after 5 days the gigabit wired network stop working, I tried to ping google on my windows 7 machine with no response.

i have tried to ipconfig /release and ipconfig /flushdns then /renew but, it seems that dhcp cannot allocate ip address.

I tried to login on my tablet on the router administrator and did a reboot on the router then after that everything is back to normal.

Any thought why is this happening.

Thanks in advance.
Gargoyle 1.9.x on Buffalo WZR-HP-AG300H
Gargoyle 1.10.x on TP-Link Archer C7 v2.0
Gargoyle 1.11.x on WRT3200 acm

coits
Posts: 118
Joined: Thu Sep 19, 2013 1:58 am
Location: canada

Re: gargoyle 1.7.1 wired network issue

Post by coits »

Hi,

After 75 days of uptime, all of a sudden no gigabit lan connection on the router. I tried to use wifi and it's working fine. I check on the connection list and all of my wired connection are not showing. but, all the wifi connection are showing.

Is this a firmware bugs? after almost 2 months of uptime, All of a sudden this problem will happen. the only solution is to reboot the router.

So we cannot have longer uptime with gargoyle, I'm using gargoyle 1.7.1 firmware from ispyisail.

Can someone please shed some light on this problem?

Thank you.
Gargoyle 1.9.x on Buffalo WZR-HP-AG300H
Gargoyle 1.10.x on TP-Link Archer C7 v2.0
Gargoyle 1.11.x on WRT3200 acm

tapper
Moderator
Posts: 1076
Joined: Sun Oct 13, 2013 5:49 pm
Location: Stoke-on-trent UK

Re: gargoyle 1.5.11 wired network issue

Post by tapper »

I dont no why but 75 days is a long time just set a reboot for 20 days or somthing like that. you can set it monthly.
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260

nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:

Re: gargoyle 1.7.1 wired network issue

Post by nworbnhoj »

coits wrote:Is this a firmware bugs? after almost 2 months of uptime ........ Can someone please shed some light on this problem?
Tapper has offered a practical workaround, but with a possible "bug" like this, that might take 2 months for a developer to reproduce, it is critically important that you capture and post the logs at the time of the failure - otherwise developers have nothing to go on. If you see this issue again could you please try and capture some logs before you reboot?
Can you help someone else get Gargoyle up and running?
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E

coits
Posts: 118
Joined: Thu Sep 19, 2013 1:58 am
Location: canada

Re: gargoyle 1.5.11 wired network issue

Post by coits »

I have a remote syslog server and have diverted all the log into it.
I will dig on the logs and will post some information that will shed some light on this issue.

Thanks
Gargoyle 1.9.x on Buffalo WZR-HP-AG300H
Gargoyle 1.10.x on TP-Link Archer C7 v2.0
Gargoyle 1.11.x on WRT3200 acm

coits
Posts: 118
Joined: Thu Sep 19, 2013 1:58 am
Location: canada

Re: gargoyle 1.5.11 wired network issue

Post by coits »

So far these are the logs on my syslog server, the moment I have no LAN network.

Before the reboot, no LAN connection.
Jul 10 05:37:23 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:37:23 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:37:27 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:37:27 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:37:36 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:37:36 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:37:52 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:37:52 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:37:57 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:37:57 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:38:05 192.168.30.1 dnsmasq-dhcp[4169]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 05:38:05 192.168.30.1 dnsmasq-dhcp[4169]: DHCPACK(br-lan) 192.168.30.133
Jul 10 05:38:31 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:38:31 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:38:36 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:38:36 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:38:40 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:38:40 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:38:48 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:38:48 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:39:04 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:39:04 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:39:37 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:39:37 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:39:40 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:39:40 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:39:49 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:39:49 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 05:40:06 192.168.30.1 dnsmasq-dhcp[4169]: DHCPDISCOVER(br-lan) 192.168.30.133
Jul 10 05:40:06 192.168.30.1 dnsmasq-dhcp[4169]: DHCPOFFER(br-lan) 192.168.30.133


These are the log after I manually restart the network using this command /etc/init.d/network restart.
Jul 10 06:34:40 192.168.30.1 netifd: Bridge 'br-lan' link is up
Jul 10 06:34:40 192.168.30.1 netifd: Interface 'lan' has link connectivity
Jul 10 06:34:41 192.168.30.1 firewall: Reloading firewall due to ifup of lan (br-lan)
Jul 10 06:34:41 192.168.30.1 kernel: [ 31.950000] device wlan0 entered promiscuous mode
Jul 10 06:34:41 192.168.30.1 kernel: [ 31.950000] br-lan: port 2(wlan0) entered forwarding state
Jul 10 06:34:41 192.168.30.1 kernel: [ 31.960000] br-lan: port 2(wlan0) entered forwarding state
Jul 10 06:34:41 192.168.30.1 kernel: [ 32.040000] br-lan: port 2(wlan0) entered disabled state
Jul 10 06:34:42 192.168.30.1 kernel: [ 32.340000] device wlan1 entered promiscuous mode
Jul 10 06:34:42 192.168.30.1 kernel: [ 32.350000] br-lan: port 3(wlan1) entered forwarding state
Jul 10 06:34:42 192.168.30.1 kernel: [ 32.350000] br-lan: port 3(wlan1) entered forwarding state
Jul 10 06:34:42 192.168.30.1 kernel: [ 32.780000] br-lan: port 1(eth0) entered forwarding state
Jul 10 06:34:42 192.168.30.1 kernel: [ 33.040000] br-lan: port 3(wlan1) entered disabled state
Jul 10 06:34:43 192.168.30.1 kernel: [ 33.790000] br-lan: port 2(wlan0) entered forwarding state
Jul 10 06:34:43 192.168.30.1 kernel: [ 33.800000] br-lan: port 2(wlan0) entered forwarding state
Jul 10 06:34:44 192.168.30.1 kernel: [ 34.110000] br-lan: port 3(wlan1) entered forwarding state
Jul 10 06:34:44 192.168.30.1 kernel: [ 34.110000] br-lan: port 3(wlan1) entered forwarding state
Jul 10 06:34:44 192.168.30.1 netifd: Network device 'wlan0' link is up
Jul 10 06:34:44 192.168.30.1 netifd: Network device 'eth1' link is up
Jul 10 06:34:44 192.168.30.1 netifd: Interface 'wan' has link connectivity
Jul 10 06:34:44 192.168.30.1 netifd: Interface 'wan' is setting up now
Jul 10 06:34:44 192.168.30.1 kernel: [ 34.360000] ar71xx: pll_reg 0xb8050014: 0x110000
Jul 10 06:34:44 192.168.30.1 kernel: [ 34.360000] eth1: link up (1000Mbps/Full duplex)
Jul 10 06:34:44 192.168.30.1 netifd: Network device 'wlan1' link is up
Jul 10 06:34:44 192.168.30.1 netifd: wan (2069): udhcpc (v1.22.1) started
Jul 10 06:34:44 192.168.30.1 netifd: wan (2069): Sending discover...
Jul 10 06:34:45 192.168.30.1 kernel: [ 35.800000] br-lan: port 2(wlan0) entered forwarding state
Jul 10 06:34:46 192.168.30.1 kernel: [ 36.110000] br-lan: port 3(wlan1) entered forwarding state
Jul 10 06:34:47 192.168.30.1 syslog: error starting threads: errno 89 (Function not implemented)
Jul 10 06:34:47 192.168.30.1 syslog: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Jul 10 06:34:47 192.168.30.1 syslog: exportfs: can't lock /var/lib/nfs/etab for writing
Jul 10 06:34:47 192.168.30.1 syslog: exportfs: could not open /var/lib/nfs/.xtab.lock for locking: errno 2 (No such file or directory)
Jul 10 06:34:47 192.168.30.1 syslog: exportfs: can't lock /var/lib/nfs/xtab for writing
Jul 10 06:34:47 192.168.30.1 netifd: wan (2069): Sending discover...
Jul 10 06:34:47 192.168.30.1 netifd: wan (2069): Sending select for 206.116.77.188...
Jul 10 06:34:48 192.168.30.1 netifd: wan (2069): Lease of 206.116.77.188 obtained, lease time 86400
Jul 10 06:34:48 192.168.30.1 netifd: Interface 'wan6' is enabled
Jul 10 06:34:48 192.168.30.1 netifd: Network alias 'eth1' link is up
Jul 10 06:34:48 192.168.30.1 netifd: Interface 'wan6' has link connectivity
Jul 10 06:34:48 192.168.30.1 netifd: Interface 'wan6' is setting up now
Jul 10 06:34:48 192.168.30.1 netifd: Interface 'wan6' is now up
Jul 10 06:34:48 192.168.30.1 netifd: Interface 'wan' is now up
Jul 10 06:34:48 192.168.30.1 syslog: uinteger - 9 = true
Jul 10 06:34:49 192.168.30.1 syslog: ERROR: No valid dynamic DNS service configurations defined
Jul 10 06:34:49 192.168.30.1 syslog: (Did you specify correct configuration file path?)
Jul 10 06:34:52 192.168.30.1 dnsmasq[2486]: started, version 2.71 cachesize 150
Jul 10 06:34:52 192.168.30.1 dnsmasq[2486]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC
Jul 10 06:34:52 192.168.30.1 dnsmasq-dhcp[2486]: DHCP, IP range 192.168.30.100 -- 192.168.30.149, lease time 12h


After the reboot, LAN connection is working.
Jul 10 07:15:11 192.168.30.1 dnsmasq-dhcp[2486]: DHCPOFFER(br-lan) 192.168.30.133
Jul 10 07:15:11 192.168.30.1 dnsmasq-dhcp[2486]: DHCPREQUEST(br-lan) 192.168.30.133
Jul 10 07:15:11 192.168.30.1 dnsmasq-dhcp[2486]: DHCPACK(br-lan) 192.168.30.133

Hope, someone from developer can decipher the problem.

Thanks in advance.
Gargoyle 1.9.x on Buffalo WZR-HP-AG300H
Gargoyle 1.10.x on TP-Link Archer C7 v2.0
Gargoyle 1.11.x on WRT3200 acm

Post Reply