The first thing I would do is to try a different RJ45 cable AND router to rule 
out your cable or homemade router being the problem. Yes, you’ll have to pick 
up a cheap router, but any $50 gadget, such as a Mikrotik RB or Ubiquiti ER-X 
will do. Most network techs have a garage full of castoff routers they can pull 
out in a pinch.

 -mel beckman

> On Jul 14, 2023, at 8:05 AM, Neil Hanlon <n...@shrug.pw> wrote:
> 
> Hi all - I apoligize for the not-necessarily-on-topic post, but I've been 
> struggling with this issue for the past two
> weeks and am about out of ideas and options other than ask here.
> 
> The short version is I recently got FIOS at my (new) house, and plugged in my 
> router (SFF PC running Vyos). Initially,
> all was fine, however, some time later, connectivity to the gateway given by 
> the DHCP server is completely lost. If I
> force a renewal, the gateway (sometimes) comes back--sometimes not. When it 
> doesn't work, the DHCPDISCOVER process has
> to start over again and I often recive a lease in a completely different 
> subnet--which isn't really the problem, but
> seems to be symptomatic of whatever is happening upstream of me.
> 
> The problem, from my perspective, is that the IPv4 gateway given to me in my 
> DHCP lease goes away before my lease
> expires--leading to broken v4 connectivity until either 1. the system goes to 
> renew the lease and fails, starting over;
> or 2. A watchdog notices and renews the lease (This is what I have attempted 
> to implement, without much success).
> 
> As a note, IPv6 connectivity (dhcpv6-pd, receiving a /56) is entirely 
> unaffected when IPv4 connectivity breaks.
> 
> For the past week, I have been monitoring to various IPv4 and IPv6 endpoints 
> over ICMP and TCP, and have been able to
> chart the outages over that period. More or less, every two hours, shortly 
> after a lease is renewed, the gateway
> disappears. I'm happy to share more details and graphs/logs with anyone who 
> might be able to help.
> 
> I have attempted to contact FIOS support several times and even had a trouble 
> ticket opened at one point--though this
> has been closed as they cannot apparently find any issue with the ONT.
> 
> I'm at my wit's end with this issue and would really appreciate any and all 
> help. Please contact me off list if you need
> additional details--I can provide ticket numbers/conversation IDs/etc, as 
> well as graphs/logs/etc.
> 
> Best,
> Neil Hanlon

Reply via email to