E3200 Fios Extender - ethernet delay

[larrysinnj]

Became a Fios customer about four months ago.  New apartment install in a 1950s vintage building.  Installer, who appeared very knowledgeable, suggested that I would have Wi-fi issues with thick cinder block walls, suggested I go with their MoCA-based Home Network Solution for an extra $10/mo.  Quite happy with it, and I've decided to toss my 3-5 yr old Orbi Router and ActionTec MoCA hardware that I used in my former home with Optimum service.

Only question - my Windows 11 computer which is hard wired into the E3200 extender takes about one minute from boot to find the ethernet connection.  I have a VOIP phone on the other phone which remains uninterrupted.

Perhaps a dhcp issue?

[Lituanus-VNO]

I have exactly the same issue.

[Cang_Household]

Hum..., you are the third person here bringing up the same issue. I will notify the engineering to take a look.

[Scooby263]

I have had this same issue since the update to 3.0 firmware months ago. Don’t know if it’s any help for engineering but it’s just with Ethernet connected devices (PlayStation 5 and Xbox) to the extender. I have tried static IP, opening ports, and even put the PS5 in DMZ. Nothing works and takes about 1-2 minutes to get online. Also have issues with them in rest mode doing auto updates. 

[Cang_Household]

If you were to plug in a Windows computer, let's say Windows 10 or 11, does the problem persist?

[larrysinnj]

Sorry, I just saw the question.  There are two devices plugged into the E3200, a Windows 11 computer, and a VOIP phone system.  The E3200 stays powered on, as does the phone.   The phone never loses connectivity, but the computer takes a minute to get a network connection (from windows desktop) consistently upon start up.

[Cang_Household]

This is a problem with the NIC driver on the Windows 11 system. Update the NIC driver would likely solve the problem.

[lloydao]

I am having the same issue but it is not Win 11 related.  I have a Win 10 laptop in one ethernet port on the extender.  The other port has a printer.  The laptop goes to sleep each night and just before I wake it in the morning I see that the 2 port switch LAN lights on the extender are out and the LAN light is out also.  When I wake the computer, the LAN lights come on but it takes about 2+ minutes before my laptop connects to the internet.  This behavior is fairly new but I cannot recall when it started happening.

If there was a firmware update to the extender within the last few months I would expect that to be the cause.

As I indicated above, entering "ipconfig" shows the ethernet LAN port down for a few minutes.

[Cang_Household]

Could you use Wireshark to capture what your computer is sending over the Ethernet during that 2 minute window?

[plasmamax1]

Not wireshark, but seeing what dhcpcd is doing on Linux:

On connection attempt:

Feb 01 18:50:10 archlinux dhcpcd[490]: wlan0: carrier lost
Feb 01 18:50:10 archlinux dhcpcd[490]: wlan0: deleting address fe80::da22:9ff8:1d22:7652
Feb 01 18:50:12 archlinux dhcpcd[490]: enp7s0: carrier acquired
Feb 01 18:50:12 archlinux dhcpcd[490]: enp7s0: IAID f5:80:3d:ae
Feb 01 18:50:12 archlinux dhcpcd[490]: enp7s0: adding address fe80::2023:9c82:4b3b:7397
Feb 01 18:50:13 archlinux dhcpcd[490]: enp7s0: soliciting an IPv6 router
Feb 01 18:50:14 archlinux dhcpcd[490]: enp7s0: rebinding lease of 192.168.1.190
Feb 01 18:50:19 archlinux dhcpcd[490]: enp7s0: DHCP lease expired
Feb 01 18:50:19 archlinux dhcpcd[490]: enp7s0: soliciting a DHCP lease
Feb 01 18:50:26 archlinux dhcpcd[490]: enp7s0: no IPv6 Routers available

Once connection succeeds:

Feb 01 18:50:13 archlinux dhcpcd[490]: enp7s0: soliciting an IPv6 router
Feb 01 18:50:14 archlinux dhcpcd[490]: enp7s0: rebinding lease of 192.168.1.190
Feb 01 18:50:19 archlinux dhcpcd[490]: enp7s0: DHCP lease expired
Feb 01 18:50:19 archlinux dhcpcd[490]: enp7s0: soliciting a DHCP lease
Feb 01 18:50:26 archlinux dhcpcd[490]: enp7s0: no IPv6 Routers available
Feb 01 18:51:20 archlinux dhcpcd[490]: enp7s0: offered 192.168.1.190 from 192.168.1.1
Feb 01 18:51:20 archlinux dhcpcd[490]: enp7s0: probing address 192.168.1.190/24
Feb 01 18:51:25 archlinux dhcpcd[490]: enp7s0: leased 192.168.1.190 for 80716 seconds
Feb 01 18:51:25 archlinux dhcpcd[490]: enp7s0: adding route to 192.168.1.0/24
Feb 01 18:51:25 archlinux dhcpcd[490]: enp7s0: adding default route via 192.168.1.1

Now when the E3200 is completely replaced with a goCoax MoCA 2.5 Adapter, the connection issues disappear, leaving just a search for an ipv6 address:

Feb 07 22:31:53 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:03 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:13 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:23 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:33 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:43 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:32:53 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:33:03 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:33:13 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information
Feb 07 22:33:23 archlinux dhcpcd[519]: enp7s0: requesting DHCPv6 information

[Cang_Household]

The puzzle seems to be putting together.

The computer is looking for IPv6 routers and neighbors before asking for the same on IPv4.

This might has to do IPv6 is enabled on G3100 and E3200 to accommodate the WAN IPv6 rollout, which has started in January. Before IPv6 hits your Central Office, I'd recommend you disable the IPv6 on G3100.

goCoax 2.5 is not a network device, but a link device, so it does not deal with IP addresses besides the internal web interface.

[JustLou3]

I just found this thread while Googling this issue. Add me to the list of people that have the same exact issue. Disabling IPv6 on the G3100 and on the system's NIC didn't help. It still takes about 90 seconds for the network to connect. It's not a Windows 11 issue either. My desktop is running Windows 10. I also tried using different NIC drivers and it didn't make a difference.  

[Cang_Household]

Could you also use Wireshark to capture what the NIC is doing during that 90 seconds? Is it goofing around before deciding it's time to actually connect? (comical)

[JustLou3]

I just downloaded it and ran it.  There are over 800 lines of stuff going on before it connects to the internet. 

FWIW, there is only 1 line that I saw that mentions IPv6. 

[Cang_Household]

Could you copy those lines into plain text and send a private message to me to see?

[plasmamax1]

I just wanted to share that disabling ipv6 did not resolve the issue. Disabling ipv6 and factory resetting the router and extender was what the verizon rep attempted. Since neither resolved the issue was why I got the gocoax adapter.

[Cang_Household]

Could you also run Wireshark to see what your NIC is doing over that time period? Does this issue occur with G3100's Ethernet?

[lloydao]

I have a capture file but it's quite long.  I don't see a way to post a .pcapng file that I saved from wireshark.  If I just copy the text it is over 20000 characters which seems to be the limit.  Suggestions as to how to get the wireshark info to you?

[Dukeb83]

I’m having this same exact issue now. Did you find a fix ?

[VL52]

Just got an extender installed by Verizon. The same issue: it takes a minute for Desktop connected by ethernet to get the IP address. Very annoying.

[chubbyone]

has this ever been fixed?  Nov 22 and still happening