I am new to Gargoyle, but have previously used DD-WRT and OpenWRT. I currently have a TP-Link Archer C7 (v2) on which I installed Gargoyle 1.8.1 last night. It was working great. I love the feature-set including DLNA and multiple sharing protocols for USB storage. After testing the USB sharing to various boxes in my house (Xbox One, Fire TV, Mac, Smart TV), it definitely performs better and is more flexible than the stock firmware.
After setting up the router the way I wanted, I went ahead and did a reboot through the web gui. After the reboot, the router was not able to obtain a WAN ip. It is set to Wired (DHCP). I have it hooked up to my Cable Modem via ethernet to the WAN port on my router. Clicking the "Renew Lease" button would bring up a dialog which said it was trying, but it still failed. The only thing that seems to work is unplugging power from the router and the cable modem, plugging in the cable modem and soon after plugging in the router. Every time I reboot using the Web GUI, it fails to obtain a WAN ip.
I also tried entering a custom MAC address for the WAN ip, but that did not help. Then, I upgraded to a 1.9.1 build (ipsy Jan. 25, 2016: viewtopic.php?f=14&t=8289). That gave me AC wireless, but it did not fix my problem with WAN ip. It works fine as long as I don't reboot the router. If I reboot, then I have to unplug everything and replug.
No WAN ip after reboot
Moderator: Moderators
Re: No WAN ip after reboot
I would be interested to know if the problem is resolved by just rebooting the cable modem?
Also, what if you set
Gargoyle - Connection - Basic - Internet/WAN Connect via:Static IP (Wired)
Also, what if you set
Gargoyle - Connection - Basic - Internet/WAN Connect via:Static IP (Wired)
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
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Re: No WAN ip after reboot
Thanks for the reply. I rebooted from the Web GUI, it failed to renew its WAN ip as per usual. I unplugged the cable modem (Arris TP722), waited a few seconds, plugged it back in. It did not renew the WAN ip. However, this time, it allowed me to release and then renew, which worked without having to unplug the router.
I also tried using a static IP which did not work, although I'm not sure I had the settings correct. I don't have a static ip with my cable internet service.
Not sure what else to do, other than see how long much uptime it can handle before needing to be restarted. Hopefully, I won't have to restart it much.
I also tried using a static IP which did not work, although I'm not sure I had the settings correct. I don't have a static ip with my cable internet service.
Not sure what else to do, other than see how long much uptime it can handle before needing to be restarted. Hopefully, I won't have to restart it much.
Re: No WAN ip after reboot
You should not have to restart it much - but it should work properly to!
That you could manually release and renew after rebooting the cable modem makes me think that the cable modem is the culprit, because you have shown that Gargoyle will accept a new IP if it is offered. Are there any configurable settings related to dhcp in you cable modem?
That you could manually release and renew after rebooting the cable modem makes me think that the cable modem is the culprit, because you have shown that Gargoyle will accept a new IP if it is offered. Are there any configurable settings related to dhcp in you cable modem?
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
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Re: No WAN ip after reboot
Unfortunately, it seems that my cable modem is not configurable. It is one from Charter Communications and from what I've read they disable web gui access. However, I never had issues like this on the stock firmware. So, I think the cable modem is ok.
Re: No WAN ip after reboot
Are you able to post the output of logread just after the issue occurs? You could use the logread plugin - or login to the router using ssh and type logread
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
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Re: No WAN ip after reboot
Doing that now- as an aside, it seems like the cpu load goes down slowly as the router has been on longer. It was high last night as I was doing a lot of read/writing to an attached hard-drive. It got up to about 2.2, then it slowly went down from then over the next 24 hours. It was 1.5 this morning, 1.0 this afternoon. Before I rebooted, it had been on for 24hrs and the cpu load was 0.5. I think my NTFS drive might be part of the problem. I need to reformat it to ext3/4.
Also, I discovered that after rebooting the router via web gui, I just need to reboot the modem. If I wait long enough, I don't have to release/renew.
Here is my log from reboot and no wan ip:
Also, I discovered that after rebooting the router via web gui, I just need to reboot the modem. If I wait long enough, I don't have to release/renew.
Here is my log from reboot and no wan ip:
Code: Select all
Thu Feb 11 21:48:32 2016 kern.info kernel: [ 47.280000] device wlan0 entered promiscuous mode
Thu Feb 11 21:48:32 2016 daemon.notice netifd: radio0 (2171): Using interface wlan0 with hwaddr 60:e3:27:3a:05:e8 and ssid "Growler"
Thu Feb 11 21:48:32 2016 daemon.notice netifd: radio1 (2172): wlan1: interface state UNINITIALIZED->ENABLED
Thu Feb 11 21:48:32 2016 daemon.notice netifd: radio1 (2172): wlan1: AP-ENABLED
Thu Feb 11 21:48:32 2016 daemon.notice netifd: wan (2339): Sending discover...
Thu Feb 11 21:48:33 2016 kern.warn kernel: [ 47.800000] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Thu Feb 11 21:48:33 2016 daemon.notice netifd: Network device 'wlan1' link is up
Thu Feb 11 21:48:34 2016 kern.info kernel: [ 49.250000] br-lan: port 2(wlan1) entered forwarding state
Thu Feb 11 21:48:34 2016 daemon.notice ntfs-3g[2790]: Version 2015.3.14 integrated FUSE 27
Thu Feb 11 21:48:34 2016 daemon.notice ntfs-3g[2790]: Mounted /dev/sda2 (Read-Write, label "growlnas", NTFS 3.1)
Thu Feb 11 21:48:34 2016 daemon.notice ntfs-3g[2790]: Cmdline options:
Thu Feb 11 21:48:34 2016 daemon.notice ntfs-3g[2790]: Mount options: allow_other,nonempty,relatime,fsname=/dev/sda2,blkdev,blksize=4096
Thu Feb 11 21:48:34 2016 daemon.notice ntfs-3g[2790]: Ownership and permissions disabled, configuration type 1
Thu Feb 11 21:48:35 2016 kern.info kernel: [ 49.660000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 21:48:35 2016 kern.info kernel: [ 49.670000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 21:48:35 2016 daemon.notice netifd: radio0 (2171): wlan0: interface state UNINITIALIZED->ENABLED
Thu Feb 11 21:48:35 2016 daemon.notice netifd: radio0 (2171): wlan0: AP-ENABLED
Thu Feb 11 21:48:35 2016 daemon.notice netifd: Network device 'wlan0' link is up
Thu Feb 11 21:48:36 2016 daemon.notice rpc.mountd[2986]: Version 1.3.2 starting
Thu Feb 11 21:48:36 2016 daemon.notice rpc.statd[2988]: Version 1.3.2 starting
Thu Feb 11 21:48:36 2016 daemon.warn rpc.statd[2988]: Flags: No-Daemon
Thu Feb 11 21:48:36 2016 daemon.notice rpc.statd[2988]: Initializing NSM state
Thu Feb 11 21:48:36 2016 daemon.warn rpc.statd[2988]: Running as root. chown /var/lib/nfs to choose different user
Thu Feb 11 21:48:37 2016 kern.info kernel: [ 51.670000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 21:48:38 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 IEEE 802.11: authenticated
Thu Feb 11 21:48:38 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 IEEE 802.11: associated (aid 1)
Thu Feb 11 21:48:38 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 RADIUS: starting accounting session 56BD47FC-00000000
Thu Feb 11 21:48:38 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 WPA: pairwise key handshake completed (RSN)
Thu Feb 11 21:48:38 2016 user.notice root: vsftpd init: mounted = 1
Thu Feb 11 21:48:38 2016 user.notice root: vsftpd init: got_lock = 1
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Forcing update:
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: service provider=no-ip.com
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: domain=purfikt.ddns.net
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://checkmyip.com
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://www.ipchicken.com
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://www.tracemyip.org
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://checkip.dyndns.org
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://checkip.org
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://www.ip-address.org
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://my-ip-address.com
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Could not determine local ip from url: http://www.selfseo.com/what_is_my_ip.php
Thu Feb 11 21:48:39 2016 daemon.info ddns_gargoyle[3043]: Update failed
Thu Feb 11 21:48:39 2016 user.emerg syslog: setting up led USB1
Thu Feb 11 21:48:39 2016 user.emerg syslog: setting up led USB2
Thu Feb 11 21:48:39 2016 user.emerg syslog: setting up led WLAN2G
Thu Feb 11 21:48:39 2016 user.emerg syslog: setting up led WLAN5G
Thu Feb 11 21:48:39 2016 daemon.info procd: - init complete -
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: started, version 2.73 cachesize 150
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: 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 loop-detect inotify
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq-dhcp[3144]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 176.58.118.172#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 106.187.47.17#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 178.32.31.41#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using local addresses only for domain lan
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: reading /tmp/resolv.conf.auto
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain micro
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain oss
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain null
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain ing
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain indy
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain gopher
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain geek
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain fur
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain free
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain bbs
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain dyn
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain parody
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.142.171.235#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 95.211.32.162#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 66.244.95.20#53 for domain glue
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 176.58.118.172#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 106.187.47.17#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 178.32.31.41#53 for domain bit
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using local addresses only for domain lan
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 8.8.8.8#53
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: using nameserver 8.8.4.4#53
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: read /etc/hosts - 12 addresses
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq[3144]: read /tmp/hosts/dhcp - 1 addresses
Thu Feb 11 21:48:40 2016 daemon.info dnsmasq-dhcp[3144]: read /etc/ethers - 7 addresses
Thu Feb 11 21:48:40 2016 daemon.info hostapd: wlan1: STA 74:c2:46:6c:98:d5 IEEE 802.11: authenticated
Thu Feb 11 21:48:40 2016 daemon.info hostapd: wlan1: STA 74:c2:46:6c:98:d5 IEEE 802.11: associated (aid 2)
Thu Feb 11 21:48:40 2016 daemon.info hostapd: wlan1: STA 74:c2:46:6c:98:d5 RADIUS: starting accounting session 56BD47FC-00000001
Thu Feb 11 21:48:40 2016 daemon.info hostapd: wlan1: STA 74:c2:46:6c:98:d5 WPA: pairwise key handshake completed (RSN)
Thu Feb 11 21:48:41 2016 daemon.info dnsmasq-dhcp[3144]: DHCPREQUEST(br-lan) 192.168.1.107 74:c2:46:6c:98:d5
Thu Feb 11 21:48:41 2016 daemon.info dnsmasq-dhcp[3144]: DHCPACK(br-lan) 192.168.1.107 74:c2:46:6c:98:d5 FireTV_stick
Thu Feb 11 21:48:42 2016 daemon.info hostapd: wlan0: STA 3c:15:c2:b7:ac:68 IEEE 802.11: authenticated
Thu Feb 11 21:48:42 2016 daemon.info hostapd: wlan0: STA 3c:15:c2:b7:ac:68 IEEE 802.11: associated (aid 1)
Thu Feb 11 21:48:42 2016 daemon.info hostapd: wlan0: STA 3c:15:c2:b7:ac:68 RADIUS: starting accounting session 56BD4801-00000000
Thu Feb 11 21:48:42 2016 daemon.info hostapd: wlan0: STA 3c:15:c2:b7:ac:68 WPA: pairwise key handshake completed (RSN)
Thu Feb 11 21:48:43 2016 daemon.info dnsmasq-dhcp[3144]: DHCPREQUEST(br-lan) 192.168.1.246 00:bb:3a:8b:81:08
Thu Feb 11 21:48:43 2016 daemon.info dnsmasq-dhcp[3144]: DHCPACK(br-lan) 192.168.1.246 00:bb:3a:8b:81:08 Fire_TV
Thu Feb 11 21:48:44 2016 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 3c:15:c2:b7:ac:68
Thu Feb 11 21:48:44 2016 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.111 3c:15:c2:b7:ac:68
Thu Feb 11 21:48:45 2016 daemon.info dnsmasq-dhcp[3144]: DHCPREQUEST(br-lan) 192.168.1.111 3c:15:c2:b7:ac:68
Thu Feb 11 21:48:45 2016 daemon.info dnsmasq-dhcp[3144]: DHCPACK(br-lan) 192.168.1.111 3c:15:c2:b7:ac:68 MBPr
Thu Feb 11 21:48:46 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 IEEE 802.11: authenticated
Thu Feb 11 21:48:46 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 IEEE 802.11: associated (aid 1)
Thu Feb 11 21:48:46 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 RADIUS: starting accounting session 56BD47FC-00000000
Thu Feb 11 21:48:46 2016 daemon.info hostapd: wlan1: STA d8:5d:e2:44:9e:d6 WPA: pairwise key handshake completed (RSN)
Thu Feb 11 21:48:53 2016 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6
Thu Feb 11 21:48:53 2016 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6
Thu Feb 11 21:48:56 2016 daemon.info dnsmasq-dhcp[3144]: DHCPDISCOVER(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6
Thu Feb 11 21:48:56 2016 daemon.info dnsmasq-dhcp[3144]: DHCPOFFER(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6
Thu Feb 11 21:48:56 2016 daemon.info dnsmasq-dhcp[3144]: DHCPREQUEST(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6
Thu Feb 11 21:48:56 2016 daemon.info dnsmasq-dhcp[3144]: DHCPACK(br-lan) 192.168.1.101 d8:5d:e2:44:9e:d6 Brother_Printer
Thu Feb 11 21:49:10 2016 authpriv.info dropbear[3235]: Child connection from 192.168.1.111:54464
Thu Feb 11 21:49:11 2016 user.notice upnp daemon: external interface not found, not starting
Thu Feb 11 21:49:16 2016 daemon.info hostapd: wlan0: STA d4:f4:6f:bd:b0:79 IEEE 802.11: authenticated
Thu Feb 11 21:49:16 2016 daemon.info hostapd: wlan0: STA d4:f4:6f:bd:b0:79 IEEE 802.11: associated (aid 2)
Thu Feb 11 21:49:16 2016 daemon.info hostapd: wlan0: STA d4:f4:6f:bd:b0:79 RADIUS: starting accounting session 56BD4801-00000001
Thu Feb 11 21:49:16 2016 daemon.info hostapd: wlan0: STA d4:f4:6f:bd:b0:79 WPA: pairwise key handshake completed (RSN)
Thu Feb 11 21:49:17 2016 daemon.info dnsmasq-dhcp[3144]: DHCPREQUEST(br-lan) 192.168.1.103 d4:f4:6f:bd:b0:79
Thu Feb 11 21:49:17 2016 daemon.info dnsmasq-dhcp[3144]: DHCPACK(br-lan) 192.168.1.103 d4:f4:6f:bd:b0:79 i6p
Thu Feb 11 21:49:18 2016 authpriv.notice dropbear[3235]: Password auth succeeded for 'root' from 192.168.1.111:54464Re: No WAN ip after reboot
Do you have DLNA on?
It will scan for ages and it uses a lot of CPU
It will scan for ages and it uses a lot of CPU
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.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: No WAN ip after reboot
Yeah, I've got DLNA turned on. I do like having that available, but I can enable it when I actually use it. I primarily use smb anyhow. Could that affect the issue with the wan ip? I think I'm going to try just starting over tomorrow. I'll do a 30/30/30 and flash to the ispy build that will be available tomorrow. I'll also reformat my drive to ext3.
Re: No WAN ip after reboot
no such thing with gargoyleI'll do a 30/30/30
google "openwrt failsafe first boot"