You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add option to set arp src addr for managed interfaces.
Relayd will send arp requests out a managed interface like this:
Who has 192.168.1.40, tell 192.168.2.1
In most cases, this works, but some clients will not send a reply (on
linux, client will not reply if /proc/sys/net/ipv4/conf/*/rp_filter is
set to 1, which happens to be the default on ubuntu-16.04).
Add '-s' option to tell relayd to use the specified addr as the arp src
addr for managed interfaces. The arp requests would then look like:
Who has 192.168.1.40, tell 192.168.1.100
for which the client properly sends a reply.
The symptoms of the problem manifest as dropped packets due to the
kernel marking the arp entry for the client as FAILED due to lack of
responses to the arp requests. Eventually (10-30 seconds later), the arp
table is updated and connectivity is restored.
The text was updated successfully, but these errors were encountered:
troth:
DEVICE: N/A (can be reproduced on any system running relayd)
LEDE version: N/A (can be reproduced on a VM running debian with relayd installed)
Steps to reproduce:
Our fix for the problem need two changes:
Our changes to relayd are here:
From commit message for my fix:
Add option to set arp src addr for managed interfaces.
The text was updated successfully, but these errors were encountered: