-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core router breaking dhcp of uplink #1045
Labels
bug
Something isn't working
Comments
Details on the last incidentThe `newyorck` network went offline (no connection to the internet possible). I connected to the core router and got the logs. Apparently there was a restart of the freifunk core router 4 minutes earlier.
|
The ips and interfaces of the core router
The tcpdump of interface `br-uplink` on the core
The tcpdump of interface `switch0.50@switch0` on the core
Trying to connect to the telekom router using dhcp on port enp0s25 of my fedora laptop I got the following ips
Trying to connect to the telekom router using dhcp on port enp0s25 of my fedora laptop I got the following tcpdump
Verifying that I can reach the telekom router and the internet, when using a static ip on my fedora laptop
Core logs after I plugged in the edgerouter between core and uplink:
Logs and state of the telekom routerThere is nothing to see in the logs:
Notes:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TLDR
On the
newyorck
location we encountered multiple times that the core router lost connection to the telkom router that is used as uplink. In these situations not only the core, but also other devices in the network weren't able to connect via dhcp to the uplink anymore. Reboots did not fix it. We needed to do a full reset of the telekom router. So it is a problem on the telekom router, but seems to be triggered by the freifunk setup, as before there were no such problems. Telekom support did not help, but provided us with a newer version of their router. This didn't fix it, the problems still happen on the current modelSpeedportSmart 4
.For now we put an edgerouter with a static ip between the core and the uplink. So this should work, but is not a solution to the problem.
The text was updated successfully, but these errors were encountered: