Hello,
Background:
I have ran a RPI 4 as a router for 1 year and a bit. It has worked
flawlessly since setting up, until 7.5 was released.
When 7.5 released I attempted an update, however it appears the RPI
kicked the bucket, the sata adapter broken as well which seemed to have
destroyed the OpenBSD install, and the SSD for some reason stopped
being detected, and then the phy stopped working, I have removed the
RPI from use and replaced it with a E6430.
I was running 7.4 since it released (ran 7.3 before that) and I never
had the following problem I will describe, I am not sure if this is
hardware or not hence why I am asking if anyone else has had a similar
issue.
When I replaced the RPI with the E6430 I picked the latest release
(7.5), and it appeared to work fine.
I would like to note my infrastructure is behind this router, this
includes my email I am using to send this, which makes debugging
slightly more difficult as it involves knocking out my servers, and I
have no other hardware available at the moment, the joys to self
hosting.
The problem/weirdness:
I noticed that throughout the day yesterday when I was testing the
temporary measure of using my other laptop (while I sourced
replacement hardware) that the pppoe interface kept losing carrier. It
would never re-establish this carrier on its own.
/etc/netstart doesn't fix the issue, rebooting does and down/up my WAN
interface (which is axen) also allowed re-establishing of the
connection.
Although this isn't a big deal, it sucks for server uptime because
every few hours the carrier is lost, and I have to manually intervene.
Again could be hardware, not too sure.
Checking the kernel logs, I see two things.
The issues tend to start when the following message is logged:
/bsd: pppoe0: received unexpected PADO
Although network service remains for a few hours until:
/bsd: pppoe0: LCP keepalive timeout
After this message, pppoe0 will never reconnect until axen is brought
down and up again, and then it reconnects almost instantly. There is no
errors logged for a while and then this appears to repeat.
Note: These are the only two log messages relating to pppoe0, here are
the axen0 messages in case its useful:
/bsd: axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX Elec.
Corp. AX88179" rev 2.10/1.00 addr 2
/bsd: axen0: AX88179, address 7c:c2:c6:44:18:53
/bsd: rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
Any ideas on what I could try?
Some configs:
hostname.axen0:
up
hostname.pppoe0:
inet 0.0.0.0 255.255.255.255 NONE pppoedev axen0 authproto chap
authname 'REDACTED' authkey 'REDACTED' up dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp pppoe0 0.0.0.1
!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
ifconfig:
axen0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 7c:c2:c6:44:18:53
index 5 priority 0 llprio 3
media: Ethernet autoselect (100baseTX full-duplex)
status: active
pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492
index 6 priority 0 llprio 3
dev: axen0 state: session
sid: 0x1f6 PADI retries: 5 PADR retries: 0 time: 00:24:26
sppp: phase network authproto chap
dns: 9.9.9.9 127.0.0.1
groups: pppoe egress
status: active
inet6 fe80::baca:3aff:fed0:bbc1%pppoe0 --> prefixlen 64
scopeid 0x6
I am not sure what else could be relevant, feel free to ask for further
logs if required :)
Take care,
--
Polarian
GPG signature: 0770E5312238C760
Website: https://polarian.dev
JID/XMPP: polarian@icebound.dev
No comments:
Post a Comment