Ultimately I moved my physical connection from port eth0 to eth4, and configured eth4 with the same config as was on eth0. Once I did that everything was stable and has been stable for days (nearly a week now). I'm not sure what could be causing an interface to work for an amount of time, then as if on-cue stop forwarding packets.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Jun 4 2022
Jun 4 2022
showipintbri renamed T4445: [EDIT] Service Restored: Outage: Interface stops forwarding, IPv4 martian seen in the logs from Outage: Interface stops forwarding, IPv4 martian seen in the logs to [EDIT] Service Restored: Outage: Interface stops forwarding, IPv4 martian seen in the logs.
showipintbri added a comment to T4445: [EDIT] Service Restored: Outage: Interface stops forwarding, IPv4 martian seen in the logs.
May 26 2022
May 26 2022
showipintbri added a comment to T4445: [EDIT] Service Restored: Outage: Interface stops forwarding, IPv4 martian seen in the logs.
I'm trying to think what could have a 110 minute timer and the only think I can think of is the DHCP lease time:
May 26 05:58:49 rtr dhclient-script-vyos[7261]: No changes to apply via vyos-hostsd-client May 26 05:58:49 rtr dhclient[7216]: bound to 72.81.238.169 -- renewal in 3075 seconds.
showipintbri added a comment to T4445: [EDIT] Service Restored: Outage: Interface stops forwarding, IPv4 martian seen in the logs.
I just caught it again. Same logs line up with my continuous ping.
May 24 2022
May 24 2022
I removed my comment as my issue was not a bug AFAIK, but rather a miss-configuration and operation.
Dec 6 2021
Dec 6 2021
As mentioned I'm running: VyOS 1.3.0-rc6
Dec 2 2021
Dec 2 2021