Re: ipv6 / rtadv problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a similar issue. I have: ifconfig_re0_ipv6="inet6 accept_rtadv" And after boot, I get: % ping6 www.google.com PING6(56=40+8+8 bytes) 2001:470:::::: --> 2a00:1450:8005::68 ^C - --- www.l.google.com ping6 statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss But, if I ping my gateway, things are fine: % ping6 2001:470::::1 PING6(56=40+8+8 bytes) 2001:470:::::: --> 2001:470::::1 16 bytes from 2001:470::::1, icmp_seq=0 hlim=64 time=1.037 ms 16 bytes from 2001:470::::1, icmp_seq=1 hlim=64 time=0.365 ms ^C - --- 2001:470::::1 ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.365/0.701/1.037/0.336 ms meatwad% ping6 www.google.com PING6(56=40+8+8 bytes) 2001:470:::::: --> 2a00:1450:8005::68 16 bytes from 2a00:1450:8005::68, icmp_seq=0 hlim=54 time=124.774 ms 16 bytes from 2a00:1450:8005::68, icmp_seq=1 hlim=54 time=123.641 ms ^C - --- www.l.google.com ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 123.641/124.208/124.774/0.566 ms % I didn't have this problem in January. Steve On 03/28/11 08:55, Daniel O'Connor wrote: > Hi, > I am trying to get a -CURRENT box to get an IPv6 address via RTADV, however I > am not having any luck. > > I have tried the following in rc.conf :- > ipv6_enable="YES" > ipv6_gateway_enable="YES" > > ifconfig_em0_ipv6="RTADV" > > (the last one I haven't seen before but it didn't seem to have an effect > anyway) > > ifconfig shows.. > em0: flags=8843 metric 0 mtu 1500 > > options=219b > ether 00:25:90:32:09:1e > inet6 fe80::225:90ff:fe32:91e%em0 prefixlen 64 scopeid 0x2 > inet 203.31.81.43 netmask 0xffc0 broadcast 203.31.81.63 > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active > > I see rtadv packets on the network :- > 12:50:46.444380 IP6 fe80::204:61ff:fe79:276f > ff02::1: ICMP6, router > advertisement, length 56 > > Other hosts can obtain a prefix just fine. This is the only 9.0 one, I have > other FreeBSD boxes but they are 8.x ish. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJNlVJUAAoJEPXPYrMgexuhztQH/0lL3cvjapSAEI6ph+CjyTbB Tm/WJdtpkUMLzW0wM8mDoLYHuXQcG4wv4QpQTcQM4Stk1869LY74nNFTkopk3pc6 TNEa7FfftrJnWGsN8f5HytOen8EGB+tXnSd6b1mXkbSUcJWKALQPFYptv5ssU5Ob +vv2T8Bei77T1OIeDZeg2rFpWQ5IfKeLfzfvnsIKsX1x+QB2+gnWvcb7bWqNMBed tgtVzU9buLSO6WefZl+Q3ykPvR5ARwdJPEzwkuYR0udFbnf6GJGsACsWI6GujfDH skvHIrDNjY39jV+k2qZKF4x7HnbehwM21qZXnxHoMqepnVGIFpo8Y+sJb0mJk+8= =XERs -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On Tue, Mar 29, 2011 at 10:19:26PM +1030, Daniel O'Connor wrote: > > On 29/03/2011, at 22:04, Bernd Walter wrote: > > My assumption is that the problem is with the other host or switch > > network and you just never noticed this so far because this kind of > > problem can easily hide for a very long time. > > Hmm, I have pretty stupid hardware, I am fairly sure none of my switches > understand multicast. There are two class of multicast capable switches. On of them are professional switches of course, but given that IPTV runs with multicast some cheap manageable switches and quite often integrated switches in plastic routers support it as well. IPv4 multicast and IPv6 multicast is very similar, but they use non colliding MAC ranges, so pure IPv4 multicast switches are not a problem for IPv6 multicast, but I'm a bit worried that some cheap devices have alpha quality IPv6 multicast support enabled. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On Tue, Mar 29, 2011 at 11:43:57PM +1030, Daniel O'Connor wrote: > > It is running a fairly old FreeBSD (6.x..), maybe there are bugs there.. I don't think there are general bugs about neighbor discovery in FreeBSD since the beginning, but NIC drivers might have multicast bugs and although you are running this host since a long time such bugs might be unnoticed. You can show and clear the neighbor cache data by using ndp command, which has similar handling as arp. If you use tcpdump to debug NDP packets be aware that by enabling promiscuous mode you get every multicast packet despite of correct filter setup, so you won't see a problem if the driver isn't configuring the filter correctly. On the other hand you can workaround a such driver bug by enabling promiscuous mode. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29/03/2011, at 23:10, Marcin Cieslak wrote: >>> Daniel O'Connor wrote: >> >> On 29/03/2011, at 8:29, Daniel O'Connor wrote: >>> On 29/03/2011, at 1:37, Sergey Kandaurov wrote: 1) ipv6_enable is obsolete in HEAD, see UPDATING. >>> >>> Ahh UPDATING, of course, thanks :) >>> 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also set (as per rfc4861). All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" >>> >>> Great, it works! >> >> I spoke a little too soon, I could not connect to a remote host until I did >> some pings, eg.. >> maarsy-acq:~>telnet -NK6 ipv6.google.com 80 >> Trying 2404:6800:8004::68... >> ^C >> maarsy-acq:~>ping6 metatron >> PING6(56=40+8+8 bytes) 2001:44b8:7c07:5581:225:90ff:fe32:91e --> >> 2001:44b8:7c07:5581:204:61ff:fe79:276f >> 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=0 hlim=64 >> time=0.507 ms >> 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=1 hlim=64 >> time=0.247 ms >> ^C >> --- metatron.gsoft.com.au ping6 statistics --- >> 2 packets transmitted, 2 packets received, 0.0% packet loss >> round-trip min/avg/max/std-dev = 0.247/0.377/0.507/0.130 ms > > Are you having this problem when talking to other v6 in the same LAN? Well, the first one (metatron) I pinged worked fine and after that it all came good. > How does your "netstat -rnf inet6" look like? Routing tables Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSlo0 => default fe80::204:61ff:fe79:276f%em0 UG em0 ::1 ::1 UH lo0 :::0.0.0.0/96 ::1 UGRSlo0 2001:44b8:7c07:5581::/64 link#2U em0 2001:44b8:7c07:5581:225:90ff:fe32:91e link#2UHS lo0 fe80::/10 ::1 UGRSlo0 fe80::%em0/64 link#2U em0 fe80::225:90ff:fe32:91e%em0 link#2UHS lo0 fe80::%lo0/64 link#5U lo0 fe80::1%lo0 link#5UHS lo0 ff01::%em0/32 fe80::225:90ff:fe32:91e%em0 U em0 ff01::%lo0/32 ::1 U lo0 ff02::/16 ::1 UGRSlo0 ff02::%em0/32 fe80::225:90ff:fe32:91e%em0 U em0 ff02::%lo0/32 ::1 U lo0 > Can you reach metatron.gsoft.com.au from your gateway? metatron IS my gateway :) It is running a fairly old FreeBSD (6.x..), maybe there are bugs there.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
>> Daniel O'Connor wrote: > > On 29/03/2011, at 8:29, Daniel O'Connor wrote: >> On 29/03/2011, at 1:37, Sergey Kandaurov wrote: >>> 1) ipv6_enable is obsolete in HEAD, see UPDATING. >> >> Ahh UPDATING, of course, thanks :) >> >>> 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also >>> set (as per rfc4861). >>> All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" >> >> Great, it works! > > I spoke a little too soon, I could not connect to a remote host until I did > some pings, eg.. > maarsy-acq:~>telnet -NK6 ipv6.google.com 80 > Trying 2404:6800:8004::68... > ^C > maarsy-acq:~>ping6 metatron > PING6(56=40+8+8 bytes) 2001:44b8:7c07:5581:225:90ff:fe32:91e --> > 2001:44b8:7c07:5581:204:61ff:fe79:276f > 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=0 hlim=64 > time=0.507 ms > 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=1 hlim=64 > time=0.247 ms > ^C > --- metatron.gsoft.com.au ping6 statistics --- > 2 packets transmitted, 2 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 0.247/0.377/0.507/0.130 ms Are you having this problem when talking to other v6 in the same LAN? How does your "netstat -rnf inet6" look like? Can you reach metatron.gsoft.com.au from your gateway? //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On Tue, Mar 29, 2011 at 08:24:53PM +1030, Daniel O'Connor wrote: > > On 29/03/2011, at 19:05, Sergey Kandaurov wrote: > >> This is repeatable after a reboot, I haven't experienced with FreeBSD 8.x. > >> > > > > I would assume an NDP communication problem or some such, > > it would be interesting to see this sort of traffic, also ifconfig and > > ndp -a output. > > Grr.. I had to reinstall today because I forgot to create a swap partition > and now I can't reproduce the problem :( NDP effectively replaces ARP for IPv6. Like ARP it is also learning by received packets and not only by direct query and because of this problems might be unnoticed. Unlike ARP NDP is using multicast - instead of sending the inquiry to a broadcast address each address has a solicatated multicast address where the query goes to. A NIC driver might have broken multicast support, I doub't that's a problem for your em, but it is more likely that the bug is on the other host. It also could be a problem with multicast aware switches - getting multicast switiching right isn't an easy task and many implementations are full of bugs. If an NDP entry expires a host typically reasks using the unicast address and the last known MAC, so once everything seems to run an underlying multicast problem can live unnoticed for a much longer time. Currently my own LAN router has a NIC driver with broken multicast support and nevertheless everything seems to work fine since months now, but I know the bug is there and that it can bite me each day. And unlike ARP NDP is ICMPv6 and not an individual protocol, some people agressivlely filter ICMPv*, which can easily catch too much. Especially since many people configuring filter lists are not aware of those solicitated addresses. My assumption is that the problem is with the other host or switch network and you just never noticed this so far because this kind of problem can easily hide for a very long time. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29/03/2011, at 22:04, Bernd Walter wrote: >> Grr.. I had to reinstall today because I forgot to create a swap partition >> and now I can't reproduce the problem :( > > NDP effectively replaces ARP for IPv6. > Like ARP it is also learning by received packets and not only by direct > query and because of this problems might be unnoticed. > > Unlike ARP NDP is using multicast - instead of sending the inquiry to > a broadcast address each address has a solicatated multicast address where > the query goes to. > A NIC driver might have broken multicast support, I doub't that's a > problem for your em, but it is more likely that the bug is on the other > host. > It also could be a problem with multicast aware switches - getting > multicast switiching right isn't an easy task and many implementations > are full of bugs. > If an NDP entry expires a host typically reasks using the unicast address > and the last known MAC, so once everything seems to run an underlying > multicast problem can live unnoticed for a much longer time. > Currently my own LAN router has a NIC driver with broken multicast > support and nevertheless everything seems to work fine since months > now, but I know the bug is there and that it can bite me each day. > > And unlike ARP NDP is ICMPv6 and not an individual protocol, some > people agressivlely filter ICMPv*, which can easily catch too much. > Especially since many people configuring filter lists are not aware > of those solicitated addresses. Thanks for the information. > My assumption is that the problem is with the other host or switch > network and you just never noticed this so far because this kind of > problem can easily hide for a very long time. Hmm, I have pretty stupid hardware, I am fairly sure none of my switches understand multicast. If I see it again I will try and get some more information -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29/03/2011, at 19:05, Sergey Kandaurov wrote: >> This is repeatable after a reboot, I haven't experienced with FreeBSD 8.x. >> > > I would assume an NDP communication problem or some such, > it would be interesting to see this sort of traffic, also ifconfig and > ndp -a output. Grr.. I had to reinstall today because I forgot to create a swap partition and now I can't reproduce the problem :( Sorry. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29 March 2011 02:12, Daniel O'Connor wrote: > > On 29/03/2011, at 8:29, Daniel O'Connor wrote: >> On 29/03/2011, at 1:37, Sergey Kandaurov wrote: >>> 1) ipv6_enable is obsolete in HEAD, see UPDATING. >> >> Ahh UPDATING, of course, thanks :) >> >>> 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also >>> set (as per rfc4861). >>> All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" >> >> Great, it works! > > I spoke a little too soon, I could not connect to a remote host until I did > some pings, eg.. > maarsy-acq:~>telnet -NK6 ipv6.google.com 80 > Trying 2404:6800:8004::68... > ^C > maarsy-acq:~>ping6 metatron > PING6(56=40+8+8 bytes) 2001:44b8:7c07:5581:225:90ff:fe32:91e --> > 2001:44b8:7c07:5581:204:61ff:fe79:276f > 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=0 hlim=64 > time=0.507 ms > 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=1 hlim=64 > time=0.247 ms > ^C > --- metatron.gsoft.com.au ping6 statistics --- > 2 packets transmitted, 2 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 0.247/0.377/0.507/0.130 ms > > maarsy-acq:~>telnet -NK6 ipv6.google.com 80 > Trying 2404:6800:8004::68... > Connected to ipv6.l.google.com. > Escape character is '^]'. > ^] > telnet> q > > This is repeatable after a reboot, I haven't experienced with FreeBSD 8.x. > I would assume an NDP communication problem or some such, it would be interesting to see this sort of traffic, also ifconfig and ndp -a output. -- wbr, pluknet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29/03/2011, at 8:29, Daniel O'Connor wrote: > On 29/03/2011, at 1:37, Sergey Kandaurov wrote: >> 1) ipv6_enable is obsolete in HEAD, see UPDATING. > > Ahh UPDATING, of course, thanks :) > >> 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also >> set (as per rfc4861). >> All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" > > Great, it works! I spoke a little too soon, I could not connect to a remote host until I did some pings, eg.. maarsy-acq:~>telnet -NK6 ipv6.google.com 80 Trying 2404:6800:8004::68... ^C maarsy-acq:~>ping6 metatron PING6(56=40+8+8 bytes) 2001:44b8:7c07:5581:225:90ff:fe32:91e --> 2001:44b8:7c07:5581:204:61ff:fe79:276f 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=0 hlim=64 time=0.507 ms 16 bytes from 2001:44b8:7c07:5581:204:61ff:fe79:276f, icmp_seq=1 hlim=64 time=0.247 ms ^C --- metatron.gsoft.com.au ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.247/0.377/0.507/0.130 ms maarsy-acq:~>telnet -NK6 ipv6.google.com 80 Trying 2404:6800:8004::68... Connected to ipv6.l.google.com. Escape character is '^]'. ^] telnet> q This is repeatable after a reboot, I haven't experienced with FreeBSD 8.x. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 29/03/2011, at 1:37, Sergey Kandaurov wrote: > 1) ipv6_enable is obsolete in HEAD, see UPDATING. Ahh UPDATING, of course, thanks :) > 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also > set (as per rfc4861). > All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" Great, it works! Thanks again. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6 / rtadv problem
On 28 March 2011 16:55, Daniel O'Connor wrote: > Hi, > I am trying to get a -CURRENT box to get an IPv6 address via RTADV, however I > am not having any luck. > > I have tried the following in rc.conf :- > ipv6_enable="YES" > ipv6_gateway_enable="YES" > > ifconfig_em0_ipv6="RTADV" > > (the last one I haven't seen before but it didn't seem to have an effect > anyway) > > ifconfig shows.. > em0: flags=8843 metric 0 mtu 1500 > > options=219b > ether 00:25:90:32:09:1e > inet6 fe80::225:90ff:fe32:91e%em0 prefixlen 64 scopeid 0x2 > inet 203.31.81.43 netmask 0xffc0 broadcast 203.31.81.63 > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active > > I see rtadv packets on the network :- > 12:50:46.444380 IP6 fe80::204:61ff:fe79:276f > ff02::1: ICMP6, router > advertisement, length 56 > > Other hosts can obtain a prefix just fine. This is the only 9.0 one, I have > other FreeBSD boxes but they are 8.x ish. > Hi. 1) ipv6_enable is obsolete in HEAD, see UPDATING. 2) Normally hosts ignore rtadv packets if ipv6_gateway_enable is also set (as per rfc4861). All you need is something like ifconfig_em0_ipv6="inet6 accept_rtadv" -- wbr, pluknet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
