autogenerated ipv6 addresses on vlans


It seems that on 8-stable the autogenerated ipv6 addresses in vlans use
the mac address of the first interface and not its own mac address. Is
there a reason for this? On 7.x it used the vlan's mac address.

The rc.conf file look like this (ipv4 and other configs removed)
##################################
ipv6_enable="YES"
ipv6_gateway_enable="YES"
ifconfig_ix0="-rxcsum -lro up"
vlans_ix0="101 3101 3103 3199"
ipv6_prefix_ix0_101="2001:1234:5678:ffff"
ifconfig_ix1="-rxcsum -lro"
ifconfig_ix2="-rxcsum -lro up"
vlans_ix2="1 8"
ipv6_prefix_ix2_1="2001:1234:5678:0003"
ipv6_prefix_ix2_8="2001:1234:5678:0001"
##################################

ifconfig with ipv4 and global ipv6 addresses stripped:
##################################
bce0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:25:64:f9:eb:5d
inet6 fe80::225:64ff:fef9:eb5d%bce0 prefixlen 64 scopeid 0x1
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
bce1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:25:64:f9:eb:5f
inet6 fe80::225:64ff:fef9:eb5f%bce1 prefixlen 64 scopeid 0x2
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
bce2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:25:64:f9:eb:61
inet6 fe80::225:64ff:fef9:eb61%bce2 prefixlen 64 scopeid 0x3
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
bce3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:25:64:f9:eb:63
inet6 fe80::225:64ff:fef9:eb63%bce3 prefixlen 64 scopeid 0x4
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:1b:21:57:b4:20
inet6 fe80::21b:21ff:fe57:b420%ix0 prefixlen 64 scopeid 0x5
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:1b:21:57:b4:21
inet6 fe80::21b:21ff:fe57:b421%ix1 prefixlen 64 scopeid 0x6
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
ix2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1a8<VLAN_MTU,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:1b:21:57:ef:7c
inet6 fe80::21b:21ff:fe57:ef7c%ix2 prefixlen 64 scopeid 0x7
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
ix3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM>
ether 00:1b:21:57:ef:7d
inet6 fe80::21b:21ff:fe57:ef7d%ix3 prefixlen 64 scopeid 0x8
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x9
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
ix0.101: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:b4:20
inet6 fe80::225:64ff:fef9:eb5d%ix0.101 prefixlen 64 scopeid 0xa
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 101 parent interface: ix0
ix0.3101: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:b4:20
inet6 fe80::225:64ff:fef9:eb5d%ix0.3101 prefixlen 64 scopeid 0xb
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 3101 parent interface: ix0
ix0.3103: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:b4:20
inet6 fe80::225:64ff:fef9:eb5d%ix0.3103 prefixlen 64 scopeid 0xc
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 3103 parent interface: ix0
ix0.3199: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:b4:20
inet6 fe80::225:64ff:fef9:eb5d%ix0.3199 prefixlen 64 scopeid 0xd
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 3199 parent interface: ix0
ix2.1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:ef:7c
inet6 fe80::225:64ff:fef9:eb5d%ix2.1 prefixlen 64 scopeid 0xe
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 1 parent interface: ix2
ix2.8: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1b:21:57:ef:7c
inet6 fe80::225:64ff:fef9:eb5d%ix2.8 prefixlen 64 scopeid 0xf
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
vlan: 8 parent interface: ix2
##################################

John
--
John Hay -- jhay@xxxxxxxxxxxxxxxxx / jhay@xxxxxxxxxxx
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: vlan limits on e1000?
    ... Intel Corporation HP NC360T PCIe DP Gigabit Server Adapter ... vlan: 5 parent interface: em1 ... vlan: 770 parent interface: em1 ...
    (freebsd-net)
  • Re: VLAN interfaces missing with snmpwalk
    ... I use MRTG/RRDTool to monitor the VLAN interfaces and ... inet xxx.xxx.xxx.xxx netmask 0xfffffffc broadcast xxx.xxx.xxx.xxx ... parent interface: em0 ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Having a problem with getting ipfw fwd to work with vlans and bge - 6.1-RC1 amd64
    ... The vlans are created with the same mac as the parent interface. ... It sort of makes sense in my mind, but definatly seems like we are matching packets to interfaces based up the src mac and dst ip's route. ... Going to move back to bge device tonight during off peak to make sure things are working with changing the vlan mac's. ... I have only tagged vlans running on em0 and the admin vlan running untagged on bge0. ...
    (freebsd-net)
  • Re: VLAN interfaces missing with snmpwalk
    ... I use MRTG/RRDTool to monitor the VLAN interfaces and ... inet xxx.xxx.xxx.xxx netmask 0xfffffffc broadcast xxx.xxx.xxx.xxx ... parent interface: em0 ...
    (comp.unix.bsd.freebsd.misc)
  • Re: arp-proxy
    ... address allocated by DHCP ... the MAC address for cust1 must never appear as a source MAC ... a broadcast from the service subnet should appear on all customer VLANs ... to the correct customer VLAN ...
    (freebsd-net)