I was so very excited to try out verizon's , since they installed a 5g cell right i
front of my house, couldn't get more point to point than less than 30ft.
After a few more months of waiting for service at our address to be available, I finally was able to
order the service for a 30 day trial.
Initial testing showed amazing speeds, realized the equipment was using 2.5 port and a 10Gbps port,
immediately invested hundreds of dollars in a 4x2.5gbps port router to take advantage of the 2+Gbps
I was getting from verizon's speed test.
First few days worked ok as I assume I was causing things to break as I was messing with the router.
I was extremely amazed and happy by Steam game update downloading at over 1Gbps.
Until I noticed all my vpns were getting disconnected overnight right around 1-3am.
As I looked at the logs on my router, I noticed their dhcp server was providing a 2m lease time! I can understand that maybe for mobile phone service it might make sense as phone move from cell to cell and you might want to recycle the used ip addresses
But that means the dhcp client attempts to renew the ip every 60s. Imagine what happens when their lv65 decides to reboot for unknown reason and takes 2+minutes, boom new ip address gets delegated and all your streaming service gets disconnected, your vpn gets disconnected, no matter how much buffering happened, you have to tell your tv to reconnect after an annoying popup.
Or try playing an online video game when you loose connections for 2m and then get disconnected instead of just seamlessly going back in if you are lucky.
I did try to use the provided CR1000A router and still experienced the same issue, I just had better luck getting ipv6 working with my openwrt router.
Then now lets talk about ipv6, again I can understand only providing a phone a /64, since that the smallest block you can delegate to a ipv6 customer, except their router automatically broadcasts 3 different wifi networks, which means requiring 3 different /64 network blocks. This can only work when providing at least a dhcp-pd of /60 ( 16 /64 ) . Try googling CR1000A and ipv6, it doesn't work, since you can't subnet a /64 into 3 different ipv6 blocks. I was only able to get ipv6 working from using ipv6 masquerading from my openwrt router.( which means only 1 /128 usable ipv6 address )
For the record, Spectrum did provide me with a /60 dhcp-pd and not just turn of my ipv6 connection when my dhcp client made the request.
( Btw you might want to teach your tech support about what ipv6 is, everyone tech I talked to said: "ipv what ?" )
So Verizon, can you treat your 5G Home internet as what it is and not just an unreliable internet 5G
hotspot ?
An extremely disappointed customer.
P.S: as I type this @ 3:37am PST on Tue Aug 22, the lv65 reboot, yet again, a new ip address is
provided and all connectivity is interrupted.
I even lost my authentication token to community.verizon.com, as I was typing this message in the browser.
Tue Aug 22 03:36:53 2023 daemon.notice netifd: wan (2194): udhcpc: lease of 72.104.1xx.xxx obtained from 10.0.0.1, lease time 120
Tue Aug 22 03:37:14 2023 daemon.notice netifd: Network device 'eth0' link is down
Tue Aug 22 03:37:14 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Aug 22 03:37:14 2023 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue Aug 22 03:37:14 2023 kern.info kernel: [49298.474620] igc 0000:01:00.0 eth0: NIC Link is Down
Tue Aug 22 03:37:14 2023 daemon.notice netifd: wan (2194): udhcpc: received SIGTERM
Tue Aug 22 03:37:14 2023 daemon.notice netifd: Interface 'wan' is now down
Tue Aug 22 03:38:49 2023 daemon.notice netifd: Network device 'eth0' link is up
Tue Aug 22 03:38:49 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Aug 22 03:38:49 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Aug 22 03:38:49 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Aug 22 03:38:49 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Aug 22 03:38:49 2023 kern.info kernel: [49393.962664] igc 0000:01:00.0 eth0: NIC Link is Up 2500
Mbps Full Duplex, Flow Control: RX/TX
Tue Aug 22 03:38:55 2023 daemon.notice netifd: wan (9666): udhcpc: lease of 10.0.0.10 obtained from
10.0.0.1, lease time 60
Tue Aug 22 03:38:55 2023 daemon.notice netifd: Interface 'wan' is now up
Tue Aug 22 03:39:25 2023 daemon.notice netifd: wan (9666): udhcpc: sending renew to server 10.0.0.1
Tue Aug 22 03:39:26 2023 daemon.notice netifd: Network device 'eth0' link is down
Tue Aug 22 03:39:26 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Aug 22 03:39:26 2023 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue Aug 22 03:39:26 2023 kern.info kernel: [49430.321482] igc 0000:01:00.0 eth0: NIC Link is Down
Tue Aug 22 03:39:26 2023 daemon.notice netifd: wan (9666): udhcpc: received SIGTERM
Tue Aug 22 03:39:26 2023 daemon.notice netifd: Interface 'wan' is now down
Tue Aug 22 03:39:30 2023 daemon.notice netifd: Network device 'eth0' link is up
Tue Aug 22 03:39:30 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Aug 22 03:39:30 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Aug 22 03:39:30 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Aug 22 03:39:30 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Aug 22 03:39:30 2023 kern.info kernel: [49434.611708] igc 0000:01:00.0 eth0: NIC Link is Up 2500
Mbps Full Duplex, Flow Control: RX/TX
Tue Aug 22 03:39:30 2023 daemon.notice netifd: wan (10485): udhcpc: started, v1.36.1
Tue Aug 22 03:39:30 2023 daemon.notice netifd: wan (10485): udhcpc: broadcasting discover
Tue Aug 22 03:39:33 2023 daemon.notice netifd: wan (10485): udhcpc: broadcasting discover
Tue Aug 22 03:39:35 2023 daemon.notice netifd: wan (10485): udhcpc: broadcasting select for 75.223.1
xx.xxx, server 10.0.0.1