duplicate epair ipv6 addresses
Frank Razenberg
frank at zzattack.org
Thu Sep 2 13:27:53 UTC 2010
Sorry Yavuz,
Here they are:
base
nfe0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric
0 mtu 1500
options=80008<VLAN_MTU,LINKSTATE>
ether 00:22:15:bb:6d:6f
inet 10.31.45.10 netmask 0xffffff00 broadcast 10.31.45.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
ether de:3b:7a:d8:3a:98
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 4 priority 128 path cost 2000
member: nfe0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 55
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 1500
ether 02:9a:c6:00:04:0a
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 1500
ether 02:da:d1:00:05:0a
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 1500
ether 02:ea:c6:00:06:0a
jail1
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 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
ether 02:00:00:00:05:0b
inet6 fe80::ff:fe00:50b%epair0b prefixlen 64 scopeid 0x2
inet 10.31.45.11 netmask 0xffffff00 broadcast 10.31.45.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
jail2
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 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair1b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
ether 02:00:00:00:06:0b
inet6 fe80::ff:fe00:60b%epair1b prefixlen 64 scopeid 0x2
inet 10.31.45.12 netmask 0xffffff00 broadcast 10.31.45.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
jail3
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 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair2b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
ether 02:00:00:00:07:0b
inet6 fe80::ff:fe00:70b%epair2b prefixlen 64 scopeid 0x2
inet 10.31.45.13 netmask 0xffffff00 broadcast 10.31.45.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
Frank
On 9/2/2010 1:10 PM, yavuz gokirmak wrote:
> Hi Frank,
>
> You forgot to paste ifconfigs..
>
>
> On 2 September 2010 14:06, Frank Razenberg <frank at zzattack.org
> <mailto:frank at zzattack.org>> wrote:
>
> Hi Yavuz,
>
> Thanks for your response. I've pasted the ifconfig output from all
> jails below.
> I've tried restarting all my jails. Stopping all 3 is no problem,
> but when I try to bring up the first jail again, I get a kernel
> panic. This seems reproducable; it happen 5/5 times I tried.
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> faujlt virtual address = 0x290
> fault code = supervisor data, page not present
>
> I do believe however this is related to my 'other' issue which I
> posted at
> http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058531.html,
> for which the solutions seems to be waiting for Bjoern to apply
> some patches.
>
> No matter which jails are active, pinging to ffe80:2::ff:fe00:70b
> results in
> ping: cannot resolve ffe80:2::ff:fe00:70b: Unknown host
>
> Frank
>
>
>
> On 9/2/2010 8:09 AM, yavuz gokirmak wrote:
>> Hi,
>> Firstly, it seems that your second jail tries to get
>> "fe80:2::ff:fe00:70b" address. But I think that second jail
>> should take an address like "fe80:2::ff:fe00:60b" because its mac
>> address is "02:00:00:00:06:0b". This is strange, could you send
>> ifconfig outputs from jails...
>>
>> Secondly, if I were you, I would create only first jail and try
>> to ping "ffe80:2::ff:fe00:70b". Try to understand who is holding
>> this address.
>>
>> best regards..
>>
>> yavuz
>>
>>
>> On 1 September 2010 20:33, Frank Razenberg <frank at zzattack.org
>> <mailto:frank at zzattack.org>> wrote:
>>
>> Hi,
>>
>> I'm receiving some messages regarding a possibly duplicate
>> IPv6 address when starting a vnet jail. I have 3 jails, and
>> the second one get started is generating some errors.
>> Starting the third one does not generate any similar error
>> messages. I've pasted the relevant log sections below:
>>
>> fileserve's /var/log/messages
>> Sep 1 17:16:08 fileserve sm-mta[2102]: NOQUEUE:
>> SYSERR(root): opendaemonsocket: daemon Daemon0: cannot bind:
>> Address already in use
>> Sep 1 17:16:08 fileserve sm-mta[2102]: daemon Daemon0:
>> problem creating SMTP socket
>> ...
>> Sep 1 17:16:08 fileserve sm-mta[2102]: NOQUEUE:
>> SYSERR(root): opendaemonsocket: daemon Daemon0: server SMTP
>> socket wedged: exiting
>> (sendmail or any other MTA is not enabled/running)
>>
>> base system:
>> Sep 1 17:16:08 frank-server kernel: epair1b: DAD detected
>> duplicate IPv6 address fe80:2::ff:fe00:70b: NS in/out=0/1, NA
>> in=1
>> Sep 1 17:16:08 frank-server kernel: epair1b: DAD complete
>> for fe80:2::ff:fe00:70b - duplicate found
>> Sep 1 17:16:08 frank-server kernel: epair1b: manual
>> intervention required
>> Sep 1 17:16:08 frank-server kernel: epair1b: possible
>> hardware address duplication detected, disable IPv6
>>
>>
>> From dmesg on boot:
>> bridge0: Ethernet address: 3a:fa:3f:1e:0e:2e
>> epair0a: Ethernet address: 02:fa:c2:00:04:0a
>> epair0b: Ethernet address: 02:00:00:00:05:0b
>> epair0a: promiscuous mode enabled
>> nfe0: link state changed to DOWN
>> nfe0: link state changed to UP
>> epair1a: Ethernet address: 02:aa:d1:00:05:0a
>> epair1b: Ethernet address: 02:00:00:00:06:0b
>> epair1a: promiscuous mode enabled
>> epair2a: Ethernet address: 02:9a:d2:00:06:0a
>> epair2b: Ethernet address: 02:00:00:00:07:0b
>> epair2a: promiscuous mode enabled
>>
>> -they seem unique to me.
>>
>> I've also attached my full /etc/rc.conf. I have applied the
>> patch on
>> http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet on
>> my /etc/rc.d/jail script so that the parameter -c vnet is
>> passed on, and the jail_jname_earlypoststart* variables are
>> issued on jail start.
>>
>> The jail's networking seems a little unstable. I can usually
>> ssh into it at 10.31.45.12 but at random times the connection
>> just stalls. Then, I can only return to the jail using jexec
>> from the base.
>> Could someone point out what I'm doing wrong? Thanks in advance.
>>
>> Frank
>>
>>
>> _______________________________________________
>> freebsd-virtualization at freebsd.org
>> <mailto:freebsd-virtualization at freebsd.org> mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>> To unsubscribe, send any mail to
>> "freebsd-virtualization-unsubscribe at freebsd.org
>> <mailto:freebsd-virtualization-unsubscribe at freebsd.org>"
>>
>>
>
>
More information about the freebsd-virtualization
mailing list