Bug #3107
closed
Virtual IP - IP Alias of bridge Interface screws up named firewall rules
0%
Description
When adding an IP Alias (Firewall -> Virtual IPs) on a bridge interface the IP interface allocation somehow gets messed up on reboot:
The console overview shows the Virtual IP, instead of the IP configured in Interfaces->BR0 (name of my bridge interface), on the bridge interface.
Also, the automatically created variables for use in firewall rules like "BR0 subnet" seem to contain the IP address of the Alias, thus blocking me out of my LAN subnet (which is part of the bridge), because I have a (pretty much standard) rule that says "pass from source 'BR0 net' port * destination * port *".
The problem occurs on the current snapshot of 2.1 amd64: 2.1-RC0 (amd64) built on Wed Jul 24 15:12:59 EDT 2013
Updated by Jim Pingle over 11 years ago
- Status changed from New to Rejected
I believe this is a duplicate of #2495 - that one specifically mentions WAN, but the symptoms are otherwise identical: IP alias is being used instead of the interface IP.
I'm going to close this one as duplicate for now, please add your comment to the other ticket.
Thanks!
Updated by