bridge, ipv6 and rtadvd
Hi All, Don't know if this is expected behaviour. My LAN (bge0) and WLAN (wlan0) are bridged in bridge0. I tried to run rtadvd on bridge0 but that didn't result in ipv6 addresses on my network. Tried running rtadvd directly /usr/sbin/rtadvd -c /etc/rtadvd.conf -f -D and saw the requests coming in from the client but that didn't result in a working ipv6 network. Wild guessing I tried loading it with /usr/sbin/rtadvd -f -D bge0 and I had a functional ipv6 network. Is this intended behaviour? Am I doing something wrong? One of the other quirks I found was that the example rtadvd.conf line from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ipv6.html does not work, the :addrs#1: makes rtadvd report getconfig bridge0 isn't defined in the configuration file or the configuration file doesn't exist. Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Name and JID support in /etc/rc.d/jail and jail(8) documentation
Hi All,
Created a small patch for 8.1 to add name support to /etc/rc.d/jail.
This doesn't upgrade /etc/rc.d/jail to the overhauled invocation of
8.0 but merely adds the ability to set a jail's name on start which
was added in FreeBSD 7.2 (May 2009).
Could this patch be considered to be applied to stable?
# diff -ruN /etc/rc.d/jail-8.1 /etc/rc.d/jail
--- /etc/rc.d/jail-8.1 2010-07-21 07:19:46.0 +0200
+++ /etc/rc.d/jail 2010-10-24 10:55:14.0 +0200
@@ -38,6 +38,7 @@
_fdescdir=${_devdir}/fd
_procdir=${_rootdir}/proc
eval _hostname=\\$jail_${_j}_hostname\
+ eval _name=\\$jail_${_j}_name\
eval _ip=\\$jail_${_j}_ip\
eval _interface=\\${jail_${_j}_interface:-${jail_interface}}\
eval _exec=\\$jail_${_j}_exec\
@@ -122,6 +123,7 @@
debug $_j procfs enable: $_procfs
debug $_j mount enable: $_mount
debug $_j hostname: $_hostname
+ debug $_j name: $_name
debug $_j ip: $_ip
jail_show_addresses ${_j}
debug $_j interface: $_interface
@@ -635,6 +637,10 @@
i=$((i + 1))
done
+ if [ -n ${_name} ] ; then
+ _flags=${_flags} -n ${_name}
+ fi
+
eval ${_setfib} jail ${_flags} -i ${_rootdir} ${_hostname} \
\${_addrl}\ ${_exec_start} ${_tmp_jail} 21
Kind regards,
Spil.
On Sun, Oct 24, 2010 at 10:52 AM, Spil Oss spil@gmail.com wrote:
Hi All,
When starting a jail you can, as of 8.0 if I'm not mistaken, set the
JID and name for a jail. This change doesn't seem to have been
incorporated into the /etc/rc.d/jail script? Looking at
http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet it wouldn't
be a huge change to add name support. The other additions in that
script look a lot more intrusive. Are there any plans to merge this
patch into the jail rc-script or is this v2 style of jail invocation
still considered to be experimental? As of 8.1 is seems to no longer
be considered experimental looking at the release notes.
The jail(8) documentation (mine lists FreeBSD 8.1 January 17, 2010)
seems to be missing documentation on the vnet command (due to the
experimental status)?
Kind regards,
Spil.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Name and JID support in /etc/rc.d/jail and jail(8) documentation
Hi All, When starting a jail you can, as of 8.0 if I'm not mistaken, set the JID and name for a jail. This change doesn't seem to have been incorporated into the /etc/rc.d/jail script? Looking at http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet it wouldn't be a huge change to add name support. The other additions in that script look a lot more intrusive. Are there any plans to merge this patch into the jail rc-script or is this v2 style of jail invocation still considered to be experimental? As of 8.1 is seems to no longer be considered experimental looking at the release notes. The jail(8) documentation (mine lists FreeBSD 8.1 January 17, 2010) seems to be missing documentation on the vnet command (due to the experimental status)? Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Changes to ipfw in 8.1
Hi, Testing FreeBSD 8.1 I noticed that I seem to have routing or nat or firewall issues. (csupped RELENG_8_1 which was -RELEASE not -RC last night?) - 8.1 booted fine - connections from the system itself were fine - connections from my jails to the internet were not working - connections from my LAN/WLAN to the internet were not working Reverting back to 8.0-p2 with the same configuration works fine. In UPDATING I see that rc.firewall and rc.firewall6 were unified. Setup is - xl0 connected to internet/public IP via dhcp - bge0/wlan0(ath0) connected to LAN - jails have ip's on bge0 in the same subnet as the LAN - allow all from any to any via bge0|wlan0|lo0 - NAT using natd My guess is that something's changed to ipfw that is affecting my network settings. Any clues where I went wrong? Help appreciated/ Kind regards, Spil. rc.conf: firewall_enable=YES firewall_script=/etc/ipfw.rules natd.conf interface xl0 dynamic yes same_ports yes # http/https to http jail redirect_port tcp 192.168.2.3:80 80 redirect_port tcp 192.168.2.3:443 443 Part of /etc/ipfw.rules #!/bin/sh cmd=ipfw -q add skip=skipto 500 pif=xl0 pif6=gif0 ext6=2001:dead:beef:1::1 ks=keep-state ipfw -q -f flush # Allow internal traffic $cmd 002 allow all from any to any via bge0 # exclude LAN traffic $cmd 003 allow all from any to any via lo0 # exclude loopback traffic $cmd 004 allow all from any to any via wlan0 # exclude WLAN traffic $cmd 005 allow all from any to any via bridge0 # exclude WLAN traffic $cmd 006 allow all from any to any via tun0 # exclude WLAN traffic # Allow all encapulated IPv6 to/from tunnel PoP $cmd 010 allow ip4 from tunnel-provider-ipv4 to me via $pif $cmd 010 allow ip4 from me to tunnel-provider-ipv4 via $pif # Black-hole some stuff using tables $cmd 050 drop ip from table(17) to any in via $pif $cmd 050 drop ip from any to table(17) out via $pif # Separate IPv6 rules (no NAT!) $cmd 060 skipto 1000 ip6 from any to any $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound packets from external $cmd 101 check-state # Authorized outbound packets $cmd 130 $skip icmp from any to any out via $pif $ks $cmd 150 $skip tcp from any to any out via $pif $ks $cmd 151 $skip udp from any to any out via $pif $ks $cmd 200 allow udp from 10.50.0.1 to me 68 in $ks # Deny all inbound traffic from non-routable reserved address spaces $cmd 300 unreach host all from 192.168.0.0/16 to any in via $pif #RFC 1918 private IP $cmd 301 unreach host all from 172.16.0.0/12 to any in via $pif #RFC 1918 private IP $cmd 302 unreach host all from 10.0.0.0/8 to any in via $pif #RFC 1918 private IP $cmd 303 unreach host all from 127.0.0.0/8 to any in via $pif #loopback $cmd 304 unreach host all from 0.0.0.0/8 to any in via $pif #loopback $cmd 305 unreach host all from 169.254.0.0/16 to any in via $pif #DHCP auto-config $cmd 306 unreach host all from 192.0.2.0/24to any in via $pif #reserved for docs $cmd 307 unreach host all from 204.152.64.0/23 to any in via $pif #Sun cluster $cmd 308 unreach host all from 224.0.0.0/3 to any in via $pif #Class D E multicast # Deny packets that did not match the dynamic rule table #$cmd 330 deny all from any to any frag in via $pif # All late fragments #$cmd 332 deny tcp from any to any established in via $pif # Deny ACK # Authorized inbound packets $cmd 400 allow icmp from any to any icmptypes 0,11 # echo reply and TTL-exceeded $cmd 420 allow tcp from any to me ssh in via $pif setup $ks $cmd 421 allow tcp from any to me smtp in via $pif $cmd 422 allow tcp from any to me http in via $pif $cmd 423 allow tcp from any to me https in via $pif $cmd 424 allow tcp from any to me imaps in via $pif #$cmd 449 unreach host ip from any to any in via $pif $cmd 448 reject log all from any to any in via $pif $cmd 449 reject log all from any to any out via $pif $cmd 450 reject log ip from any to any # This is skipto location for outbound stateful rules $cmd 500 divert natd ip from any to any out via $pif $cmd 510 allow ip from any to any ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Changes to ipfw in 8.1
Hi Sergey, Has the change from ip to ip4 solved the problem for you? The documentation states that proto 'ip' is the same as 'all' Matches any packet. Rule # 60 $cmd 060 skipto 1000 ip6 from any to any will have already skipped to the ipv6 rules block thus proto 'ip' should always match remaining packets. Meanwhile I found bug 148137 [ipfw] call order of natd and ipfw startup scripts http://www.freebsd.org/cgi/query-pr.cgi?pr=148137cat=conf Don't know if that's directly related, but it may be worth a try to revert back to the RELENG_8_0 script. Will let you now my findings. Kind regards, Spil. On Wed, Jul 21, 2010 at 2:57 PM, Sergey G Nasonov snaso...@bcc.ru wrote: Hello Spill, I have get the same trouble after updating my 8.0 Stable. I thing you need modify some firewall rules. Please change $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound to $cmd 100 divert natd ip4 from any to any in via $pif # Mangle inbound and $cmd 500 divert natd ip from any to any out via $pif to $cmd 500 divert natd ip4 from any to any out via $pif accordingly. -- Best Regards, Nasonov Sergey On Wed, Jul 21, 2010 at 11:40 AM, Spil Oss spil@gmail.com wrote: Hi, Testing FreeBSD 8.1 I noticed that I seem to have routing or nat or firewall issues. (csupped RELENG_8_1 which was -RELEASE not -RC last night?) - 8.1 booted fine - connections from the system itself were fine - connections from my jails to the internet were not working - connections from my LAN/WLAN to the internet were not working Reverting back to 8.0-p2 with the same configuration works fine. In UPDATING I see that rc.firewall and rc.firewall6 were unified. Setup is - xl0 connected to internet/public IP via dhcp - bge0/wlan0(ath0) connected to LAN - jails have ip's on bge0 in the same subnet as the LAN - allow all from any to any via bge0|wlan0|lo0 - NAT using natd My guess is that something's changed to ipfw that is affecting my network settings. Any clues where I went wrong? Help appreciated/ Kind regards, Spil. rc.conf: firewall_enable=YES firewall_script=/etc/ipfw.rules natd.conf interface xl0 dynamic yes same_ports yes # http/https to http jail redirect_port tcp 192.168.2.3:80 80 redirect_port tcp 192.168.2.3:443 443 Part of /etc/ipfw.rules #!/bin/sh cmd=ipfw -q add skip=skipto 500 pif=xl0 pif6=gif0 ext6=2001:dead:beef:1::1 ks=keep-state ipfw -q -f flush # Allow internal traffic $cmd 002 allow all from any to any via bge0 # exclude LAN traffic $cmd 003 allow all from any to any via lo0 # exclude loopback traffic $cmd 004 allow all from any to any via wlan0 # exclude WLAN traffic $cmd 005 allow all from any to any via bridge0 # exclude WLAN traffic $cmd 006 allow all from any to any via tun0 # exclude WLAN traffic # Allow all encapulated IPv6 to/from tunnel PoP $cmd 010 allow ip4 from tunnel-provider-ipv4 to me via $pif $cmd 010 allow ip4 from me to tunnel-provider-ipv4 via $pif # Black-hole some stuff using tables $cmd 050 drop ip from table(17) to any in via $pif $cmd 050 drop ip from any to table(17) out via $pif # Separate IPv6 rules (no NAT!) $cmd 060 skipto 1000 ip6 from any to any $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound packets from external $cmd 101 check-state # Authorized outbound packets $cmd 130 $skip icmp from any to any out via $pif $ks $cmd 150 $skip tcp from any to any out via $pif $ks $cmd 151 $skip udp from any to any out via $pif $ks $cmd 200 allow udp from 10.50.0.1 to me 68 in $ks # Deny all inbound traffic from non-routable reserved address spaces $cmd 300 unreach host all from 192.168.0.0/16 to any in via $pif #RFC 1918 private IP $cmd 301 unreach host all from 172.16.0.0/12 to any in via $pif #RFC 1918 private IP $cmd 302 unreach host all from 10.0.0.0/8 to any in via $pif #RFC 1918 private IP $cmd 303 unreach host all from 127.0.0.0/8 to any in via $pif #loopback $cmd 304 unreach host all from 0.0.0.0/8 to any in via $pif #loopback $cmd 305 unreach host all from 169.254.0.0/16 to any in via $pif #DHCP auto-config $cmd 306 unreach host all from 192.0.2.0/24 to any in via $pif #reserved for docs $cmd 307 unreach host all from 204.152.64.0/23 to any in via $pif #Sun cluster $cmd 308 unreach host all from 224.0.0.0/3 to any in via $pif #Class D E multicast # Deny packets that did not match the dynamic rule table #$cmd 330 deny all from any to any frag in via $pif # All late fragments #$cmd 332 deny tcp from any to any established in via $pif # Deny ACK # Authorized inbound packets $cmd 400 allow icmp from any to any icmptypes 0,11 # echo reply and TTL-exceeded $cmd 420 allow tcp from any to me ssh in via $pif setup $ks $cmd 421 allow tcp from any to me smtp in via $pif $cmd 422 allow tcp from any to me http in via $pif $cmd 423 allow tcp from any to me https in via $pif $cmd 424 allow tcp from any to me imaps
Re: Changes to ipfw in 8.1
Hi Sergey, I'm dumbstruck! Switching 'ip' to 'ip4' in both the divert rules fixed my problem. Personally I think that should go into the UPDATING file as well. I wouldn't have found it if you hadn't told me! Many thanks, Spil. On Wed, Jul 21, 2010 at 9:08 PM, Spil Oss spil@gmail.com wrote: Hi Sergey, Has the change from ip to ip4 solved the problem for you? The documentation states that proto 'ip' is the same as 'all' Matches any packet. Rule # 60 $cmd 060 skipto 1000 ip6 from any to any will have already skipped to the ipv6 rules block thus proto 'ip' should always match remaining packets. Meanwhile I found bug 148137 [ipfw] call order of natd and ipfw startup scripts http://www.freebsd.org/cgi/query-pr.cgi?pr=148137cat=conf Don't know if that's directly related, but it may be worth a try to revert back to the RELENG_8_0 script. Will let you now my findings. Kind regards, Spil. On Wed, Jul 21, 2010 at 2:57 PM, Sergey G Nasonov snaso...@bcc.ru wrote: Hello Spill, I have get the same trouble after updating my 8.0 Stable. I thing you need modify some firewall rules. Please change $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound to $cmd 100 divert natd ip4 from any to any in via $pif # Mangle inbound and $cmd 500 divert natd ip from any to any out via $pif to $cmd 500 divert natd ip4 from any to any out via $pif accordingly. -- Best Regards, Nasonov Sergey On Wed, Jul 21, 2010 at 11:40 AM, Spil Oss spil@gmail.com wrote: Hi, Testing FreeBSD 8.1 I noticed that I seem to have routing or nat or firewall issues. (csupped RELENG_8_1 which was -RELEASE not -RC last night?) - 8.1 booted fine - connections from the system itself were fine - connections from my jails to the internet were not working - connections from my LAN/WLAN to the internet were not working Reverting back to 8.0-p2 with the same configuration works fine. In UPDATING I see that rc.firewall and rc.firewall6 were unified. Setup is - xl0 connected to internet/public IP via dhcp - bge0/wlan0(ath0) connected to LAN - jails have ip's on bge0 in the same subnet as the LAN - allow all from any to any via bge0|wlan0|lo0 - NAT using natd My guess is that something's changed to ipfw that is affecting my network settings. Any clues where I went wrong? Help appreciated/ Kind regards, Spil. rc.conf: firewall_enable=YES firewall_script=/etc/ipfw.rules natd.conf interface xl0 dynamic yes same_ports yes # http/https to http jail redirect_port tcp 192.168.2.3:80 80 redirect_port tcp 192.168.2.3:443 443 Part of /etc/ipfw.rules #!/bin/sh cmd=ipfw -q add skip=skipto 500 pif=xl0 pif6=gif0 ext6=2001:dead:beef:1::1 ks=keep-state ipfw -q -f flush # Allow internal traffic $cmd 002 allow all from any to any via bge0 # exclude LAN traffic $cmd 003 allow all from any to any via lo0 # exclude loopback traffic $cmd 004 allow all from any to any via wlan0 # exclude WLAN traffic $cmd 005 allow all from any to any via bridge0 # exclude WLAN traffic $cmd 006 allow all from any to any via tun0 # exclude WLAN traffic # Allow all encapulated IPv6 to/from tunnel PoP $cmd 010 allow ip4 from tunnel-provider-ipv4 to me via $pif $cmd 010 allow ip4 from me to tunnel-provider-ipv4 via $pif # Black-hole some stuff using tables $cmd 050 drop ip from table(17) to any in via $pif $cmd 050 drop ip from any to table(17) out via $pif # Separate IPv6 rules (no NAT!) $cmd 060 skipto 1000 ip6 from any to any $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound packets from external $cmd 101 check-state # Authorized outbound packets $cmd 130 $skip icmp from any to any out via $pif $ks $cmd 150 $skip tcp from any to any out via $pif $ks $cmd 151 $skip udp from any to any out via $pif $ks $cmd 200 allow udp from 10.50.0.1 to me 68 in $ks # Deny all inbound traffic from non-routable reserved address spaces $cmd 300 unreach host all from 192.168.0.0/16 to any in via $pif #RFC 1918 private IP $cmd 301 unreach host all from 172.16.0.0/12 to any in via $pif #RFC 1918 private IP $cmd 302 unreach host all from 10.0.0.0/8 to any in via $pif #RFC 1918 private IP $cmd 303 unreach host all from 127.0.0.0/8 to any in via $pif #loopback $cmd 304 unreach host all from 0.0.0.0/8 to any in via $pif #loopback $cmd 305 unreach host all from 169.254.0.0/16 to any in via $pif #DHCP auto-config $cmd 306 unreach host all from 192.0.2.0/24 to any in via $pif #reserved for docs $cmd 307 unreach host all from 204.152.64.0/23 to any in via $pif #Sun cluster $cmd 308 unreach host all from 224.0.0.0/3 to any in via $pif #Class D E multicast # Deny packets that did not match the dynamic rule table #$cmd 330 deny all from any to any frag in via $pif # All late fragments #$cmd 332 deny tcp from any to any established in via $pif # Deny ACK # Authorized inbound packets $cmd 400 allow icmp from
ipv6_ifconfig_interface_aliasn not working
Hi, I'm trying to set ipv6 aliases for my jails in my rc.conf but it doesn't seem to work as advertised. I have a /48 range assigned to me (for this example 2001:dead:beef) and am trying to assign ipv6 addresses to a jail. The jails will all have ipv6 addresses in the 2001:dead:beef:1 range. From man rc.conf Aliases should be set as ipv6_ifconfig_interface_aliasn My bge0 config in /etc/rc.conf: ifconfig_bge0=inet6 2001:dead:beef:::1/64 up ipv4_addrs_bge0=10.10.2.1/24 10.10.2.2/24 10.10.2.3/24 10.10.2.5/24 10.10.2.6/24 ipv6_ifconfig_bge0_alias0=2001:dead:beef:1::5/64 rtadvd_interfaces=wlan0 bge0 Additional ipv6 config in /etc/rc.conf ipv6_enable=YES ipv6_gateway_enable=YES The 2001:dead:beef:1::5/64 address is not assigned to bge0. There must be some stupid mistake I'm making in my config. Is it perhaps the ifconfig_bge0 line that screws up my config? Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ipv6_ifconfig_interface_aliasn not working
Thanks for the hints Matthew! Cleaning up my config I found the culprit. Copied ipv6_network_interfaces=gif0 from some guide which off course defeated all my efforts to configure ipv6 on the other interfaces. The ipv6_addrs_interface knob doesn't seem to work (this is 8.0-p2), can't find any references to it in the subr files either. Saw that there's quite a bit of changes in -head though Kind regards, Spil. On Fri, May 14, 2010 at 11:40 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/05/2010 10:07:23, Spil Oss wrote: I'm trying to set ipv6 aliases for my jails in my rc.conf but it doesn't seem to work as advertised. I have a /48 range assigned to me (for this example 2001:dead:beef) and am trying to assign ipv6 addresses to a jail. The jails will all have ipv6 addresses in the 2001:dead:beef:1 range. From man rc.conf Aliases should be set as ipv6_ifconfig_interface_aliasn My bge0 config in /etc/rc.conf: ifconfig_bge0= ipv4_addrs_bge0=10.10.2.1/24 10.10.2.2/24 10.10.2.3/24 10.10.2.5/24 10.10.2.6/24 ipv6_ifconfig_bge0_alias0= rtadvd_interfaces=wlan0 bge0 Additional ipv6 config in /etc/rc.conf ipv6_enable=YES ipv6_gateway_enable=YES The 2001:dead:beef:1::5/64 address is not assigned to bge0. There must be some stupid mistake I'm making in my config. Is it perhaps the ifconfig_bge0 line that screws up my config? Hmmm... for consistencies' sake you should probably be using: ipv6_ifconfig_bge0=2001:dead:beef:::1/64 ipv6_ifconfig_bge0_alias0=2001:dead:beef:1::5/64 or, to make things absolutely parallel to your IPv4 settings: ipv6_addrs_bge0=2001:dead:beef:::1/64 2001:dead:beef:1::5/64 Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvtGpoACgkQ8Mjk52CukIyauACeIVpsDf2VfGT0IpJXf0DQ2wLc ROQAoIomIPblYcDCtYDU1pjDakzHMbWN =OwJ5 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD-8.0 802.11n support with ath
Hi All, Got myself an Atheros AR5416 card to upgrade my HostAP to Wireless-N speed. Somehow I can't find a way to convince the driver to go into 11n mode # ifconfig wlan0 mode 11b # ifconfig wlan0 mode 11g # ifconfig wlan0 mode 11n ifconfig: SIOCSIFMEDIA (media): Device not configured # uname -a FreeBSD server.example.org 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #1: Thu Jan 14 16:35:41 UTC 2010 root@:/usr/obj/usr/src/sys/SERVER80 i386 # dmesg | grep ath ath0: Atheros 5416 mem 0xfcfd-0xfcfd irq 9 at device 3.0 on pci1 ath0: [ITHREAD] ath0: AR5416 mac 13.10 RF2133 phy 8.1 kernel was compiled with options AH_SUPPORT_AR5416 The man-page for ifconfig specifies only 11a, 11b and 11g as modes. The part is functioning fine in 11g mode. Am I missing something obvious or is Wireless-N support not fully implemented yet? Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-8.0 802.11n support with ath
Thanks for the confirmation! Is anything known re. a timeline for implementation of wireless-N? (8.1? 9.0?) Kind regards, Spil On Sat, Feb 27, 2010 at 1:43 PM, Bernhard Schmidt bschm...@techwires.net wrote: On Sat, Feb 27, 2010 at 01:27:09PM +0100, Spil Oss wrote: Hi All, Got myself an Atheros AR5416 card to upgrade my HostAP to Wireless-N speed. Somehow I can't find a way to convince the driver to go into 11n mode # ifconfig wlan0 mode 11b # ifconfig wlan0 mode 11g # ifconfig wlan0 mode 11n ifconfig: SIOCSIFMEDIA (media): Device not configured It's either mode 11na or mode 11ng. The man-page for ifconfig specifies only 11a, 11b and 11g as modes. The part is functioning fine in 11g mode. Am I missing something obvious or is Wireless-N support not fully implemented yet? There is no rate control algo fuer 11n, afaik, you will only be able to use legacy rates. -- Bernhard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Problem with alias length in base Sendmail
Hi All, Today I ran into the BUG documented in the aliases man-page. If you have compiled sendmail with DBM support instead of NEWDB, you may have encountered problems in dbm(3) restricting a single alias to about 1000 bytes of information. snip Looking at Sendmail, it is compiled with NEWDB so the restriction would not apply. # sendmail -d0.1 -bv root Version 8.14.3 Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG If my alias (including whitespace) exceeds ca. 1000 characters, running `make aliases` will report an error. /etc/mail/aliases: line 320: alias too long Resulting in an aliases.db file without the too long alias 550 5.1.1 ali...@example.org... User unknown Which means to me that the alias is simply skipped and the rest of the aliases database is installed. There is a workaround documented with the bug in the man-page, but I'd very much like to understand why this is failing. FreeBSD gw.example.org 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #2: Thu Jun 11 12:58:02 CEST 2009 r...@gw.example.org:/usr/obj/usr/src/sys/MYKERNEL i386 Kind regards, Spil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem with alias length in base Sendmail
Hi jhell, aliases can be used as mailing-lists (remember to also have a listname-owner alias if you wish to use it that way) And there is a work-around, also documented in the aliases man-page. split it up in multiple parts that are lists again mailinglist: mailinglist-part1, mailinglist-part2, mailinglist-part3 mailinglist-part1: recipie...@example.org, recipie...@example.net mailinglist-part2: recepie...@example.net, recipie...@example.org Still curious as to why the NEWDB in FreeBSD does not support more than ca. 1000-bytes in an alias. Kind regards, Spil. On Sun, Jan 24, 2010 at 7:03 PM, jhell jh...@dataix.net wrote: On Sun, 24 Jan 2010 04:50, spil.oss@ wrote: Hi All, Today I ran into the BUG documented in the aliases man-page. If you have compiled sendmail with DBM support instead of NEWDB, you may have encountered problems in dbm(3) restricting a single alias to about 1000 bytes of information. snip Looking at Sendmail, it is compiled with NEWDB so the restriction would not apply. # sendmail -d0.1 -bv root Version 8.14.3 Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG If my alias (including whitespace) exceeds ca. 1000 characters, running `make aliases` will report an error. /etc/mail/aliases: line 320: alias too long Resulting in an aliases.db file without the too long alias 550 5.1.1 ali...@example.org... User unknown Which means to me that the alias is simply skipped and the rest of the aliases database is installed. There is a workaround documented with the bug in the man-page, but I'd very much like to understand why this is failing. FreeBSD gw.example.org 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #2: Thu Jun 11 12:58:02 CEST 2009 r...@gw.example.org:/usr/obj/usr/src/sys/MYKERNEL i386 Kind regards, Spil That's either one hell of a pipe or the owner of that email address can be proud that no-one will ever email him/her ;) Can you post the alias in question ? Maybe there is another way that you could go about doing this if it is not just a test case trying to flaunt the adequate limits of sendmail. -- jhell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Problems with network in jail
Hi all, Is it mandatory to add device mem to jails to enable network via the gateway? Left ezjail with FreeBSD-6.3 (and a hardware replacement of my server) and am now starting again with FreeBSD-7.1. Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin create build 127.0.0.3` and forgot to add the alias to lo0, so no networking off-course. So I added the 127.0.0.3 alias to lo0 `ifconfig lo0 inet 127.0.0.3 alias` and restarted the jail Then I could get to the host machine, but not outside via the gateway. `netstat -nr` was returning errors netstat: kvm not available: /dev/mem: No such file or directory Routing tables rt_tables: symbol not in namelist But I could use the dns on the host, but was restricted to the host. After adding mem to the devfs_rules for my jail, I can see the routing tables And with mem added to devfs, I can also connect via the gateway on the host (NAT) If it's required to add 'mem' to the devfs rules to enable networking in the jail, it may be worth adding to the FAQ and/or the man-pages for ezjail-admin and jail? (and perhaps add a devfsrules_netjail to the default/devfs.rules) Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with network in jail
Hi Peter, Thanks a lot! Will read up on that. (luckily I do speak german/swiss-german). From discussions on ##FreeBSD IRC I learned that it is not recommended to use lo0 for jails! On FreeBSD-6.3 I succesfully used lo0/127.0.0.2 for my mysql jail that needed to be addressed only locally, but ONLY LOCALLY, no other access. It may be possible to add a line similar to 00100 divert 8668 ip from any to any in via xl0 to my ipfw/NAT config, but being warned, I'm not going down that path. Since I moved my portbuild jail to bridge0/172.17.2.17 it works as expected, without device mem! And to boot I made errors when creating my aliases (ifconfig bridge0 inet 172.17.2.17 netmask *172.17.2.255* in stead of 255.255.255.0) I will protect the jails that only need to be connected to from local by adding rules to my ipfw setup Now Iet's hope that my failures/problems serve as reference for future users of (ez)jail! Kind regards, Spil. 2009/1/8 Oliver Peter li...@peter.de.com: On Thu, 8 Jan 2009 11:07:04 +0100 Spil Oss spil@googlemail.com wrote: Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin create build 127.0.0.3` and forgot to add the alias to lo0, so no networking off-course. So I added the 127.0.0.3 alias to lo0 `ifconfig lo0 inet 127.0.0.3 alias` and restarted the jail If you use the loopback device for your jails you have to add NAT rules to your host machine, this documentation is very useful: http://www.rootforum.de/wiki/freebsd/04_jail_infrastructure#packet_filter_einrichten (The article is in German, but the configuration stuff should be understandable anyway) -- Oliver PETER, email: oli...@peter.de.com, ICQ# 113969174 If it feels good, you're doing something wrong. -- Coach McTavish ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
reboot after panic: page fault
Hi all, Posted a message earlier about a panic due to a privileged instruction fault. As a result of that I am now running a kernel with debug symbols. Last night my server crashed again, and now I'm wondering if the community is interested, the crash is probably due to a faulty memory module. 01:20 irssi segfaulted Apr 13 01:30:41 gigabeast savecore: reboot after panic: page fault Apr 13 01:30:41 gigabeast savecore: writing core to vmcore.1 Apr 13 01:30:49 gigabeast kernel: pid 537 (testparm), uid 0: exited on signal 11 (core dumped) Apr 13 01:30:50 gigabeast kernel: pid 544 (smbd), uid 0: exited on signal 6 (core dumped) This morning the machine was in an unusable state (ssh unreachable, display wouldn't switch on), machine wouldn't start at all (no POST) until I removed the memory module that I added after the previous crash. Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: reboot after panic: privileged instruction fault
Hi Bjoern, Was looking at that page, but my kernel doesn't have debug enabled. Someone suggested getting a backtrace using the vanilla kernel, that kernel should still be in /boot/kernel but I can't get it to fly! /boot/kernel.old]# kgdb /boot/kernel.old/kernel /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. Cannot access memory at address 0xc0c04f54 (kgdb) Kind regards, Spil. On 11/04/2008, Bjoern A. Zeeb [EMAIL PROTECTED] wrote: On Fri, 11 Apr 2008, Spil Oss wrote: Yesterday my to-be server running FreeBSD 7.0 #0 has rebooted after a kernel panic. FreeBSD newserver.example.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Fri Apr 4 07:22:22 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE70 i386 Please find messages and kernel-configuration attached. Could you get a backtrace? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html might help you with further debugging. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
reboot after panic: privileged instruction fault
Yesterday my to-be server running FreeBSD 7.0 #0 has rebooted after a kernel panic. FreeBSD newserver.example.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Fri Apr 4 07:22:22 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE70 i386 Please find messages and kernel-configuration attached. This morning I tried to set the default route, but that returned an error not being able to connect to a socket. An hour later I was able to set the default route succesfully. Fortunately I was still configuring and had not migrated to the new server yet. Please advise on steps I can to take to resolve this. Kind regards, Spil. Apr 4 18:41:02 su: bspil01 to root on /dev/ttyp0 Apr 4 23:48:18 kernel: stray irq7 Apr 5 00:39:08 gigabeast kernel: stray irq7 Apr 5 05:35:27 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 5 06:35:26 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 5 11:40:32 gigabeast su: bspil01 to root on /dev/ttyp5 Apr 5 12:05:01 gigabeast su: bspil01 to root on /dev/ttyp3 Apr 5 13:27:44 gigabeast su: bspil01 to root on /dev/ttyp2 Apr 5 14:14:40 gigabeast kernel: stray irq7 Apr 5 16:10:18 gigabeast kernel: stray irq7 Apr 5 16:27:18 gigabeast kernel: too many stray irq 7's: not logging anymore Apr 5 16:43:54 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 5 18:43:54 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 5 20:43:53 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 5 22:43:52 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 6 20:40:27 gigabeast sshd[12083]: error: PAM: authentication error for bspil01 from nlyehvedw1nb541.bachfreund.nl Apr 6 20:51:53 gigabeast su: bspil01 to root on /dev/ttyp4 Apr 6 21:04:34 gigabeast kernel: rtfree: 0xc2d30348 has 1 refs Apr 7 03:01:00 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 7 10:45:02 gigabeast kernel: acpi_video0: ACPI video extension on vgapci0 Apr 7 10:45:02 gigabeast kernel: acpi_video1: ACPI video extension on vgapci1 Apr 7 10:45:02 gigabeast kernel: evaluation of \_SB_.PCI0.VID2._DOD makes no sense Apr 7 20:43:00 gigabeast kernel: bge0: link state changed to DOWN Apr 7 20:43:01 gigabeast kernel: bge0: link state changed to UP Apr 7 20:48:24 gigabeast login: ROOT LOGIN (root) ON ttyv1 Apr 7 20:49:31 gigabeast kernel: acpi_video0: detached Apr 7 20:49:31 gigabeast kernel: acpi_video1: detached Apr 7 20:49:44 gigabeast kernel: acpi_video0: ACPI video extension on vgapci0 Apr 7 20:49:44 gigabeast kernel: acpi_video1: ACPI video extension on vgapci1 Apr 7 20:49:44 gigabeast kernel: evaluation of \_SB_.PCI0.VID2._DOD makes no sense Apr 7 21:17:43 gigabeast kernel: acpi_video0: detached Apr 7 21:17:43 gigabeast kernel: acpi_video1: detached Apr 7 21:17:49 gigabeast kernel: acpi_video0: ACPI video extension on vgapci0 Apr 7 21:17:49 gigabeast kernel: acpi_video1: ACPI video extension on vgapci1 Apr 7 21:17:49 gigabeast kernel: evaluation of \_SB_.PCI0.VID2._DOD makes no sense Apr 8 03:01:01 gigabeast kernel: rtfree: 0xc2d30bb8 has 2 refs Apr 8 19:01:37 gigabeast ntpd[76240]: ntpd 4.2.0-a Thu Apr 3 22:57:31 UTC 2008 (1) Apr 8 19:02:47 gigabeast ntpd[76240]: ntpd exiting on signal 15 Apr 8 19:03:37 gigabeast ntpd[76267]: ntpd 4.2.0-a Thu Apr 3 22:57:31 UTC 2008 (1) Apr 8 19:32:32 gigabeast ntpd[76267]: kernel time sync enabled 2001 Apr 9 02:39:59 gigabeast ntpd[76267]: kernel time sync enabled 6001 Apr 10 11:02:54 gigabeast ntpd[76267]: kernel time sync enabled 6001 Apr 10 11:19:57 gigabeast ntpd[76267]: kernel time sync enabled 2001 Apr 10 11:59:03 gigabeast syslogd: kernel boot file is /boot/kernel/kernel Apr 10 11:59:03 gigabeast kernel: Copyright (c) 1992-2008 The FreeBSD Project. Apr 10 11:59:03 gigabeast kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Apr 10 11:59:03 gigabeast kernel: The Regents of the University of California. All rights reserved. Apr 10 11:59:03 gigabeast kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Apr 10 11:59:03 gigabeast kernel: FreeBSD 7.0-RELEASE #0: Fri Apr 4 07:22:22 CEST 2008 Apr 10 11:59:03 gigabeast kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE70 Apr 10 11:59:03 gigabeast kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Apr 10 11:59:03 gigabeast kernel: CPU: Intel(R) Pentium(R) M processor 1400MHz (1398.82-MHz 686-class CPU) Apr 10 11:59:03 gigabeast kernel: Origin = GenuineIntel Id = 0x695 Stepping = 5 Apr 10 11:59:03 gigabeast kernel: Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE Apr 10 11:59:03 gigabeast kernel: Features2=0x180EST,TM2 Apr 10 11:59:03 gigabeast kernel: real memory = 535453696 (510 MB) Apr 10 11:59:03 gigabeast kernel: avail memory = 514461696 (490 MB) Apr 10 11:59:03 gigabeast kernel: acpi0: DELL CPi R on motherboard Apr 10 11:59:03 gigabeast kernel: acpi0: [ITHREAD] Apr 10 11:59:03 gigabeast kernel: acpi0: reservation of 0, 9fc00 (3) failed Apr 10 11:59:03 gigabeast
Re: Problems with IPv6-less kernel and world
Hi Michael, Well, actually I'm proposing a change to the GENERIC kernel and make.conf.example to add to the comment that one should add WITHOUT_IPV6 to the make.conf if you enable NO_INET6. That sounds to me like something completely different than contacting all port-maintainers. There may off course be a lot of ports in the ports-collection that do not correctly handle WITHOUT_IPV6, and the maintainers of these ports should be contaced on a per-port basis. Kind regards, Spil. On 07/02/07, Michael [EMAIL PROTECTED] wrote: Spil Oss wrote: Hi All, I have NO_INET6 in my /etc/make.conf and INET6 is commented out in my kernel config. Until today I did *not* have WITHOUT_IPV6 in my make.conf In 6.1 I have been unable to run php 5.2 in combination with mail/roundcube, it segfaulted apache, 5.1.6_3 was fine. Since my upgrade to 6.2-RELEASE I was no longer able to connect to the MSN network using irc/bitlbee_1.0.3_3 (which worked fine on 6.1) and every account I had took an additional 75 seconds to load (timeout on the socket) (net.inet.tcp.keepinit: 75000? or net.inet.tcp.keepintvl: 75000?) After trying all kinds of things (openssl, gnutls), today I found out that bitlbee had a --ipv6 knob in it's config and was able to run bitlbee again after fiddling the Makefile. Then I set WITHOUT_IPV6 in my make.conf and that worked as well. To my surprise, a newly compiled PHP 5.2 now also works Should there not be a warning in the examples and man-pages for the make.conf and GENERIC that you should set WITHOUT_IPV6 if you disable INET6 and/or set NO_INET6? Would save idiots like undersigned tripping into this dark hole Kind Regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] I couldn't agree more. This makes it tough for those of us that want to get rid of the overhead of the IPV6 protocol in our systems, and a lot more work in researching whether or not a particular binary will cause problems. What you'll probably have to do Spil is contact the maintainer of each of those ports and request that some form of option or note be added to the port/pkg_desc. Michael Lawver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient taking up all CPU
Hi all,
Rebuilt dhclient with the bpf.c from RELENG_6 ( line 285 == - =)
According to the cvs commit log this fixes my problem.
Still leaves me wondering why this was not applied to RELENG_6_1
Kind regards,
Spil.
On 05/11/06, Brooks Davis [EMAIL PROTECTED] wrote:
It should be fixed in STABLE. The particular fixes were to bpf.c so I
belive (but have not verified) that if you grab the latest version of
that file, put it in src/sbin/dhclient/ and rebuild dhclient the
problems will go away.
-- Brooks
On Sun, Nov 05, 2006 at 09:12:25PM +0100, Spil Oss wrote:
Hi all,
Been experiencing this same behaviour every now-and-then.
FreeBSD/i386 6.1-RELEASE-p10
Any solutions to this?
Kind regards,
Spil.
On 06/05/06, Lodewijk V??ge [EMAIL PROTECTED] wrote:
hello,
a while ago someone reported the same problem I had been seeing, that
dhclient starts taking up 100% CPU. it's probably something comcast
is doing.
I couldn't get the requested coredump then, if I set kern.corefile
to /tmp/%N.core and kill -QUIT it, it doesn't seem to produce a
coredump. but it happened again just now, and I was able to attach
gdb. this is where it's spinning, in receive_packet() in bpf.c:
(gdb)
285 if (interface-rbuf_offset == interface-
rbuf_len) {
(gdb)
299 if (interface-rbuf_len - interface-
rbuf_offset
(gdb)
306 memcpy(hdr, interface-rbuf[interface-
rbuf_offset],
(gdb)
313 if (interface-rbuf_offset + hdr.bh_hdrlen +
hdr.bh_caplen
(gdb)
320 interface-rbuf_offset += hdr.bh_hdrlen;
(gdb)
327 if (hdr.bh_caplen != hdr.bh_datalen) {
(gdb)
328 interface-rbuf_offset =
(gdb)
331 continue;
(gdb)
385 } while (!length);
and then it goes back to line 285. interesting variables are:
(gdb) p *interface
$1 = {next = 0x0, hw_address = {htype = 1 '\001', hlen = 6 '\006',
haddr = \000\021??\223?\000\000\000\000\000\000\000\000\000},
primary_address = {s_addr = 0},
name = vr0, '\0' repeats 12 times, rfdesc = 7, wfdesc = 7,
rbuf = 0x807d000 \022?\\Dk\214, rbuf_max = 4096,
rbuf_offset = 416, rbuf_len = 415, ifp = 0x806f160, client =
0x8075000, noifmedia = 0, errors = 0, dead = 0, index = 2}
(gdb) p length
$2 = 0
(gdb) p hdr
$3 = {bh_tstamp = {tv_sec = 0, tv_usec = 0}, bh_caplen = 4294901760,
bh_datalen = 4294901778, bh_hdrlen = 65535}
this is FreeBSD/i386 6.1-RC as of about two weeks ago.
Lodewijk
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient taking up all CPU
Hi all,
Been experiencing this same behaviour every now-and-then.
FreeBSD/i386 6.1-RELEASE-p10
Any solutions to this?
Kind regards,
Spil.
On 06/05/06, Lodewijk Vöge [EMAIL PROTECTED] wrote:
hello,
a while ago someone reported the same problem I had been seeing, that
dhclient starts taking up 100% CPU. it's probably something comcast
is doing.
I couldn't get the requested coredump then, if I set kern.corefile
to /tmp/%N.core and kill -QUIT it, it doesn't seem to produce a
coredump. but it happened again just now, and I was able to attach
gdb. this is where it's spinning, in receive_packet() in bpf.c:
(gdb)
285 if (interface-rbuf_offset == interface-
rbuf_len) {
(gdb)
299 if (interface-rbuf_len - interface-
rbuf_offset
(gdb)
306 memcpy(hdr, interface-rbuf[interface-
rbuf_offset],
(gdb)
313 if (interface-rbuf_offset + hdr.bh_hdrlen +
hdr.bh_caplen
(gdb)
320 interface-rbuf_offset += hdr.bh_hdrlen;
(gdb)
327 if (hdr.bh_caplen != hdr.bh_datalen) {
(gdb)
328 interface-rbuf_offset =
(gdb)
331 continue;
(gdb)
385 } while (!length);
and then it goes back to line 285. interesting variables are:
(gdb) p *interface
$1 = {next = 0x0, hw_address = {htype = 1 '\001', hlen = 6 '\006',
haddr = \000\021ؠ\223?\000\000\000\000\000\000\000\000\000},
primary_address = {s_addr = 0},
name = vr0, '\0' repeats 12 times, rfdesc = 7, wfdesc = 7,
rbuf = 0x807d000 \022?\\Dk\214, rbuf_max = 4096,
rbuf_offset = 416, rbuf_len = 415, ifp = 0x806f160, client =
0x8075000, noifmedia = 0, errors = 0, dead = 0, index = 2}
(gdb) p length
$2 = 0
(gdb) p hdr
$3 = {bh_tstamp = {tv_sec = 0, tv_usec = 0}, bh_caplen = 4294901760,
bh_datalen = 4294901778, bh_hdrlen = 65535}
this is FreeBSD/i386 6.1-RC as of about two weeks ago.
Lodewijk
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld failure in libexec.mail.local on 6.1 Release
l.s. After running cvsup to RELENG_6_1, I started `make buildworld KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to Update Your System' In libexec/mail.local I get the following on stderr /usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn' /usr/local/lib/libsasl.so: undefined reference to `ldap_unbind' /usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry' /usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s' /usr/local/lib/libsasl.so: undefined reference to `ldap_set_option' /usr/local/lib/libsasl.so: undefined reference to `ldap_memfree' /usr/local/lib/libsasl.so: undefined reference to `ldap_init' /usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s' /usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree' From stdout I had === libexec/mail.local (all) cc -O2 -pipe -funroll-loops -march=pentium3m -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/sasl1 -DSASL -c /usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c cc -O2 -pipe -funroll-loops -march=pentium3m -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/sasl1 -DSASL -L/usr/local/lib -o mail.local mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a -lsasl *** Error code 1 Stop in /usr/src/libexec/mail.local. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. portversion -v on ldap shows [EMAIL PROTECTED]:~]# portversion -v | grep ldap openldap-client-2.2.30 = up-to-date with port And in /usr/local/lib I do find lrwxr-xr-x 1 root wheel 16 Jan 18 23:27 liblber-2.2.so - liblber-2.2.so.7 -rw-r--r-- 1 root wheel67109 Jan 18 23:27 liblber-2.2.so.7 -rw-r--r-- 1 root wheel73738 Jan 18 23:27 liblber.a lrwxr-xr-x 1 root wheel 16 Jan 18 23:27 liblber.so - liblber-2.2.so.7 lrwxr-xr-x 1 root wheel 16 Jan 18 23:27 libldap-2.2.so - libldap-2.2.so.7 -rw-r--r-- 1 root wheel 233395 Jan 18 23:27 libldap-2.2.so.7 -rw-r--r-- 1 root wheel 278908 Jan 18 23:27 libldap.a lrwxr-xr-x 1 root wheel 16 Jan 18 23:27 libldap.so - libldap-2.2.so.7 lrwxr-xr-x 1 root wheel 18 Jan 18 23:27 libldap_r-2.2.so - libldap_r-2.2.so.7 -rw-r--r-- 1 root wheel 254255 Jan 18 23:27 libldap_r-2.2.so.7 -rw-r--r-- 1 root wheel 310072 Jan 18 23:27 libldap_r.a lrwxr-xr-x 1 root wheel 18 Jan 18 23:27 libldap_r.so - libldap_r-2.2.so.7 [EMAIL PROTECTED]:/usr/local/lib]# uname -a FreeBSD beastie 6.0-STABLE FreeBSD 6.0-STABLE #1: Tue Jan 17 12:53:38 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE6 i386 Probably something obvious that I'm missing? Thanks in advance, Spil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nve timeout (and down) regression?
My home-network is so simple I could just tie the desktop to the server's NIC with a cross-cable (xl 3c905C to nve). Let's see if the 3Com 16-port switch is the culprit! Spil. On 24/03/06, Kevin Oberman [EMAIL PROTECTED] wrote: Date: Fri, 24 Mar 2006 22:33:17 +0200 From: Ion-Mihai Tetcu [EMAIL PROTECTED] On Thu, 23 Mar 2006 14:34:24 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Thu, 23 Mar 2006 21:59:56 + (UTC) From: Bjoern A. Zeeb [EMAIL PROTECTED] On Thu, 23 Mar 2006, JoaoBR wrote: On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote: nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for me) in end of dezember since a month or so with recent releng_6 the problem came back, timeouts and stopping rx/tx did you do more updates in the timeframe from december to about a month ago? if the problem was gone and is back now any (exact) dates to narrow down the timeframe where the problem came back would be very helpful. nve0: NVIDIA nForce MCP9 Networking Adapter port 0xbc00-0xbc07 mem 0xfebfa000-0xfebfafff irq 22 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfa000 nve0: Ethernet address 00:0a:48:1d:c6:97 miibus1: MII bus on nve0 nve0: bpf attached nve0: Ethernet address: 00:0a:48:1d:c6:97 nve0: [MPSAFE] This happens w/o any real activity on that interface (which goes into an Allied Telesyn switch): ... Mar 24 19:39:54 worf kernel: nve0: device timeout (1) Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN Mar 24 19:39:55 worf kernel: nve0: link state changed to UP Mar 24 19:40:14 worf kernel: nve0: device timeout (1) Mar 24 19:40:14 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:15 worf kernel: nve0: link state changed to UP Mar 24 19:40:33 worf kernel: nve0: device timeout (2) Mar 24 19:40:33 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:34 worf kernel: nve0: link state changed to UP Mar 24 19:45:52 worf kernel: nve0: device timeout (1) Mar 24 19:45:52 worf kernel: nve0: link state changed to DOWN Mar 24 19:45:53 worf kernel: nve0: link state changed to UP . FreeBSD worf.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 21 01:39:15 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Note that we are running on i386 running am an AMD64 platform. I updated my system (which was happy on Feb. 15 code) to March 13 code and I am still running fine. No errors at all. Also, another system was updated to RELENG_6 yesterday and it is also running clean. Again, all systems are identical dual core AMD64 systems running i386 code. (We would like to run amd64, but OpenOffice.org still does not run on it and we need that.) Only the system in Iowa with the AT switch is seeing problems. Even if there is no traffic, it is possible that something that is negotiated by the switch is triggering the problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Release schedule for 2006
As a FreeBSD-n00b with some 'friends' that know FreeBSD better/well I can only say Please add this kind of information to the Handbook Any addition to the handbook on tracking down problems and smarter ways to fix things would be greatly appreciated. I found myself recompiling my kernel to test changes to a device's driver, but now you tell me I could have done that a lot smarter! Whenever I get my 'knickers-in-a-twist' when using FreeBSD my first point of reference is 'The Handbook'. Any additional information in there would greatly be appreciated. Learning-curve is very, very steep when you're used to lslpp and windowsupdate to patch your system. I _do_ appreciate that most developers and users are very experienced in using FreeBSD, but that makes it increasingly difficult for the not-so-fortunate to come up to speed with the use of FreeBSD. Spil. On 12/17/05, Kövesdán Gábor [EMAIL PROTECTED] wrote: Wilko Bulte wrote: On Sat, Dec 17, 2005 at 01:54:34PM -0800, Joe Rhett wrote.. On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: There will be three FreeBSD 6 releases in 2006. While this is nice, may I suggest that it is time to put aside/delay one release cycle and come up with a binary update mechanism supported well by the OS? Increasing the speed of releases is good. Increasing the number of deployed systems out of date because there are no easy binary upgrade mechanisms is bad. It has been bad, it's getting worse. So, when will you fix it? Or hire someone to fix it? FreeBSD after all is mostly a volunteer operation. I agree. And after all, tracking a security branch isn't too difficult, but the most people think that they have to do a complete make buildworld after a security advisory, but this isn't true. For example there was that cvsbug issue in September: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:20.cvsbug.asc One can read here: b) Execute the following commands as root: # cd /usr/src # patch /path/to/patch # cd /usr/src/gnu/usr.bin/cvs/cvsbug # make obj make depend make make install # cd /usr/src/gnu/usr.bin/send-pr # make obj make depend make make install Is that difficult? I don't think so. No reboot required and it doesn't take more than 5 minutes even on a slower machine. Only the vulnerabilities in the kernel are problematic for servers, since they require a reboot. I think I'll submit a PR with a patch to clarify this in Handbook. Do you consider this useful? Regards, Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Buildkernel failure due to wlan dependency - update comments of GENERIC?
When trying to build a RELENG_6_0 kernel with SMP support and unneccessary devices commented out, I got a failure whilst compiling the ural device. This was due to the fact that I had disabled wlan, but still had ural enabled. Can the comment on ural be modified so one immediately sees this dependency? device umass # Disks/Mass storage - Requires scbus and da device ural# Ralink Technology RT2500USB wireless NICs - Requires wlan (and possibly requires additional devices) Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
xl1: watchdog timeout on 6-STABLE with 3c575B cardbus NIC
Since upgrading to 6-STABLE I get errors on my cardbus NIC. If I have the patience to wait for echo on an ssh terminal one could say that it works, but in a real world it's unusable. Hopefully helpful details: * Worked fine on 5.4 * Whilst downloading a freebsd iso over ftp, no watchdog timeouts occured and speed was 100%, but immediately after the download finished they started popping up again (connecting seems to be slow though) * Inbound connections on xl1 are extremely laggy, switching screens via ssh take a long while to start but then suddenly the whole screen is redrawn. * My xl0 is fine (3Com 3c905C-TX Fast Etherlink XL) ssh, smb, all works as expected. * booting no-acpi results in the same error snippet from dmesg: cardbus0: Resource not specified in CIS: id=14, size=80 cardbus0: Resource not specified in CIS: id=18, size=80 xl1: 3Com 3c575B Fast Etherlink XL port 0x1000-0x107f mem 0x8800-0x887f,0x8880-0x8800 00ff irq 10 at device 0.0 on cardbus0 miibus1: MII bus on xl1 tdkphy0: TDK 78Q2120 media interface on miibus1 tdkphy0: 10baseT, 100baseTX, auto xl1: Ethernet address: 00:00:86:57:76:22 cutcut xl1: watchdog timeout xl1: watchdog timeout xl1: watchdog timeout Anyone got a clue what happens here and how I can fix this? Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
