
MAC Addresses usage
107
Tip
The interface settings in the configuration have a
restrict-mac
setting which, when set to
true
causes the same MAC to be used for all subnets and operations on that specific interface
(port group / VLAN combination).
B.2. Changing MAC address
There is no reason for any network device to maintain the same MAC address for ever. It is normal for the
MAC address to change if the network card is changed on a PC, for example.
However, it is inconvenient if MAC addresses change simply because a device is power cycled or a new
configuration is loaded. This can cause delays accessing the device if other devices have the MAC cached. It
is also a serious problem for ISP links as above where ports are locked to only accept one MAC.
The way the FireBrick manages MAC addresses is designed to be a bit sticky so that a config change will not
usually cause a MAC address assigned to a subnet or interface to change.
B.2. How the FireBrick allocates MAC
addresses
To meet these requirements the FireBrick allocates MAC addresses so specific aspects of the configuration
when it is loaded, and stores this separately in persistent data. If the config is then changed, such as changing
the order of interface definitions, then the allocated MAC stays with the config object based on some key aspect
(such as port group and VLAN tag for interfaces, or IP for subnets).
B.2.1. Interface
Each interface object is allocated a MAC, keyed by the port group and VLAN tag of the interface. This is used
for dynamic IPv6 allocation on the interface using router announcements (RA) and any other interface specific
uses that are not relates to a subnet.
B.2.2. Subnet
Each subnet object is allocated a MAC, which is used for all of the IPs listed in that subnet object. This allows
many IPs to have the same MAC by listing them in the same subnet object. The MAC allocation is keyed on
the port group and VLAN tag and the first listed IP address in the subnet. If a later subnet has the same first IP
listed then this is allocated a separate MAC (i.e. the key for the MAC is also based on which instance of this
specific first IP it is, 1st, 2nd, 3rd, within the interface).
DCHP client subnets work in much the same way - they are based on the port group and VLAN tag and which
instance of DHCP client they are (1st, 2nd, 3rd, etc) within the interface. The special case for DHCP clients is
that the first of these within an interface is given the same MAC as the interface itself.
B.2.3. PPPoE
Each PPPoE object is given a MAC. This is keyed on the port group and VLAN and works in the same way
as if it was a DHCP client subnet in a corresponding interface. i.e. where there is an interface with same port
group and VLAN the PPPoE object gets the interface MAC.
B.2.4. Base MAC
The factory default config has interfaces listed left to right, and a DHCP client in the first interface. This means
the base MAC address of the FireBrick is allocated to the left hand interface and DHCP client on that interface.
This is the same MAC address used by the boot loader which transmits on the left most port on power up.
Содержание FB6402
Страница 1: ...FireBrick FB6402 User Manual FB6000 Versatile Network Appliance...
Страница 2: ......