Bug 198521
Summary: | VRF: VRF device does not egress all broadcast(255.255.255.255) destined packet | ||
---|---|---|---|
Product: | Networking | Reporter: | Sukumar (sukumarg1973) |
Component: | IPV4 | Assignee: | David Ahern (dsahern) |
Status: | RESOLVED CODE_FIX | ||
Severity: | blocking | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Linux version 4.9.71 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Sukumar
2018-01-19 12:59:23 UTC
Thanks for the bug report. The suggested change allows a packet to go out, but it is not the complete solution -- responses do not make it back to the sending socket. Getting that to happen is a bigger change. I'll get a patch out in the next few days. The reported problem is resolved by commit 1e19c4d689dc ("net: vrf: Add support for sends to local broadcast address"). That patch will get backported to 4.14. With that change you can bind a socket to the enslaved device using SO_BINDTODEVICE, send to the local broadcast address and receive responses. A follow on change, commit 9515a2e082f9 ("net/ipv4: Allow send to local broadcast from a socket bound to a VRF") allows a socket to be bound to a VRF device and use IP_UNICAST_IF to set the egress interface. This patch will be in 4.16 and up. |