Re: ipv6 in FreeBSD 9
On 14/01/2012 18:07, Marco Beishuizen wrote: Hi, In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces=YES. But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable Or, maybe there was an error with mergemaster? old scripts, new kernel variables? BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 in FreeBSD 9
On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. Regards, Marco -- Kin, n.: An affliction of the blood.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 in FreeBSD 9
On 15/01/2012 21:41, Marco Beishuizen wrote: On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Sorry, meant to say, I don't use ipv6 so I can't do much debugging. Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. OK, in the error messages you posted it seems that some script checks or use these variables. Maybe try to run the different networking scripts manually and see where it fails. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 in FreeBSD 9
On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Sorry, meant to say, I don't use ipv6 so I can't do much debugging. Aaah, :-), perhaps I should have read better. Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. OK, in the error messages you posted it seems that some script checks or use these variables. Maybe try to run the different networking scripts manually and see where it fails. Thanks for the tip. I'll do some trial and error and dig deeper. -- Paul's Law: You can't fall off the floor.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 in FreeBSD 9
On Sat, Jan 14, 2012 at 06:07:01PM +0100, Marco Beishuizen wrote: Hi, In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces=YES. But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? This works for me: ifconfig_em0_ipv6=inet6 accept_rtadv ip6addrctl_policy=ipv6_prefer No other IPv6-related settings done anywhere else. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 in FreeBSD 9
On Sat, 14 Jan 2012, the wise Yuri Pankov wrote: In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces=YES. But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? This works for me: ifconfig_em0_ipv6=inet6 accept_rtadv ip6addrctl_policy=ipv6_prefer No other IPv6-related settings done anywhere else. No didn't work. Still the same error messages. Marco -- Kamikazes do it once. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
gahn wrote: Thanks Steve: the router that sending RA is juniper and the protocol router-advertisement has been activated: g...@lab_1 show interfaces fe-0/0/3 ... Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 59) ... Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::214:f600:aa2c:d403 Addresses, Flags: Is-Preferred Is-Primary Destination: fec0:10:5::/64, Local: fec0:10:5:0:214:f600:aa2c:d403 fec0::/10 was deprecated per RFC3879. Perhaps the Juniper unit is obeying this and just not sending the prefix in the advertisement? Everything else looks good, so lets test that possibility (as remote as it is). Take your tcpdump one step further: lab# tcpdump -n -i bge1 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge1, link-type EN10MB (Ethernet), capture size 96 bytes 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 ff02::1: ICMP6, router advertisement, length 24 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 ff02::1: ICMP6, router advertisement, length 24 # tcpdump -n -i bge1 -s 0 -w /path/to/file.pcap ip6 After a time of that running (there won't be any STDOUT output), stop the capture, and open the file in Wireshark. (I've never figured out how to get tcpdump to read the data portion of the packets from a file). With the -s0, it will capture the headers and the data of each packet, so you should be able to tell whether the RA announcements do actually contain the prefix you are trying to get configured. Something that I should have asked from the get-go...do you have any sort of firewall running on the box? I'll set this up in my lab here today. Although we don't have any Juniper units, I'll see if I can recreate the problem with Cisco hardware. You may also want to test using a non-deprecated address space. The documentation address may work for instance. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
Thanks Steve: We use fec0::... as global unique IPv6 address in the lab environment. the IPv6 routers in our lab uses fec0:0:5::/64 with eui-64 addressing scheme (for testing). From the host lab (freebsd) machine, it clearly sees two link-local addresses for two IPv6 routers via RA messages. the IP routers also sent But why not the host lab configure itself with global unique address with prefix fec0:0:5:0::/64 (provided by the routers)? What shall I do to accomplish this on FreeBSD? --- On Thu, 2/12/09, Steve Bertrand st...@ibctech.ca wrote: From: Steve Bertrand st...@ibctech.ca Subject: Re: ipv6 and freebsd To: ipfr...@yahoo.com Cc: freebsd general questions freebsd-questions@freebsd.org Date: Thursday, February 12, 2009, 6:20 AM gahn wrote: Thanks Steve: the router that sending RA is juniper and the protocol router-advertisement has been activated: g...@lab_1 show interfaces fe-0/0/3 ... Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 59) ... Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::214:f600:aa2c:d403 Addresses, Flags: Is-Preferred Is-Primary Destination: fec0:10:5::/64, Local: fec0:10:5:0:214:f600:aa2c:d403 fec0::/10 was deprecated per RFC3879. Perhaps the Juniper unit is obeying this and just not sending the prefix in the advertisement? Everything else looks good, so lets test that possibility (as remote as it is). Take your tcpdump one step further: lab# tcpdump -n -i bge1 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge1, link-type EN10MB (Ethernet), capture size 96 bytes 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 ff02::1: ICMP6, router advertisement, length 24 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 ff02::1: ICMP6, router advertisement, length 24 # tcpdump -n -i bge1 -s 0 -w /path/to/file.pcap ip6 After a time of that running (there won't be any STDOUT output), stop the capture, and open the file in Wireshark. (I've never figured out how to get tcpdump to read the data portion of the packets from a file). With the -s0, it will capture the headers and the data of each packet, so you should be able to tell whether the RA announcements do actually contain the prefix you are trying to get configured. Something that I should have asked from the get-go...do you have any sort of firewall running on the box? I'll set this up in my lab here today. Although we don't have any Juniper units, I'll see if I can recreate the problem with Cisco hardware. You may also want to test using a non-deprecated address space. The documentation address may work for instance. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
gahn wrote: Thanks Steve: We use fec0::... as global unique IPv6 address in the lab environment. the IPv6 routers in our lab uses fec0:0:5::/64 with eui-64 addressing scheme (for testing). From the host lab (freebsd) machine, it clearly sees two link-local addresses for two IPv6 routers via RA messages. the IP routers also sent But why not the host lab configure itself with global unique address with prefix fec0:0:5:0::/64 (provided by the routers)? What shall I do to accomplish this on FreeBSD? Well, I got this working with no issues. The router I used is an old Cisco 2651XM, and my box is FreeBSD 7.1. I even went as far to use space out of fec0::/10. Were you able to get a full pcap to ensure your global prefix is within the RA messages? If the global accept_rtadv is set to 1, and the interface is also told to accept the advertisements, then I can't explain why this is not working for you, other than a firewall on the host blocking inbound ICMP (which is very bad for IPv6, for this reason, and due to the havoc breaking PMTUd can cause). Remember that tcpdump will capture the RA's on the wire before they are dropped by any packet filter. Can you ping6 the lab host from the router, using its link-local address? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
gahn wrote: What shall I do to accomplish this on FreeBSD? For clarification and completeness, here is exactly what I did: First, config the router (Cisco): interface FastEthernet0/0 ip address 192.168.3.2 255.255.255.0 duplex auto speed auto ipv6 address 2607:F118:A::1/64 ipv6 address FEC0:10::1/64 ipv6 nd ra-lifetime 210 ipv6 nd prefix 2607:F118:A::/64 ipv6 nd prefix FEC0:10::/64 Next, on the host, ensure we are properly prepared: # sysctl -a net.inet6.ip6.accept_rtadv net.inet6.ip6.accept_rtadv: 1 # ndp -i fxp0 linkmtu=1500, maxmtu=1500, curhlim=64, basereachable=30s0ms, reachable=39s, retrans=1s0ms Flags: nud accept_rtadv Ensure there is not a blanket ICMP filter on the host, by pinging the link local address from the router (even if you can ping, it is still possible that ICMP type 9 are being blocked): # ping fe80::20d:60ff:fe4c:81ca Output Interface: FastEthernet0/0 Packet sent with a source address of FE80::20A:F4FF:FE0B:B109 ! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms Ensure we see RAs on the wire: # tcpdump -n -i fxp0 ip6 listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes 09:30:50.820717 IP6 fe80::20a:f4ff:fe0b:b109 ff02::1: ICMP6, router advertisement, length 96 Capture the entire packet with the RA information to make sure that the router is actually sending the prefixes we want to autoconf. Dump this info into a file, so we can scp it to our workstation to read it into Wireshark: # tcpdump -n -i fxp0 -s 0 -w /var/log/test.pcap ip6 What does Wireshark tell us about the advertisement: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 1... = Onlink .1.. = Auto ..0. = Not router address ...0 = Not site prefix Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 2607:f118:a:: *** ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 1... = Onlink .1.. = Auto ..0. = Not router address ...0 = Not site prefix Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: fec0:10:: *** So by this point, we've confirmed that everything is in order. I don't know if FreeBSD will autoconf if the 'L' bit (Onlink) flag is set to 0, so check that too. Let's see our ifconfig output: # ifconfig fxp0 inet6 fe80::20d:60ff:fe4c:81ca%fxp0 prefixlen 64 scopeid 0x1 inet 192.168.3.1 netmask 0xff00 broadcast 192.168.3.255 inet6 2607:f118:a:0:20d:60ff:fe4c:81ca prefixlen 64 autoconf inet6 fec0:10::20d:60ff:fe4c:81ca prefixlen 64 autoconf The last thing to try, is to ping6 the known IPv6 address of the router from the host. Perhaps ifconfig is not displaying the learnt addressing information until it is used. (This situation did come up for me, but it may have been a coincidence in timing. I haven't been able to reproduce it). Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
Steve: Thanks for the help. well i find the problem: on the juniper routers, the configuration missed the statement of prefix fec0:: under the clause of router-advertisement. Once i set that right, it works as it should be. best --- On Thu, 2/12/09, Steve Bertrand st...@ibctech.ca wrote: From: Steve Bertrand st...@ibctech.ca Subject: Re: ipv6 and freebsd To: ipfr...@yahoo.com Cc: freebsd general questions freebsd-questions@freebsd.org Date: Thursday, February 12, 2009, 6:20 AM gahn wrote: Thanks Steve: the router that sending RA is juniper and the protocol router-advertisement has been activated: g...@lab_1 show interfaces fe-0/0/3 ... Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 59) ... Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::214:f600:aa2c:d403 Addresses, Flags: Is-Preferred Is-Primary Destination: fec0:10:5::/64, Local: fec0:10:5:0:214:f600:aa2c:d403 fec0::/10 was deprecated per RFC3879. Perhaps the Juniper unit is obeying this and just not sending the prefix in the advertisement? Everything else looks good, so lets test that possibility (as remote as it is). Take your tcpdump one step further: lab# tcpdump -n -i bge1 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge1, link-type EN10MB (Ethernet), capture size 96 bytes 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 ff02::1: ICMP6, router advertisement, length 24 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 ff02::1: ICMP6, router advertisement, length 24 # tcpdump -n -i bge1 -s 0 -w /path/to/file.pcap ip6 After a time of that running (there won't be any STDOUT output), stop the capture, and open the file in Wireshark. (I've never figured out how to get tcpdump to read the data portion of the packets from a file). With the -s0, it will capture the headers and the data of each packet, so you should be able to tell whether the RA announcements do actually contain the prefix you are trying to get configured. Something that I should have asked from the get-go...do you have any sort of firewall running on the box? I'll set this up in my lab here today. Although we don't have any Juniper units, I'll see if I can recreate the problem with Cisco hardware. You may also want to test using a non-deprecated address space. The documentation address may work for instance. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
Thanks Steve: the router that sending RA is juniper and the protocol router-advertisement has been activated: g...@lab_1 show interfaces fe-0/0/3 ... Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 59) ... Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::214:f600:aa2c:d403 Addresses, Flags: Is-Preferred Is-Primary Destination: fec0:10:5::/64, Local: fec0:10:5:0:214:f600:aa2c:d403 g...@lab_r2 show interfaces fe-0/0/3 ... Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 32) Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::214:f600:aa2c:3c03 Addresses, Flags: Is-Preferred Is-Primary Destination: fec0:0:5::/64, Local: fec0:0:5:0:214:f600:aa2c:3c03 g...@lab:~:$ sysctl -a net.inet6.ip6.accept_rtadv net.inet6.ip6.accept_rtadv: 1 g...@lab:~:$ ndp -i bge1 linkmtu=0, maxmtu=1500, curhlim=64, basereachable=30s0ms, reachable=36s, retrans=1s0ms Flags: nud accept_rtadv g...@lab:~:$ ifconfig bge1 bge1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:06:5b:f0:7d:21 inet6 fe80::206:5bff:fef0:7d21%bge1 prefixlen 64 scopeid 0x2 inet 10.0.5.10 netmask 0xff00 broadcast 10.0.5.255 media: Ethernet autoselect (100baseTX full-duplex) status: active lab# tcpdump -n -i bge1 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge1, link-type EN10MB (Ethernet), capture size 96 bytes 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 ff02::1: ICMP6, router advertisement, length 24 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 ff02::1: ICMP6, router advertisement, length 24 --- On Tue, 2/10/09, Steve Bertrand st...@ibctech.ca wrote: From: Steve Bertrand st...@ibctech.ca Subject: Re: ipv6 and freebsd To: ipfr...@yahoo.com Cc: freebsd general questions freebsd-questions@freebsd.org Date: Tuesday, February 10, 2009, 10:35 AM gahn wrote: Thanks for the tips. But i still only see the fe80::..., link-local address, not the fec0:... something as I expected. Provide the output to: # sysctl -a net.inet6.ip6.accept_rtadv # ndp -i fxp0 # ifconfig fxp0 ...and, run a tcpdump on fxp0 capturing only IPv6 packets. Eventually you should see the router advertisements: # tcpdump -n -i fxp0 ip6 If you don't see them, check your router config. What type of router is it? Most routers have RAs disabled by default. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
gahn wrote: Ok, i meant the configuration of ipv6_network_interface=fxp0 alone doesn't seem to be working: [...] how could I enable IPv6 only on the interface fxp0 instead of every interface? It is possible to completely disable IPv6 on an interface, but man (8) ndp recommends against doing this manually. However, you can pretty well achieve the same effect by informing the interfaces to not accept RAs. First (and to answer your next question), enable 'auto config'. You can put the next line in /etc/sysctl.conf to enable it at boot (without the word 'sysctl'): pearl# sysctl net.inet6.ip6.accept_rtadv=1 Now, you can disable acceptance of rtadv messages on individual interfaces by: pearl# ndp -i fxp1 -- -accept_rtadv ...or re-enable: pearl# ndp -i fxp1 -- accept_rtadv So, I think that this will suit your requirements. The only difference being is that although the unused interfaces won't accept RAs, they will still have a link-local address. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
Thanks for the tips. But i still only see the fe80::..., link-local address, not the fec0:... something as I expected. --- On Tue, 2/10/09, Steve Bertrand st...@ibctech.ca wrote: From: Steve Bertrand st...@ibctech.ca Subject: Re: ipv6 and freebsd To: ipfr...@yahoo.com Cc: freebsd general questions freebsd-questions@freebsd.org Date: Tuesday, February 10, 2009, 6:28 AM gahn wrote: Ok, i meant the configuration of ipv6_network_interface=fxp0 alone doesn't seem to be working: [...] how could I enable IPv6 only on the interface fxp0 instead of every interface? It is possible to completely disable IPv6 on an interface, but man (8) ndp recommends against doing this manually. However, you can pretty well achieve the same effect by informing the interfaces to not accept RAs. First (and to answer your next question), enable 'auto config'. You can put the next line in /etc/sysctl.conf to enable it at boot (without the word 'sysctl'): pearl# sysctl net.inet6.ip6.accept_rtadv=1 Now, you can disable acceptance of rtadv messages on individual interfaces by: pearl# ndp -i fxp1 -- -accept_rtadv ...or re-enable: pearl# ndp -i fxp1 -- accept_rtadv So, I think that this will suit your requirements. The only difference being is that although the unused interfaces won't accept RAs, they will still have a link-local address. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
gahn wrote: Thanks for the tips. But i still only see the fe80::..., link-local address, not the fec0:... something as I expected. Provide the output to: # sysctl -a net.inet6.ip6.accept_rtadv # ndp -i fxp0 # ifconfig fxp0 ...and, run a tcpdump on fxp0 capturing only IPv6 packets. Eventually you should see the router advertisements: # tcpdump -n -i fxp0 ip6 If you don't see them, check your router config. What type of router is it? Most routers have RAs disabled by default. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipv6 and freebsd
Ok, i meant the configuration of ipv6_network_interface=fxp0 alone doesn't seem to be working: for /etc/rc.conf: #ipv6_enable=YES ipv6_network_interface=fxp0 u...@lab:~:$ ifconfig fxp0 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:06:5b:f0:7d:21 inet 10.0.0.1 netmask 0xff80 broadcast 10.0.0.127 media: Ethernet autoselect (100baseTX full-duplex) status: active then I modified the file /etc/rc.conf: ipv6_enable=YES ipv6_network_interface=fxp0 then it enabled the IPv6 on every interface. how could I enable IPv6 only on the interface fxp0 instead of every interface? Also how could I enable the feature of auto configuration? I have a router configured on the same subnet on the interface fxp0 as eui-64 and sending out router-advertisement. so far i don't see the automatically configured IPv6 address on the interface fxp0 except the link-local address (the one starts with fe80::). why is that? --- On Mon, 2/9/09, gahn ipfr...@yahoo.com wrote: From: gahn ipfr...@yahoo.com Subject: ipv6 and freebsd To: freebsd general questions freebsd-questions@freebsd.org Date: Monday, February 9, 2009, 2:53 PM Hi all: Free questions with FreeBSD and IPV6. I am running 7.1. 1) My machine has multiple interfaces and some of interfaces I would like to run IP v6 but not all of them. How could I do that? Currently ipv6_enable=YES enables every interface of this machine, and ipv6_network_interface=fxp0 doesn't seem to do anything. 2) I have a router that is running IPv6 router-advertisement. How could I run autoconfiguration mode on the interface of my FreeBSD machine? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
