Discussion:
[netbsd4.0]could you tell me why NetBSD did not send link-local NS when NetBSD rebooted.
(too old to reply)
wang_jiabo
2009-02-12 05:14:25 UTC
Permalink
Hello, all:
could you tell me why NetBSD did not send link-local NS when NetBSD
rebooted.
I add ip6mode=autohost in /etc/rc.conf and add up in ifconfig.<IF> file
thanks
jiabo



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2009-02-12 08:11:21 UTC
Permalink
Post by wang_jiabo
could you tell me why NetBSD did not send link-local NS when NetBSD
rebooted.
I add ip6mode=autohost in /etc/rc.conf and add up in ifconfig.<IF> file
Works for me - I've just tested it with NetBSD/i386 4.0.1 (caution - wide!):

08:05:11.599259 00:50:ba:80:0e:40 > 33:33:ff:80:0e:40, ethertype IPv6 (0x86dd), length 78: :: > ff02::1:ff80:e40: icmp6: neighbor sol: who has fe80::250:baff:fe80:e40
08:05:12.221896 00:50:ba:80:0e:40 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::250:baff:fe80:e40 > ff02::2: icmp6: router solicitation
08:05:12.604434 00:d0:b7:75:c0:2c > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::2d0:b7ff:fe75:c02c > ff02::1: icmp6: router advertisement
08:05:12.661833 00:50:ba:80:0e:40 > 33:33:ff:80:0e:40, ethertype IPv6 (0x86dd), length 78: :: > ff02::1:ff80:e40: icmp6: neighbor sol: who has 2001:638:403:5050:250:baff:fe80:e40
08:05:14.901969 00:50:ba:80:0e:40 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::250:baff:fe80:e40 > ff02::2: icmp6: router solicitation
08:05:15.839241 00:d0:b7:75:c0:2c > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::2d0:b7ff:fe75:c02c > ff02::1: icmp6: router advertisement

What is in your ifconfig.<IF> ? What is IF? Does it show up in the
boot messages? How did you try to detect the NS packet?

Regards,
-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
wang_jiabo
2009-02-12 08:45:17 UTC
Permalink
my ifconfig.<IF> file added a "up" word,
my IF is wm0
my log messages please see attatchment
I can get global NS,but could not get link-local NS
I used "tcpdump -i eth0 -s 4096 -w netbsd.dump" , eth0 is my monitor
device network interface.
when netbsd rebooted, I used ifconfig -a to show my network interface :
wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx,TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
enabled=0
address: 00:16:76:21:e8:9d
media: Ethernet autoselect (1000baseT
full-duplex,flowcontrol,rxpause,txpause)
status: active
inet 192.168.0.4 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::216:76ff:fe21:e89d%wm0 prefixlen 64 scopeid 0x1
inet6 3ffe:501:ffff:103:216:76ff:fe21:e89d prefixlen 64
rtk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:1d:0f:19:59:fc
media: Ethernet autoselect (none)
status: no carrier
inet6 fe80::21d:fff:fe19:59fc%rtk0 prefixlen 64 scopeid 0x2
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

thanks
Post by Ignatios Souvatzis
Post by wang_jiabo
could you tell me why NetBSD did not send link-local NS when NetBSD
rebooted.
I add ip6mode=autohost in /etc/rc.conf and add up in ifconfig.<IF> file
08:05:11.599259 00:50:ba:80:0e:40 > 33:33:ff:80:0e:40, ethertype IPv6 (0x86dd), length 78: :: > ff02::1:ff80:e40: icmp6: neighbor sol: who has fe80::250:baff:fe80:e40
08:05:12.221896 00:50:ba:80:0e:40 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::250:baff:fe80:e40 > ff02::2: icmp6: router solicitation
08:05:12.604434 00:d0:b7:75:c0:2c > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::2d0:b7ff:fe75:c02c > ff02::1: icmp6: router advertisement
08:05:12.661833 00:50:ba:80:0e:40 > 33:33:ff:80:0e:40, ethertype IPv6 (0x86dd), length 78: :: > ff02::1:ff80:e40: icmp6: neighbor sol: who has 2001:638:403:5050:250:baff:fe80:e40
08:05:14.901969 00:50:ba:80:0e:40 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::250:baff:fe80:e40 > ff02::2: icmp6: router solicitation
08:05:15.839241 00:d0:b7:75:c0:2c > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::2d0:b7ff:fe75:c02c > ff02::1: icmp6: router advertisement
What is in your ifconfig.<IF> ? What is IF? Does it show up in the
boot messages? How did you try to detect the NS packet?
Regards,
-is
Ignatios Souvatzis
2009-02-12 08:59:51 UTC
Permalink
Post by wang_jiabo
my ifconfig.<IF> file added a "up" word,
my IF is wm0
my log messages please see attatchment
I can get global NS,but could not get link-local NS
I used "tcpdump -i eth0 -s 4096 -w netbsd.dump" , eth0 is my monitor
device network interface.
sounds like Linux, so it's a different machine. How did you connect it?

