Internet continually dropping - no IPv4 address

[Roverst88]

This weekend my Internet cut out completely. I logged in to the router and found 'no IPv4 address'. Phoned Vodafone, and the Internet came back on after being instructed to turn off the Openreach-installed socket and the router for 2 mins (and then reconnect).

Internet has been fine for 4 days since. Then today, the same thing's happened again. Cut out. No IPv4 address. I did the same thing I did 4 days ago, and the Internet worked again. Then, an hour later, cut out, no IPv4 address.

What's going on here, and how do I get this solved? I'm WFH and this is affecting my capacity to do my job.

Thanks,

[Pluginz]

Evening bud 🙂
Whats your internet type ?  DSL ? Fibre ?  What speed do vodafone say you can achieve ?

It sounds like your current profile has been set too high (Internet Speed) by vodafone. Meaning it'll keep dropping sync.

There's absolutely no point, continously disconnecting the router, or turning the power off and back on again.
It doesn't achieve anything. Just makes it worse. It may initially work after you connect it back up again. Doesnt matter.

The constant unplugging and powering down, will only hurt your total internet speed over time, as it cannot stablise.
Mainly because it keeps getting disconnected (By you).
Do not listen to vodafone, they are full of hot air.

If the profile has been set too high, it'll keep dropping out.  
They need to back your profile speed off, and turn it down a tad, until it's stable.
It's not your problem, but vodafone are possibly creating one, by lying to you about the internet speeds you can achieve. I'm just guessing here.

Get them to back it off, turn it down, or whatever.
It's got to be stable, otherwise you threaten to leave, without paying them an early termination fee.

If this isnt of any help, sorry.  Thats all i can think of, if the ipv4 is dropping on your router.

Good luck man 🙂

[Cynric]

@Pluginz The OP apparently has FTTP as they have been instructed to turn off the Open Reach "socket" , it's not everyone who knows what an ONT is. 

Without seeing something from the router logs it's not going to be immediately obvious whether it is a router fault or something else.

[Roverst88]

Yep, ONT is what I was referring to.

I've turned off IPv6 to see if it makes a tangible difference.

Router logs are downloaded here: https://www.mediafire.com/file/n9x4mkosmcqfvk9/syslog.log+(3).txt/file

Though seems the log only extends to this morning at 6am, as opposed to yesterday when the internet was dropping.

Cheers,

[Cynric]

@Roverst88 Interesting log. Looks like IPv6 is having a bad day. If turning it off doesn't work for you then try a factory reset.

[Roverst88]

Just dropped again, unfortunately. I have tried a factory reset last weekend, when the initial disconnects occurred.

These are the logs that catch the drop: https://www.mediafire.com/file/2z7ycw21jzi7lj8/syslog.log_%25284%2529.txt/file

Router overview page says 'no IPv4 address'.

[Roverst88]

Hi,

I'm on Full Fibre 500. The Internet dropped another three times yesterday after I posted. I saw mentioned that turning off IPv6 settings may help, so I've done so and it hasn't dropped since (so far).

I'll keep what you mentioned in mind if it keeps losing connection.

Cheers

[Ripshod]

What firmware version does your router report in it's status pages (Full string please)? I feel your firmware was updated shortly before you started with the problems as I see several compile errors in the log.

Contact vodafone and see if they can push another update - that's the only fix. 

[Roverst88]

Current firmware version is: 22.1.0404-6421030

If I can ask, is that the most telling thing you notice in the logs?

Cheers,

[Ripshod]

---

@Roverst88 wrote:

22.1.0404-6421030

---

That's the abbreviated version. You'll have to dig a little deeper to find the full version - there's another two groups of numbers that follow.

"22 MARCH, 25 13:20:52 firewall Warning DROP wan out: IN=pppoe-wan OUT=pppoe-wan MAC= src=2001:0470:0001:0fb5:0000:0000:0000:0190 DST=2a0a:ef40:0d2e:c300:4b33:07a8:c40c:d931 LEN=64 TC=0 HOPLIMIT=243 FLOWLBL=0 PROTO=TCP SPT=56101 DPT=389 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8008000"...... You stated earlier that you had disabled IPv6, it isn't.

