Re: NIC
Dear all, Thanks for your advise and suggestions; I have bought the Intel Pro/1000GT. regards, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: NIC
I don't think dell has their own brand of NIC's in my experience intel has always great quality and support (drivers) for their nic cards -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Jos Chrispijn Sent: Monday, May 04, 2009 3:47 PM To: FreeBSD Questions Subject: NIC In order to speed up my LAN backups a little bit, I would like to replace my old 10/100 nic with a 10/100/1000 one. Should be placed in an ancient Dell of 5 years old. Can someone pls advise on the type nic I should buy (not necessarily a Dell brand)? thanks, Jos Chrispijn -- No one is listening until you make a mistake... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NIC
On Mon, 4 May 2009, Jos Chrispijn wrote: In order to speed up my LAN backups a little bit, I would like to replace my old 10/100 nic with a 10/100/1000 one. Should be placed in an ancient Dell of 5 years old. Can someone pls advise on the type nic I should buy (not necessarily a Dell brand)? The Intel cards are well regarded. A Pro/1000 (PWLA8391GT) works well here. Many other brands of gigabit cards are based on Realtek chipsets, which are not as well regarded. The Realtek gigabit built into the MSI P45 Neo-3 FR motherboard seems to work fine. Probably everyone else will point this out also, but replacing the card alone won't give you gigabit; you also need a switch and maybe new wiring. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: NIC
Jean-Paul Natola writes: I don't think dell has their own brand of NIC's in my experience intel has always great quality and support (drivers) for their nic cards Conversely, cards based on RealTek chips have a reputation of being both inexpensive /and/ cheap. (This may or may not be true of the wireless cards.) The drivers for the Intel cards are written by Intel; I've got a dual-port Pro/1000 GT, and the thing is a _rock_. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NIC
On Mon, May 04, 2009 at 04:31:16PM -0400, Robert Huff wrote: Conversely, cards based on RealTek chips have a reputation of being both inexpensive /and/ cheap. (This may or may not be true of the wireless cards.) The first generation of RealTek chips were little more than a shift register and deserved a poor reputation for requiring a lot of CPU resources. That got RT into market share and now have satisfactory product. The drivers for the Intel cards are written by Intel; I've got a dual-port Pro/1000 GT, and the thing is a _rock_. Ditto. Intel NICs are exceptionally well supported. If one must run Windows, an Intel NIC and Intel driver provide a lot of features which are otherwise missing. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NIC crashes on heavy compile or HD action!
Coen Watstaatervoor wrote: I'm running a Supermicro webserver with a fresh install op FreeBSD 6.2-P9. With these hardware specs: Supermicro Superserver 5014CT P4 SATA 1x Intel Pentium 631 3.0Ghz SKT775 FSB800 2MB 2x Kingston 512MB DDR2 667 PC5300 2x Seagate 80GB SATA 1x 3ware 8006-2LP SATA RAID When I try to install some add-ons, like PostgresSQL, the NIC seems to be bugging. I get complete time-outs or pings around 3000ms. The network connection is up and running as is should but the server won't reply. Ok, I'll bite. YMMV. Is there a console, or are you doing everything remotely? From remote, it's very hard to determine exactly what the issue is, I'd think. Now, assuming it is the NIC, what NIC is it? Is a dmesg available? There is no logging of any errors or problems and after the compile (or even a rm –rf /usr/ports) is finished the server is available again. You mean that rm'ing a large directory structure hangs things up? Is there anyone who has seen this kind of behavior before? Are there any tools, monitoring options, available so I can maybe get closer to the cause of this problem? Depending on what you already know, and what you suspect the problem is, what about systat(1), top(1), ktrace(1), ptrace(1), iostat(8)? Try and use the console if possible; if disk, CPU, etc. seem to be OK, then suspect an issue with the NIC. As I said, YMMV. Good luck. Kevin Kinsey -- I have a hard time being attracted to anyone who can beat me up. -- John McGrath, Atlanta sportswriter, on women weightlifters. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NIC crashes on heavy compile or HD action!
file a PR Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Coen Watstaatervoor Sent: Thursday, December 13, 2007 7:55 AM To: freebsd-questions@freebsd.org Subject: NIC crashes on heavy compile or HD action! I'm running a Supermicro webserver with a fresh install op FreeBSD 6.2-P9. With these hardware specs: Supermicro Superserver 5014CT P4 SATA 1x Intel Pentium 631 3.0Ghz SKT775 FSB800 2MB 2x Kingston 512MB DDR2 667 PC5300 2x Seagate 80GB SATA 1x 3ware 8006-2LP SATA RAID When I try to install some add-ons, like PostgresSQL, the NIC seems to be bugging. I get complete time-outs or pings around 3000ms. The network connection is up and running as is should but the server won't reply. There is no logging of any errors or problems and after the compile (or even a rm –rf /usr/ports) is finished the server is available again. Is there anyone who has seen this kind of behavior before? Are there any tools, monitoring options, available so I can maybe get closer to the cause of this problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.17.1/1183 - Release Date: 12/13/2007 9:15 AM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC of DELL PowerEdge Blade 1955 Server is not detected by FreeBSD 6.2
Hi, Can't go for Current. Is this possible into FreeBSD 6.2 Production Release ? Tom Judge wrote: Sachin Sharma wrote: Hi All, NIC (Network Card) of PowerEdge Blade 1955 Server is not detected by FreeBSD 6.2. I need FreeBSD in these server . Please help me. Thanks I think this may be supported in CURRENT but im not sure, you might want to ask in [EMAIL PROTECTED] Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC problems
On Wednesday 06 December 2006 08:38, Matthew Edwards wrote: Hi, I have a Intel Desktop Board D946GZIS and im using FreeBSD 6.2 Pre-release. I can't get the NIC to work. Please can someone help me as this is urgent. __ Matthew Edwards Clarotech Consulting (Pty) Ltd. Tel:+27 21 762-2928 Fax:+27 21 762-7654 Cell: +27 82 471-3443 Web:www.clarotech.co.za ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Matthew, What are some of the symptoms? Has the nic worked before? If so, are there any error messages in /var/log/messages? What does ifconfig -a show? lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC driver question
U can always add additional Intel/3COM NIC, in case the builtin card is not recognized. -- Aftab Jahan Subedar CEO/Software Engineer Subedar Technologies Ltd Soubedar Baag Bibir Bagicha #1 North Jatra Bari Dhaka 1204 Bangladesh http://www.DhakaStockExchangeGame.com Frank Bonnet wrote: Hello I will receive in few days my new mail server the machine will be an IBM X3650 bi xeon. I wonder what would be the best network interface to plug in (if necessary) as I don't know for now what is the builtin interfaces in this machine. To be clear I'm asking gurus on what is the best FreeBSD supported NIC driver to avoid eventual perfomances problems. Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC driver question
El Mar 21 Nov 2006 09:57, Peter A. Giessel escribió: man em: *** QUOTE *** AUTHORS The em driver was written by Intel Corporation [EMAIL PROTECTED]. *** END QUOTE *** man bge: *** QUOTE *** AUTHORS The bge driver was written by Bill Paul [EMAIL PROTECTED]. *** END QUOTE *** Hi: Forget about bge, since Bill Paul do not support this driver anymore! Here is the mail that he send me some months ago. - El Mar 14 Mar 2006 22:22, escribió: Of all the gin joints in all the towns in all the world, Martin Alejandro Paredes Sanchez had to walk into mine and say: Hi: The problem is that the network card is not detected, is a network card Boradcom in the mother board. I see a chip with this numbers: Broadcom BCM5751FKFB HS0521 P21 744910 N Whit dmesg | grep -i ethe I got: pci2: network, ethernet at device 0.0 (no driver attached) With pciconf -lv I got: [EMAIL PROTECTED]:0:0: class=0x02 card=0x02f71014 chip=0x167e14e4 rev=0x11 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5751F NetXtreme Fast Ethernet PCI Express' class= network subclass = ethernet The manual for bge(4), says: bge -- Broadcom BCM570x/5714/5721/5750/5751/5789 PCI Gigabit Ethernet adapter driver is this nic supported? TIA Oh for crap's sake. How many people are going to keep bothering me with this. For the umpity-umpth time, I do not support this driver anymore! Why don't you make a tiny bit of effort and find out for yourself if the NIC is supported! Edit /sys/dev/bge/if_bgereg.h, and change this: #define BCOM_DEVICEID_BCM5751M 0x167D to this: #define BCOM_DEVICEID_BCM5751M 0x167E Then recompile your kernel and find out for yourself it it works. Then mail all your findings to the freebsd-current mailing list and ask for someone to update the driver. -Bill -- === == -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems === == Ignorance may be bliss, but delusion is ecstasy! -Perki === == ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC not coming up when Ethernet Cable is replugged
change of subject,something must have gone wrong when copy and pasting, sorry On Nov 6, 2006, at 9:56 AM, Mailinglists wrote: Hello all, i am having a strange Problem, which was more apparent under FreeBSD 5.5 and 6.0, but still happens to me under 6.1, on different machines with different NIC`s. Basically when during the day something happens to my Machines Network Connection, for example someone pulls out the Cable, when it is re-plugged in, sometimes it doesn't become active anymore. It doesn't says No Carrier under ifconfig, but the Machine cannot be pinged and also cannot ping another host. Restarting the Machine is no help.Helping is logging in as root, and issuing a ifconfig vr0 down followed by a ifconfig vr0 up. Then there is a console message saying vr0: Using force reset command. After that everything works again as usual. For some machines this is a real problem for me because they dont have Keyboard Mouse or Monitor, and i cant get in remotely. Thanks for any Ideas, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] !DSPAM:1084,454e95556571669696758! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release
Chris wrote: On Sep 12, 2006, at 3:12 PM, Alex Zbyslaw wrote: Chris wrote: Is there any single source where one can go to see what has been changed on the various components of the OS. Go to the source :-) http://www.freebsd.org/cgi/cvsweb.cgi/ Wow! That's an excellent resource and the bge driver does have numerous changes that all dance around or on the same issues. It appears they've been being addressed for months. Supporting that, two people have responded and said both a Tyan and several IBMs are working perfectly with the Broadcom. Based on the 6.1-RELEASE-p6 AMD64 system I did yesterday (a different server), I didn't see any of these changes on the source date for if_bge.c. I'm guessing this has to do with how I cvsup and the fact that I remain tracking only 6.1-RELEASE. I used: *default release=cvs tag=RELENG_6_1 in the supfile and these changes are not pulled under that tag. How does one approach that, set the tag to RELENG_6 which does grab these. From the handbook it seems to recommend not moving forward from a RELEASE for a production type of implementation. How does one grab specific changes to a driver without actually cvsupping to that entire revision or am I missing something really basic and I should be using the RELENG_6 tag for my production servers? It really looks like that's the version of the bge driver I should be using. If you click on if_bge.c (which I guess you did to see all the comments), you'll see above each comment a Branch: which tells you where the changes have been committed. E.g. Revision *1.91.2.17* http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c?rev=1.91.2.17content-type=text/x-cvsweb-markup / (*download* http://www.freebsd.org/cgi/cvsweb.cgi/%7Echeckout%7E/src/sys/dev/bge/if_bge.c?rev=1.91.2.17content-type=text/plain) - annotate http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c?annotate=1.91.2.17 - [select for diffs] http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c?r1=1.91.2.17, /Thu Sep 7 08:49:10 2006 UTC/ (6 days, 2 hours ago) by /oleg/ Branch: *RELENG_6 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c?only_with_tag=RELENG_6 * Changes since *1.91.2.16: +24 -5 lines* Diff to previous 1.91.2.16 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.91.2.16r2=1.91.2.17 (colored http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.91.2.16r2=1.91.2.17f=h) to branchpoint 1.91 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.91r2=1.91.2.17 (colored http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.91r2=1.91.2.17f=h) next main 1.92 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.92r2=1.91.2.17 (colored http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.92r2=1.91.2.17f=h) MFC rev. 1.140 Properly lock ifmedia callbacks. This should prevent concurrent access to PHY. Following issues should be resolved: - random watchdog timeouts (caused by concurrent phy access) - some link state issues - non working TX if media type was set explicitly PR: kern/98738 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=98738 which looks like one you'd want! You'll see the tag is RELENG_6 so yes you will need to cvsup to this (aka 6-STABLE) to get those changes. Presumably the changes will make it to 6.2-RELEASE, so you could switch to tracking that when it comes out. I would be wary of actively tracking a production server with STABLE. If you upgrade to STABLE now and it works, just leave it unless there are security patches. At least one change is to HEAD/Main which is aka 7-CURRENT. That would be risky for a production box. Alternatively you could just try downloading the two files and copying them over your existing ones (after backing them up!) and just try and see if a make buildkernel will compile them. If the changes don't rely on anything outside of these two files, you'd likely be fine. Of course, keep a copy of your current working kernel in e.g. /boot/kernel.works. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release
Alex Zbyslaw wrote: Alternatively you could just try downloading the two files and copying them over your existing ones (after backing them up!) and just try and see if a make buildkernel will compile them. If the changes don't rely on anything outside of these two files, you'd likely be fine. Of course, keep a copy of your current working kernel in e.g. /boot/kernel.works. Sorry for the hideous http links in previous email. What *I* saw before I sent it was not what I got. sigh Also, download the RELENG_6 versions of the files if you try this approach. Downloading the HEAD versions would be riskier and more likely to fail. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release - Obtaining changes not in RELEASE
On Sep 13, 2006, at 4:03 AM, Alex Zbyslaw wrote: Chris wrote: Is there any single source where one can go to see what has been changed on the various components of the OS. Go to the source :-) http://www.freebsd.org/cgi/cvsweb.cgi/ Wow! That's an excellent resource and the bge driver does have numerous changes that all dance around or on the ... Based on the 6.1-RELEASE-p6 AMD64 system I did yesterday (a different server), I didn't see any of these changes on the source date for if_bge.c. I'm guessing this has to do with how I cvsup and the fact that I remain tracking only 6.1-RELEASE. I used: *default release=cvs tag=RELENG_6_1 in the supfile and these changes are not pulled under that tag. How does one approach that, set the tag to RELENG_6 which does grab these. From the handbook it seems to recommend not moving forward from a RELEASE for a production type of implementation. How does one grab specific changes to a driver without actually cvsupping to that entire revision or am I missing something really basic and I should be using the RELENG_6 tag for my production servers? It really looks like that's the version of the bge driver I should be using. If you click on if_bge.c (which I guess you did to see all the comments), you'll see above each comment a Branch: which tells you where the changes have been committed. E.g. Revision *1.91.2.17* http://www.freebsd.org/cgi/cvsweb.cgi/src/ sys/dev/bge/if_bge.c?rev=1.91.2.17content-type=text/x-cvsweb- markup / (*download* http://www.freebsd.org/cgi/cvsweb.cgi/% 7Echeckout%7E/src/sys/dev/bge/if_bge.c?rev=1.91.2.17content- type=text/plain) - annotate http://www.freebsd.org/cgi/ cvsweb.cgi/src/sys/dev/bge/if_bge.c?annotate=1.91.2.17 - [select for diffs] http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ if_bge.c?r1=1.91.2.17, /Thu Sep 7 08:49:10 2006 UTC/ (6 days, 2 hours ago) by /oleg/ Branch: *RELENG_6 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/ dev/bge/if_bge.c?only_with_tag=RELENG_6 * Changes since *1.91.2.16: +24 -5 lines* Diff to previous 1.91.2.16 http://www.freebsd.org/cgi/cvsweb.cgi/ src/sys/dev/bge/if_bge.c.diff?r1=1.91.2.16r2=1.91.2.17 (colored http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ if_bge.c.diff?r1=1.91.2.16r2=1.91.2.17f=h) to branchpoint 1.91 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ if_bge.c.diff?r1=1.91r2=1.91.2.17 (colored http:// www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff? r1=1.91r2=1.91.2.17f=h) next main 1.92 http://www.freebsd.org/ cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.92r2=1.91.2.17 (colored http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ if_bge.c.diff?r1=1.92r2=1.91.2.17f=h) MFC rev. 1.140 Properly lock ifmedia callbacks. This should prevent concurrent access to PHY. Following issues should be resolved: - random watchdog timeouts (caused by concurrent phy access) - some link state issues - non working TX if media type was set explicitly PR: kern/98738 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=98738 which looks like one you'd want! You'll see the tag is RELENG_6 so yes you will need to cvsup to this (aka 6-STABLE) to get those changes. Presumably the changes will make it to 6.2-RELEASE, so you could switch to tracking that when it comes out. I would be wary of actively tracking a production server with STABLE. If you upgrade to STABLE now and it works, just leave it unless there are security patches. At least one change is to HEAD/Main which is aka 7-CURRENT. That would be risky for a production box. Alternatively you could just try downloading the two files and copying them over your existing ones (after backing them up!) and just try and see if a make buildkernel will compile them. If the changes don't rely on anything outside of these two files, you'd likely be fine. Of course, keep a copy of your current working kernel in e.g. /boot/kernel.works. --Alex Alex, Excellent and detailed information. I read the handbook and Complete FreeBSD but couldn't grasp the relationship between CURRENT, STABLE, and RELEASE and the cvsup tags definitively. This is important when buying new hardware running ahead of RELEASE changes (e.g. the Broadcom 5704). Last time (a then leading edge server with a U320 Adaptec controller), I manually updated the driver source just to get it to production and made my source out of sync and then feared cvsuping further. I think you've given me, in a nutshell, how to do this more responsibly. Let me take a shot at it for posterity. 1. Take the machine to STABLE via RELENG_6, if it tests reliably, go production and freeze 2. security patch through the .asc file patches until RELEASE 6.2 3. cvsup to RELEASE 6.2 aka RELENG_6_2 (when available and if needed hardware changes were indeed incorporated) 4. given no hardware additions, continue to cvsup on RELENG_6_2_0 for Security Patches
Re: NIC Questions for 6.1 Release - Obtaining changes not in RELEASE
Chris wrote: Excellent and detailed information. I read the handbook and Complete FreeBSD but couldn't grasp the relationship between CURRENT, STABLE, and RELEASE and the cvsup tags definitively. This is important when buying new hardware running ahead of RELEASE changes (e.g. the Broadcom 5704). Last time (a then leading edge server with a U320 Adaptec controller), I manually updated the driver source just to get it to production and made my source out of sync and then feared cvsuping further. I think you've given me, in a nutshell, how to do this more responsibly. Let me take a shot at it for posterity. RELENG = The official release versions; as well tested as things come. Only get security patches. CURRENT = The very bleeding edge. Updated often. Not recommended for any critical machine. STABLE = Changes that have run well in CURRENT, fix problems or improve performance etc, and are things which will form part of the next RELEASE. Bugs and other issues much less likely than CURRENT. So developed software generally goes from CURRENT (when tested) - STABLE - next RELENG. But, not all software in CURRENT automatically goes to STABLE. CURRENT (right now) is what will be RELENG_7_0, and not all changes there will be suitable for 6. 1. Take the machine to STABLE via RELENG_6, if it tests reliably, go production and freeze 2. security patch through the .asc file patches until RELEASE 6.2 3. cvsup to RELEASE 6.2 aka RELENG_6_2 (when available and if needed hardware changes were indeed incorporated) 4. given no hardware additions, continue to cvsup on RELENG_6_2_0 for Security Patches for server life-cycle This should work fine. In step 4, you can consider upgrading from RELENG_6_2 to RELENG_6_3 etc etc, obviously testing. The more critical a machine, however, the less likely you are to want to do that. If you have any kind of farm, then keeping identical hardware and using one machine as a test bed for any upgrades is also a possible scenario. The farm can be as small as two machines - one a backup for the other, but also usable for testing upgrades. I think it would be technically possible (if unlikely), that a security patch for STABLE might not apply cleanly if you are not running the latest STABLE. In such a case, you might again have to bite the bullet and update to the latest STABLE and test again. This is only likely to happen if the bug is some kind of kernel internal, and even then only if some other code for it in STABLE has changed since you did your upgrade. As I say, I think this would be unlikely. Depending on what the machine in question actually does, how it is firewalled etc, it might be that you don't even bother to apply a security patch. (No doubt some will shout when I say that), but you have to analyse what risk the security whole actually poses to *your machine*. You could always seek advice here if such an issue arises, I think a light is clicking on. Thanks VERY much, You're welcome. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release
On Sep 12, 2006, at 12:01 PM, Peter A. Giessel wrote: On 2006/09/12 10:52, Chris seems to have typed: These are coming out of the boot as: bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 The computer is a Tyan s4884 quad opteron (duals). I have a Tyan S2882G3NR-D with: bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfc9c-0xfc9c,0xfc9b-0xfc9b irq 24 at device 9.0 on pci2 running on the AMD64 version of FreeBSD: FreeBSD 6.1-RELEASE-p2 #4: Sun Jul 2 22:27:35 AKDT 2006 (dual Opteron 246's) Its been stable since the update to 6.1 (went from 6.0 directly to 6.1-p2). This is encouraging. I will forego the cost of the Intel NICs and just go to 6.1-p6. Thank you very much. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release
Chris wrote: Is there any single source where one can go to see what has been changed on the various components of the OS. Go to the source :-) http://www.freebsd.org/cgi/cvsweb.cgi/ Especially for changes to limited components like a specific ethernet driver, it quite easy to see if anything has changed recently, as well as the comments in the commit logs. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC Questions for 6.1 Release
On Sep 12, 2006, at 3:12 PM, Alex Zbyslaw wrote: Chris wrote: Is there any single source where one can go to see what has been changed on the various components of the OS. Go to the source :-) http://www.freebsd.org/cgi/cvsweb.cgi/ Wow! That's an excellent resource and the bge driver does have numerous changes that all dance around or on the same issues. It appears they've been being addressed for months. Supporting that, two people have responded and said both a Tyan and several IBMs are working perfectly with the Broadcom. Based on the 6.1-RELEASE-p6 AMD64 system I did yesterday (a different server), I didn't see any of these changes on the source date for if_bge.c. I'm guessing this has to do with how I cvsup and the fact that I remain tracking only 6.1-RELEASE. I used: *default release=cvs tag=RELENG_6_1 in the supfile and these changes are not pulled under that tag. How does one approach that, set the tag to RELENG_6 which does grab these. From the handbook it seems to recommend not moving forward from a RELEASE for a production type of implementation. How does one grab specific changes to a driver without actually cvsupping to that entire revision or am I missing something really basic and I should be using the RELENG_6 tag for my production servers? It really looks like that's the version of the bge driver I should be using. Thanks for all this input, it's pretty embarrassing to idle such a cool server for 6 months ;-), Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and Jumbo Frames
On Mar 13, 2006, at 2:57 PM, Sean Murphy wrote: How do I set Jumbo Frames on a Gigabit NIC in FreeBSD? ifconfig _device_ mtu 8192 ...where you would use em0, bge0, or whatever the actual interface device is. See the manpages for the various devices, for example man em: Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility con- figures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. ...which usually will discuss the MTU sizes the specific devices can handle. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and Jumbo Frames
Charles Swiger wrote: On Mar 13, 2006, at 2:57 PM, Sean Murphy wrote: How do I set Jumbo Frames on a Gigabit NIC in FreeBSD? ifconfig _device_ mtu 8192 ...where you would use em0, bge0, or whatever the actual interface device is. See the manpages for the various devices, for example man em: Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility con- figures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. ...which usually will discuss the MTU sizes the specific devices can handle. ---Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What do I need to add to the rc.conf config line so that it sets up the mtu for jumbo 16128 bytes size and sets the speed from auto to 1000? I have this so far... ifconfig_em0=inet x.x.x.x netmask x.x.x.x 1000baseTX ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and Jumbo Frames
Sean Murphy writes: What do I need to add to the rc.conf config line so that it sets up the mtu for jumbo 16128 bytes size and sets the speed from auto to 1000? I have this so far... ifconfig_em0=inet x.x.x.x netmask x.x.x.x 1000baseTX You can't: 16114 is the maximum frame size. As for the rest, try: ifconfig_em0=inet x.x.x.x netmask x.x.x.x media 1000baseTX mtu 16114 Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and Jumbo Frames
On Mar 13, 2006, at 5:02 PM, Sean Murphy wrote: What do I need to add to the rc.conf config line so that it sets up the mtu for jumbo 16128 bytes size and sets the speed from auto to 1000? I have this so far... ifconfig_em0=inet x.x.x.x netmask x.x.x.x 1000baseTX Something like: ifconfig_em0=inet x.x.x.x netmask x.x.x.x 1000baseTX mtu 16128 ...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC ON FREEBSD 6.0
HOW DO I MAKE MY GIRLFRIEND GIVE ME MORE TIME TO BE AT THE COMPUTER? THX DANIEL A. A. LDRADA[AT]GMAIL.COM On 1/24/06, michael paquette [EMAIL PROTECTED] wrote: HOW DO i GET MY NIC CARD TO WORK ON MY LAPTOP USING FREEBSD ? THX MICHAEL PAQUETTE [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC ON FREEBSD 6.0
michael paquette wrote: HOW DO i GET MY NIC CARD TO WORK ON MY LAPTOP USING FREEBSD ? Why don't you tell us what the NIC actually is? And please STOP SHOUTING. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC ON FREEBSD 6.0
Alex Zbyslaw wrote: michael paquette wrote: HOW DO i GET MY NIC CARD TO WORK ON MY LAPTOP USING FREEBSD ? Why don't you tell us what the NIC actually is? And please STOP SHOUTING. And consider http://www.freebsd.org and the documentation listed there. Tom Veldhouse ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC
Vitalie Apostu [EMAIL PROTECTED] wrote: When I unplug UTP cable from NIC card and plug it back the system cannot ping any host in network. Does anybody know how to fix it? Did you try ifconfig $nic_device up? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: NIC
Please don't top post and don't forget to CC [EMAIL PROTECTED] Vitalie Apostu [EMAIL PROTECTED] wrote: It will work if I do ifconfig up or restart. Why do not do automatically? -Original Message- From: Fabian Keil [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 7:29 AM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: NIC Vitalie Apostu [EMAIL PROTECTED] wrote: When I unplug UTP cable from NIC card and plug it back the system cannot ping any host in network. Does anybody know how to fix it? Did you try ifconfig $nic_device up? I guess it would violate POLA, I for one wouldn't expect the NIC to get up by itself. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: NIC
Fabian Keil wrote: -Original Message- From: Fabian Keil [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 7:29 AM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: NIC Vitalie Apostu [EMAIL PROTECTED] wrote: When I unplug UTP cable from NIC card and plug it back the system cannot ping any host in network. Does anybody know how to fix it? Did you try ifconfig $nic_device up? I guess it would violate POLA, I for one wouldn't expect the NIC to get up by itself. If cable is pulled and plugged back in when the machine is already up, I would be astonished if it didn't just come back. In fact, I just tried it to be sure, and everything just worked. Vitalie, perhaps some info about the kind of NIC you have might help. Also can you show ifconfig 1) before you pull the cable 2) after you pull the cable 3) after you plug the cable back in At least then we could compare what happens for you with what happens for me. For reference, I see: Before: sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.1.2 netmask 0xff00 broadcast 192.168.1.255 ether 00:11:d8:94:74:49 media: Ethernet autoselect (1000baseTX full-duplex,flag0,flag1) status: active Pulled: sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.1.2 netmask 0xff00 broadcast 192.168.1.255 ether 00:11:d8:94:74:49 media: Ethernet autoselect (none) status: no carrier Back in: sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.1.2 netmask 0xff00 broadcast 192.168.1.255 ether 00:11:d8:94:74:49 media: Ethernet autoselect (1000baseTX full-duplex,flag0,flag1) status: active --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC bonding/teaming
On 13 Jan 2006, at 20:22, jim feldman wrote: Does 6.x have a nic bonding/teaming/failover feature like the linux bond (rnd robin, failover, ld bal, trunking)? I'm thinking multiple nics, one server, same lan/vlan. I've read up on CARP and one2many, but they don't seem to do what bond does. I think you want ng_one2many(4). Ceri PGP.sig Description: This is a digitally signed message part
Re: NIC bonding/teaming
At 16:47 2006-01-13, Ceri Davies wrote: On 13 Jan 2006, at 20:22, jim feldman wrote: Does 6.x have a nic bonding/teaming/failover feature like the linux bond (rnd robin, failover, ld bal, trunking)? I'm thinking multiple nics, one server, same lan/vlan. I've read up on CARP and one2many, but they don't seem to do what bond does. I think you want ng_one2many(4). Ceri Hi, I did a lot of tests with carp (was not appropriate at all), and ng_one2many I was able to make two nics appears at one with ng_one2many, but after severals days of tests and research, dropped it because it caused bad side effects and when I was pulling one nic out, it was stopping to transmit/receive for some moment. Also on the switch, both nics were registering the same mac address so my cisco was sending me warning about it every minute. If you find a way to make it work that works perfectly, let me know, I think a lot of people will benefit from it cause there is a bunch of people asking for nic teaming and no real solution... personnally, I ended up doing the redundancy at layer 3 instead of layer 2. I used quagga (or zebra) and put one nic in a separate subnet. I then used ospf to share routes. basically, my website is on an ip I binded to my loopback adapter and there is two gateways (both nics) to the rest of the network. It's not a solution I'm proud of because I wish I would have succeed to team the nic like I could have done on windows or linux, but I didn't find a working solution... Good luck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC bonding/teaming
In the last episode (Jan 13), Ian Lord said: At 16:47 2006-01-13, Ceri Davies wrote: On 13 Jan 2006, at 20:22, jim feldman wrote: Does 6.x have a nic bonding/teaming/failover feature like the linux bond (rnd robin, failover, ld bal, trunking)? I'm thinking multiple nics, one server, same lan/vlan. I've read up on CARP and one2many, but they don't seem to do what bond does. I think you want ng_one2many(4). I did a lot of tests with carp (was not appropriate at all), and ng_one2many I was able to make two nics appears at one with ng_one2many, but after severals days of tests and research, dropped it because it caused bad side effects and when I was pulling one nic out, it was stopping to transmit/receive for some moment. Also on the switch, both nics were registering the same mac address so my cisco was sending me warning about it every minute. That's because you forgot to configure your cisco and tell it those two ports were trunked together :) Another alternative to ng_one2many is ng_fec, which despite its name does not actually negotiate the FEC protocol with the remote end (you have to hardcode it on the switch), but does do mac/ip port hashing. That prevents packet reordering within flows. Patches to add LACP negotiation (FEC is obsolete) are welcome though :) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC bonding/teaming
At 17:14 2006-01-13, Dan Nelson wrote: In the last episode (Jan 13), Ian Lord said: At 16:47 2006-01-13, Ceri Davies wrote: On 13 Jan 2006, at 20:22, jim feldman wrote: Does 6.x have a nic bonding/teaming/failover feature like the linux bond (rnd robin, failover, ld bal, trunking)? I'm thinking multiple nics, one server, same lan/vlan. I've read up on CARP and one2many, but they don't seem to do what bond does. I think you want ng_one2many(4). I did a lot of tests with carp (was not appropriate at all), and ng_one2many I was able to make two nics appears at one with ng_one2many, but after severals days of tests and research, dropped it because it caused bad side effects and when I was pulling one nic out, it was stopping to transmit/receive for some moment. Also on the switch, both nics were registering the same mac address so my cisco was sending me warning about it every minute. That's because you forgot to configure your cisco and tell it those two ports were trunked together :) Another alternative to ng_one2many is ng_fec, which despite its name does not actually negotiate the FEC protocol with the remote end (you have to hardcode it on the switch), but does do mac/ip port hashing. That prevents packet reordering within flows. Patches to add LACP negotiation (FEC is obsolete) are welcome though :) Oups :) Forgot to mention I was looking for switch redundancy also... So each nics were plugged into 2 separate switches so I was not able to configure the switch as trunk or etherchannel... On windows, I am able to team the nics on two different switches without problem with the hp or Intel teaming software, I guess only one nic works at the same time and register it's mac address in the switch tcam... For the original question, it should work with ng_one2Many :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC suggestion
On Wednesday 06 July 2005 11:32, Casey Scott wrote: I am experiencing the same rebooting under network stress that others on this list have reported. The box is using 3com 905b's, and I would like to try another NIC in the box to make sure that this isn't just a driver issue, though I strongly suspect it isn't. Can someone suggest a common 100 MB NIC that has proven to be very stable in 5.x? Intel EtherExpress PROs (fxp driver) are pretty much universally respected. -- Kirk Strauser pgpqqrK224JAC.pgp Description: PGP signature
Re: NIC suggestion
On Jul 6, 2005, at 12:32 PM, Casey Scott wrote: I am experiencing the same rebooting under network stress that others on this list have reported. The box is using 3com 905b's, and I would like to try another NIC in the box to make sure that this isn't just a driver issue, though I strongly suspect it isn't. Can someone suggest a common 100 MB NIC that has proven to be very stable in 5.x? The two that come to mind are the DEC 21x4x Tulip (dc) and the Intel 8255x (fxp). -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NIC suggestion
I would like to inquire about what FreeBSD version are you running? Did you do a fresh install of 5.4 to a empty disk or did you do the build world process? Build world means you are running the old file system. Fresh install means you are running the new file system. During the development and integrating of the new file system into 5.x there where a lot of reports of system hangs and auto rebooting when the system was under heavy load. A nic was never considered as the problem then so maybe your nic is not the problem now. Maybe the new file system heavy load problem is not completely fixed yet. If I remember correctly it was never determined if the heavy load problem was caused by old file system using new file system code or new file system using new code and just not performing under heavy load. Just my thoughts about your problem from a different prospective. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Casey Scott Sent: Wednesday, July 06, 2005 12:33 PM To: freebsd-questions@freebsd.org Subject: NIC suggestion I am experiencing the same rebooting under network stress that others on this list have reported. The box is using 3com 905b's, and I would like to try another NIC in the box to make sure that this isn't just a driver issue, though I strongly suspect it isn't. Can someone suggest a common 100 MB NIC that has proven to be very stable in 5.x? Casey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC suggestion
On Wednesday 06 July 2005 11:32, Casey Scott wrote: I am experiencing the same rebooting under network stress that others on this list have reported. The box is using 3com 905b's, and I would like to try another NIC in the box to make sure that this isn't just a driver issue, though I strongly suspect it isn't. Can someone suggest a common 100 MB NIC that has proven to be very stable in 5.x? Intel EtherExpress PROs (fxp driver) are pretty much universally respected. Kirk Strauser We have had good experiences with the Intel based (fxp) NICs at 10, 100 and 1000 Mb. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC suggestion
On Jul 6, 2005, at 10:32 AM, Casey Scott wrote: I am experiencing the same rebooting under network stress that others on this list have reported. The box is using 3com 905b's, and I would like to try another NIC in the box to make sure that this isn't just a driver issue, though I strongly suspect it isn't. Can someone suggest a common 100 MB NIC that has proven to be very stable in 5.x? I use some dc driver based ones, though they are hard to find now and they work really well as well as some em based ones. Don't remember off hand the model number though Chad Casey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY
On Mon, 21 Mar 2005 20:20:26 -0800 (PST), stheg olloydson [EMAIL PROTECTED] wrote: it was said: How install in FreeBSD NIC card nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY ? Hello, If you are using 5.3, try the nv driver in ports/net/. After building it, load it as a kernel module. I know it works for MCP2. This may be available in earlier versions, too; I do not know. good luck, stheg So does this mean i can use my NIC on my asus sk8n (nforce 3 chip) too ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
On Mar 21, 2005, at 9:31 PM, Kevin Kinsey wrote: *If I'm wrong, it's Chuck's fault, heh heh ?! It's always my fault, even when it's not my fault. (I must have done something. What did I do, again? :-) -- -Chuck guilty! Swiger PS: Kevin's suggestion is not a bad idea, either that or submitting the pciconf data as a PR, so it doesn't get lost ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY
On Tue, 22 Mar 2005 17:46:15 +0100, Rafal Swiderski [EMAIL PROTECTED] wrote: How install in FreeBSD NIC card nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY ? Hello, If you are using 5.3, try the nv driver in ports/net/. After building it, load it as a kernel module. I know it works for MCP2. This may be available in earlier versions, too; I do not know. good luck, stheg So does this mean i can use my NIC on my asus sk8n (nforce 3 chip) too ? Yes, my motherboard is asus a7n8x-x (nForce2) and my NIC card work corretly after i installed driver nv Alrighdy :) The kldload if_nv.ko works when i do ifconfig and plug in the network cable i see nv0 going from inacative to active :) But when i edit boot/load.conf and rc.conf my sk8n amd64 keeps on rebooting just right before showing me the bsd boot menu ? I guess this means i need to use a boot cd to fix this ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Charles Swiger wrote: On Mar 21, 2005, at 9:31 PM, Kevin Kinsey wrote: *If I'm wrong, it's Chuck's fault, heh heh ?! It's always my fault, even when it's not my fault. (I must have done something. What did I do, again? :-) I can take the pressure off of you Chuck. Call 1-900-BLAME-ME. Fifty cents per minute to hear sincere apologies and promises to do better. Groveling at additional expense. ;) Robert P.S. please do not call the above number as I have no idea if it works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Andrew Robinson wrote: Hello FreeBSD community, I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. (I also tried the February Stable, with no change as far as I can tell). WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. My FreeBSD kernel is generic, and both the following lines are uncommented: device miibus # MII bus support device re # RealTek 8139C+/8169/8169S/8110S The output from ifconfig is: fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 02:90:f5:40:24:d8 ch 1 dma -1 plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 and what I think is the relevant part of dmesg is: firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 fwe0: Ethernet address: 02:90:f5:40:24:d8 fwe0: if_start running deferred for Giant It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Thanks much! It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. -- Cheers, Kevin. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi, Andrew-- On Mar 21, 2005, at 1:54 PM, Andrew Robinson wrote: It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Take a look at the output of pciconf -v -l. The odds are that it lists a PCI ID for your NIC that the FreeBSD driver doesn't know about. Use that information to update /usr/src/sys/pci/if_rlreg.h and /usr/src/sys/dev/re/if_re.c, and see whether that gets you a working driver. If you're not sure how to do this, post the pciconf info for just your NIC so that others can try to update the code and get you a working driver... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2005-03-21, Kevin G. Eliuk scribbled these curious markings: It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. Perhaps a better idea, which doesn't depend upon X, would be to use pciconf, which is in the base system. pciconf -lv (run as root) should give the details about the card. Best Regards, Christopher Nehren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCPx0Zk/lo7zvzJioRAvatAJ9QGm6Hm3TAbOGb3pA11b1ujrbPLwCgoFNI krajXADlcfMUT2oFp37AqqQ= =6tuC -END PGP SIGNATURE- -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi Kevin, It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. Here it is: ### pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x2580 Intel Corp. Device unknown pci bus 0x cardnum 0x01 function 0x00: vendor 0x8086 device 0x2581 Intel Corp. Device unknown pci bus 0x cardnum 0x1b function 0x00: vendor 0x8086 device 0x2668 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x2658 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x2659 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x265a Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x03: vendor 0x8086 device 0x265b Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x07: vendor 0x8086 device 0x265c Intel Corp. Device unknown pci bus 0x cardnum 0x1e function 0x00: vendor 0x8086 device 0x244e Intel Corp. 82801BA/CA/DB/EB PCI Bridge pci bus 0x cardnum 0x1f function 0x00: vendor 0x8086 device 0x2640 Intel Corp. Device unknown pci bus 0x cardnum 0x1f function 0x01: vendor 0x8086 device 0x266f Intel Corp. Device unknown pci bus 0x cardnum 0x1f function 0x03: vendor 0x8086 device 0x266a Intel Corp. Device unknown pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x10de device 0x00c8 nVidia Corporation Device unknown pci bus 0x000a cardnum 0x00 function 0x00: vendor 0x104c device 0xac50 Texas Instruments PCI1410 PC card Cardbus Controller pci bus 0x000a cardnum 0x01 function 0x00: vendor 0x104c device 0x8023 Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) pci bus 0x000a cardnum 0x02 function 0x00: vendor 0x105a device 0x3373 Promise Technology, Inc. Device unknown pci bus 0x000a cardnum 0x03 function 0x00: vendor 0x10ec device 0x8169 Realtek Semiconductor Co., Ltd. RTL-8169 pci bus 0x000a cardnum 0x05 function 0x00: vendor 0x1814 device 0x0201 Device unknown I would appreciate any thoughts - thanks! Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi Chuck, Thanks for the suggestion - that's beyond my exerptise, but here is the (hopefully relevant) output of pciconf ### [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:5:0: class=0x028000 card=0x68331462 chip=0x02011814 rev=0x01 hdr=0x00 vendor = 'Ralink Technology Corp' class= network ### I would appreciate any further advice or assistance, Andrew - Original Message - From: Charles Swiger [EMAIL PROTECTED] Date: Monday, March 21, 2005 11:12 am Subject: Re: NIC won't DHCP or configure Hi, Andrew-- On Mar 21, 2005, at 1:54 PM, Andrew Robinson wrote: It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Take a look at the output of pciconf -v -l. The odds are that it lists a PCI ID for your NIC that the FreeBSD driver doesn't know about. Use that information to update /usr/src/sys/pci/if_rlreg.h and /usr/src/sys/dev/re/if_re.c, and see whether that gets you a working driver. If you're not sure how to do this, post the pciconf info for just your NIC so that others can try to update the code and get you a working driver... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Andrew Robinson wrote: Hi Chuck, Thanks for the suggestion - that's beyond my exerptise, but here is the (hopefully relevant) output of pciconf ### [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:5:0: class=0x028000 card=0x68331462 chip=0x02011814 rev=0x01 hdr=0x00 vendor = 'Ralink Technology Corp' class= network ### I would appreciate any further advice or assistance, Andrew Hi, Andrew! Normally I wouldn't suggest this, but I'm thinking in this case you should trim all the really relevant bits of this conversation into one well-edited email with a proper introduction and send it over to [EMAIL PROTECTED], unless someone pipes up and helps you with this Real Soon Now(tm). I'm thinking that it would be fairly trivial*, and most of those fellas would love to have FreeBSD support another 1000Mbps NIC Kevin Kinsey *If I'm wrong, it's Chuck's fault, heh heh ?! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY
it was said: How install in FreeBSD NIC card nVidia nForce MCP Network Adapter based on Realtek 8201BL PHY ? Hello, If you are using 5.3, try the nv driver in ports/net/. After building it, load it as a kernel module. I know it works for MCP2. This may be available in earlier versions, too; I do not know. good luck, stheg __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
On Mon, 21 Mar 2005 10:54:24 -0800, Andrew Robinson [EMAIL PROTECTED] wrote: Hello FreeBSD community, I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. (I also tried the February Stable, with no change as far as I can tell). WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. My FreeBSD kernel is generic, and both the following lines are uncommented: device miibus # MII bus support device re # RealTek 8139C+/8169/8169S/8110S The output from ifconfig is: fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 02:90:f5:40:24:d8 ch 1 dma -1 plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 and what I think is the relevant part of dmesg is: firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 fwe0: Ethernet address: 02:90:f5:40:24:d8 fwe0: if_start running deferred for Giant It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Thanks much! Andrew My advice, try a different network switch / hub. Read on to find out why. Trying to do the poor man's Norton Ghost at a local school for a WinXP lab (using dd over ssh), I had some stupid issues. The NIC in question was an onboard SiS 900. Here's what I had using various live-cd distros: winxp (installed) - i got an IP address knoppix and DSL (both debian) - I got an IP address System Rescue CD (gentoo) - no address g4u and obsd live cd (obsd) - no address (never did try fbsd, but obsd is fairly close) When I moved a sample PC closer to the DHCP server, every distro above got an address. The lab has an older d-link 24 port switch. There are 4 switches total between the lab and the dhcp server. When I moved the PC, it was then connected to a netgear 5-port 100mb switch, still about 4 switches away from the dhcp server. I tried setting an address with ifconfig for each of the failing distros, with no success. I vaguely remember getting some weird issues reagarding the PHY in obsd... I have no idea what the cause is (just discovered this last week), but am strongly suspicious of the d-link switch. I'm going to replace it (assuming funds are available) soon. Just thought I'd pass it on, in case it helps. GS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NIC failover
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Khavkine Sent: Friday, January 14, 2005 12:09 PM To: freebsd-questions@freebsd.org Subject: NIC failover Hi Folks. Is there a way to configure 2 NIC's in a failover fasion connected to 2 different switches with FreeBSD 5.3R ? Thanx Paul Paul Khavkine Networks/Systems Planning and Engineering DISTRIBUTEL Communications. 740 Notre Dame West, Suite 1135 Montreal, Quebec, Canada, H3C 3X6 +1-514-877-5505 x 263 http://www.distributel.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You could set up a script to check the connection of nic0, and if no connection, ifconfig nic1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nic aggregation/teaming (AFT or similar)
J Hi all, J I want to find out if there is any support for NIC teaming (AFT) in J FreeBSD. I found this post from 2000 J http://groups.google.ca/groups?hl=enlr=threadm=8c72ap%24le4%241%40nnrp1.deja.comrnum=1prev=/groups%3Fq%3D%2522FreeBSD%2520does%2520NOT%2520support%2520Cabletron%27s%2520SmartTrunking%2522%26hl%3Den%26lr%3D%26sa%3DN%26tab%3Dwg J Has there been any developments with this? We are using AFT with dual J intel nics for switch redundancy on Linux boxes. I really want to try J and move to FreeBSD, and this is the only major issue that I can see. J Any information is greatly appreciated, J -Jev J P.S. I'm not subscribed to questions, so please CC any replies. J ___ J freebsd-questions@freebsd.org mailing list J http://lists.freebsd.org/mailman/listinfo/freebsd-questions J To unsubscribe, send any mail to [EMAIL PROTECTED] - Have a look at netgraph http://www.freebsd.org/cgi/man.cgi?query=netgraphsektion=4apropos=0manpath=FreeBSD+5.3-RELEASE+and+Ports I am not really shure if this is what you are looking for but maybe :) Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nic aggregation/teaming (AFT or similar)
Has there been any developments with this? We are using AFT with dual intel nics for switch redundancy on Linux boxes. I really want to try and move to FreeBSD, and this is the only major issue that I can see. if you're looking for single-path redundancy and not increased throughput, you could use CARP (patches are here: http://people.freebsd.org/~mlaier/CARP/). the patches apply cleanly to 5.x, and seem to work just fine. if you need more information, check the list archives. good luck! joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and RPM of a hard disk
Ajesh John wrote: Hi, How can I know if there is an in-built NIC in my mother-board? And How can I know the RPM of my hard disk?, Is it possible to know both these in FreeBSD?, I'm using FreeBSD5.1 - Release, For the NIC, ifconfig will show all the network devices installed on a machine but if you want to confirm if it's onboard.. look at the back of the machine, often above the usb ports. As for the hard drive the only way to find the rpm is to grab the model number and look it up :) - Mike Woods IT Technician ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC and RPM of a hard disk
Mike Woods wrote: Ajesh John wrote: Hi, How can I know if there is an in-built NIC in my mother-board? And How can I know the RPM of my hard disk?, Is it possible to know both these in FreeBSD?, I'm using FreeBSD5.1 - Release, For the NIC, ifconfig will show all the network devices installed on a machine but if you want to confirm if it's onboard.. look at the back of the machine, often above the usb ports. As for the hard drive the only way to find the rpm is to grab the model number and look it up :) Type in dmesg at the console, use scroll lock and the up/down keys to move around. somewhere around the end of it it will display something such as ad0: 38154MB TOSHIBA MK4025GAS [77520/16/63] ata0-master BIOSPIO. Common Drive speeds (in newer computers): EIDE(ATA): 7200, 5400 SATA: 7200, 1 SCSI: 1, 15000 laptop: 4200, 5400 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC problem
Heya Andy Right under the line for rl0 I see this: options=8VLAN_MTU IT only specifies that it uses a VLAN_MTU, which limit's the size of the packet's being transmitted. It does not tell you that you actually use a VLAN thingy. How can I recreate the rl0 interface without the VLAN option? I think it's default (someone correct me if i am wrong), since i have it also. I could really use some help on this one! Any advice is appreciated! HTH, -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl A Dutch community for helping newcomers on the hackerscene ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC question...
device pcn # AMD Am79C79x PCI 10/100 NICs In the new DNS server I'm building, is the following ifconfig line correct for the first AMD NIC: ifconfig_pcn0=inet 216.231.43.140 netmask 255.255.255.0 Yes, that looks good (if the ip address and the netmask are correct ;-) Be sure to either recompile your kernel with the following options device miibus device pcn or to load the module version of the driver: if_pcn.ko For more options of that NIC driver, you can have a look at its man page: pcn(4). Simon signature.asc Description: Digital signature
Re: NIC question...
On Sun, Apr 04, 2004 at 10:17:36PM +0200, Simon Barner wrote: device pcn # AMD Am79C79x PCI 10/100 NICs In the new DNS server I'm building, is the following ifconfig line correct for the first AMD NIC: ifconfig_pcn0=inet 216.231.43.140 netmask 255.255.255.0 Yes, that looks good (if the ip address and the netmask are correct ;-) Be sure to either recompile your kernel with the following options device miibus device pcn or to load the module version of the driver: if_pcn.ko For more options of that NIC driver, you can have a look at its man page: pcn(4). Thanks very much. I just found the GENERIC kernel file; yup, both devices are in by default. (It makes sense to me at least to have just about every dev in by default. If somebody wanted less functionality, trimming back could be a fine-tune option. gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC card not showing up during 5.1 install
[Format recovered--see http://www.lemis.com/email/email-format.html] Overlong lines. On Wednesday, 24 September 2003 at 18:45:47 +1000, Anthony Carmody wrote: i am building a new server for a client and my hardware vendor changed my usual hardware profile to use an 800fsb ASUS Mainboard, it runs the Intel 865G chipset. I have tried installing 5.1 but it cannot see to onboard Ethernet and seems to get upset running the mouse when the XF86 server starts up for some reason. i have 2 bootable installer discs for 5.1 made from ISO images some months ago. I had a look at the current HARDWARE.TXT in the first disc and the network card is supported so it says Intel 82562-based Fast Ethernet NICs when i get the prompt during installation to configure network connections i only get a sellection of four serial connections PPP SLIP etc. I remember being given a choice of one NIC as well so, does this mean it might be there somewhere? when i run a 'netstat -i' i cant see anything that looks like a NIC. Just serial ports etc. I assume this is only running interfaces, correct? what should i be looking for? Do a minimal install, then run # pciconf -vl The output looks something like (showing NICs only): [EMAIL PROTECTED]:12:0: class=0x02 card=0x032010bd chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:18:0: class=0x02 card=0x764c1462 chip=0x30651106 rev=0x74 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6102 Rhine II PCI Fast Ethernet Controller' class= network subclass = ethernet Show us what you see there. If you can identify the NIC in the output, you don't need to show the rest. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
RE: NIC card not showing up during 5.1 install [asus p4p800 MB]
OK, this is what i get: [NIC entry, not the rest] [EMAIL PROTECTED]:8:0: class=0x202 card=0x80f81043 chip=0x10508086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass= ethernet I minimal install from 5.1 made from the ISO images from the FTP site. as in a basic install using the /stand/sysinstall blah blah. i'm not very good with installs as i have never really had much trouble before. should i make a CD from some 'CURRENT' version? all my hardware should be supported according to the HAREWARE.txt in the CD image i have for 5.1. [sorry about the email format. im using my thinkpad plagued by M$] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Greg 'groggy' Lehey Sent: Wednesday, 24 September 2003 6:53 PM To: Anthony Carmody Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: NIC card not showing up during 5.1 install [Format recovered--see http://www.lemis.com/email/email-format.html] Overlong lines. On Wednesday, 24 September 2003 at 18:45:47 +1000, Anthony Carmody wrote: i am building a new server for a client and my hardware vendor changed my usual hardware profile to use an 800fsb ASUS Mainboard, it runs the Intel 865G chipset. I have tried installing 5.1 but it cannot see to onboard Ethernet and seems to get upset running the mouse when the XF86 server starts up for some reason. i have 2 bootable installer discs for 5.1 made from ISO images some months ago. I had a look at the current HARDWARE.TXT in the first disc and the network card is supported so it says Intel 82562-based Fast Ethernet NICs when i get the prompt during installation to configure network connections i only get a sellection of four serial connections PPP SLIP etc. I remember being given a choice of one NIC as well so, does this mean it might be there somewhere? when i run a 'netstat -i' i cant see anything that looks like a NIC. Just serial ports etc. I assume this is only running interfaces, correct? what should i be looking for? Do a minimal install, then run # pciconf -vl The output looks something like (showing NICs only): [EMAIL PROTECTED]:12:0: class=0x02 card=0x032010bd chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:18:0: class=0x02 card=0x764c1462 chip=0x30651106 rev=0x74 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6102 Rhine II PCI Fast Ethernet Controller' class= network subclass = ethernet Show us what you see there. If you can identify the NIC in the output, you don't need to show the rest. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC numbering
On Mon, Feb 17, 2003 at 02:08:19PM +0100, Cliff Sarginson wrote: On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? Here's an example. The original setup: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier After the cards are switched around in the PCI slots: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier How can I keep rl0 associated with MAC 00:e0:29:85:49:b6 and rl1 associated with MAC 00:e0:29:85:49:d0 and still be able to add cards or move them around? TIA, Terry Todd To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
On Tue, Feb 18, 2003 at 11:02:30AM -0600, Terry Todd wrote: On Mon, Feb 17, 2003 at 02:08:19PM +0100, Cliff Sarginson wrote: On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? Here's an example. The original setup: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier After the cards are switched around in the PCI slots: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier How can I keep rl0 associated with MAC 00:e0:29:85:49:b6 and rl1 associated with MAC 00:e0:29:85:49:d0 and still be able to add cards or move them around? About the best you can do is use ifconfig(8) to set the MAC address at the same time as you configure the interface: ifconfig rl0 ether 00:e0:29:85:49:b6 ifconfig rl1 ether 00:e0:29:85:49:d0 which will cause the MAC address to stick with the interface number, rather than the actual card. That will work if you just keep the two cards as you've shown here, but if you add a new card that happens to end up as rl0 then you'll probably end up with a mess. As far as I know, there's no way of wiring down interface numbers to PCI bus slots, analogously to the way you can wire down SCSI devices by bus, target and LUN --- see the section on 'SCSI DEVICE CONFIGURATION' in LINT. You'ld probably have to go a bit linux-ish and have, say, eth0 as the generic name for an ethernet interface independant of the actual chipset on the NIC in order to make the most sense of that sort of wiring-down idea. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
In article local.mail.freebsd-questions/[EMAIL PROTECTED] you write: On Tue, Feb 18, 2003 at 11:52:22AM -0600, Jonathan Lemon wrote: In article local.mail.freebsd-questions/[EMAIL PROTECTED] you write: On Tue, Feb 18, 2003 at 11:02:30AM -0600, Terry Todd wrote: On Mon, Feb 17, 2003 at 02:08:19PM +0100, Cliff Sarginson wrote: On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? Here's an example. The original setup: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier After the cards are switched around in the PCI slots: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier How can I keep rl0 associated with MAC 00:e0:29:85:49:b6 and rl1 associated with MAC 00:e0:29:85:49:d0 and still be able to add cards or move them around? About the best you can do is use ifconfig(8) to set the MAC address at the same time as you configure the interface: ifconfig rl0 ether 00:e0:29:85:49:b6 ifconfig rl1 ether 00:e0:29:85:49:d0 which will cause the MAC address to stick with the interface number, rather than the actual card. That will work if you just keep the two cards as you've shown here, but if you add a new card that happens to end up as rl0 then you'll probably end up with a mess. As far as I know, there's no way of wiring down interface numbers to PCI bus slots, analogously to the way you can wire down SCSI devices by bus, target and LUN --- see the section on 'SCSI DEVICE CONFIGURATION' in LINT. You'ld probably have to go a bit linux-ish and have, say, eth0 as the generic name for an ethernet interface independant of the actual chipset on the NIC in order to make the most sense of that sort of wiring-down idea. Actually, this capability has been in 5.0 for a long time, but I don't think that it was ever MFC'd to 4.x. There are network aliases for the actual physical devices, which appear as /dev/netN, where N is the index number used. These can be wired either by name or ether number at boot time: Allow wiring of net aliases in /boot/device.hints of the form: hint.net.1.dev=lo0 or hint.net.12.ether=00:a0:c9:c9:9d:63 So for the original poster, you could do (in 5.0): hint.net.1.ether=00:e0:29:85:49:b6 hint.net.2.ether=00:e0:29:85:49:d0 ifconfig net1 rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier ifconfig net2 rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier And the 'net1','net2' aliases will remain bound to whichever driver has those actual ethernet addresses, regardless of PCI ordering. -- Jonathan Thanks. That works for after the system is booted up and running. I tried adding ifconfig_net1/2 lines to rc.conf and it didn't work. ifconfig_net1=inet 10.0.0.3 netmask 255.0.0.0 You'll need to manually specify the interface list, the default is to configure only the physical interfaces, not any aliases: network_interfaces=lo0 net1 net2 -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
In article local.mail.freebsd-questions/[EMAIL PROTECTED] you write: On Tue, Feb 18, 2003 at 11:02:30AM -0600, Terry Todd wrote: On Mon, Feb 17, 2003 at 02:08:19PM +0100, Cliff Sarginson wrote: On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? Here's an example. The original setup: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier After the cards are switched around in the PCI slots: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier How can I keep rl0 associated with MAC 00:e0:29:85:49:b6 and rl1 associated with MAC 00:e0:29:85:49:d0 and still be able to add cards or move them around? About the best you can do is use ifconfig(8) to set the MAC address at the same time as you configure the interface: ifconfig rl0 ether 00:e0:29:85:49:b6 ifconfig rl1 ether 00:e0:29:85:49:d0 which will cause the MAC address to stick with the interface number, rather than the actual card. That will work if you just keep the two cards as you've shown here, but if you add a new card that happens to end up as rl0 then you'll probably end up with a mess. As far as I know, there's no way of wiring down interface numbers to PCI bus slots, analogously to the way you can wire down SCSI devices by bus, target and LUN --- see the section on 'SCSI DEVICE CONFIGURATION' in LINT. You'ld probably have to go a bit linux-ish and have, say, eth0 as the generic name for an ethernet interface independant of the actual chipset on the NIC in order to make the most sense of that sort of wiring-down idea. Actually, this capability has been in 5.0 for a long time, but I don't think that it was ever MFC'd to 4.x. There are network aliases for the actual physical devices, which appear as /dev/netN, where N is the index number used. These can be wired either by name or ether number at boot time: Allow wiring of net aliases in /boot/device.hints of the form: hint.net.1.dev=lo0 or hint.net.12.ether=00:a0:c9:c9:9d:63 So for the original poster, you could do (in 5.0): hint.net.1.ether=00:e0:29:85:49:b6 hint.net.2.ether=00:e0:29:85:49:d0 ifconfig net1 rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier ifconfig net2 rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier And the 'net1','net2' aliases will remain bound to whichever driver has those actual ethernet addresses, regardless of PCI ordering. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
On Tue, Feb 18, 2003 at 11:52:22AM -0600, Jonathan Lemon wrote: In article local.mail.freebsd-questions/[EMAIL PROTECTED] you write: On Tue, Feb 18, 2003 at 11:02:30AM -0600, Terry Todd wrote: On Mon, Feb 17, 2003 at 02:08:19PM +0100, Cliff Sarginson wrote: On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? Here's an example. The original setup: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier After the cards are switched around in the PCI slots: $ ifconfig -a rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier How can I keep rl0 associated with MAC 00:e0:29:85:49:b6 and rl1 associated with MAC 00:e0:29:85:49:d0 and still be able to add cards or move them around? About the best you can do is use ifconfig(8) to set the MAC address at the same time as you configure the interface: ifconfig rl0 ether 00:e0:29:85:49:b6 ifconfig rl1 ether 00:e0:29:85:49:d0 which will cause the MAC address to stick with the interface number, rather than the actual card. That will work if you just keep the two cards as you've shown here, but if you add a new card that happens to end up as rl0 then you'll probably end up with a mess. As far as I know, there's no way of wiring down interface numbers to PCI bus slots, analogously to the way you can wire down SCSI devices by bus, target and LUN --- see the section on 'SCSI DEVICE CONFIGURATION' in LINT. You'ld probably have to go a bit linux-ish and have, say, eth0 as the generic name for an ethernet interface independant of the actual chipset on the NIC in order to make the most sense of that sort of wiring-down idea. Actually, this capability has been in 5.0 for a long time, but I don't think that it was ever MFC'd to 4.x. There are network aliases for the actual physical devices, which appear as /dev/netN, where N is the index number used. These can be wired either by name or ether number at boot time: Allow wiring of net aliases in /boot/device.hints of the form: hint.net.1.dev=lo0 or hint.net.12.ether=00:a0:c9:c9:9d:63 So for the original poster, you could do (in 5.0): hint.net.1.ether=00:e0:29:85:49:b6 hint.net.2.ether=00:e0:29:85:49:d0 ifconfig net1 rl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:b6 media: Ethernet autoselect (10baseT/UTP) status: no carrier ifconfig net2 rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:e0:29:85:49:d0 media: Ethernet autoselect (10baseT/UTP) status: no carrier And the 'net1','net2' aliases will remain bound to whichever driver has those actual ethernet addresses, regardless of PCI ordering. -- Jonathan Thanks. That works for after the system is booted up and running. I tried adding ifconfig_net1/2 lines to rc.conf and it didn't work. ifconfig_net1=inet 10.0.0.3 netmask 255.0.0.0 Terry Todd To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? TIA, Terry Todd To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message I had the same problem with ATA drives on NetBSD. Maybe you could define the NICs statically in the kernel file... ( i don't remember if it is still possible fro PCI devices.) Hope it helps. Bye To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC numbering
On Mon, Feb 17, 2003 at 01:30:09PM +0100, Andrea Franceschini wrote: On Sat, Feb 15, 2003 at 08:28:35AM -0600, Terry Todd wrote: When you have more than one of the same type of NIC card in one machine is there a way to insure that the NIC numbering remains attached to the same card / MAC address if more cards are added or they are moved around? arp -s (or arp -S) may help. See man arp. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC problem?
Vincent Chen [EMAIL PROTECTED] writes: I have a DE-220 10M NIC connect to a server with realtek 8139 NIC using cross over cable. The transfer speed usually over 500K bytes. Recently, the server crashed and I have to connect this DE-220 NIC to another server with Intel 82559 NIC using the same cross over cable. After that, the transfer is terrible. Usually below 10K bytes.I see a lot of collision in 'netstat -in' command on intel side but nothing unusual on DE-220 side. Is there any thing I can do to solve this problem? You almost certainly have a duplex mismatch. Get the two sides to agree on the duplex setting, and they should run up close to wire speed. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC not found
On Sat, Sep 28, 2002 at 03:52:23AM -0700, Doug White wrote: On Sat, 28 Sep 2002, Bob Bomar wrote: On Fri, Sep 27, 2002 at 02:01:26PM -0700, Doug White wrote: pciconf -lv output? I cant get past the install, I cant select the NIC to use because it can not assign the resource. Is there a work around for this? Can you get the info from your 4.7RC install? (it may just be pciconf -l there.) I can't really do anything unless I can determine what the PCI IDs are that its looking for. Sorry, I miss understood. Here it is: fxp0@pci0:11:0: class=0x02 card=0x10308086 chip=0x10308086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82559 PCI Networking device' class= network subclass = ethernet -- /\ | Bob Bomar [EMAIL PROTECTED] http://www.bomar.us/~bob | || | FreeBSD: The Power to Serve. http://www.freeBSD.org | \/ msg03283/pgp0.pgp Description: PGP signature
Re: NIC not found
Sorry, I miss understood. Here it is: fxp0@pci0:11:0: class=0x02 card=0x10308086 chip=0x10308086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82559 PCI Networking device' class= network subclass = ethernet Since you've said it can not assign the resource your best bet is to disable 'PnP OS' in your BIOS and then restart the install. This was not necessary for me in 4.5 (disabling PnP) but was, on the same hardware, for 4.6.x. I have tried it both ways, enabled and disabled. -- /\ | Bob Bomar [EMAIL PROTECTED] http://www.bomar.us/~bob | || | FreeBSD: The Power to Serve. http://www.freeBSD.org | \/ msg03310/pgp0.pgp Description: PGP signature
Re: NIC problem
On Tue, Sep 17, 2002 at 11:55:03PM -0400, dfolkins wrote: here is a just in case: have you tried using different ports on the switch? or a different switch? Yes, I have. I found out that this card and another card in another box have the same MAC address. -- /\ | Bob Bomar [EMAIL PROTECTED] http://www.bomar.us/~bob | || | FreeBSD: The Power to Serve. http://www.freeBSD.org | \/ msg02046/pgp0.pgp Description: PGP signature
Re: NIC problem
At Wed, 18 Sep 2002 it looks like Bob Bomar composed: On Tue, Sep 17, 2002 at 11:55:03PM -0400, dfolkins wrote: here is a just in case: have you tried using different ports on the switch? or a different switch? Yes, I have. I found out that this card and another card in another box have the same MAC address. Hmm, that's interesting. Care to share the vendors of those cards? That's not something you normally see. I'd like to know as to guide me in future purchases of NIC cards, thanks. -- |72--| Bill Schoolcraft PO Box 210076 -o) San Francisco CA 94121 /\ UNIX, A Way Of Life._\_v http://forwardslashunix.com/raw To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC problem
On Tue, Sep 17, 2002 at 08:22:21PM -0400, Bob Bomar wrote: I have a dual P-200 file server that is haveing some connection problems. When I ssh to the box, I login in fine, but some times it lags for a while, but the two boxes are physically sitting next to each other, and are on ports that are side by side on the switch. While I ssh out of the box from the console, to another box on the LAN, it is still intermitant. Any body have any ideas? Long lags in ssh connections usually point to lack of PTR entries in for the connecting clients. -- Jonathan Chen [EMAIL PROTECTED] -- Opportunity does not knock, it presents itself when you beat down the door - W.E. Channing To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC problem
On Tue, 17 Sep 2002, Bob Bomar wrote: I have a dual P-200 file server that is haveing some connection problems. When I ssh to the box, I login in fine, but some times it lags for a while, but the two boxes are physically sitting next to each other, and are on ports that are side by side on the switch. While I ssh out of the box from the console, to another box on the LAN, it is still intermitant. Any body have any ideas? This is just a stab in the dark, but could it be DNS? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC problem
On Tue, 17 Sep 2002, Bob Bomar wrote: I have a dual P-200 file server that is haveing some connection problems. When I ssh to the box, I login in fine, but some times it lags for a while, but the two boxes are physically sitting next to each other, and are on ports that are side by side on the switch. While I ssh out of the box from the console, to another box on the LAN, it is still intermitant. Any body have any ideas? What type of ethernet card(s) is in the box? Is the switch reporting any type of errors? Nick Rogness [EMAIL PROTECTED] - WARNING TO ALL PERSONNEL: Firings will continue until morale improves. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NIC problem
A linksys, dc0, and the switch is a linksys 8-port, so I cant see any errors. I have swaped it out with an Intel card, fxp0, but it does the same thing. Anything wierd in the logfiles? Any device timeouts, eg fxp0 device timeout? There are no messages regarding timeouts or anything. I have noticed though that sometimes this box runs slower than my single P-166. -- /\ | Bob Bomar [EMAIL PROTECTED] http://www.bomar.us/~bob | || | FreeBSD: The Power to Serve. http://www.freeBSD.org | \/ msg01965/pgp0.pgp Description: PGP signature
Re: NIC problem
On Tue, Sep 17, 2002 at 09:13:52PM -0400, John wrote: On your p200... run 'netstat -i' ssh p200 do some intermitant stuff.. close ssh session run 'netstat -i' again... Look for any errors on the interface you are using. Please post the results back. -John Just did that, and no errors came out. The only diffrences were the amount of packets sent/recieved. -- /\ | Bob Bomar [EMAIL PROTECTED] http://www.bomar.us/~bob | || | FreeBSD: The Power to Serve. http://www.freeBSD.org | \/ msg01971/pgp0.pgp Description: PGP signature
Re: NIC problem
- Original Message - From: Bob Bomar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 17, 2002 8:22 PM Subject: NIC problem here is a just in case: have you tried using different ports on the switch? or a different switch? -- dfolkins To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
