Project

General

Profile

Actions

Bug #3520

closed

IPV6 address on LAGG VLAN not reachable

Added by Branko Lukman about 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/14/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1-IPv6
Affected Architecture:

Description

I have a /64 network via GIF .

Lan interface is a LAGG (loadbalancing) interface with 2 VLANS. On ipv4 all works fine.
if i try to add a ipv6 address to LAGG-VLAN interface, it accepts and sets a address, but it is not visible from the router or any other machine in LAN.

I have configured an new interface for ipv6 only , where evrithing works.

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:1f
inet 86.58.64.233 netmask 0xffffff00 broadcast 86.58.64.255
inet6 fe80::290:7fff:fe2f:a31f%re0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:20
inet6 fe80::290:7fff:fe2f:a320%re1 prefixlen 64 scopeid 0x2
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:21
media: Ethernet autoselect
status: no carrier
re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:22
inet6 fe80::290:7fff:fe2f:a322%re3 prefixlen 64 scopeid 0x4
inet6 2001:15c0:65ff:87ce::1 prefixlen 64
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a323%re4 prefixlen 64 scopeid 0x5
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a324%re5 prefixlen 64 scopeid 0x6
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
enc0: flags=0<> metric 0 mtu 1536
pflog0: flags=100<PROMISC> metric 0 mtu 33192
pfsync0: flags=0<> metric 0 mtu 1460
syncpeer: 224.0.0.240 maxupd: 128 syncok: 1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a323%lagg0 prefixlen 64 scopeid 0xb
inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
laggproto loadbalance
laggport: re5 flags=4<ACTIVE>
laggport: re4 flags=4<ACTIVE>
lagg0_vlan4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a31f%lagg0_vlan4 prefixlen 64 scopeid 0xc
inet 10.10.10.1 netmask 0xffffff00 broadcast 10.10.10.255
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
vlan: 4 vlanpcp: 0 parent interface: lagg0
lagg0_vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a31f%lagg0_vlan2 prefixlen 64 scopeid 0xd
inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255
inet6 2001:15c0:65ff:87ce::10:1 prefixlen 64 duplicated
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
vlan: 2 vlanpcp: 0 parent interface: lagg0
lagg0_vlan5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a31f%lagg0_vlan5 prefixlen 64 scopeid 0xe
inet 10.10.7.1 netmask 0xffffff00 broadcast 10.10.7.255
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
vlan: 5 vlanpcp: 0 parent interface: lagg0
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
inet6 fe80::290:7fff:fe2f:a31f%pppoe0 prefixlen 64 scopeid 0xf
inet 86.61.76.135 --> 213.250.19.90 netmask 0xffffffff
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
ovpns1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
inet6 fe80::290:7fff:fe2f:a31f%ovpns1 prefixlen 64 scopeid 0x11
inet 10.0.8.1 --> 10.0.8.1 netmask 0xffffff00
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
Opened by PID 99774
gif1: flags=9051<UP,POINTOPOINT,RUNNING,LINK0,MULTICAST> metric 0 mtu 1280
tunnel inet 86.58.64.233 --> 212.18.63.73
inet6 2001:15c0:65ff:7ce::2 --> 2001:15c0:65ff:7ce::1 prefixlen 128
inet6 fe80::290:7fff:fe2f:a31f%gif1 prefixlen 64 scopeid 0x10
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
options=1<ACCEPT_REV_ETHIP_VER>

[2.1.1-PRERELEASE][]/root(121): ping6 2001:15c0:65ff:87ce::1
PING6 2001:15c0:65ff:87ce::1 --> 2001:15c0:65ff:87ce::1
16 bytes from 2001:15c0:65ff:87ce::1, icmp_seq=0 hlim=64 time=0.420 ms
16 bytes from 2001:15c0:65ff:87ce::1, icmp_seq=1 hlim=64 time=0.261 ms
^C
--- 2001:15c0:65ff:87ce::1 ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.261/0.341/0.420/0.079 ms

[2.1.1-PRERELEASE][]/root(122): ping6 2001:15c0:65ff:87ce::10:1
PING6 2001:15c0:65ff:87ce::1 --> 2001:15c0:65ff:87ce::10:1
c^C
--- 2001:15c0:65ff:87ce::10:1 ping6 statistics ---
14 packets transmitted, 0 packets received, 100.0% packet loss

Actions #1

Updated by Vinícius Zavam about 10 years ago

See the duplicated in lagg0_vlan2 (re4+re5)?

lagg0_vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:90:7f:2f:a3:23
inet6 fe80::290:7fff:fe2f:a31f%lagg0_vlan2 prefixlen 64 scopeid 0xd
inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255
inet6 2001:15c0:65ff:87ce::10:1 prefixlen 64 duplicated
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
vlan: 2 vlanpcp: 0 parent interface: lagg0

Why is re3 sitting at the same IPv6 address space?
lagg0_vlan2 is a VLAN and it "must" be in another network, but re3's.

re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 00:90:7f:2f:a3:22
inet6 fe80::290:7fff:fe2f:a322%re3 prefixlen 64 scopeid 0x4
inet6 2001:15c0:65ff:87ce::1 prefixlen 64
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active

It may be just a config mistake... or a typo.

Actions #2

Updated by Chris Buechler almost 10 years ago

  • Status changed from New to Rejected

config issue, not bug. Can't have 2 interfaces on the same subnet.

Actions

Also available in: Atom PDF