we have a phone vendor needing one of the IPs from our /29. Rather than let the SIP traffic get handled by the edgerouter, we set up a bridge group for the WAN
br1 has the wan IP of the edgerouter
eth2 and eth6 are in the group
eth2 -> ISP
eth6 -> phone system
before this, we had the ISP configured directly on eth2, and we made this change remotely.
so first try was to just make all the changes
- delete IP from eth2
- add ip to br1
- add eth6 and eth2 into bridge group
when we did the commit-confirm, br1 was created with the IP, but we got an error about being unable to configure an address on a bridged interface. Doing 'run show interfaces' showed that the IP existed on both br1 and eth2. eth6 was unplugged and eth2 was not part of the bridge group, so br1 was down.
We rebooted and tried again but similar results.
We were able to accomplish this in a way I'd like to not have to repeat... lol
- create br1 and add eth6 to it
- commit and save
- delete the IP on eth2, add IP to br1... then here's where it gets interesting
- I ran 'sudo shutdown -r +3', kind of a meta commit-confirm
- then the following one-liner 'commit ; set interfaces ethernet eth2 bridge bridge-group br1 ; commit'
Luckily, this worked so i ran 'sudo shutdown -c' to cancel the pending shutdown.
Let me know if I need to provide any additional information, but hopefully it's enough to reproduce the problem.