Re: accepting rtadv broken on 9-STABLE, re driver?
On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato h...@freebsd.org wrote: It is an unexpected behavior and the flag should be set on all interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and the result of ifconfig -a? Back at work so I have access to the machine again: rc.conf: hostname=tech304.office.xxx.net ifconfig_re0=inet 192.168.93.23/24 defaultrouter=192.168.93.1 ipv6_activate_all_interfaces=YES ipv6_ifconfig_re0=inet6 accept_rtadv sshd_enable=YES linux_enable=YES ntpd_enable=YES ntpdate_enable=YES vboxnet_enable=YES tcp_drop_synfin=YES icmp_log_redirect=YES update_motd=NO dbus_enable=YES hald_enable=YES moused_enable=NO moused_nondefault_enable=NO oss_enable=NO #nginx nginx_enable=YES fcgiwrap_enable=YES fcgiwrap_user=www samba_enable=YES #samba_config=/usr/local/etc/samba34/smb.conf lpd_enable=YES #slim_enable=YES exim_enable=YES sendmail_enable=NONE nfs_client_enable=YES smartd_enable=YES zfs_enable=YES sysctl.conf: # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 net.inet.tcp.drop_synfin=1 net.inet.icmp.log_redirect=1 vfs.usermount=1 net.inet6.ip6.accept_rtadv=1 # ifconfig -a 11:43:29 tech304:~ ifconfig -a re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether d0:67:e5:17:e1:32 inet6 fe80::d267:e5ff:fe17:e132%re0 prefixlen 64 scopeid 0x2 inet 192.168.93.23 netmask 0xff00 broadcast 192.168.93.255 inet6 2607:f4e0:100:104:d267:e5ff:fe17:e132 prefixlen 64 autoconf nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL vboxnet0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 0a:00:27:00:00:00 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL Regards, Mark ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
Mark Felder f...@feld.me wrote in op.v7tvkbkr34t2sn@tech304: fe On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato h...@freebsd.org fe wrote: fe fe It is an unexpected behavior and the flag should be set on all fe interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and fe the result of ifconfig -a? fe fe Back at work so I have access to the machine again: (snip) fe # ifconfig -a fe fe 11:43:29 tech304:~ ifconfig -a fe re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric fe 0 mtu 1500 fe options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC fe ether d0:67:e5:17:e1:32 fe inet6 fe80::d267:e5ff:fe17:e132%re0 prefixlen 64 scopeid 0x2 fe inet 192.168.93.23 netmask 0xff00 broadcast 192.168.93.255 fe inet6 2607:f4e0:100:104:d267:e5ff:fe17:e132 prefixlen 64 autoconf fe nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL fe media: Ethernet autoselect (100baseTX full-duplex) fe status: active re0 seems to have ACCEPT_RTADV. What is the problem? fe lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 fe options=3RXCSUM,TXCSUM fe inet6 ::1 prefixlen 128 fe inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 fe inet 127.0.0.1 netmask 0xff00 fe nd6 options=21PERFORMNUD,AUTO_LINKLOCAL fe vboxnet0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 fe ether 0a:00:27:00:00:00 fe nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL -- Hiroki pgpbpIcH7lXYo.pgp Description: PGP signature
Re: accepting rtadv broken on 9-STABLE, re driver?
On Mon, 09 Jan 2012 13:02:24 -0600, Hiroki Sato h...@freebsd.org wrote: re0 seems to have ACCEPT_RTADV. What is the problem? That's because I haven't rebooted Let's start fresh. The normal ipv6 configuration anyone would use: -ipv6_activate_all_interfaces=YES in rc.conf -NO mention of net.inet6.ip6.accept_rtadv in sysctl.conf I boot up, re0 *does not* have ACCEPT_RTADV. I try forcing via the sysctl: net.inet6.ip6.accept_rtadv=1 Still doesn't work! I finally have to result to: ifconfig re0 inet6 accept_rtadv Why? What makes this machine different? All the other machines I run do not require this to get ACCEPT_RTADV. Is it the re driver? My other machines have em and ath interfaces. Thanks, Mark ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
Mark Felder f...@feld.me wrote in op.v7t4xpuh34t2sn@tech304: fe On Mon, 09 Jan 2012 13:02:24 -0600, Hiroki Sato h...@freebsd.org fe wrote: fe fe re0 seems to have ACCEPT_RTADV. What is the problem? fe fe That's because I haven't rebooted fe fe Let's start fresh. fe fe The normal ipv6 configuration anyone would use: fe fe -ipv6_activate_all_interfaces=YES in rc.conf fe fe -NO mention of net.inet6.ip6.accept_rtadv in sysctl.conf fe fe I boot up, re0 *does not* have ACCEPT_RTADV. This is an expected behavior. ACCEPT_RTADV is disabled by default on 9.X. fe I try forcing via the sysctl: net.inet6.ip6.accept_rtadv=1 fe fe Still doesn't work! This needs a reboot. Did you reboot the box? fe Why? What makes this machine different? All the other machines I run fe do not require this to get ACCEPT_RTADV. Is it the re driver? My other fe machines have em and ath interfaces. Putting the following line net.inet6.ip6.accept_rtadv=1 into /etc/sysctl.conf, and then removing the following line ipv6_ifconfig_re0=inet6 accept_rtadv should work, I think. (Of course a reboot is needed after that). -- Hiroki pgpEXn0yC1Kgo.pgp Description: PGP signature
Re: accepting rtadv broken on 9-STABLE, re driver?
On Mon, 09 Jan 2012 19:56:47 -0600, Hiroki Sato h...@freebsd.org wrote: This is an expected behavior. ACCEPT_RTADV is disabled by default on 9.X. Thanks for clarifying. I'll make sure I update our documentation at work regarding how exactly to get ACCEPT_RTADV working so this is clarified. Regards, Mark ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
Mark Felder f...@feld.me wrote in op.v7ogp01w34t2sn@tech304: fe I figured I would end up putting that in rc.conf as a temporary fix, fe but maybe that's just the long term solution. It seems so odd to me fe that the sysctl change doesn't automatically cause the ACCEPT_RTADV fe option to show up for re0, but it does for vboxnet0. Perhaps there fe should be a cleaner way to do this in rc.conf like how we do fe ifconfig_re0=DHCP ? Is it correct that ACCEPT_RTADV option was enabled on the vboxnet0 and not on re0, even after setting net.inet6.ip6.accept_rtadv to 1 at boot time and ipv6_activate_all_interfaces=YES? -- Hiroki pgppWW5QuZYbd.pgp Description: PGP signature
Re: accepting rtadv broken on 9-STABLE, re driver?
Hiroki Sato h...@freebsd.org wrote: Is it correct that ACCEPT_RTADV option was enabled on the vboxnet0 and not on re0, even after setting net.inet6.ip6.accept_rtadv to 1 at boot time and ipv6_activate_all_interfaces=YES? -- Hiroki Yes, that is the behavior I witnessed. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
Mark Felder f...@feld.me wrote in 891fe25c-1560-479f-b855-1713c1c7a...@email.android.com: fe Hiroki Sato h...@freebsd.org wrote: fe fe Is it correct that ACCEPT_RTADV option was enabled on the vboxnet0 fe and not on re0, even after setting net.inet6.ip6.accept_rtadv to 1 at fe boot time and ipv6_activate_all_interfaces=YES? fe fe -- Hiroki fe fe Yes, that is the behavior I witnessed. It is an unexpected behavior and the flag should be set on all interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and the result of ifconfig -a? -- Hiroki pgpXVsZ5gW92U.pgp Description: PGP signature
accepting rtadv broken on 9-STABLE, re driver?
Hi guys, I upgraded my desktop at work just around christmas to 9-PRERELEASE builds and ipv6 has been broken since then. I've been too busy at work to fix it but today I finally had the chance to figure it out. Currently I'm running: 12:11:15 tech304:~ uname -a FreeBSD tech304.office.supranet.net 9.0-STABLE FreeBSD 9.0-STABLE #2 r229703M: Fri Jan 6 11:01:58 CST 2012 r...@tech304.office.supranet.net:/usr/obj/tank/svn/sys/GENERIC amd64 and my ipv6 is not working. In rc.conf I have ipv6_enable_all_interfaces=YES which sets the link local and I had net.inet6.ip6.accept_rtadv=1 in sysctl.conf. I can confirm that it was indeed activated in sysctl, but ifconfig didn't think so: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether d0:67:e5:17:e1:32 inet6 fe80::d267:e5ff:fe17:e132%re0 prefixlen 64 scopeid 0x2 inet 192.168.93.23 netmask 0xff00 broadcast 192.168.93.255 nd6 options=23PERFORMNUD,AUTO_LINKLOCAL## Where's the ACCEPT_RTADV??? media: Ethernet autoselect (100baseTX full-duplex) status: active I have to manually do # ifconfig re0 inet6 accept_rtadv to get it to work. Am I missing something? Grepping /etc/rc.d/ for rtadv finds no clues. Is this broken for everyone, for the re driver, or am I just crazy? Here's pciconf for the device -- let me know if any further info would be useful: re0@pci0:4:0:0: class=0x02 card=0x04f51028 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet Thanks, Mark ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
On 6 January 2012 22:19, Mark Felder f...@feld.me wrote: Hi guys, Hi, I upgraded my desktop at work just around christmas to 9-PRERELEASE builds and ipv6 has been broken since then. I've been too busy at work to fix it but today I finally had the chance to figure it out. Currently I'm running: 12:11:15 tech304:~ uname -a FreeBSD tech304.office.supranet.net 9.0-STABLE FreeBSD 9.0-STABLE #2 r229703M: Fri Jan 6 11:01:58 CST 2012 r...@tech304.office.supranet.net:/usr/obj/tank/svn/sys/GENERIC amd64 and my ipv6 is not working. In rc.conf I have ipv6_enable_all_interfaces=YES which sets the link local and I had You mean ipv6_activate_all_interfaces=YES ? net.inet6.ip6.accept_rtadv=1 in sysctl.conf. I can confirm that it was indeed activated in sysctl, but ifconfig didn't think so: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether d0:67:e5:17:e1:32 inet6 fe80::d267:e5ff:fe17:e132%re0 prefixlen 64 scopeid 0x2 inet 192.168.93.23 netmask 0xff00 broadcast 192.168.93.255 nd6 options=23PERFORMNUD,AUTO_LINKLOCAL ## Where's the ACCEPT_RTADV??? media: Ethernet autoselect (100baseTX full-duplex) status: active I have to manually do # ifconfig re0 inet6 accept_rtadv to get it to work. Am I missing something? Grepping /etc/rc.d/ for rtadv finds no clues. Is this broken for everyone, for the re driver, or am I just crazy? What is in your rc.conf? Do you have inet6 accept_rtadv keyword in it? IIRC it should be enough to specify ifconfig_re0_ipv6=inet6 accept_rtadv without additional tweaks. Consult with rc.conf(5). HTH, pluknet ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
On Fri, 06 Jan 2012 12:49:45 -0600, Sergey Kandaurov pluk...@gmail.com wrote: You mean ipv6_activate_all_interfaces=YES ? Yes... Unfortunately that's what I get for typing it manually and being distracted at the time. :-) What is in your rc.conf? Do you have inet6 accept_rtadv keyword in it? IIRC it should be enough to specify ifconfig_re0_ipv6=inet6 accept_rtadv without additional tweaks. Consult with rc.conf(5). I figured I would end up putting that in rc.conf as a temporary fix, but maybe that's just the long term solution. It seems so odd to me that the sysctl change doesn't automatically cause the ACCEPT_RTADV option to show up for re0, but it does for vboxnet0. Perhaps there should be a cleaner way to do this in rc.conf like how we do ifconfig_re0=DHCP ? Thanks, Mark ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: accepting rtadv broken on 9-STABLE, re driver?
Looping in hrs@ because he's the author of those changes. On 01/06/2012 11:35, Mark Felder wrote: On Fri, 06 Jan 2012 12:49:45 -0600, Sergey Kandaurov pluk...@gmail.com wrote: You mean ipv6_activate_all_interfaces=YES ? Yes... Unfortunately that's what I get for typing it manually and being distracted at the time. :-) What is in your rc.conf? Do you have inet6 accept_rtadv keyword in it? IIRC it should be enough to specify ifconfig_re0_ipv6=inet6 accept_rtadv without additional tweaks. Consult with rc.conf(5). I figured I would end up putting that in rc.conf as a temporary fix, but maybe that's just the long term solution. It seems so odd to me that the sysctl change doesn't automatically cause the ACCEPT_RTADV option to show up for re0, but it does for vboxnet0. Perhaps there should be a cleaner way to do this in rc.conf like how we do ifconfig_re0=DHCP ? -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