Neighbour solicitations are sent to an address-specific multicast group,
so they're not necessarily received at all switch ports. The best method
to capture would be with an oldstyle 10 MBit non-switching hub in between.

Regards,
-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
wang_jiabo
2009-02-12 09:09:03 UTC
Permalink
I used a cross cable to connect them between netbsd and monitor
device(linux).
I think the issue is from NetBSD or my netbsd device. I think my boot
messages did not show up for wm0, is it correct ?
Thanks
jiabo
Post by Ignatios Souvatzis
Post by wang_jiabo
my ifconfig.<IF> file added a "up" word,
my IF is wm0
my log messages please see attatchment
I can get global NS,but could not get link-local NS
I used "tcpdump -i eth0 -s 4096 -w netbsd.dump" , eth0 is my monitor
device network interface.
sounds like Linux, so it's a different machine. How did you connect it?
Neighbour solicitations are sent to an address-specific multicast group,
so they're not necessarily received at all switch ports. The best method
to capture would be with an oldstyle 10 MBit non-switching hub in between.
Regards,
-is
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Manuel Bouyer
2009-02-12 11:31:04 UTC
Permalink
Post by wang_jiabo
I used a cross cable to connect them between netbsd and monitor
device(linux).
I think the issue is from NetBSD or my netbsd device. I think my boot
messages did not show up for wm0, is it correct ?
What would you expect for wm0 in the boot messages ?
--
Manuel Bouyer, LIP6, Universite Paris VI. ***@lip6.fr
NetBSD: 26 ans d'experience feront toujours la difference
--

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2009-02-12 14:14:28 UTC
Permalink
Post by wang_jiabo
I used a cross cable to connect them between netbsd and monitor
device(linux).
I think the issue is from NetBSD or my netbsd device.
Out of the blue test: try (at least the kernel from) 4.0.1 - I can't see
relevant driver fixes in the release notes, but there was a fix in the
generic neighbour discovery code that might have an influence.
Post by wang_jiabo
I think my boot messages did not show up for wm0, is it correct ?
On the mailing list? Yes, but I didn't copy them into my answer - no
need to multiply them. Everything seems fine with them.


Regards,
-is


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2009-02-13 07:20:47 UTC
Permalink
Post by wang_jiabo
I used a cross cable to connect them between netbsd and monitor
device(linux).
This might be the problem. Maybe the two machines don't agree on
whether they've auto-negotiated the link before the NetBSD side
sends the NS? Can you try with a switch in between, please?

Regards,
-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
wang_jiabo
2009-02-13 07:34:29 UTC
Permalink
Hi, all :

I could not get NS yet so far. yes , I used a switch to connect all the
devices. I did 4 things(all the things was configured ip6mode=autohost
in /etc/rc.conf and add "up" in file /etc/ifconfig.interface):
1. didn't use a switch, just used a cross cable between 2 devices,
one is netbsd4.0, another was performed to capture tcpdump info. could
not get NS
2. all the devices connected to a switch, closed the spanning tree
protocol, could not get NS
3. all the devices connected to a switch, closed the spanning tree,
and set "sysctl -w net.inet6.ip6.dad_count=3 " or 5 in /etc/rc.local,
could not get NS
4. all the devices connected to a switch, closed the spanning tree,
installed 4.0.1 and changed NIC card, could not get NS
thanks


if we used a very old old machine , maybe we can get link-local NS, but
I did not test, because I could not get very old NIC on nowadays
I am sure if we used a new machine like hp xw1800 or dell optiplex 745,
we could not get link-local NS.
if somebody can get NS to use a new machine, please tell me machine name
thanks
jiabo
Post by Ignatios Souvatzis
Post by wang_jiabo
I used a cross cable to connect them between netbsd and monitor
device(linux).
This might be the problem. Maybe the two machines don't agree on
whether they've auto-negotiated the link before the NetBSD side
sends the NS? Can you try with a switch in between, please?
Regards,
-is
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...