1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

When IP changes connection is lost

Discussion in 'Tomato Firmware' started by Lost Dog, Aug 18, 2010.

  1. Lost Dog

    Lost Dog LI Guru Member

    I've got Verizon (soon to be Frontier) FIOS. I have a coax connection going to an Actiontec MI424WR that is placed in bridge mode. My WRT54GL (Tomato 1.28) is then connected to the Actiontec.

    The problem I have is when the Verizon dynamic IP changes (about once a month) I lose my WAN connection. A reboot of the WRT54GL fixes the problem.

    The WAN connection type is DHCP and my IP address is the address given by Verizon as passed through the Actiontec bridge.

    As chance would have it, this has occurred each time I've left the country on a trip which really messes things up back at home considering we use VOIP and suddenly my family has no phone or internet. They now know to power cycle the router but it is still a hassle.

    Is there any built in option to check for a connection and reboot the router? Is this a bug of some sort that when a new IP address is given the connection is dropped?

    Thanks!
     
  2. rhester72

    rhester72 Network Guru Member

    Logs?

    Rodney
     
  3. Lost Dog

    Lost Dog LI Guru Member

    <sigh>

    I have failed... Unfortunately before I switched to FIOS I had no issues at all and never even bothered turning logging on. I can't believe I neglected to do this to try and solve my issues.

    Ok, I've got remote logging turned on and messages are being dumped to my server. When it happens again I'll have logs in hand.

    Sorry to come here unprepared!

    Neil
     
  4. mstombs

    mstombs Network Guru Member

    I think this is the dhcp renew bug caused by ISPs who source the renew packet from an unexpected source IP, and therefore get blocked by the firewall. Initial connection works because that is broadcast. You could try recent teddy_bear builds which may have fixed this using busybox udhcp configuration, but first try the dd-wrt patch which works for some users:-

    http://www.dd-wrt.com/wiki/index.php/Iptables#Firewall_blocks_DHCP_renewal_responses
     
  5. Lost Dog

    Lost Dog LI Guru Member

    I've given that Iptables line a try. I'll see how it works and keep my logs going.

    Thanks.
     
  6. gingernut

    gingernut LI Guru Member

    I'm experiencing a similar problem.

    I have my adsl modem bridged to a RT-N16 which controls my pppoe conexion.

    I have never had any pppoe conexion problems what so ever using any tomato version in the past, I 've even rolled back from build 48 to previous just to test but with no luck.

    The problem is that everything can be working perfectly for 1, 3, 5 or more days and then, at no specific time of day, I can't get on line.

    When I log into the RT-N16 to check it's status on the overview page it has just the connecting message. From here on no matter what I do to the asus, soft/hard reboots, new cables, turning on/off jumbo frames and also, as some others have said, changing the WAN Port Speed but all this dosen't help what so ever, tomato is trapped in some kind of connecting loop.

    Section of Log:
    Code:
    RT-N16 daemon.info pppoe[442]: Resending...
    Jan  1 01:00:31 RT-N16 daemon.info pppoe[442]: Resending...
    Jan  1 01:00:32 RT-N16 daemon.err nmbd[484]: Samba name server RT-N16 is now a local master browser for workgroup CASA on subnet 192.168.2.1
    Jan  1 01:00:34 RT-N16 daemon.info pppoe[442]: Resending...
    Jan  1 01:00:39 RT-N16 daemon.info pppoe[442]: Sending PADI.
    Jan  1 01:00:47 RT-N16 user.info redial[441]: WAN down. Reconnecting...
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq[467]: exiting on receipt of SIGTERM
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq[507]: started, version 2.55 cachesize 150
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq[507]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts TFTP
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq-dhcp[507]: DHCP, IP range 192.168.2.100 -- 192.168.2.149, lease time 1d
    Jan  1 01:00:47 RT-N16 daemon.warn dnsmasq[507]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq[507]: read /etc/hosts - 2 addresses
    Jan  1 01:00:47 RT-N16 daemon.info dnsmasq[507]: read /etc/hosts.dnsmasq - 1 addresses
    Jan  1 01:00:52 RT-N16 daemon.info pppoe[509]: Starting
    Jan  1 01:00:52 RT-N16 daemon.info pppoe[509]: Sending PADI.
    Jan  1 01:00:52 RT-N16 user.info redial[510]: Started. Time: 30
    Jan  1 01:01:02 RT-N16 daemon.info pppoe[509]: Resending...
    Jan  1 01:01:12 RT-N16 daemon.info pppoe[509]: Resending...
    Jan  1 01:01:16 RT-N16 daemon.info pppoe[509]: Resending...
    Jan  1 01:01:23 RT-N16 daemon.info pppoe[509]: Resending...
    Jan  1 01:01:29 RT-N16 daemon.info pppoe[509]: Sending PADI.
    Jan  1 01:01:32 RT-N16 user.info redial[510]: WAN down. Reconnecting...
    Jan  1 01:01:32 RT-N16 daemon.info dnsmasq[507]: exiting on receipt of SIGTERM
    Jan  1 01:01:33 RT-N16 daemon.info dnsmasq[515]: started, version 2.55 cachesize 150
    Jan  1 01:01:33 RT-N16 daemon.info dnsmasq[515]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts TFTP
    Jan  1 01:01:33 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCP, IP range 192.168.2.100 -- 192.168.2.149, lease time 1d
    Jan  1 01:01:33 RT-N16 daemon.warn dnsmasq[515]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 01:01:33 RT-N16 daemon.info dnsmasq[515]: read /etc/hosts - 2 addresses
    Jan  1 01:01:33 RT-N16 daemon.info dnsmasq[515]: read /etc/hosts.dnsmasq - 1 addresses
    Jan  1 01:01:38 RT-N16 daemon.info pppoe[517]: Starting
    Jan  1 01:01:38 RT-N16 daemon.info pppoe[517]: Sending PADI.
    Jan  1 01:01:38 RT-N16 user.info redial[518]: Started. Time: 30
    Jan  1 01:01:48 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:01:58 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:02:03 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:02:07 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:02:09 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPDISCOVER(br0) 00:1a:92:6d:f0:73 
    Jan  1 01:02:09 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPOFFER(br0) 192.168.2.127 00:1a:92:6d:f0:73 
    Jan  1 01:02:09 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPREQUEST(br0) 192.168.2.127 00:1a:92:6d:f0:73 
    Jan  1 01:02:09 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPACK(br0) 192.168.2.127 00:1a:92:6d:f0:73 Ginger-PC
    Jan  1 01:02:10 RT-N16 daemon.info pppoe[517]: Sending PADI.
    Jan  1 01:02:13 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:02:14 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPINFORM(br0) 192.168.2.127 00:1a:92:6d:f0:73 
    Jan  1 01:02:14 RT-N16 daemon.info dnsmasq-dhcp[515]: DHCPACK(br0) 192.168.2.127 00:1a:92:6d:f0:73 Ginger-PC
    Jan  1 01:02:17 RT-N16 daemon.info pppoe[517]: Resending...
    Jan  1 01:02:18 RT-N16 user.info redial[518]: WAN down. Reconnecting...
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq[515]: exiting on receipt of SIGTERM
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq[523]: started, version 2.55 cachesize 150
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq[523]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts TFTP
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq-dhcp[523]: DHCP, IP range 192.168.2.100 -- 192.168.2.149, lease time 1d
    Jan  1 01:02:18 RT-N16 daemon.warn dnsmasq[523]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq[523]: read /etc/hosts - 2 addresses
    Jan  1 01:02:18 RT-N16 daemon.info dnsmasq[523]: read /etc/hosts.dnsmasq - 1 addresses
    Jan  1 01:02:23 RT-N16 daemon.info pppoe[535]: Starting
    Jan  1 01:02:23 RT-N16 daemon.info pppoe[535]: Sending PADI.
    Jan  1 01:02:23 RT-N16 user.info redial[536]: Started. Time: 30
    Jan  1 01:02:33 RT-N16 daemon.info pppoe[535]: Resending...
    Jan  1 01:02:43 RT-N16 daemon.info pppoe[535]: Resending...
    Jan  1 01:02:47 RT-N16 daemon.info pppoe[535]: Resending...
    Jan  1 01:02:51 RT-N16 daemon.info pppoe[535]: Resending...
    Jan  1 01:02:58 RT-N16 daemon.info pppoe[535]: Sending PADI.
    Jan  1 01:03:02 RT-N16 daemon.info dnsmasq[523]: exiting on receipt of SIGTERM
    etc
    
    The one and only thing that gets me back on line is rebooting the adsl modem.

    I know this is probably an ISP specific problem as I have tried many possible solutions but without effect.

    Any help is appreciated.
     
  7. teddy_bear

    teddy_bear Network Guru Member

    gingernut,
    I'm sure your issue is not the same as Lost Dog's (that one should be fixed by iptables rule posted by mstombs - and is common for Verizon FIOS).

    In your case - since you didn't have this issue before with the same firmware, and rebooting the modem helps - it looks like a problem with the modem. Might be worth trying another modem if possible.
     
  8. gingernut

    gingernut LI Guru Member

    Hi TB,

    Unfortunatly I've tried another adsl modem and the same problem persists.

    I've also tried a total reconfigure after a erase nvram thorough and just for testing I reflashed tomato using the Asus firmware restoration utility and reconfigured but nothing seems to help.

    I suppose I should try a different router/firmware and maybe take everything out of my local network except the adsl modem.

    Thanks

    Edit: One other strange thing is that once the Asus gets an IP, after an adsl modem reboot, on tomato's menu overview page I can press the disconnect button, wait 10 or more seconds just to be sure, then press the connect button and it gets given an IP instantly, sometimes new sometimes the same, but I can reproduce this process time after time with no problem what so ever. That's what really bugs me.
     

Share This Page