WAN IP changed, but old address still used as source



  • Hello

    Just observed really weird behavior with the last snapshot (2.0-RC1 (i386) built on Sun Mar 13 07:27:46 EDT 2011).

    WAN ip changed like 15 mins ago, but according to the packet capture on WAN the old ip is still used as a source for NATed packets!

    
    Mar 14 20:41:57 	dnsmasq[62415]: using nameserver x.x.x.x#53
    Mar 14 20:41:57 	dnsmasq[62415]: using nameserver x.x.x.x#53
    Mar 14 20:41:57 	dnsmasq[62415]: reading /etc/resolv.conf
    Mar 14 20:41:48 	php: : Resyncing OpenVPN instances for interface WAN.
    Mar 14 20:41:43 	php: : Gateways status could not be determined, considering all as up/active.
    Mar 14 20:41:42 	php: : Gateways status could not be determined, considering all as up/active.
    Mar 14 20:41:42 	php: : phpDynDNS: (Success) IP Address Changed Successfully! (x.x.166.205)
    Mar 14 20:41:42 	php: : phpDynDNS: updating cache file /conf/dyndns_wandyndns'xxxxx.homedns.org'.cache: x.x.166.205
    Mar 14 20:41:42 	php: : DynDns debug information: x.x.166.205 extracted from local system.
    Mar 14 20:41:42 	php: : DynDns: _checkIP() starting.
    Mar 14 20:41:42 	php: : DynDns: Current Service: dyndns
    Mar 14 20:41:42 	php: : DynDns: DynDns _checkStatus() starting.
    Mar 14 20:41:41 	php: : DynDns: DynDns _update() starting.
    Mar 14 20:41:41 	php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: x.x.34.82 WAN IP: x.x.166.205
    Mar 14 20:41:41 	php: : DynDns: Cached IP: x.x.34.82
    Mar 14 20:41:41 	php: : DynDns: Current WAN IP: x.x.166.205
    Mar 14 20:41:41 	php: : DynDns debug information: x.x.166.205 extracted from local system.
    Mar 14 20:41:41 	php: : DynDns: _checkIP() starting.
    Mar 14 20:41:41 	php: : DynDns: _detectChange() starting.
    Mar 14 20:41:40 	php: : DynDns: updatedns() starting
    Mar 14 20:41:40 	php: : DynDns: Running updatedns()
    Mar 14 20:41:39 	apinger: Starting Alarm Pinger, apinger(29815)
    Mar 14 17:41:39 	check_reload_status: reloading filter
    Mar 14 17:41:38 	check_reload_status: reloading filter
    Mar 14 20:41:38 	apinger: Exiting on signal 15.
    Mar 14 20:41:38 	php: : ROUTING: change default route to x.x.160.1
    Mar 14 17:41:33 	check_reload_status: Rewriting resolv.conf
    Mar 14 20:41:33 	apinger: ALARM: GW_WAN(x.x.32.1) *** down ***
    
    

    20:55 and later I still see in wireshark:
    Internet Protocol, Src: x.x.34.82 (x.x.34.82), Dst: …


  • Rebel Alliance Developer Netgate

    Check your state table, do you still see state table entries for your old IP?



  • State table was checked before I posted - my old address wasn't there. After that I started packet capture on WAN.
    I will wait for the next provider initiated reconnect and double check again.


Log in to reply