"22 MARCH, 25 14:01:33 system Error Failed to send to ff02::1%guest@br-guest (Invalid argument)".......Yet this shows you have.

The actual point where the WAN goes down - then back up (some of the lines make no sense): (read from bottom to top)

22 MARCH, 25	14:01:35	wan		Notice  		Reloading firewall due to ifupdate of wan (pppoe-wan)
22 MARCH, 25	14:01:35	system		Info    		 generate_adv_data : CPE_Wwan_Up 0
22 MARCH, 25	14:01:35	wan		Info    		 generate_adv_data : CPE_Wan_Up 0
22 MARCH, 25	14:01:35	system		Info    		 generate_adv_data : CPE_Wlan_Up 1
22 MARCH, 25	14:01:35	wan		Notice  		Interface 'wan6' is disabled
22 MARCH, 25	14:01:35	wan		Error   		<67> [UBUS_INTF]: ubus_intf_event_handler: Recevied WAN event but
22 MARCH, 25	14:01:35	wan		Info    		network.interface event received iface=wan6 action=ifdown
22 MARCH, 25	14:01:35	wan		Info    		ubus_network_event_handler : IFNAME wan6
22 MARCH, 25	14:01:35	wan		Notice  		Interface 'wan6' is now down
22 MARCH, 25	14:01:34	wan		Notice  		wan6 (13348): Command failed: ubus call network.interface notify_proto { "action": 0
22 MARCH, 25	14:01:34	wan		Debug   		Script /lib/netifd/ppp-down finished (pid 7797)
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: LAST STATE: <Idle>
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: Effective retry wait time 9
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: Max retry wait time 10
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: Min retry wait time 5
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: Nb of retries 1
22 MARCH, 25	14:01:34	system		Critical		CONNECTION: Failed to resolve.
22 MARCH, 25	14:01:34	system		Error   		APP_TRACE: bad address 'vfcc.publicacs.vodafone.co.uk'
22 MARCH, 25	14:01:34	data		Warning 		no servers found in /tmp/resolv.conf.d/resolv.conf.auto
22 MARCH, 25	14:01:34	wan		Debug   		Script /lib/netifd/ppp-down finished (pid 7803)
22 MARCH, 25	14:01:34	data		Warning 		no servers found in /tmp/resolv.conf.d/resolv.conf.auto
22 MARCH, 25	14:01:34	wan		Info    		ubus_network_event_handler : IFNAME wan
22 MARCH, 25	14:01:34	wan		Error   		<67> [UBUS_INTF]: ubus_intf_event_handler: Recevied WAN event but
22 MARCH, 25	14:01:34	system		Info    		CONNECTION: Connecting to server
22 MARCH, 25	14:01:34	wan		Error   		<67> [UBUS_INTF]: ubus_intf_event_handler: Recevied WAN event but
22 MARCH, 25	14:01:34	wan		Info    		ubus_network_event_handler : IFNAME wan
22 MARCH, 25	14:01:34	system		Info    		PROT_TRACE: Events are waiting
22 MARCH, 25	14:01:34	wan		Error   		<67> [UBUS_INTF]: ubus_intf_event_handler: Recevied WAN event but
22 MARCH, 25	14:01:34	wan		Info    		network.interface event received iface=wan action=ifdown
22 MARCH, 25	14:01:34	wan		Info    		ubus_network_event_handler : wan is UP
22 MARCH, 25	14:01:34	wan		Info    		ubus_network_event_handler : IFNAME wan
22 MARCH, 25	14:01:34	wan		Notice  		Interface 'wan' has lost the connection
22 MARCH, 25	14:01:34	system		Debug   		sent [LCP TermReq id=0x2 "Peer not responding"]
22 MARCH, 25	14:01:34	wan		Debug   		Script /lib/netifd/ppp-down started (pid 7803)
22 MARCH, 25	14:01:34	system		Error   		Failed to send DHCPV6 message to ff02::1:2 (Invalid argument)
22 MARCH, 25	14:01:34	wan		Notice  		Interface 'wan6' has link connectivity loss
22 MARCH, 25	14:01:34	wan		Notice  		Network alias 'pppoe-wan' link is down
22 MARCH, 25	14:01:34	wan		Notice  		Network device 'pppoe-wan' link is down
22 MARCH, 25	14:01:34	wan		Debug   		Script /lib/netifd/ppp-down started (pid 7797)
22 MARCH, 25	14:01:34	system		Info    		Sent 336928075 bytes
22 MARCH, 25	14:01:34	system		Info    		Connect time 998.8 minutes.
22 MARCH, 25	14:01:34	wan		Error   		<67> [UBUS_INTF]: ubus_intf_event_handler: Recevied WAN event but
22 MARCH, 25	14:01:34	wan		Info    		ubus_network_event_handler : IFNAME wan
22 MARCH, 25	14:01:34	system		Notice  		Connection state changed to disconnecting (phase 9)
22 MARCH, 25	14:01:34	system		Notice  		Serial link appears to be disconnected.
22 MARCH, 25	14:01:34	system		Info    		No response to 3 echo-requests

The Digital Voice event that triggered the reboot:

22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::REGTERMOBJ]:E: destructIppTerm:772 - Ignore unregister IPPTERM: 0xb5317680 for sip profile: 0x1c16350
22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::REGTERMOBJ]:E: registerStateChanged:1643 - In case of a previous send socket error
22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::REGTERMOBJ]:E: registerStateChanged:1579 - statusCode 200
22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::INTERFACESELECTION]:E: eventProcessForDefault:601 - Event (2) not be process (MMPBX_ERROR_NOTSUPPORTED)
22 MARCH, 25	14:00:41	voice		Debug   		[MMNETWORKSIP]  :E: mmNetworkSipGetSubscriptionNotifier:7352 - MMPBX_ERROR_NOTSUPPORTED
22 MARCH, 25	14:00:41	voice		Debug   		[MMNETWORKSIP]  :E: mmNetworkSipGetSubscriptionNotifier:7352 - MMPBX_ERROR_NOTSUPPORTED
22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::REGTERMOBJ]:E: regTermObjFirewallRuleUpdate:4692 - Unable to retrieve currentDestination from SIP network ..
22 MARCH, 25	14:00:41	voice		Info    		SIP Registration: SIP: voi002442205 : Deregister
22 MARCH, 25	14:00:41	voice		Debug   		[MMNETWORKSIP]  :E: mmNetworkSipGetSubscriptionNotifier:7352 - MMPBX_ERROR_NOTSUPPORTED
22 MARCH, 25	14:00:41	voice		Debug   		[MMNETWORKSIP]  :E: mmNetworkSipGetSubscriptionNotifier:7352 - MMPBX_ERROR_NOTSUPPORTED
22 MARCH, 25	14:00:41	voice		Debug   		received cmd:iptables -t filter -C MMPBX -p tcp --dport 5065 -s 148.252.154.196  -m comment --comment Allow_SIP -j ACCEPT
22 MARCH, 25	14:00:41	voice		Debug   		received cmd:iptables -t filter -C MMPBX -p udp --dport 5065 -s 148.252.154.196  -m comment --comment Allow_SIP -j ACCEPT
22 MARCH, 25	14:00:41	voice		Debug   		[MMRVSIPIMPL::NETWORKOBJ]:C: onStackLogEvent:2189 - TRANSACTION  - TransactionTransportTrxStateChangeEv -

The internet didn't go down, the connection was reset by the router because of a SIP failure. As we have no control over the SIP settings on vodafone routers the problem is a misconfiguration by Vodafone.