PF Configuration - FreeBSD Release 9.0 x64
Dear FreeBSD Guys, It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. block in log quick from 41.211.2.239/32 to any Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' ___ 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: PF Configuration - FreeBSD Release 9.0 x64
On 11 Sep 2012, at 10:15, Shiv. Nath prabh...@digital-infotech.net wrote: Dear FreeBSD Guys, It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. block in log quick from 41.211.2.239/32 to any Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' ___ 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 It says it received a *response* so my understanding is *you* are trying to connect. Adjust your rule and see if it's any better.___ 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: PF Configuration - FreeBSD Release 9.0 x64
On Tue, Sep 11, 2012 at 10:15 AM, Shiv. Nath prabh...@digital-infotech.net wrote: Dear FreeBSD Guys, It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. block in log quick from 41.211.2.239/32 to any try block log quick ... instead. -- chs, ___ 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: PF Configuration - FreeBSD Release 9.0 x64
Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' ___ 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 It says it received a *response* so my understanding is *you* are trying to connect. Adjust your rule and see if it's any better.___ 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 Dear D. Fleuriot Christer. S Thanks for your response and help, logically, you are correct (It says it received a *response* so my understanding is *you* are trying to connect) but frankly speaking, i don't know what is happening. i have 5,000 active public IP address configured in my network. The problematic IP belongs to one of my customer 41.211.2.239. i see the same log in many other server as well. i am bit confuse because how 10 servers from my data center has decided to send something to same particular IP whereas there are many thousand other ip available to send something. it is like that machine is sending broadcast and my servers receive it, but it confuse when reading logs. have you come across this kind of issue before? Thanks for your assistance, i will try to block using block log quick ... instead, or i will put this IP to VLAN to stop broadcasting. ___ 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
Kernel panic with geom_multipath + ZFS
Hi, I'm under the illusion that I've found a bug in the FreeBSD kernel, but since I'm new to FreeBSD, a quiet voice tells me it's probably a case of you're doing it wrong. Also, I'm not sure if this is the right place to complain. So feel free to redirect me. I'll start with some context: * FreeBSD storage.[...] 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 * There are 5 expansion units attached via SAS, daisy-chained. Each unit has 12 disks, totalling at 60 disks. To provide path redundancy, the units are connected HBA-1-2-3-4-5 and HBA-5-4-3-2-1. * I've configured a ZFS on top, with 6 RAID-Z2 arrays of 8+2 disks each. This setup should be able to survive a disk failure. However, manually ejecting one of the disks causes a kernel panic. I've manually OCR'd it below. The panic is not triggered by the ejection itself. I can see that fact in the kernel log a few seconds after the ejection. I think the panic is triggered by access to the (now ejected) disk. fault code= supervisor read data, page not present instruction pointer = 0x20:0x807ced68 stack pointer = 0x28:0xff80002ecb70 frame pointer = 0x28:0xff80002ecbc0 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 13 (g_down) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x184 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80g3f874 at g_io_schedule_down+0x1d4 #7 0x807cfb7c at g_down_procbody+0x5c #8 0x8080682f at fork_exit+0x11f #9 0x80b0366e at fork_trampoline+0xe Uptime: 7m16s Automatic reboot in 15 seconds - press a key on the console to abort So the question is either what am I doing wrong? or can anyone confirm this is a bug? thanks in advance, Niels PS: I'm trying to post via email and read via nntp://gmane, I'm not sure how well this works. ___ 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: PF Configuration - FreeBSD Release 9.0 x64
On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot m...@my.gd wrote: On 11 Sep 2012, at 10:15, Shiv. Nath prabh...@digital-infotech.net wrote: It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' It says it received a *response* so my understanding is *you* are trying to connect. But it's avahi (a zeroconf implementation) so the response is to a broadcast; the remote machine in question may also be broadcasting. I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ 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: PF Configuration - FreeBSD Release 9.0 x64
On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery allber...@gmail.com wrote: On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot m...@my.gd wrote: On 11 Sep 2012, at 10:15, Shiv. Nath prabh...@digital-infotech.net wrote: It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' It says it received a *response* so my understanding is *you* are trying to connect. But it's avahi (a zeroconf implementation) so the response is to a broadcast; the remote machine in question may also be broadcasting. I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. You do know that avahi-daemon's main use is to advertise _services_ running on a host? ___ 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: PF Configuration - FreeBSD Release 9.0 x64
On Tue, Sep 11, 2012 at 11:12 AM, Kimmo Paasiala kpaas...@gmail.com wrote: On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery allber...@gmail.com wrote: On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot m...@my.gd wrote: On 11 Sep 2012, at 10:15, Shiv. Nath prabh...@digital-infotech.net wrote: It says it received a *response* so my understanding is *you* are trying to connect. But it's avahi (a zeroconf implementation) so the response is to a broadcast; the remote machine in question may also be broadcasting. I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. You do know that avahi-daemon's main use is to advertise _services_ running on a host? Yes, but zeroconf-style services are often more of a peer-to-peer nature instead of fixed (which don't *need* zeroconf). It's also a larger attack surface. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ 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: PF Configuration - FreeBSD Release 9.0 x64
I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. You do know that avahi-daemon's main use is to advertise _services_running on a host? Yes, but zeroconf-style services are often more of a peer-to-peer nature instead of fixed (which don't *need* zeroconf). It's also a larger attack surface. Dear Brandon A Kimmo P. Thanks for the kind assistance and advices, in my case disabling avahi would not effect me much because it is only a mail server. thanks once again. ___ 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: bsnmpd always died on HDD detach
Mikolaj Golub wrote: On Mon, Sep 10, 2012 at 04:46:15PM +0200, Miroslav Lachman wrote: Mikolaj Golub wrote: On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: I am running bsnmpd with basic snmpd.config (only community and location changed). When there is a problem with HDD and disk disapeared from ATA channel (eg.: disc physically removed) the bsnmpd always dumps core: kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) I see this for a long rime on all releases of 7.x and 8.x branches (i386 and amd64). I did not tested 9.x. Is it a known bug, or should I file PR? Do you happen to run bsnmp-ucd too? If you do then what version is it? In bsnmp-ucd-0.3.5 I introduced a bug that lead to bsnmpd crash on a disk detach. It has been fixed (thanks to Brian Somers) in 0.3.6. No, I never installed bsnmpd-ucd. We are using plain bsnmpd from base without any modules. It is used by MRTG only for network traffic. Nothing else. Then the backtrace might be useful. gdb /usr/sbin/bsnmpd /path/to/bsnmpd.core bt # gdb /usr/sbin/bsnmpd /bsnmpd.core 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 amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `bsnmpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libbegemot.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbegemot.so.4 Reading symbols from /lib/libbsnmp.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libbsnmp.so.5 Reading symbols from /usr/lib/libwrap.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwrap.so.6 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/snmp_mibII.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_mibII.so Reading symbols from /usr/lib/snmp_pf.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_pf.so Reading symbols from /usr/lib/snmp_hostres.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_hostres.so Reading symbols from /lib/libkvm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /usr/lib/libdevinfo.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdevinfo.so.5 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgeom.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libgeom.so.5 Reading symbols from /usr/lib/libmemstat.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libmemstat.so.3 Reading symbols from /lib/libbsdxml.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbsdxml.so.4 Reading symbols from /lib/libsbuf.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libsbuf.so.5 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x000801046cba in refresh_disk_storage_tbl () from /usr/lib/snmp_hostres.so (gdb) bt #0 0x000801046cba in refresh_disk_storage_tbl () from /usr/lib/snmp_hostres.so #1 0x0008010478bd in refresh_device_tbl () from /usr/lib/snmp_hostres.so #2 0x000801047be6 in start_device_tbl () from /usr/lib/snmp_hostres.so #3 0x00080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 #4 0x0040616a in main () Is it all you need? (I don't know how to use gdb) It is on FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Miroslav Lachman ___ 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
Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. This installation is a zfs root, but I don't think this has anything to do with this. Yes, I think that the maintainer of igb and/or lagg driver should absolutely look into this... On 09/07/2012 12:01 PM, Simon Dick wrote: We've had similar problems with lagg at work, each lagg is made up of one igb and one em port, sometimes for no apparent reason they seem to stop passing through traffic. The easiest way we've found to get it working again is ifconfig down and up on one of the physical interfaces. This is on 8.1 On 3 September 2012 19:25, Giulio Ferro au...@zirakzigil.org wrote: No idea anybody why this bug happens? Patches? On 08/29/2012 10:22 PM, Giulio Ferro wrote: On 08/28/2012 11:12 AM, Damien Fleuriot wrote: Hi Giulio, Just to clear things up: igb0: 192.168.9.60/24 lagg0: 192.168.12.21/24 Yes. Actually I notice now that the lagg0 address is different from what I wrote below in my rc.conf (192.168.12.7). I've just made many test with different configuration, but no matter, it just doesn't work... What's the IP of the host you're trying ssh connections from ? I'm just trying to connect to and from management interface igb0 (192.168.9.60). From external pc I do : ssh myuser@192.168.9.60 From that server I do : ssh myuser@pcaddress Just to be more precise, the consequences are: 1) daemon sshd on the server gets stuck and becomes unkillable 2) the first connection may work, but then the program ssh on the server becomes unresponsive and unkillable If I don't create a lagg0 interface and just connect (say) igb1 to the data switch, I've no problem and everything works. Just to answer others' question, I connect igb1, igb2 and igb3 to the same data switch in ports configured for aggregation. I connect igb0 to another management switch (of course not configured for aggregation) Also, just in case, did you enable any firewall ? (PF, ipfw) As I already said, no. Nothing is working/active on this server, just sshd. Thank you. On 27 August 2012 21:22, Giulio Ferro au...@zirakzigil.org wrote: Hi, thanks for the answer Here is what you asked for: # ifconfig igb0 igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether ... inet 192.168.9.60 netmask 0xff00 broadcast 192.168.9.255 inet6 prefixlen 64 scopeid 0x1 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active # netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.9.1UGS 00 igb0 127.0.0.1 link#12UH 00lo0 192.168.9.0/24 link#1 U 0 14 igb0 192.168.9.60 link#1 UHS 00lo0 192.168.12.0/24link#13U 0 109 lagg0 192.168.12.21 link#13UHS 00lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 ::1 link#12 UH lo0 :::0.0.0.0/96 ::1 UGRS lo0 fe80::/10 ::1 UGRS lo0 fe80::%igb0/64link#1U igb0 fe80::ea39:35ff:feb6:a0d4%igb0link#1 UHS lo0 fe80::%igb1/64link#2U igb1 fe80::ea39:35ff:feb6:a0d5%igb1link#2 UHS lo0 fe80::%igb2/64link#3U igb2 fe80::ea39:35ff:feb6:a0d6%igb2link#3 UHS lo0 fe80::%igb3/64link#4U igb3 fe80::ea39:35ff:feb6:a0d7%igb3link#4 UHS lo0 fe80::%lo0/64 link#12 U lo0 fe80::1%lo0 link#12 UHS lo0 fe80::%lagg0/64 link#13 U lagg0 fe80::ea39:35ff:feb6:a0d5%lagg0 link#13 UHS lo0 ff01::%igb0/32fe80::ea39:35ff:feb6:a0d4%igb0 U igb0 ff01::%igb1/32fe80::ea39:35ff:feb6:a0d5%igb1 U igb1 ff01::%igb2/32
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. ___ 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
Clang as default compiler
Today I decided to take the plunge and make clang the default compiler, ie I set WITH_CLANG=yes WITH_CLANG_IS_CC=yes WITH_CLANG_EXTRAS=yes in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options After successful install I went on to upgrade some ports. Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) Best regards Andreas ___ 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: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 11 Sep 2012, Giulio Ferro wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA ifconfig_xl0=up closed_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport xl0 laggport wlan0 ifconfig_lagg0_alias0=inet 10.0.0.4 netmask 0xff00 I use aliasX to add the address and netmask. -- DE ___ 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: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 11 Sep 2012, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org wrote: cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. This was my experience too, though it's been quite a while since I tried it combined onto the same ifconfig line. -- DE ___ 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: Kernel panic with geom_multipath + ZFS
In article 504f4049.9080...@dest-unreach.be, nio...@dest-unreach.be writes: I'm under the illusion that I've found a bug in the FreeBSD kernel, but since I'm new to FreeBSD, a quiet voice tells me it's probably a case of you're doing it wrong. Nope. It's a known bug in the version of geom_multipath that shipped with FreeBSD 9.0. It's fixed in 9.1. -GAWollman ___ 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: Clang as default compiler
On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote: Today I decided to take the plunge and make clang the default compiler, ie I set WITH_CLANG=yes WITH_CLANG_IS_CC=yes WITH_CLANG_EXTRAS=yes in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? It probably is. However, WITHOUT_GCC is not supported yet. On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm l#i386-and-x86_002d64-Options Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in the FreeBSD source directory for supported march switches. ___ 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: bsnmpd always died on HDD detach
On Tue, Sep 11, 2012 at 10:16:57PM +0200, Miroslav Lachman wrote: (gdb) bt #0 0x000801046cba in refresh_disk_storage_tbl () from /usr/lib/snmp_hostres.so #1 0x0008010478bd in refresh_device_tbl () from /usr/lib/snmp_hostres.so #2 0x000801047be6 in start_device_tbl () from /usr/lib/snmp_hostres.so #3 0x00080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 #4 0x0040616a in main () Is it all you need? (I don't know how to use gdb) It is on FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Not sure we can get more than provided from this core as snmp_hostres is not built with debugging symbols. You can try rebuilding snmp_hostres with -g option, intalling and running gdb/bt again DEBUG_FLAGS=-g make -C /usr/src/usr.sbin/bsnmpd/modules/snmp_hostres clean all install AFAIK it might work or not. If it does not then wait for another crash :-) -- Mikolaj Golub ___ 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
