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

Bridge interface and MAC filtering issue #111

Closed
oblique opened this issue Apr 23, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@oblique
Copy link

commented Apr 23, 2015

Hi,

When a bridge interface is created it always have the smallest MAC address of the slave interfaces.
If a user wants to have a bridge interface but he/she is connected to a network that has MAC filtering then he/she will not be able to establish a connection if the MAC address is not recognized by the router.

I'm willing to implement MACAddressOf=<interface name> which it will change the MAC address of bridge interface to the MAC address of <interface name> exactly after all slave interfaces are added.

What do you think?

@oblique

This comment has been minimized.

Copy link
Author

commented Apr 23, 2015

I fixed my problem with the following:

Description="Bridge eth0-tap0"
Interface=br0
Connection=bridge
BindsToInterfaces=(eth0 tap0)
IP=no
ExecUpPost="ip link set dev br0 address $(cat /sys/class/net/eth0/address); IP=dhcp; ip_set"
ExecDownPre="IP=dhcp"

## Ignore (R)STP and immediately activate the bridge
SkipForwardingDelay=yes

But MACAddressOf=<interface name> would be a good feature to have.

@joukewitteveen

This comment has been minimized.

Copy link
Owner

commented Jun 14, 2015

Sounds reasonable, please suggest an implementation.

hummeltech added a commit to hummeltech/netctl that referenced this issue May 23, 2019

hummeltech added a commit to hummeltech/netctl that referenced this issue May 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.