similar to: FreeBSD Errata Notice FreeBSD-EN-09:03.fxp

I've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to

Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running

Okay, no one had any idea concerning my Radmin question, which I still haven''t figured out. However, I am now trying to figure out an FXP problem. All of the needed details are listed below the description problem. Problem: I have a local windows XP pro computer running FlashFXP behind shorewall 2.0.9 (unpatched) with only two interfaces (ppp0 and eth1) as loc:192.168.1.5. The server

Hi, I noticed that my 4.8R box seems to have a NFS problem. I use a FreeBSD/i386 4.8R box as a NFS server, and a FreeBSD/i386 5-CURRENT (as of today) as the NFS client. On the client, /a (on the server) can be mounted successfully with -o rw,bg,intr,mntudp options. However, when a large amount of write operations such as "cp -r /home/ncvs /a" are performed on the client, the

Motherboard ASUS CUSL2-C with 815EP chipset and two Intel 82559 Pro/100 Ethernet cards exibits the following. dmesg reports usual text only a few seconds after reboot. Later it displays a single line with a fragment of ipfw log, e.g. 167 213.131.11.152 in via fxp0 which seems to change with each new activity of ipfw. Files /var/log/dmesg.today and /var/log/dmesg.yesterday rotate daily as usual

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-09:09.pipe Security Advisory The FreeBSD Project Topic: Local information disclosure via direct pipe writes Category: core Module: kern

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-10:03.zfs Security Advisory The FreeBSD Project Topic: ZFS ZIL playback with insecure permissions Category: contrib Module: zfs Announced:

I've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to

Hello, after upgrading my system from 7.1-RELEASE to recent RELENG_7 I noticed stalled network transfers in certain cases. I have an Intel PRO/100 ethernet adapter (card=0x00408086 chip=0x12298086 rev=0x0c). In general networking works fine. I can ping hosts, surf on websites and so on. But if I send large files (>1 MB) to my server the transfer stalls after a few kilobytes. This concerns FTP

Dear Sirs, I did the following command (against ldapsam backend): net groupmap add rid=3002 unixgroup=wheel type=local ntgroup=Marketoids comment=Mm -d 10 I just wanted to add new group. But instead of that I saw many-many-many records: lib/smbldap.c:smbldap_search(963) passdb/pdb_ldap.c:ldapsam_getgroup(2008) they all wanted to find group with gidNumber=4294967295, yes, sure, there's

Hello again :) With POLLING enabled I experience about 10%-25% performance drop when copying files over network. Tested with both SAMBA and NFS. Is it normal? FreeBSD 7.1-PRERELEASE #0: Sat Sep 6 01:52:12 CEST 2008 fxp0: <Intel 82801DB (ICH4) Pro/100 Ethernet> port 0xc800-0xc83f mem 0xe1021000-0xe1021fff irq 20 at device 8.0 on pci1 # ifconfig fxp0 fxp0:

Hello, smbmount from smbfsx-2.04b-1 kernel 2.2.7 I got a little problem with smbfs. Everything works fine, but sometimes i get doubled directory entries (not all of them). I turned debug on in smbfs and it looks that the doubled items come from NT server (4.0 server SP5 (PDC)). Listing from smbclient is fine. Here is an example from ls -l on smb share: -rw-rw---- 1 root samba 848

Hello everyone, I have issues with samba on FreeBSD. Before I get into the gory details. I'll outline some research I've done. As well as try to show that the people who ask for help and are curious as to why they are getting poor performance from their file server are not A. Crazy, B. Inexperienced and / or C. Twits. (Mind you there is every possibility that I could be covered under

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

Hi there After having posted a while ago about the trouble I had with 3.0.23 I gave it another try with 3.0.23d I installed the current version on our samba PDC and BDC while the member server was still running 3.0.22. This setup has worked for a couple of weeks with no issues. I then upgraded the member server two days ago to 3.0.23d and after serveral hours I could not connect via ssh to

On Thu, 5 Jun 2003, Shaun Jurrens wrote: > On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote: > #> Hi Shaun, > #> > #> Thanks for the input! Glad to hear I'm not the only one > #> > #> In my case, both the SCSI and NIC are integrated on the motherboard, so I > #> cannot really move them around... :) > #> > #> Also, as I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 6.3. The new list is below and at <URL: http://security.freebsd.org/ >. Users of FreeBSD 6.3 are advised to upgrade promptly to a newer release, either by downloading an updated source tree and building updates

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 6.3. The new list is below and at <URL: http://security.freebsd.org/ >. Users of FreeBSD 6.3 are advised to upgrade promptly to a newer release, either by downloading an updated source tree and building updates

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to run a QEMU VM on top of a FreeBSD 7.x server ... I've tried the exact same setup on my desktop, using 192.168.1.x and an fxp device, and it all works perfectly, but as soon as I do this on another machine on a public IP, I'm not getting any routing, I can't even ping it from the same machine ... My first thought was