Skip to content
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

local 802.11 ARP requests not forwarded #991

Closed
slightlyunconventional opened this issue Dec 5, 2023 · 2 comments
Closed

local 802.11 ARP requests not forwarded #991

slightlyunconventional opened this issue Dec 5, 2023 · 2 comments

Comments

@slightlyunconventional
Copy link

firmware version: 3.23.8.0

My network topology is:

mesh
└ ki7kkm-mobile (LiteBeam 5 AC)
  ├ element (laptop)
  └ ki7kkm-services (server)

All links are wireless; the LiteBeam is running an 802.11 access point and the server and laptop are connected to its SSID.

When attempting to ssh directly from the laptop to the server, I get "no route to host" errors. However, I can ssh from the laptop to the LiteBeam, and then from the LiteBeam to the server.

tcpdump on the laptop and server reveals that the laptop is sending ARP "who has" requests which are never answered. The server never sees those requests.

I expected that the LiteBeam would forward the ARP lookups for the server, but that doesn't seem to be happening. I noticed that br-lan has the MAC address for wlan0 (70:a7:41:1f:c9:ec), but wlan0 is the mesh interface, which isn't part of br-lan. Should it have the MAC for wlan1 (72:a7:41:1e:c9:ec) instead?

supportdata-KI7KKM-MOBILE-202312020032.gz

I haven't worked much with bridges, so I'm probably missing something simple...

@slightlyunconventional
Copy link
Author

aredn setup

@slightlyunconventional
Copy link
Author

I upgraded to 3.23.12.0 and I no longer see this problem. I don't know if that's causation or correlation, but either way I'm closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant