9.0 w/ACPI enabled, excluding NICs
Hi, I am running a small personal file server. To ensure constant network access, had to disable the ACPI, hence no power saving at all. The CPU gets very warm as everything (presumably) is running at full throttle. Is there any way to disable the ACPI partially, i.e. allow spin-down for disks etc, but keep the NICs running? Hope that this question was understandable. Thanks. Regards, Ronny Mandal ___ 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: 9.0 w/ACPI enabled, excluding NICs
I am running a small personal file server. To ensure constant network access, had to disable the ACPI, hence no power saving at all. The CPU why you had to disable ACPI. i never ever seen network problems with ACPI. basically it works, or it doesn't at all. gets very warm as everything (presumably) is running at full throttle. Is there any way to disable the ACPI partially, i.e. allow spin-down for disks etc, but keep the NICs running? This is IMHO not about FreeBSD support of ACPI but possible BIOS settings that turn on some kind of hibernation. Hope that this question was understandable. Thanks. Regards, Ronny Mandal ___ 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: 9.0 w/ACPI enabled, excluding NICs
On 13.07.2012 15:52, Wojciech Puchar wrote: I am running a small personal file server. To ensure constant network access, had to disable the ACPI, hence no power saving at all. The CPU why you had to disable ACPI. i never ever seen network problems with ACPI. basically it works, or it doesn't at all. When the server is idle with ACPI enabled, it did not respond to ping after a short period. With ACPI disabled, this was alleviated. So, basically, it will stop working after a while. My guess is that ACPI will shut down the power for the NIC. But that is only a guess. Furthermore, when ACPI is disabled, no network problem arises. This suggests, at least to me, that ACPI is somehow involved. gets very warm as everything (presumably) is running at full throttle. Is there any way to disable the ACPI partially, i.e. allow spin-down for disks etc, but keep the NICs running? This is IMHO not about FreeBSD support of ACPI but possible BIOS settings that turn on some kind of hibernation. Each and every power saving function in the BIOS is disabled. Nevertheless, I believe that a selective ACPI configuration should resolve this issue, Hope that this question was understandable. Thanks. Regards, Ronny Mandal ___ 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: 9.0 w/ACPI enabled, excluding NICs
On Jul 13, 2012 8:34 AM, Ronny Mandal ronn...@volatile.no wrote: On 13.07.2012 15:52, Wojciech Puchar wrote: I am running a small personal file server. To ensure constant network access, had to disable the ACPI, hence no power saving at all. The CPU why you had to disable ACPI. i never ever seen network problems with ACPI. basically it works, or it doesn't at all. When the server is idle with ACPI enabled, it did not respond to ping after a short period. With ACPI disabled, this was alleviated. So, basically, it will stop working after a while. My guess is that ACPI will shut down the power for the NIC. But that is only a guess. Furthermore, when ACPI is disabled, no network problem arises. This suggests, at least to me, that ACPI is somehow involved. gets very warm as everything (presumably) is running at full throttle. Is there any way to disable the ACPI partially, i.e. allow spin-down for disks etc, but keep the NICs running? This is IMHO not about FreeBSD support of ACPI but possible BIOS settings that turn on some kind of hibernation. Each and every power saving function in the BIOS is disabled. Nevertheless, I believe that a selective ACPI configuration should resolve this issue, Hope that this question was understandable. Thanks. Regards, Ronny Mandal ___ 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 A «band-aid» type fix could be to ping gw (once) using cron 0-59/5 or something Waitman Gobble San Jose California ___ 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: 9.0, Samba and two NICs
On Fri, Feb 24, 2012 at 3:45 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 02/24/12 21:39, Ronny Mandal wrote: Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? What address is the w7 using? If it is using 192.X, that could be the problem. That or some variation... such as the w7 using wireless and 192.x? Sorry about the late answer and missing info. The W7 is using both, i.e. wireless and wired. Strangely enough, it works now. Here is what I did: The interface parameter; I put the 10.* before the 192.* and stopped and started the samba-service. After that, the wired card were utilized when I copied to and from the share. interfaces = 192.168.0.232 10.0.0.2 127.0.0.1 changed to interfaces = 10.0.0.2 192.168.0.232 127.0.0.1 (I tried this earlier, but it seems that /usr/local/etc/rc.d/samba restart did not properly re-read the configuration.) Regards, Ronny Mandal ___ 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
9.0, Samba and two NICs
Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? Thanks. -- Best regards, Ronny Mandal ___ 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: 9.0, Samba and two NICs
On 02/24/12 21:39, Ronny Mandal wrote: Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? What address is the w7 using? If it is using 192.X, that could be the problem. That or some variation... such as the w7 using wireless and 192.x? ___ 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: Which of these NICs will work?
On 03/09/2010 18:32:49, Robert Huff wrote: Ryan Coleman writes: Any thoughts? I need/want to get a multi-port NIC for my new system but I haven't purchased the guts for the server yet. http://www.newegg.com/Product/ProductList.aspx?Submit=ENEN=100010064+600013872+600016290QksAutoSuggestion=ShowDeactivatedMark=FalseConfigurator=IsNodeId=1Subcategory=27description=Ntk=CFG=SpeTabStoreType=srchInDesc= Basically, this machine will have two external (real-world) IPs and one network LAN (10.0.1.0/24) address, finding three-NIC motherboards is not exactly possible so this is my alternative. Intel network cards have a very good reputation; I have been running a dual-port Pro/1000 GT for years and the thing is still a rock. Others will have a better opinion on performance issues. The Intel employee who maintains the driver is frequently seen on current@ and occasionally on questi...@. Nice guy, very responsive. I second all the other respondents praise of the Intel cards. Intel is a safe choice of NIC -- basically you can be sure that it will not only be supported, but it will work very well. Of the other branded NICs there, unfortunately it is impossible to say much about them based on the manufacturers name. The important thing is the chipset. If the chipset is supported then you can be 99% certain the card will work. (The other 1% are manufacturers who do stupid things to the card firmware.) Unfortunately that is the sort of useful information that vendors almost never tell you on a website. Probably because they think all those letters and numbers will scare people away. They're right of course: that sort of cheap card tends to use chipsets from people like RealTek, many of whose products attract a wholly justified level of opprobrium. [Definitely avoid things that use the rl(4) driver. Stuff that uses re(4) is passable for some uses.] Also working well is quite subjective. It depends on the sort of traffic patterns and load levels you need to deal with. Cheaper NICs will not be able to cope with sustained mega-bit levels of traffic and complicated networking layouts, but they will be fine for occasional light use in a desktop box. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Which of these NICs will work?
based on 10+ exprience and working with a dozen models, I recommend intel cards: - Intel explicitly supports freebsd. - the cards are highly stable - have best performance among all other cards on freebsd and if you look for best performance, buy a card based on 82575 or 82576 controllers. On 9/3/2010 8:28 PM, Ryan Coleman wrote: Any thoughts? I need/want to get a multi-port NIC for my new system but I haven't purchased the guts for the server yet. http://www.newegg.com/Product/ProductList.aspx?Submit=ENEN=100010064+600013872+600016290QksAutoSuggestion=ShowDeactivatedMark=FalseConfigurator=IsNodeId=1Subcategory=27description=Ntk=CFG=SpeTabStoreType=srchInDesc= Basically, this machine will have two external (real-world) IPs and one network LAN (10.0.1.0/24) address, finding three-NIC motherboards is not exactly possible so this is my alternative. I'm looking for FreeBSD 7-9 support. Rather run 8.1-RELEASE (same as my other two machines right now). Thanks, Ryan ___ 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
Which of these NICs will work?
Any thoughts? I need/want to get a multi-port NIC for my new system but I haven't purchased the guts for the server yet. http://www.newegg.com/Product/ProductList.aspx?Submit=ENEN=100010064+600013872+600016290QksAutoSuggestion=ShowDeactivatedMark=FalseConfigurator=IsNodeId=1Subcategory=27description=Ntk=CFG=SpeTabStoreType=srchInDesc= Basically, this machine will have two external (real-world) IPs and one network LAN (10.0.1.0/24) address, finding three-NIC motherboards is not exactly possible so this is my alternative. I'm looking for FreeBSD 7-9 support. Rather run 8.1-RELEASE (same as my other two machines right now). Thanks, Ryan ___ 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
Which of these NICs will work?
Ryan Coleman writes: Any thoughts? I need/want to get a multi-port NIC for my new system but I haven't purchased the guts for the server yet. http://www.newegg.com/Product/ProductList.aspx?Submit=ENEN=100010064+600013872+600016290QksAutoSuggestion=ShowDeactivatedMark=FalseConfigurator=IsNodeId=1Subcategory=27description=Ntk=CFG=SpeTabStoreType=srchInDesc= Basically, this machine will have two external (real-world) IPs and one network LAN (10.0.1.0/24) address, finding three-NIC motherboards is not exactly possible so this is my alternative. Intel network cards have a very good reputation; I have been running a dual-port Pro/1000 GT for years and the thing is still a rock. Others will have a better opinion on performance issues. The Intel employee who maintains the driver is frequently seen on current@ and occasionally on questi...@. Nice guy, very responsive. 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: Which of these NICs will work?
I have several Intel multi-port, (2 port, 4 port and even some 2 port fibre-optic), cards in use. All have been rock-solid, stable performers, and have hardware VLAN tagging and trunking capability. I have some 4 port cards in use with LACP+VLAN Trunking, and then use vlan interfaces in FreeBSD configured per vlan. This allows many networks to share the same interface and is great for virtualization type situations too. Just my two cents - but I'd pay the extra for the Intel because I know it just works predictably and reliably. -- Nathan Vidican nat...@vidican.com Happy FreeBSD'er since 2.2.1:) On Fri, Sep 3, 2010 at 1:32 PM, Robert Huff roberth...@rcn.com wrote: Ryan Coleman writes: Any thoughts? I need/want to get a multi-port NIC for my new system but I haven't purchased the guts for the server yet. http://www.newegg.com/Product/ProductList.aspx?Submit=ENEN=100010064+600013872+600016290QksAutoSuggestion=ShowDeactivatedMark=FalseConfigurator=IsNodeId=1Subcategory=27description=Ntk=CFG=SpeTabStoreType=srchInDesc= Basically, this machine will have two external (real-world) IPs and one network LAN (10.0.1.0/24) address, finding three-NIC motherboards is not exactly possible so this is my alternative. Intel network cards have a very good reputation; I have been running a dual-port Pro/1000 GT for years and the thing is still a rock. Others will have a better opinion on performance issues. The Intel employee who maintains the driver is frequently seen on current@ and occasionally on questi...@. Nice guy, very responsive. 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 ___ 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
bonding NICs with netgraph
Hi, I am setting up a freebsd box to act as a snort sensor on a network. The box has three nics, one internal nic for talking on the network and to the management server, and two nics on a single pci card that each connect to SPAN ports on my switch. I am trying to bind the two adapters on the freebsd box so I have one virtual adapter that snort can listen to. I have been researching netgraph for some time and the script I have been using to configure the adapters is: Code: #!/bin/sh echo Trying kldload ng_ether... kldload ng_ether echo Putting dual adapters into promisc mode... ifconfig em0 promisc -arp up ifconfig em1 promisc -arp up echo Trying mkpeer . eiface hook ether ngctl mkpeer . eiface hook ether echo Trying mkpeer ngeth0: one2many lower one ngctl mkpeer ngeth0: one2many lower one echo Trying ngctl connect em0: ngeth0: lower lower many0 ngctl connect em0: ngeth0:lower lower many0 echo Trying ngctl connect em1: ngeth0: lower lower many1 ngctl connect em1: ngeth0:lower lower many1 echo Tryinh ifconfig ngeth0 -arp up ifconfig ngeth0 -arp up However when I run the script I get: Code: Trying kldload ng_ether... Putting dual adapters into promisc mode... Trying mkpeer . eiface hook ether Trying mkpeer ngeth0: one2many lower one ngctl: send msg: Protocol family not supported Trying ngctl connect em0: ngeth0: lower lower many0 ngctl: send msg: No such file or directory Trying ngctl connect em1: ngeth0: lower lower many1 ngctl: send msg: No such file or directory Tryinh ifconfig ngeth0 -arp up Now 'ngeth0' appears in ifconfig: Code: ngeth0: flags=88c3UP,BROADCAST,RUNNING,NOARP,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:00:00:00:00:00 but when I TCPDUMP from it it never records any packets even though I know the span ports are sending the individual NICs data. I have been googling the error messages that are returned by the bonding script but have been unable to get packets to cross ngeth0. Any advice or tips for troubleshooting this would be greatly appreciated. Thank you in advance. Will Urbanski ___ 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: Recommendations for NICs?
In recent testing with 8-Stable, we couldn't get our Intel cards to push more than 450Mbps. We put some Broadcom cards in and we can get 980Mbps. On Thu, Jan 21, 2010 at 10:27 AM, John j...@starfire.mn.org wrote: This used to be a hot topic long ago, but now seems to have become rather dormant. Does that mean that all NICs are pretty much commodity with all the good features (unaligned scatter/gather, etc), or does it just mean that machine performance has grown to the point where we don't care anymore? The hardware.html page tells me what may owrk, but not what may work WELL. The on-board NIC uses the fxp driver. Should I look for another card that uses the same driver? Are those good, or are both good and bad cards supproted by the same driver? The list doesn't give any of the featuers which used to be assocaited with good or bad cards - just the names. Thanks! -- John Lind j...@starfire.mn.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 ___ 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
Recommendations for NICs?
This used to be a hot topic long ago, but now seems to have become rather dormant. Does that mean that all NICs are pretty much commodity with all the good features (unaligned scatter/gather, etc), or does it just mean that machine performance has grown to the point where we don't care anymore? The hardware.html page tells me what may owrk, but not what may work WELL. The on-board NIC uses the fxp driver. Should I look for another card that uses the same driver? Are those good, or are both good and bad cards supproted by the same driver? The list doesn't give any of the featuers which used to be assocaited with good or bad cards - just the names. Thanks! -- John Lind j...@starfire.mn.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: Recommendations for NICs?
Hi-- On Jan 21, 2010, at 9:27 AM, John wrote: This used to be a hot topic long ago, but now seems to have become rather dormant. Does that mean that all NICs are pretty much commodity with all the good features (unaligned scatter/gather, etc), or does it just mean that machine performance has grown to the point where we don't care anymore? The hardware.html page tells me what may owrk, but not what may work WELL. The on-board NIC uses the fxp driver. Should I look for another card that uses the same driver? Intel (fxp, em) and Broadcom (bce, bge) make fine NICs, and the older DEC/Intel 21x4x Tulip series (dc/de) was quite good as well. The Marvel Yukon (msk) and nVidia MCP (nfe/nve) seem to be OK (although older nVidia hardware had bugs); the Realtek (re/rl) and VIA (vr/vge) are at the bottom of the heap, especially the older pre-gigabit hardware. Regards, -- -Chuck ___ 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: Recommendations for NICs?
On Thu, Jan 21, 2010 at 10:12:29AM -0800, Chuck Swiger wrote: Hi-- On Jan 21, 2010, at 9:27 AM, John wrote: This used to be a hot topic long ago, but now seems to have become rather dormant. Does that mean that all NICs are pretty much commodity with all the good features (unaligned scatter/gather, etc), or does it just mean that machine performance has grown to the point where we don't care anymore? The hardware.html page tells me what may owrk, but not what may work WELL. The on-board NIC uses the fxp driver. Should I look for another card that uses the same driver? Intel (fxp, em) and Broadcom (bce, bge) make fine NICs, and the older DEC/Intel 21x4x Tulip series (dc/de) was quite good as well. The Marvel Yukon (msk) and nVidia MCP (nfe/nve) seem to be OK (although older nVidia hardware had bugs); the Realtek (re/rl) and VIA (vr/vge) are at the bottom of the heap, especially the older pre-gigabit hardware. Thanks! That's perfect. I have a chance to buy a few Intel Pro 10/100 (fxp) cards. I guess I'll take it! Just curious, though - you don't mention 3Com cards one way or the other, yet there's a lot of them out there. Any comment on those? Regards, -- -Chuck ___ 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 -- John Lind j...@starfire.mn.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: Recommendations for NICs?
Chuck Swiger writes: This used to be a hot topic long ago, but now seems to have become rather dormant. Intel (fxp, em) and Broadcom (bce, bge) make fine NICs, and the older DEC/Intel 21x4x Tulip series (dc/de) was quite good as well. Let me add my vote for Intel: I have a dual-port Pro/1000, and the thing is a rock: h...@jerusalem uptime 1:28PM up 3 days, 20:56, 7 users, load averages: 2.47, 2.32, 2.28 h...@jerusalem netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll em01500 Link#1 00:0e:0c:a8:a7:e8 7814719 0 5448800 0 354923 em01500 fe80:1::20e:c fe80:1::20e:cff:f0 -3 - - em01500 209.6.88.0/21 209.6.91.204 4586806 - 5448773 - - em11500 Link#2 00:0e:0c:a8:a7:e923378 0 1104 0 0 em11500 10.0.0.0 jerusalem.scallop 825417 - 1096 - - em11500 fe80:2::20e:c fe80:2::20e:cff:f0 -4 - - The other nifty thing? The driver. Written by Intel waves at Jack Vogel, with superlative turn-around on problems or documentation questions, and open source. 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: Recommendations for NICs?
On Jan 21, 2010, at 10:20 AM, John wrote: [ ... ] Thanks! That's perfect. I have a chance to buy a few Intel Pro 10/100 (fxp) cards. I guess I'll take it! If you don't need gigabit, the fxp cards are great-- very reliable and some even support interrupt mitigation in firmware (which generally wasn't around until gigabit). Just curious, though - you don't mention 3Com cards one way or the other, yet there's a lot of them out there. Any comment on those? The older 3com NICs used by ed/vx (including 3c5xx NE2000 clones) tended to be flaky and had issues with buffer memory causing corrupted packet data, and they generally couldn't do bus-mastering DMA. The later 3com 9xx models used by xl are much better, but they aren't on the same level as fxp or dc-- I wouldn't bother with anything prior to a 3c905. Regards, -- -Chuck ___ 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: Recommendations for NICs?
On Thu, Jan 21, 2010 at 12:20:34PM -0600, John wrote: On Thu, Jan 21, 2010 at 10:12:29AM -0800, Chuck Swiger wrote: Intel (fxp, em) and Broadcom (bce, bge) make fine NICs, and the older DEC/Intel 21x4x Tulip series (dc/de) was quite good as well. The Marvel Yukon (msk) and nVidia MCP (nfe/nve) seem to be OK (although older nVidia hardware had bugs); the Realtek (re/rl) and VIA (vr/vge) are at the bottom of the heap, especially the older pre-gigabit hardware. Thanks! That's perfect. I have a chance to buy a few Intel Pro 10/100 (fxp) cards. I guess I'll take it! Snag 'em! My favorite no worry NIC. In recent years one could pick them up surplus for $2 to $5. Then they just work. And if one is forced to use Windows the Intel driver (not the one Windows ships) adds a lot of useful stuff which is missing, such as the ability to *see* (without leaving the application) what IP address the card is using. Oh, and not only that but the Intel cards work (without need to install drivers) on MacOS X PCI machines. Just curious, though - you don't mention 3Com cards one way or the other, yet there's a lot of them out there. Any comment on those? 3com's downfall has been due to their mixed bag of sometimes great, sometimes disappointing. -- 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: Recommendations for NICs?
Personally, I've had the best success with fxp and em cards (Intel), and the worst with broadcom-based on-board nics, but have tried and worked with many different cards over the years on FreeBSD. Hands-down though, I prefer Intel's NIC offerings. IIRC - Intel contributed to the development and supports the fxp driver too, so I've always tried to send my business to the vendor which supports my specific use of their product rather than the one which expects me or requires me to rely solely on the reverse-engineering and support of the open-source community to figure it out themselves. To me, I feel a whole lot 'safer' with the knowledge that the hardware manufacturer knows and understands my application better than the next guy (cough* insert plug for Apple anyone?). Just my opinion and experience though - I offer no technical merit as I've honestly not bothered to try anything else in recent years (habitually stick with what works I guess). -- Nathan Vidican nat...@vidican.com On Thu, Jan 21, 2010 at 12:27 PM, John j...@starfire.mn.org wrote: This used to be a hot topic long ago, but now seems to have become rather dormant. Does that mean that all NICs are pretty much commodity with all the good features (unaligned scatter/gather, etc), or does it just mean that machine performance has grown to the point where we don't care anymore? The hardware.html page tells me what may owrk, but not what may work WELL. The on-board NIC uses the fxp driver. Should I look for another card that uses the same driver? Are those good, or are both good and bad cards supproted by the same driver? The list doesn't give any of the featuers which used to be assocaited with good or bad cards - just the names. Thanks! -- John Lind j...@starfire.mn.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 ___ 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: Recommendations for NICs?
Let me add my vote for Intel: I have a dual-port Pro/1000, and the thing is a rock: I am planning to get a Pro/1000 MT dual port card, do you know that will it works well in 32bit PCI slot on FreeBSD? Thanks, C.C. ___ 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: Recommendations for NICs?
C. C. Tang writes: Let me add my vote for Intel: I have a dual-port Pro/1000, and the thing is a rock: I am planning to get a Pro/1000 MT dual port card, do you know that will it works well in 32bit PCI slot on FreeBSD? I have one of these: Pro/1000 GT Dual Port Gigabit Ethernet Controller (82546EB) It has worked perfectly, with one tertiary exception that happened due to a (non-FreeBSD related) driver change: for some reason, DHCP tries to send packets before the driver decides it's ready to accept them. This causes a 30-60 second delay during startup, but afterwards everything is fine. 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: Wireless NICs on 7.2
On Thu, Jul 2, 2009 at 4:14 PM, Paul B. Maholone...@gmail.com wrote: $ ifconfig ral0 list scan SSID BSSID CHAN RATE S:N INT CAPS livingroom 00:13:10:b9:e7:d6 6 54M -93:-95 100 E 93 is too low. Paul, I really appreciate your help. I'm obviously not an expert on either wireless networks or radio communication in general. But I doubt the accuracy of the scan. First of all, there's an XP box less than a foot away getting a very good signal (according to both the MS and the Belkin utilities), and successfully communicating with the wireless network. When I move the FBSD box and put the XP box in it's place, the XP box continues to report a good signal and continues to communicate with the network. While the XP box is reporting variations in rate and signal, the FBSD box reports no change. Secondly, when I run ifconfig ral0 up scan, the scan hangs. It never completes or reports results. According to the man page, it's supposed to complete the scan, report the results, and exit. I have to Ctrl-C and run ifconfig ral0 list scan to get the results. So I know that at least part of the scan function doesn't work and I know that it's not detecting changes in rate and signal that are being reported by the XP box. 1) The XP box works fine with the Linksys NIC in it. 2) Both the XP and FBSD boxes are Dell Optiplex GX270, so they have identical hardware aside from the wireless NICs. 3) The md5 checksum for the install CD is correct, so I should have a good installation of 7.2 4) I seem to be getting a good signal, good enough to communicate with the network. 5) Both the Belkin and the Linksys work fine in the XP box. 6) The FBSD box always reports the same data, regardless of changes in conditions. 7) If I move the boxes and test them in the same physical location, oriented in the same direction, the XP box works and the FBSD box doesn't. So my guess is that output from a scan is the result of a problem in the driver, and not the result of actual conditions. If I thought I could solve this with a high gain antenna, I'd buy one in a second. But at the moment I have pretty good reason to believe that the problem isn't signal strength. I'd still like to compile a working ndis driver for either the Belkin F5D7000 v.7032 or the Linksys WMP54G v.4.1, if that is possible, or get the ral driver to work with the Linksys. I'd be willing to move from 7.2 to 6.4 if anyone has had success with that. ___ 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: Wireless NICs on 7.2
On 7/3/09, Robert Hall rjh...@gmail.com wrote: On Thu, Jul 2, 2009 at 4:14 PM, Paul B. Maholone...@gmail.com wrote: $ ifconfig ral0 list scan SSIDBSSID CHAN RATE S:N INT CAPS livingroom 00:13:10:b9:e7:d66 54M -93:-95 100 E 93 is too low. Paul, I really appreciate your help. I'm obviously not an expert on either wireless networks or radio communication in general. But I doubt the accuracy of the scan. First of all, there's an XP box less than a foot away getting a very good signal (according to both the MS and the Belkin utilities), and successfully communicating with the wireless network. When I move the FBSD box and put the XP box in it's place, the XP box continues to report a good signal and continues to communicate with the network. While the XP box is reporting variations in rate and signal, the FBSD box reports no change. Secondly, when I run ifconfig ral0 up scan, the scan hangs. It never completes or reports results. According to the man page, it's supposed to complete the scan, report the results, and exit. I have to Ctrl-C and run ifconfig ral0 list scan to get the results. So I know that at least part of the scan function doesn't work and I know that it's not detecting changes in rate and signal that are being reported by the XP box. That have sense only if station is associated. Reported driver signal is to low to be usefull. 1) The XP box works fine with the Linksys NIC in it. 2) Both the XP and FBSD boxes are Dell Optiplex GX270, so they have identical hardware aside from the wireless NICs. 3) The md5 checksum for the install CD is correct, so I should have a good installation of 7.2 4) I seem to be getting a good signal, good enough to communicate with the network. 5) Both the Belkin and the Linksys work fine in the XP box. 6) The FBSD box always reports the same data, regardless of changes in conditions. 7) If I move the boxes and test them in the same physical location, oriented in the same direction, the XP box works and the FBSD box doesn't. So my guess is that output from a scan is the result of a problem in the driver, and not the result of actual conditions. If I thought I could solve this with a high gain antenna, I'd buy one in a second. But at the moment I have pretty good reason to believe that the problem isn't signal strength. I'd still like to compile a working ndis driver for either the Belkin F5D7000 v.7032 or the Linksys WMP54G v.4.1, if that is possible, or get the ral driver to work with the Linksys. I'd be willing to move from 7.2 to 6.4 if anyone has had success with that. I'm aware of similar problems with rum(4) driver - signal is too low comparing to linux rt73 and ndisulator. I don't have ral(4) card so I can not comment on that. Alternative approach would be to explore AP settings. -- Paul ___ 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: Wireless NICs on 7.2
On 7/2/09, Robert Hall rjh...@gmail.com wrote: And what about TX/RX signal? I don't know where to look for that. :) It is part of scan output. Could you put backtrace somewhere? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html Backtrace from crashing with a Belkin ndis: (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd5f9571c, eva=0) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd5f9571c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd5f9571c) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc32b5239 in BLKWGDv7_sys_drv_data_start () from /boot/modules/BLKWGDv7_sys.ko Previous frame inner to this frame (corrupt stack?) And from a Linksys crash (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd600cb98, eva=382216) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd600cb98, usermode=0, eva=382216) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd600cb98) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc329dde6 in rt61_sys_drv_data_start () from /boot/modules/./rt61_sys.ko Previous frame inner to this frame (corrupt stack?) I hope this is what you were asking for. :) Does crash happens if you load them after boot? -- Paul ___ 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: Wireless NICs on 7.2
On Thu, Jul 2, 2009 at 6:04 AM, Paul B. Maholone...@gmail.com wrote: On 7/2/09, Robert Hall rjh...@gmail.com wrote: And what about TX/RX signal? I don't know where to look for that. :) It is part of scan output. I don't remember seeing that in the output. I'll put the Linksys back in the FBSD box and look for it. Does it have another name? I can't find it on the ifconfig man page. On the XP box, the Linksys utility says that the transmit rate is 12 Mbps and the receive rate is 5.5 Mbps. When I move the Linksys NIC to the FBSD box, I get: $ ifconfig ral0 list scan SSIDBSSID CHAN RATE S:N INT CAPS livingroom 00:13:10:b9:e7:d66 54M -93:-95 100 E I think the 54M is what you're asking for? I looked in man ifconfig and couldn't find TX or RX so I'm guessing that you're asking about the rate at which data is passed. Thanks for your help. ___ 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: Wireless NICs on 7.2
On 7/2/09, Robert Hall rjh...@gmail.com wrote: On Thu, Jul 2, 2009 at 6:04 AM, Paul B. Maholone...@gmail.com wrote: On 7/2/09, Robert Hall rjh...@gmail.com wrote: And what about TX/RX signal? I don't know where to look for that. :) It is part of scan output. I don't remember seeing that in the output. I'll put the Linksys back in the FBSD box and look for it. Does it have another name? I can't find it on the ifconfig man page. On the XP box, the Linksys utility says that the transmit rate is 12 Mbps and the receive rate is 5.5 Mbps. When I move the Linksys NIC to the FBSD box, I get: $ ifconfig ral0 list scan SSIDBSSID CHAN RATE S:N INT CAPS livingroom 00:13:10:b9:e7:d66 54M -93:-95 100 E 93 is too low. I think the 54M is what you're asking for? I looked in man ifconfig and couldn't find TX or RX so I'm guessing that you're asking about the rate at which data is passed. Thanks for your help. -- Paul ___ 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
Wireless NICs on 7.2
I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. It sort of works with the ral driver; I can set the ssid and inet and other values, but it won't associate with the access point or establish a useful connection. I've tried compiling ndis drivers for both the Linksys and a Belkin F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the system when they load, leading to a reboot. Groveling through vmcore doesn't give me any clues about why the Belkin ndis crashes. The Linksys crash sends a message that it can't open /compat/ndis/rt2561s.bin. I googled for the firmware files and put them in /compat/ndis, but ndis still crashes. Both cards work fine on the XP box. Has anyone gotten either card to work on 7.2, either by using the ral driver or by compiling an ndis driver? ___ 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: Wireless NICs on 7.2
On 7/1/09, Robert Hall rjh...@gmail.com wrote: I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. It sort of works with the ral driver; I can set the ssid and inet and other values, but it won't associate with the access point or establish a useful connection. Does it get any scan results? What kind of AP setup: NONE, WEP, WPA, WPA2 ... ? I've tried compiling ndis drivers for both the Linksys and a Belkin F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the system when they load, leading to a reboot. Groveling through vmcore doesn't give me any clues about why the Belkin ndis crashes. The Linksys crash sends a message that it can't open /compat/ndis/rt2561s.bin. I googled for the firmware files and put them in /compat/ndis, but ndis still crashes. Both cards work fine on the XP box. You are using i386 FreeBSD, right? Has anyone gotten either card to work on 7.2, either by using the ral driver or by compiling an ndis driver? ___ 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 -- Paul ___ 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: Wireless NICs on 7.2
On Wed, Jul 1, 2009 at 1:55 PM, Paul B. Maholone...@gmail.com wrote: On 7/1/09, Robert Hall rjh...@gmail.com wrote: I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. It sort of works with the ral driver; I can set the ssid and inet and other values, but it won't associate with the access point or establish a useful connection. Does it get any scan results? Yes. Scanning seems to work fine. What kind of AP setup: NONE, WEP, WPA, WPA2 ... ? No security. I've tried compiling ndis drivers for both the Linksys and a Belkin F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the system when they load, leading to a reboot. Groveling through vmcore doesn't give me any clues about why the Belkin ndis crashes. The Linksys crash sends a message that it can't open /compat/ndis/rt2561s.bin. I googled for the firmware files and put them in /compat/ndis, but ndis still crashes. Both cards work fine on the XP box. BTW, I'm not getting the open file failed message any longer, but the ndis driver still crashes the system. You are using i386 FreeBSD, right? I should have posted this originally: $ uname -a FreeBSD stamfordbru.krig.net 7.2-RELEASE FreeBSD 7.2-RELEASE #3: Wed Jul 1 11:40:35 EDT 2009 r...@stamfordbru.krig.net:/usr/obj/usr/src/sys/STAMFORDBRU0 i386 ___ 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: Wireless NICs on 7.2
On 7/1/09, Robert Hall rjh...@gmail.com wrote: On Wed, Jul 1, 2009 at 1:55 PM, Paul B. Maholone...@gmail.com wrote: On 7/1/09, Robert Hall rjh...@gmail.com wrote: I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. It sort of works with the ral driver; I can set the ssid and inet and other values, but it won't associate with the access point or establish a useful connection. Does it get any scan results? Yes. Scanning seems to work fine. And what about TX/RX signal? What kind of AP setup: NONE, WEP, WPA, WPA2 ... ? No security. I've tried compiling ndis drivers for both the Linksys and a Belkin F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the system when they load, leading to a reboot. Groveling through vmcore doesn't give me any clues about why the Belkin ndis crashes. The Linksys crash sends a message that it can't open /compat/ndis/rt2561s.bin. I googled for the firmware files and put them in /compat/ndis, but ndis still crashes. Both cards work fine on the XP box. BTW, I'm not getting the open file failed message any longer, but the ndis driver still crashes the system. Could you put backtrace somewhere? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html You are using i386 FreeBSD, right? I should have posted this originally: $ uname -a FreeBSD stamfordbru.krig.net 7.2-RELEASE FreeBSD 7.2-RELEASE #3: Wed Jul 1 11:40:35 EDT 2009 r...@stamfordbru.krig.net:/usr/obj/usr/src/sys/STAMFORDBRU0 i386 ___ 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 -- Paul ___ 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: Wireless NICs on 7.2
And what about TX/RX signal? I don't know where to look for that. :) Could you put backtrace somewhere? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html Backtrace from crashing with a Belkin ndis: (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd5f9571c, eva=0) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd5f9571c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd5f9571c) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc32b5239 in BLKWGDv7_sys_drv_data_start () from /boot/modules/BLKWGDv7_sys.ko Previous frame inner to this frame (corrupt stack?) And from a Linksys crash (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd600cb98, eva=382216) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd600cb98, usermode=0, eva=382216) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd600cb98) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc329dde6 in rt61_sys_drv_data_start () from /boot/modules/./rt61_sys.ko Previous frame inner to this frame (corrupt stack?) I hope this is what you were asking for. :) ___ 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: Multiple NICs routing question
At 06:26 AM 10/9/2008, Konrad Heuer wrote: Hello, I've a server box with four NICs addressing different subnets: NIC1: one class c subnet of same class b network NIC2: another class c subnet of same class b network NIC3: local unrouted network NIC4: local unrouted network In the current configuration I use a default gateway (and no routing daemon) in the subnet addressed by NIC1. Now of course, if a client in an arbitrary different class c subnet contacts the server using the ip address of NIC2, it gets a reply from NIC1. How can I cange this? I'd like the server to answer via the interface the client uses when connecting. Maybe that's a silly question, but thanks for any reply! Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] You can have only one default gateway, that should be to where all other traffic should go. Add static routes to your specific subnets, public or private for the routing of that traffic. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Multiple NICs routing question
Hello, I've a server box with four NICs addressing different subnets: NIC1: one class c subnet of same class b network NIC2: another class c subnet of same class b network NIC3: local unrouted network NIC4: local unrouted network In the current configuration I use a default gateway (and no routing daemon) in the subnet addressed by NIC1. Now of course, if a client in an arbitrary different class c subnet contacts the server using the ip address of NIC2, it gets a reply from NIC1. How can I cange this? I'd like the server to answer via the interface the client uses when connecting. Maybe that's a silly question, but thanks for any reply! Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [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: Multiple NICs routing question
I've a server box with four NICs addressing different subnets: NIC1: one class c subnet of same class b network NIC2: another class c subnet of same class b network NIC3: local unrouted network NIC4: local unrouted network In the current configuration I use a default gateway (and no routing daemon) in the subnet addressed by NIC1. Now of course, if a client in an arbitrary different class c subnet contacts the server using the ip address of NIC2, it gets a reply from NIC1. You should give more details about your configuration. If any client on the class B on NIC2 can contact your server, you must configure the NIC for the class B. The routing stack will take charge of excluding the class C on NIC1 from the class B on NIC2. It's very bad that the client that connects via the NIC2 has a subnet of class B and that the NIC2 is configured for class C only. If you configure: NIC1 192.168.1.1 255.255.255.0 NIC2 192.168.2.1 255.255.0.0 Client 192.168.127.23 255.255.0.0 it should work. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: two nics each with dsl and the third for LAN and am not able to get any milage out of one dsl.
I just inherited a second dsl line and don't have a server to connect it too so I have it connected to a third nic that I have in the Dell that has the first dsl connection and the LAN. I have been running pf on the two nics with nat and squid in transparent proxy mode without any issues. My problem is that I haven't come up with a way to really take advantage of the new dsl to reduce traffic on the first. I'm not even dreaming of load balancing just sharing some of the load. I had thought about trying to get squid to use the second connection but my feeble attempts at redirecting it haven't made much sense nor have they worked. Most of our traffic is outgoing rather than incoming, if that helps. I'm sure someone else must have a similar setup and are doing better than I. Anything is better than nothing. Basically, I think and hope that I am just drowning in a glass of water. Thanks for any suggestions. ed it all well depends on how many wires you need to make your boss happy. if you feel like u can be replaced with a router maybe you should start making half-way websites rather than doing 2 way internet connections. but there is a shoe for every foot. i actually admire the creativity of the pf coders. i hope you have at least 2 gateways. please don't drown. http://www.openbsd.org/faq/pf/pools.html Thank you for doc! Might End up using my side aswell. Unfortunately most of my servers run ipfw. Wow! Thanks, Nash. This should do it. I just read through it and had no idea it even existed. Especially the nat for two IP's I'll start trying it tomorrow and will post the results. Thanks again, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two nics each with dsl and the third for LAN and am not able to get any milage out of one dsl.
Quoting Nash Nipples [EMAIL PROTECTED]: I just inherited a second dsl line and don't have a server to connect it too so I have it connected to a third nic that I have in the Dell that has the first dsl connection and the LAN. I have been running pf on the two nics with nat and squid in transparent proxy mode without any issues. My problem is that I haven't come up with a way to really take advantage of the new dsl to reduce traffic on the first. I'm not even dreaming of load balancing just sharing some of the load. I had thought about trying to get squid to use the second connection but my feeble attempts at redirecting it haven't made much sense nor have they worked. Most of our traffic is outgoing rather than incoming, if that helps. I'm sure someone else must have a similar setup and are doing better than I. Anything is better than nothing. Basically, I think and hope that I am just drowning in a glass of water. Thanks for any suggestions. ed it all well depends on how many wires you need to make your boss happy. if you feel like u can be replaced with a router maybe you should start making half-way websites rather than doing 2 way internet connections. but there is a shoe for every foot. i actually admire the creativity of the pf coders. i hope you have at least 2 gateways. please don't drown. http://www.openbsd.org/faq/pf/pools.html Wow! Thanks, Nash. This should do it. I just read through it and had no idea it even existed. Especially the nat for two IP's I'll start trying it tomorrow and will post the results. Thanks again, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
two nics each with dsl and the third for LAN and am not able to get any milage out of one dsl.
I just inherited a second dsl line and don't have a server to connect it too so I have it connected to a third nic that I have in the Dell that has the first dsl connection and the LAN. I have been running pf on the two nics with nat and squid in transparent proxy mode without any issues. My problem is that I haven't come up with a way to really take advantage of the new dsl to reduce traffic on the first. I'm not even dreaming of load balancing just sharing some of the load. I had thought about trying to get squid to use the second connection but my feeble attempts at redirecting it haven't made much sense nor have they worked. Most of our traffic is outgoing rather than incoming, if that helps. I'm sure someone else must have a similar setup and are doing better than I. Anything is better than nothing. Basically, I think and hope that I am just drowning in a glass of water. Thanks for any suggestions. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two nics each with dsl and the third for LAN and am not able to get any milage out of one dsl.
I just inherited a second dsl line and don't have a server to connect it too so I have it connected to a third nic that I have in the Dell that has the first dsl connection and the LAN. I have been running pf on the two nics with nat and squid in transparent proxy mode without any issues. My problem is that I haven't come up with a way to really take advantage of the new dsl to reduce traffic on the first. I'm not even dreaming of load balancing just sharing some of the load. I had thought about trying to get squid to use the second connection but my feeble attempts at redirecting it haven't made much sense nor have they worked. Most of our traffic is outgoing rather than incoming, if that helps. I'm sure someone else must have a similar setup and are doing better than I. Anything is better than nothing. Basically, I think and hope that I am just drowning in a glass of water. Thanks for any suggestions. ed it all well depends on how many wires you need to make your boss happy. if you feel like u can be replaced with a router maybe you should start making half-way websites rather than doing 2 way internet connections. but there is a shoe for every foot. i actually admire the creativity of the pf coders. i hope you have at least 2 gateways. please don't drown. http://www.openbsd.org/faq/pf/pools.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB nics
Hi guys. I have a little usb nic, and I would like to be able to attach it for service purposes from time to time. Unfortunately, there doesn't seem to be any clear instructions on how to do this, and my time is short. The nic is an AXIS 88772 which I think might be covered by drivers. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
if_bridge, if_tap and wireless NICs
Hello, I've finally gotten emulators/qemu to work with bridge/tap networking on FreeBSD-7.0-BETA1 i386 using bfe0: Broadcom BCM4401-B0 Fast Ethernet For reference, I used the tutorial listed at: http://forums.bsdnexus.com/viewtopic.php?id=1563 My issue is, however, that QEMU/bridge/tap does not work with my wireless NIC (ath0: Atheros 5212) The question, is there a work-around for this issue? My first thought was to bridge the loopback device. I tried adding the loopback device lo0 to the bridge (ifconfig bridge0 addm lo0 up) but that failed with an error (ifconfig: BRDGADD lo0: Invalid argument). Any help, pointers is much appreciated. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multiple NICs - custom protocol development
Len Gross [EMAIL PROTECTED] writes: First, thanks for the response; It's nice to see some community support. Here is what I am trying to do: I am building a custom MAC protocol for a wireless system that has different software on the head end and the clients. It is not peer-to-peer, While the hardware is being developed I want to use Ethernet as a physical layer. So,I want to use one card running server code and one card running client code initially. Later I will do the checkout with multiple client machines and a single server. If the OS loops a packet back (At the IP layer) before it gets to my MAC layer then I can't test any code. If the client and server are sharing an IP stack, then the packets *should* be looped back at the IP layer. You want separate stacks for testing with IP, and in my earlier message I listed some ways to do that with a single machine. Getting a second PC is always an option too, and often a simple answer. Another option could be to fake (or wrap) the socket calls, but I doubt that's really going to be worthwhile for you. I prefer to never spend more time debugging the testbed than absolutely necessary. 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: Multiple NICs - custom protocol development
Len Gross [EMAIL PROTECTED] writes: I have a host on my local 192.168.0 / 24 subnet that works fine in getting to the Internet via a default route.via a wireless connection. I want to develop some custom link protocols and I have placed two Ethernet NICs in the box. I want to be able to send packets from one NIC to the other and maintain the link to the Internet. I've tried a large number of things via rc.conf but when I ping of the cards it is not going out the interface; it just gets looped back. (I test this by disconnecting the crossover cable between the two cards.) My current rc.conf has the following attempt, but this fails. # router_enable=Yes gateway_enable=Yes # Ethernet 1: ifconfig_xl0=inet 192.168.1.1 netmask 255.255.255.0 # Ethernet 2 ifconfig_rl0=inet 192.168.2.1 netmask 255.255.255.0 # # Set up loop between the two ethernet cards static_routes xtor, rtox route_rtox = -host 192.168.1.1 192.168.2.1 route_xtor = -host 192.168.2.1 192.168.1.1 Can I do what I want or must I have a second development box? What you want to do doesn't make sense; there is no reason to send packets to yourself over a wire. If your machine is sending packets to itself, the best path is over the loopback, and it doesn't make sense to send it over a different path. So you need to examine *why* you want to do that before you can figure out the best approach to your root problem. I do protocol development and testing through a number of different approaches, but for basic development there's usually no problem with letting the packets go over the loopback. For working on something like DHCP, I need separate IP stacks, because that will modify the routing tables differently on the server and the client(s). For that, I find virtual machines (qemu, most recently) to be the easiest and most flexible environment. I have also used environments based on bpf(4) interfaces when I was working with IP stacks that ran separately from the system's kernel. 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: Multiple NICs - custom protocol development
First, thanks for the response; It's nice to see some community support. Here is what I am trying to do: I am building a custom MAC protocol for a wireless system that has different software on the head end and the clients. It is not peer-to-peer, While the hardware is being developed I want to use Ethernet as a physical layer. So,I want to use one card running server code and one card running client code initially. Later I will do the checkout with multiple client machines and a single server. If the OS loops a packet back (At the IP layer) before it gets to my MAC layer then I can't test any code. -- Len On 9/20/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Len Gross [EMAIL PROTECTED] writes: I have a host on my local 192.168.0 / 24 subnet that works fine in getting to the Internet via a default route.via a wireless connection. I want to develop some custom link protocols and I have placed two Ethernet NICs in the box. I want to be able to send packets from one NIC to the other and maintain the link to the Internet. I've tried a large number of things via rc.conf but when I ping of the cards it is not going out the interface; it just gets looped back. (I test this by disconnecting the crossover cable between the two cards.) My current rc.conf has the following attempt, but this fails. # router_enable=Yes gateway_enable=Yes # Ethernet 1: ifconfig_xl0=inet 192.168.1.1 netmask 255.255.255.0 # Ethernet 2 ifconfig_rl0=inet 192.168.2.1 netmask 255.255.255.0 # # Set up loop between the two ethernet cards static_routes xtor, rtox route_rtox = -host 192.168.1.1 192.168.2.1 route_xtor = -host 192.168.2.1 192.168.1.1 Can I do what I want or must I have a second development box? What you want to do doesn't make sense; there is no reason to send packets to yourself over a wire. If your machine is sending packets to itself, the best path is over the loopback, and it doesn't make sense to send it over a different path. So you need to examine *why* you want to do that before you can figure out the best approach to your root problem. I do protocol development and testing through a number of different approaches, but for basic development there's usually no problem with letting the packets go over the loopback. For working on something like DHCP, I need separate IP stacks, because that will modify the routing tables differently on the server and the client(s). For that, I find virtual machines (qemu, most recently) to be the easiest and most flexible environment. I have also used environments based on bpf(4) interfaces when I was working with IP stacks that ran separately from the system's kernel. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Multiple NICs - custom protocol development
I have a host on my local 192.168.0 / 24 subnet that works fine in getting to the Internet via a default route.via a wireless connection. I want to develop some custom link protocols and I have placed two Ethernet NICs in the box. I want to be able to send packets from one NIC to the other and maintain the link to the Internet. I've tried a large number of things via rc.conf but when I ping of the cards it is not going out the interface; it just gets looped back. (I test this by disconnecting the crossover cable between the two cards.) My current rc.conf has the following attempt, but this fails. # router_enable=Yes gateway_enable=Yes # Ethernet 1: ifconfig_xl0=inet 192.168.1.1 netmask 255.255.255.0 # Ethernet 2 ifconfig_rl0=inet 192.168.2.1 netmask 255.255.255.0 # # Set up loop between the two ethernet cards static_routes xtor, rtox route_rtox = -host 192.168.1.1 192.168.2.1 route_xtor = -host 192.168.2.1 192.168.1.1 Can I do what I want or must I have a second development box? -- Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
Nikos Vassiliadis schrieb: I don't think this is an auto negotiation issue. How can a Windows machine that is connected to the same switch as my two FreeBSD machines and does not even talk to them explicitly influence the autonegotation of the FreeBSD NIC? I didn't say that a Windows machine can influence adversely a FreeBSD machine. In my case, to the contrary, a Windows machine does positively influence the FreeBSD machines. Look: - One switch connected to bge3 on both FreeBSD machines, no other connections. - The machines cannot ping each other. - Hook up a Windows machine that basically does nothing at all to another port of the switch. - As a result, the machines can now ping each other. - Disconnect the Windows machine. - The machines continue working normally. (Symptom is that the NIC reports the link as up (PCS synched) but no traffic can be exchanged.) This message is from revision 1.71 of the bge driver. In short I would really try what's recommended there. Well, that bug in revision 1.71 was discussed somewhere in the 4.x branch and a patch was submitted to current at the time. So I would guess that it is already included in 6.2!? hm, what happens if you disable ARP? ifconfig intX -arp and use static ARP? Point taken, this does not fix it. On the other hand, forcing the link speed likewise does not fix the problem, so I don't think it is an auto negotiation problem, either. In the meantime, I have found out that the affected interfaces show similar problems on Linux (Debian Etch). I'm starting to get the impression that this is a hardware issue. There was a bug reported for the BIOS of this xSeries 346 that leads to PCI configuration errors resulting in SCO Unixware not picking up network connections. I flashed the updated BIOS, but to no avail. Thanks Regards Tobias -- Universität Stuttgart|Fakultät für Architektur und Stadtplanung|casinoIT 70174 Stuttgart Geschwister-Scholl-Straße 24D T +49 (0)711 121-4228 F +49 (0)711 121-4276 E [EMAIL PROTECTED] I http://www.casino.uni-stuttgart.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
On Friday 31 August 2007 20:55:13 Tobias Ernst wrote: Hi, I have further news on this problem. It really seems to be a driver/hardware issue. As I said, the two servers have 6 NICs each. These are: bge0, bge1: BCM5750, integrated on the motherboard bge2, bge3: BCM5704, PCIX card bge4, bge5: BCM5704, PCIX card ... I can instantly ping the other machine after booting up when using bge0, bge1 or bge2 on both machines. I cannot initially ping the other machine when using bge3, bge4 or bge5. Since you suspect hardware, can you physically switch bge2/3/4/5 around in the PCI chain? Like, now bge4 becomes new bge2. If the OS still gives problems from the new bge3 onwards, one might suspect the PCI card or something in PCI interface (ordering/bios interrupt clashes/ X) at which point I'd take it to -hardware or -stable with a verbose boot message attached. -- Mel People using reply to all on lists, must think I need 2 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange arp problem with bge nics
Dear all, I've got two xSeries 346 servers here with a total of 6 Broadcom gigabit NIC's each. I'm going to build a firewall with them, but right now I'm in an early testing stage. The OS is FreeBSD 6.2-RELEASE for amd64. Each of the machines is currently configured to have an IP from our internal LAN on bge0. I use that link to ssh into the machines for testing purposes. (This is a temporary solution, of course). Both machines have their bge0 connected to our primary switch, where dozens of other computers are connected as well. Networking works normally here. Each machine also has got an IP address from a different network on the respective bge5 interface. The bge5 interfaces are connected to a switch having no other connections, i.e. this is a two machine network for testing purposes. My problem is I can ping machine #2 from machine #1 when using the IP addresses configured on the bge1 NICs. I cannot ping the other machine when using the IP addresses configured on the bge5 NICs as ARP entries remain incomplete. I can then configure bge5 to promiscous mode on one machine, and after about 10 seconds the ping starts working. Here's what ipconfig and netstat -nr say right after booting: Machine #1: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet XX.XX.159.253 netmask 0xfe00 broadcast XX.XX.159.255 ether 00:14:5e:ac:71:c9 bge5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet XX.XX.248.158 netmask 0xff00 broadcast XX.XX.248.255 ether 00:10:18:11:72:40 Destination GatewayFlagsRefs Use Netif default 141.58.159.254 UGS 00 bge0 127.0.0.1 127.0.0.1 UH 00lo0 XX.XX.158/23 link#1 UC 00 bge0 XX.XX.158.1 00:17:f2:93:01:30 UHLW13 bge0 XX.XX.159.254 00:04:76:19:03:de UHLW20 bge0 XX.XX.248/24 link#6 UC 00 bge5 Machine #2: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet XX.XX.159.252 netmask 0xfe00 broadcast XX.XX.159.255 ether 00:14:5e:b4:2e:82 bge5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet XX.XX.248.254 netmask 0xff00 broadcast XX.XX.248.255 ether 00:10:18:11:6f:45 Destination GatewayFlagsRefs Use Netif default XX.XX.159.254 UGS 00 bge0 127.0.0.1 127.0.0.1 UH 00lo0 XX.XX.158/23 link#1 UC 00 bge0 XX.XX.158.1 00:17:f2:93:01:30 UHLW1 14 bge0 XX.XX.159.254 00:04:76:19:03:de UHLW20 bge0 XX.XX.248/24 link#6 UC 00 bge5 Now, if I ping XX.XX.248.254 from machine #1, I get Sendto: Host is down. The ARP table looks like this: x.de (XX.XX.248.254) at (incomplete) on bge5 [ethernet] This goes on indefinitely. I can then do ifconfig bge5 promisc on ANY of the two machines (e.g. I can even do it on machine #2, or I can do it on machine #1!) and about 10 seconds later, the ARP table on machine #1 gets completed and from then on, the network connection will work normally, even if I do ifconfig bge5 -promisc after that. I can even delete the arp table entries on both machines, but they will be reinstated as soon as I issue the next ping. I need to reboot to trigger the strange behaviour again. I have already tried to use a different switch and have also tried using a crosslink cable. Both show the same behaviour. This is a vanilla install of 6.2-RELEASE. No firewalling of any sort is enabled yet. The only thing I did is add option BRIDGE to the kernel config on machine #1 and build a custom kernel (i.e. my kernel config on machine #1 only differs from GENERIC in that one line. Machine #2 still has the binary kernel from CD.) Am I overlooking something or is this a bug? What should I do next? I am not going to run the machines in the particular configuration described above, but I am now worried that there might be a bug in the bge driver and that I should not put these machines in production at all, at least not with FreeBSD. Regards Tobias -- Universität Stuttgart|Fakultät für Architektur und Stadtplanung|casinoIT 70174 Stuttgart Geschwister-Scholl-Straße 24D T +49 (0)711 121-4228 F +49 (0)711 121-4276 E [EMAIL PROTECTED] I http://www.casino.uni-stuttgart.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
Hi, I have further news on this problem. It really seems to be a driver/hardware issue. As I said, the two servers have 6 NICs each. These are: bge0, bge1: BCM5750, integrated on the motherboard bge2, bge3: BCM5704, PCIX card bge4, bge5: BCM5704, PCIX card I have now greatly simplified the test case: Only connect any two interfaces with the same number with a crosslink cable or an otherwise unused switch. Assign two IP addresses from within the same subnet. E.g., make bge0 on machine #1 10.0.0.1 and bge0 on machine #2 10.0.0.2. Don't connect anything else. I can instantly ping the other machine after booting up when using bge0, bge1 or bge2 on both machines. I cannot initially ping the other machine when using bge3, bge4 or bge5. In this case, I first have to put one of the interfaces into promiscuous mode, wait for the ping to come through, then disable promiscuous mode. Incidentally, the working interfaces all sit on IRQ3, while the other three sit on IRQ7, IRQ11 and IRQ5, respectively. Where do I take this from here? I need at least four interfaces working for the configuration I need to implement. I could do away with the other two, but four is the minimum I need. Incidentally, another option to wake up the ping, apart from setting and unsetting promiscous modem, is to connect any Windows machine to the same switch. As soon as a Windows machine is present on the switch, the ping between the two FreeBSD machines works right out from the start. This looks like a minor issue at first glance, because everything seems to be normal once the ping is set going, and I could just write a script that enables promiscuous mode on startup for a certain amount of time, and there will always be Windows boxes on the network anyway. However, I am now wary that there might be other hidden bugs or hardware problems, and I have no use for those in a production machine ... Best regards Tobias -- Universität Stuttgart|Fakultät für Architektur und Stadtplanung|casinoIT 70174 Stuttgart Geschwister-Scholl-Straße 24D T +49 (0)711 121-4228 F +49 (0)711 121-4276 E [EMAIL PROTECTED] I http://www.casino.uni-stuttgart.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
On Friday 31 August 2007 21:55, Tobias Ernst wrote: Hi, I have further news on this problem. It really seems to be a driver/hardware issue. As I said, the two servers have 6 NICs each. These are: bge0, bge1: BCM5750, integrated on the motherboard bge2, bge3: BCM5704, PCIX card bge4, bge5: BCM5704, PCIX card I have now greatly simplified the test case: Only connect any two interfaces with the same number with a crosslink cable or an otherwise unused switch. Assign two IP addresses from within the same subnet. E.g., make bge0 on machine #1 10.0.0.1 and bge0 on machine #2 10.0.0.2. Don't connect anything else. I can instantly ping the other machine after booting up when using bge0, bge1 or bge2 on both machines. I cannot initially ping the other machine when using bge3, bge4 or bge5. In this case, I first have to put one of the interfaces into promiscuous mode, wait for the ping to come through, then disable promiscuous mode. Incidentally, the working interfaces all sit on IRQ3, while the other three sit on IRQ7, IRQ11 and IRQ5, respectively. Where do I take this from here? I need at least four interfaces working for the configuration I need to implement. I could do away with the other two, but four is the minimum I need. Incidentally, another option to wake up the ping, apart from setting and unsetting promiscous modem, is to connect any Windows machine to the same switch. As soon as a Windows machine is present on the switch, the ping between the two FreeBSD machines works right out from the start. This looks like a minor issue at first glance, because everything seems to be normal once the ping is set going, and I could just write a script that enables promiscuous mode on startup for a certain amount of time, and there will always be Windows boxes on the network anyway. However, I am now wary that there might be other hidden bugs or hardware problems, and I have no use for those in a production machine ... If you take a look here http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c you will see some problems with some chipsets regarding auto negotiation. http://www.freebsd.org/cgi/query-pr.cgi?pr=94833 How all these apply to your case? Did you try down-ing and up-ing the interfaces? Did you try without forcing a link speed(check ifconfig -m) Just wild guesses... HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
On Friday 31 August 2007 22:30, I correctly wrote: Did you try without forcing a link speed(check ifconfig -m) s/without // anything useful in dmesg? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
Nikos Vassiliadis schrieb: On Friday 31 August 2007 22:30, I correctly wrote: Did you try without forcing a link speed(check ifconfig -m) s/without // anything useful in dmesg? No, nothing at all in dmesg. I don't think this is an auto negotiation issue. How can a Windows machine that is connected to the same switch as my two FreeBSD machines and does not even talk to them explicitly influence the autonegotation of the FreeBSD NIC? If the NIC were not properly negotiated, it would not even see the broadcasts of the Windows machine, I would think. It must be something with ARP and TCP/IP in connection with that particular river, I suppose. The cards properly negotiate whatever the particular switch (tried several, 100 and 1000) supports and I also tried setting various fixed rates and duplex settings when using a cross link cable. This does not change anything. The interface is live and running, it just does not properly perform ARP up to the point when I either put the interface in promiscuous mode for a while or send some Windows broadcasts. Regards Tobias -- Universität Stuttgart|Fakultät für Architektur und Stadtplanung|casinoIT 70174 Stuttgart Geschwister-Scholl-Straße 24D T +49 (0)711 121-4228 F +49 (0)711 121-4276 E [EMAIL PROTECTED] I http://www.casino.uni-stuttgart.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange arp problem with bge nics
On Fri, 31 Aug 2007 22:48:35 +0200, Tobias Ernst [EMAIL PROTECTED] wrote: I don't think this is an auto negotiation issue. How can a Windows machine that is connected to the same switch as my two FreeBSD machines and does not even talk to them explicitly influence the autonegotation of the FreeBSD NIC? I didn't say that a Windows machine can influence adversely a FreeBSD machine. My question was about the NIC's link status. It's crystal clear now that your links are up. But: (Symptom is that the NIC reports the link as up (PCS synched) but no traffic can be exchanged.) This message is from revision 1.71 of the bge driver. In short I would really try what's recommended there. It must be something with ARP and TCP/IP in connection with that particular river, I suppose. hm, there's nothing bge-specific in TCP/IP nor ARP. The cards properly negotiate whatever the particular switch (tried several, 100 and 1000) supports and I also tried setting various fixed rates and duplex settings when using a cross link cable. This does not change anything. The interface is live and running, it just does not properly perform ARP up to the point when I either put the interface in promiscuous mode for a while or send some Windows broadcasts. hm, what happens if you disable ARP? ifconfig intX -arp and use static ARP? I'd go the driver-fiddling way myself. HTH Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[multiple NIC issue] two NICs in the same subnet problem.
Hi, I found an issue for a long time. For test requirement without any switch/hub: One host has two NICs and with the same subnet setting. (local)NIC1: 10.0.0.1/8 (local)NIC2: 10.0.0.2/8 (direct connect peer) 10.0.0.10/8 (direct connect peer) 10.0.0.20/8 ping command: #ping 10.0.0.10 -c 5 -S 10.0.0.1 In Linux, while I assign source interface and IP address, ex. ping 10.0.0.10 -I eth0 ..packet will be sent by NIC1 ping 10.0.0.20 -I eth1 ..packet will be sent by NIC2 In BSD, while I assign source interface/IP address, packet always be sent by NIC1. The NIC2 looks like dead. Until I set #ifconfig eth0 down and NIC2 would be got up. So the ping command parameter -S would be broke down in this case. The packets format maybe is correct but NIC2 couldn't work. If this is NOT a BUG, please tell me BSD is followed which standard? Or what the purpose of BSD to define this behavior? Thanks Regards Myron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to correctly use 2 on board nics
Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to correctly use 2 on board nics
Ivan Carey wrote: Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan You may want to take a look at if_lacc. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to correctly use 2 on board nics
Tom Judge wrote: Ivan Carey wrote: Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan You may want to take a look at if_lacc. Tom What is if_lacc ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to correctly use 2 on board nics
Ivan Carey wrote: Tom Judge wrote: Ivan Carey wrote: Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan You may want to take a look at if_lacc. Tom What is if_lacc ? My bad, sorry should be if_lagg. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to correctly use 2 on board nics
The most common configuration for using two nic's is one nic is used for your dsl or cable modem connection to your ISP and the second nic services your local LAN. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ivan Carey Sent: Tuesday, June 05, 2007 6:55 AM To: freebsd-questions@freebsd.org Subject: How to correctly use 2 on board nics Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan ___ 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: How to correctly use 2 on board nics
Bob wrote: The most common configuration for using two nic's is one nic is used for your dsl or cable modem connection to your ISP and the second nic services your local LAN. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ivan Carey Sent: Tuesday, June 05, 2007 6:55 AM To: freebsd-questions@freebsd.org Subject: How to correctly use 2 on board nics Hello I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. Any ideas would help. Thanks, Ivan ___ 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] I guess the 'correct' way of using two NICs is really dependent upon what your goal of using two NICs is. Do you want to be able to serve two networks out of the NICs, one from each interface? Do you want to create a gateway of some sort? What is it, exactly, you are trying to accomplish by doing this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to correctly use 2 on board nics
Quoting Ivan Carey [EMAIL PROTECTED]: I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? Manually specifying network_interfaces is deprecated (take that line out). Putting both NIC's on the same subnet and segment but with different IP's like this may not be too useful.. If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. That is because the route to 192.168.1.1 is associated with em0 at this point. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. For that to be most useful you'll want to set something up so they can share the same IP. The lagg(4) (link aggregation) virtual interface has already been mentioned, but I believe it is still only available in -CURRENT. Other possibilities might include attaching ifconfig scripts to link up/down events or [lack of] ping responses on one or both interfaces. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to correctly use 2 on board nics
John Nielsen wrote: Quoting Ivan Carey [EMAIL PROTECTED]: I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? Manually specifying network_interfaces is deprecated (take that line out). Putting both NIC's on the same subnet and segment but with different IP's like this may not be too useful.. If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. That is because the route to 192.168.1.1 is associated with em0 at this point. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. For that to be most useful you'll want to set something up so they can share the same IP. The lagg(4) (link aggregation) virtual interface has already been mentioned, but I believe it is still only available in -CURRENT. Other possibilities might include attaching ifconfig scripts to link up/down events or [lack of] ping responses on one or both interfaces. JN I thought I saw if_lagg MFC'd to RELENG_6 a few weeks back on [EMAIL PROTECTED] After checking cvsweb it is available in RELENG_6. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Netgear WG111 / WG111T USB NICs
Hello, Running 6.2-STABLE on i386... Anyone know if there is support for USB Wireless NICs? I have a Netgear WG111 that is recognized as /dev/ugen0, but that's it. Netgear also makes their T model (WG111T) that has their Super G technolgy that often uses Atheros chipsets. Since Atheros is well supported, anyone know if that one works? -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
recommendations for wireless nics
Hi all, looking for any recommendations regarding wireless lan pci cards and freebsd, please. Thx in advance. Cheers, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recommendations for wireless nics
Don't get the motorolas; you can check, but classically, they all have non-open-source (and therefore unsupported) broadcom chipsets. My usual method is to type in the model number of the card and chipset into a google search, which ususally works. I'd say the atheros cards are most widely used in freebsd, although anything prism/orinoco has been supported forever too. I tried a ralink with my laptop (non pci obviously), but all laptops these days will lock up the bios if you don't put a manufacturer approved card in, so I didn't get to try it. Intel cards are also supported by iwi and ipw(?) drivers. Just type man wlan to get a list of drivers, man for each driver will give you a pretty good idea of what chipsets. Another consideration is that the pci-pcmcia docks are supported in freebsd - I have an atheros card in a proprietary linksys dock for my primary personal server with no hiccups. I don't know under 6.2, but under 6.1 both intel and texas instruments chipsets were supported, but you had to build some propriety/closed source/licenced thingamabob from /usr/ports to get them to work, so they are good after your system is running, but a pain if you are installing and they are your only card. Summary: my best luck has been the atheros. Had some trouble on prism with dhclient not renewing the ip when the link would drop intermittently. Several others reported similar issues. One resolution that I did not try was to use an alternate dhclient package from /usr/ports, don't recall which. Best, Steve On 2/3/07, Paul Eskello [EMAIL PROTECTED] wrote: Hi all, looking for any recommendations regarding wireless lan pci cards and freebsd, please. Thx in advance. Cheers, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recommendations for wireless nics
On Sat, Feb 03, 2007 at 06:53:28PM +0100, Paul Eskello wrote: Hi all, looking for any recommendations regarding wireless lan pci cards and freebsd, please. It is impossible to give a general recommendation like buy brand X, model Y. Manufacturers sometimes switch chipsets on their cards without changing the model number, and brand names may not be available depending on where on the globe you are located. The best advice is to look at all the wireless drivers (zgrep for 802.11 in /usr/share/man/man4/*), and look at cards in shops to identify the chips they use. In my experience, the chipset used is seldom if ever noted in the documentation or on the packaging. Sometimes all the chips (not just the transmitter) are covered under a RF shield, in which case you're out of luck. In my experience, if you go into a computer shop and ask for a 802.11 card with a type Z chipset, the most likely response from the salesperson will be a blank stare. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpkyeToqgFON.pgp Description: PGP signature
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
On Wed, 17 Jan 2007, Ted Mittelstaedt wrote: yes, but guess what - FBSD 6.2 is now released, so just install that and the updated driver is already in the kernel You were just waiting to say that weren't you :) -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, January 15, 2007 7:27 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Mon, 15 Jan 2007, Ted Mittelstaedt wrote: Is the bge driver enabled by default? -Dan I don't know what broadcom chip your MB has but the majority of those cards are supported here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ You should be able to just copy over the 2 files to your src/sys/dev/bge/ directory and recompile your 6.1-release kernel with no problems. I did. Look carefully at the chip on your MB and post the BCM model number on it if this doesen't work. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 13, 2007 5:34 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- [23:49:00] LarpGM: Did my little TP comment scare you off? [23:49:22] ilzarion: no, the shrieking retarded child eating people did -Feb 06, 2001, times apparent. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- When I'm lost, and confused, and trying to make a U-turn, nothing annoys me more than someone telling me to watch out for the tombstone! How often does that happen, Fab? -David Feld Tom Fabry, sometime in High School. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
Heh - I too have had servers that had the nice little catch-22 of you couldn't read a CD in them so you had to do an FTP install - but the current freebsd release didn't have a working ethernet driver for the embedded nic on the server, so while you could boot the server with a floppy, you couldn't install freebsd on it. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, January 18, 2007 12:06 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Wed, 17 Jan 2007, Ted Mittelstaedt wrote: yes, but guess what - FBSD 6.2 is now released, so just install that and the updated driver is already in the kernel You were just waiting to say that weren't you :) -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, January 15, 2007 7:27 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Mon, 15 Jan 2007, Ted Mittelstaedt wrote: Is the bge driver enabled by default? -Dan I don't know what broadcom chip your MB has but the majority of those cards are supported here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ You should be able to just copy over the 2 files to your src/sys/dev/bge/ directory and recompile your 6.1-release kernel with no problems. I did. Look carefully at the chip on your MB and post the BCM model number on it if this doesen't work. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 13, 2007 5:34 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- [23:49:00] LarpGM: Did my little TP comment scare you off? [23:49:22] ilzarion: no, the shrieking retarded child eating people did -Feb 06, 2001, times apparent. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- When I'm lost, and confused, and trying to make a U-turn, nothing annoys me more than someone telling me to watch out for the tombstone! How often does that happen, Fab? -David Feld Tom Fabry, sometime in High School. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
yes, but guess what - FBSD 6.2 is now released, so just install that and the updated driver is already in the kernel Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, January 15, 2007 7:27 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Mon, 15 Jan 2007, Ted Mittelstaedt wrote: Is the bge driver enabled by default? -Dan I don't know what broadcom chip your MB has but the majority of those cards are supported here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ You should be able to just copy over the 2 files to your src/sys/dev/bge/ directory and recompile your 6.1-release kernel with no problems. I did. Look carefully at the chip on your MB and post the BCM model number on it if this doesen't work. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 13, 2007 5:34 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- [23:49:00] LarpGM: Did my little TP comment scare you off? [23:49:22] ilzarion: no, the shrieking retarded child eating people did -Feb 06, 2001, times apparent. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ 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: Broadcom Nics in Tyan Transport GT24 (B3992)
I don't know what broadcom chip your MB has but the majority of those cards are supported here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ You should be able to just copy over the 2 files to your src/sys/dev/bge/ directory and recompile your 6.1-release kernel with no problems. I did. Look carefully at the chip on your MB and post the BCM model number on it if this doesen't work. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 13, 2007 5:34 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
On Mon, 15 Jan 2007, Ted Mittelstaedt wrote: Is the bge driver enabled by default? -Dan I don't know what broadcom chip your MB has but the majority of those cards are supported here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ You should be able to just copy over the 2 files to your src/sys/dev/bge/ directory and recompile your 6.1-release kernel with no problems. I did. Look carefully at the chip on your MB and post the BCM model number on it if this doesen't work. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 13, 2007 5:34 AM Subject: Re: Broadcom Nics in Tyan Transport GT24 (B3992) On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- [23:49:00] LarpGM: Did my little TP comment scare you off? [23:49:22] ilzarion: no, the shrieking retarded child eating people did -Feb 06, 2001, times apparent. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? -Dan Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- You're not normal! -Michael G. Kessler, referring to my modem online time. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
--On January 13, 2007 8:34:50 AM -0500 Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: On Fri, 12 Jan 2007, Ted Mittelstaedt wrote: Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Which driver is that? My 6.1 install won't see them at all: pci4: PCI bus on pcib4 pci4: network, ethernet at device 4.0 (no driver attached) pci4: network, ethernet at device 4.1 (no driver attached) Also, I'm running 6.1-RELEASE, will the cvs drivers from CURRENT work? They're working for me. grep bce /var/run/dmesg.boot bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 mem 0xf400-0xf5ff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: MII bus on bce0 bce0: Ethernet address: 00:13:72:fb:2a:ad bce1: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 mem 0xf800-0xf9ff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus1: MII bus on bce1 bce1: Ethernet address: 00:13:72:fb:2a:ab You have to get the if_bce.c source that has this in it: // /* BCE Driver Version */ // char bce_driver_version[] = v0.9.6; and then recompile your kernel. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
question about Intel NICs
I have a machine that's getting re-purposed, and - based on comments made here - I'd like to replace the RealTek-based NIC with Intel. However ... I've never dealt with Intel cards before, and I'm not certain which model is the right choice. A search of the Intel web site suggests either the PRO/1000 MT or the PRO/1000 GT. Given the machine is vanilla PCI and will be mostly a workstation with some light server functionality, I'm open to counsel. (Preferably with data, but anecdote will do. :-) 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: question about Intel NICs
On Sat, Jan 13, 2007 at 03:42:22PM -0500, Robert Huff wrote: I have a machine that's getting re-purposed, and - based on comments made here - I'd like to replace the RealTek-based NIC with Intel. However ... I've never dealt with Intel cards before, and I'm not certain which model is the right choice. A search of the Intel web site suggests either the PRO/1000 MT or the PRO/1000 GT. Given the machine is vanilla PCI and will be mostly a workstation with some light server functionality, I'm open to counsel. (Preferably with data, but anecdote will do. :-) You probably want the PRO/1000 GT. The PRO/1000 MT is a somewhat older design and the desktop version of the MT is probably a bit difficult to get hold of today. (The server version of the pro/1000 mt has a 64-bit connector which would not confer any extra benefit to you if you just have a normal 32-bit PCI slot.) Both the MT and GT NICs should work fine for you but the GT model is probably both easier and cheaper to find in stores today. FWIW I have a PRO/1000 GT card in one of my machines and it works just fine. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Broadcom Nics in Tyan Transport GT24 (B3992)
Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom Nics in Tyan Transport GT24 (B3992)
Use the latest Broadcom driver from FreeBSD CVS. The one included in 6.1 release is buggy. Ted - Original Message - From: Dan Mahoney, System Admin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 12, 2007 5:02 PM Subject: Broadcom Nics in Tyan Transport GT24 (B3992) Hey all, I have a Transport GT24 (B3992 Motherboard), and while it has one intel nic which works well, I'd like to be able to use the onboard broadcom network cards. Is there a known way of making them work? I seem to recall some dealy where you could use a windows driver? -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ 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]
Broadcomm NetXtreme BCM5708 NICs and 6.1 RELEASE
I'm posting this for documentary purposes in case someone has this problem and wants to find the answer. Under the 6.1 RELEASE, with all sources cvsup'd to current, both world and kernel rebuilt, the Broadcommm NetExtreme 5708 NICs will fall over under very light load when using a remote connection. (Console outbound connections work fine.) For example, trying to build apache22 from ports causes the NICs to fail, and only a reboot will fix the problem. The console error message is Error mapping mbuf into TX chain! Not good for servers. :-) The solution is to update the if_bce.c source to version 0.9.6 from the current 0.9.5, then rebuild world and kernel. Here's a webpage that has a brief explanation and a link to the updated source file: http://www.ifdnrg.com/freebsd_broadcom_dell_1950.htm Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Binding NICs
Is there currently any way to bind three network interfaces to a single IP address? With our NetApp (yeah, I realize its a whole different animal, but still), we can use the vif interface or virtual interface to increase bandwidth to the device. I've looked at carp and bridging and I don't think these are going to do what I'm wanting - just wondering if there's some command I'm not familiar with to bind network interfaces so they load-balance... Thanks, D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Binding NICs
In the last episode (Aug 16), Derrick T. Woolworth said: Is there currently any way to bind three network interfaces to a single IP address? With our NetApp (yeah, I realize its a whole different animal, but still), we can use the vif interface or virtual interface to increase bandwidth to the device. I've looked at carp and bridging and I don't think these are going to do what I'm wanting - just wondering if there's some command I'm not familiar with to bind network interfaces so they load-balance... Try ng_fec or ng_one2many. Make sure you configure trunking on whatever switch you attach the ports too, also. -- 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]
Help! FreeBSD Webserver with two NICs
Hello Gurus I think you might help me I want to run a webserver which will be having a good traffic. At present, I have a 100/10 Mbps internet connection (fiber-optics) but with this connection I cannot get Fixed IP for the webserver. To get the Fixed-IP, I am getting a 24/1 Mbps internet line through Telephone line. But I am just in doubt that my webserver might not be able to server the documents with good serving speed due to 1 Mbps upstream... So, I came to an idea that if I use two NICs, one NIC bounded to 100/10 Mbps to serve the pages and one which would be bound with 24/1 Mbps connection with Fixed-IP to litsen the requests my Question is that is it possible and if so, how? I am planning to install FreeBSD as a OS. Thanks VJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Help! FreeBSD Webserver with two NICs
I think you might help me I want to run a webserver which will be having a good traffic. At present, I have a 100/10 Mbps internet connection (fiber-optics) but with this connection I cannot get Fixed IP for the webserver. To get the Fixed-IP, I am getting a 24/1 Mbps internet line through Telephone line. But I am just in doubt that my webserver might not be able to server the documents with good serving speed due to 1 Mbps upstream... So, I came to an idea that if I use two NICs, one NIC bounded to 100/10 Mbps to serve the pages and one which would be bound with 24/1 Mbps connection with Fixed-IP to litsen the requests my Question is that is it possible and if so, how? I am planning to install FreeBSD as a OS. Holy cow where do you live for those speeds? Can you use a service like DynDNS.org and just use the 100/10 connection? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! FreeBSD Webserver with two NICs
Maan Jee wrote: Hi! At present, I have a 100/10 Mbps internet connection (fiber-optics) but with this connection I cannot get Fixed IP for the webserver. Sweet. Why-O-Why won't they give you a static IP on that line? :) Here (Sweden) we have full 100/100mbit to some appartment buildings WITH fixed IP. But basicly you can only pull/push 1mbit, since there is a 300GB traffic limit imposed. :) So, I came to an idea that if I use two NICs, one NIC bounded to 100/10 Mbps to serve the pages and one which would be bound with 24/1 Mbps connection with Fixed-IP to litsen the requests my Question is that is it possible and if so, how? Not possible the easy way: you can't reply to a request from a different IP than the one the request was sent to due to TCP socket limitations. The clients expects an answer from IP x on the socket it opened, but instead receives unknown data on a new socket coming from IP Y. To get this working you would need a third fixed IP/machine somewhere and do tunneling with two channels combined. That way your inbound traffic would go via the fixed IP and the outbound via the big pipe. Giving me an idea right away: if you have any such point available close by with a fixed IP (some machine somewhere in a rack with good bandwidth): tunnel it to your home. But if you would have that, you wouldn't have the webserver at home anyway, would you? :) -- Robin Vley F/X Services Managed Hosting http://www.fx-services.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipf and ipnat stopped working, no routing between nics.
Hi, I rebooted my machine last night, and everything started working again. But no, I didnt check that. And after I was looking at some sysctls late last night, I did speculate about whether those you mention were right or not. Problem resolved, and thanks for the help :) ps. Sorry I accidentally spammed the list. It didnt seem as if my emails went through at the time. On 3/31/06, Erik Norgaard [EMAIL PROTECTED] wrote: Daniel A. wrote: Hi, I run a FreeBSD 6.0 at home in my closet. Yesterday, while I was linking IRCd services with a friend of mine, my router completely stopped routing any packets between the internal nic (sis0) and the external nic (rl0). The only thing that I can think of, whoich could have caused this, is that I ran ettercap on the server to diagnose why our servers wouldnt link. I did NOT run any ARP poisoning or DNS spoofing attacks on myself. But I didnt notice if the routing stopped at that point, or later, because I could always connect to my server, and the server could always connect to the internet. The situation is still the same. I have tried to do - ipf -Fa -f /etc/ipf.rules; ipnat -FC -f /etc/ipnat.rules - Didnt help - cd /etc/rc.d; ./ipfilter restart; ./ipnat restart - Didnt help - Launch ettercap again and exit cleanly after telling it to stop sniffing. A tcpdump reveals that, indeed, no packets at all make it from sis0 to rl0. So my conclusion is that ipnat forgot how to route between the two interfaces. Could anyone please give some pointers? did you check # sysctl -a |grep forward you should have net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipf and ipnat stopped working, no routing between nics.
(My apologies if you're recieving this email for the third time. It doesnt seem as the previous ones reached the list) Hi, I run a FreeBSD 6.0 at home in my closet. Yesterday, while I was linking IRCd services with a friend of mine, my router completely stopped routing any packets between the internal nic (sis0) and the external nic (rl0). The only thing that I can think of, whoich could have caused this, is that I ran ettercap on the server to diagnose why our servers wouldnt link. I did NOT run any ARP poisoning or DNS spoofing attacks on myself. But I didnt notice if the routing stopped at that point, or later, because I could always connect to my server, and the server could always connect to the internet. The situation is still the same. I have tried to do - ipf -Fa -f /etc/ipf.rules; ipnat -FC -f /etc/ipnat.rules - Didnt help - cd /etc/rc.d; ./ipfilter restart; ./ipnat restart - Didnt help - Launch ettercap again and exit cleanly after telling it to stop sniffing. A tcpdump reveals that, indeed, no packets at all make it from sis0 to rl0. So my conclusion is that ipnat forgot how to route between the two interfaces. Could anyone please give some pointers? Included stuff: _ipf.rules [EMAIL PROTECTED] etc $ cat ipf.rules # Let clients behind the firewall send out to the internet, and replies to # come back in by keeping state. pass out quick on rl0 proto tcp all flags S keep state pass out quick on rl0 proto udp all keep state pass out quick on rl0 proto icmp all keep state # Allow everything on local net pass in quick on sis0 all pass out quick on sis0 all # loopback stuff pass in quick on lo0 all pass out quick on lo0 all # Since nothing should be coming from these address ranges, block them block in quick on rl0 from 192.168.0.0/16 to any block in quick on rl0 from 172.16.0.0/12 to any block in quick on rl0 from 127.0.0.0/8 to any block in quick on rl0 from 10.0.0.0/8 to any block in quick on rl0 from 169.254.0.0/16 to any block in quick on rl0 from 192.0.2.0/24 to any block in quick on rl0 from 204.152.64.0/23 to any block in quick on rl0 from 224.0.0.0/3 to any # Let's let people access the services running behind this system # Let's let people access the services running on this system #pass in quick on rl0 proto tcp from any to any port 3 5 flags S keep state #Passive FTP #pass in quick on rl0 proto tcp from any to any port = 20 flags S keep state #Active FTP #pass in quick on rl0 proto tcp from any to any port = 21 flags S keep state #FTP pass in quick on rl0 proto tcp from any to any port = 22 flags S keep state #SSH pass in quick on rl0 proto tcp from any to any port = 80 flags S keep state #WWW pass in quick on rl0 proto tcp from any to any port = 113 flags S keep state #oidentd pass in quick on rl0 proto udp from any to any port = 123 keep state #ntpd pass in quick on rl0 proto tcp from any to any port = 6697 flags S keep state #ircd, SSL pass in quick on rl0 proto tcp from any to any port = 6667 flags S keep state #ircd, non-SSL #pass in quick on rl0 proto tcp from any to any port = 7029 flags S keep state #irc link pass in quick on rl0 proto tcp from any to 192.168.0.2/32 port = 9541 keep state pass in quick on rl0 proto udp from any to 192.168.0.2/32 port = 9542 keep state # Steam Dedicated Server #pass in quick on rl0 proto udp from any to any port = 1200 # Friends network #pass in quick on rl0 proto udp from any to any port 26999 27016 # Gameport #pass in quick on rl0 proto udp from any to any port = 27020 #pass in quick on rl0 proto tcp from any to any port 27029 27040 #pass in quick on rl0 proto tcp from any to any port = 27015 # SRCDS Rcon # Block everything else block in quick on rl0 _ipf.rules END _ipnat.rules #rdr rl0 0/0 port 9541 - 192.168.0.2 port 9541 tcp #rdr rl0 0/0 port 9542 - 192.168.0.2 port 9542 udp map rl0 192.168.0.0/29 - 0/32 proxy port 21 ftp/tcp #map rl0 0.0.0.0/0 - 0/32 proxy port 21 ftp/tcp map rl0 192.168.0.0/29 - 0/32 portmap tcp/udp 1025:65000 map rl0 192.168.0.0/29 - 0/32 _ipnat.rules END _ifconfig -a [EMAIL PROTECTED] etc $ ifconfig -a fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 options=8VLAN_MTU ether 02:00:0a:04:69:d1 ch 1 dma -1 sis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::20a:e6ff:fe53:fc1e%sis0 prefixlen 64 scopeid 0x2 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 ether 00:0a:e6:53:fc:1e media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:2ff:fe00:27f3%rl0 prefixlen 64 scopeid 0x3 inet 87.49.144.133 netmask 0xff80 broadcast 87.49.144.255 ether 00:b0:02:00:27:f3 media: Ethernet
ipf and ipnat stopped working, no routing between nics.
Hi, I run a FreeBSD 6.0 at home in my closet. Yesterday, while I was linking IRCd services with a friend of mine, my router completely stopped routing any packets between the internal nic (sis0) and the external nic (rl0). The only thing that I can think of, whoich could have caused this, is that I ran ettercap on the server to diagnose why our servers wouldnt link. I did NOT run any ARP poisoning or DNS spoofing attacks on myself. But I didnt notice if the routing stopped at that point, or later, because I could always connect to my server, and the server could always connect to the internet. The situation is still the same. I have tried to do - ipf -Fa -f /etc/ipf.rules; ipnat -FC -f /etc/ipnat.rules - Didnt help - cd /etc/rc.d; ./ipfilter restart; ./ipnat restart - Didnt help - Launch ettercap again and exit cleanly after telling it to stop sniffing. A tcpdump reveals that, indeed, no packets at all make it from sis0 to rl0. So my conclusion is that ipnat forgot how to route between the two interfaces. Could anyone please give some pointers? ifconfig Description: Binary data ipf.rules Description: Binary data ipnat.rules Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipf and ipnat stopped working, no routing between nics.
Daniel A. wrote: Hi, I run a FreeBSD 6.0 at home in my closet. Yesterday, while I was linking IRCd services with a friend of mine, my router completely stopped routing any packets between the internal nic (sis0) and the external nic (rl0). The only thing that I can think of, whoich could have caused this, is that I ran ettercap on the server to diagnose why our servers wouldnt link. I did NOT run any ARP poisoning or DNS spoofing attacks on myself. But I didnt notice if the routing stopped at that point, or later, because I could always connect to my server, and the server could always connect to the internet. The situation is still the same. I have tried to do - ipf -Fa -f /etc/ipf.rules; ipnat -FC -f /etc/ipnat.rules - Didnt help - cd /etc/rc.d; ./ipfilter restart; ./ipnat restart - Didnt help - Launch ettercap again and exit cleanly after telling it to stop sniffing. A tcpdump reveals that, indeed, no packets at all make it from sis0 to rl0. So my conclusion is that ipnat forgot how to route between the two interfaces. Could anyone please give some pointers? did you check # sysctl -a |grep forward you should have net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dual bge nics slow transfer - no transfer
I have a tyan k8wd with dual bge nics but they are painfully slow on transfer rates. Is there something I need to put in the hints file to fix this?? Thanks! dmesg output Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #1: Tue Mar 14 05:43:23 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/QUAD Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Dual Core AMD Opteron(tm) Processor 270 (1989.05-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f12 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SS Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,b25,LM,3DNow+,3DNow Hyperthreading: 2 logical CPUs real memory = 4227792896 (4031 MB) avail memory = 4083822592 (3894 MB) ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 5 on acpi0 pci_link1: ACPI PCI Link LNKB irq 9 on acpi0 pci_link2: ACPI PCI Link LNKC irq 11 on acpi0 pci_link3: ACPI PCI Link LNKD irq 10 on acpi0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci3: ACPI PCI bus on pcib1 ohci0: OHCI (generic) USB controller mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: OHCI (generic) USB controller mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered atapci0: SiI 3114 SATA150 controller port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xac00-0xac03,0xa880-0xa88f ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ata4: ATA channel 2 on atapci0 ata5: ATA channel 3 on atapci0 pci3: display, VGA at device 6.0 (no driver attached) fxp0: Intel 82551 Pro/100 Ethernet port 0xa800-0xa83f mem 0xfeafb000-0xfeafbfff,0xfeaa-0xfeab irq 18 at miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:41:62:0d isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci1: AMD 8111 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pc ata0: ATA channel 0 on atapci1 ata1: ATA channel 1 on atapci1 pci0: serial bus, SMBus at device 7.2 (no driver attached) pci0: bridge at device 7.3 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfc80-0xfc80,0xfc8f-0xfc8f miibus1: MII bus on bge0 brgphy0: BCM5704 10/100/1000baseTX PHY on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:41:62:4c bge1: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfc83-0xfc83,0xfc82-0xfc82 miibus2: MII bus on bge1 brgphy1: BCM5704 10/100/1000baseTX PHY on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:41:62:4d pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci1: ACPI PCI bus on pcib3 pci0: base peripheral, interrupt controller at device 11.1 (no driver attached) acpi_button0: Power Button on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1
RE: dual bge nics slow transfer - no transfer
This was posted a few weeks back. net.inet.tcp.inflight.enable If I set this value to 0, my bandwitdh problems are resolved. Give this a try and post back if it solved your problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Busby Sent: Monday, March 20, 2006 12:55 PM To: freebsd-questions@freebsd.org Subject: dual bge nics slow transfer - no transfer I have a tyan k8wd with dual bge nics but they are painfully slow on transfer rates. Is there something I need to put in the hints file to fix this?? Thanks! dmesg output Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #1: Tue Mar 14 05:43:23 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/QUAD Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Dual Core AMD Opteron(tm) Processor 270 (1989.05-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f12 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR ,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SS Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,b25,LM,3DNow+,3DNow Hyperthreading: 2 logical CPUs real memory = 4227792896 (4031 MB) avail memory = 4083822592 (3894 MB) ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 5 on acpi0 pci_link1: ACPI PCI Link LNKB irq 9 on acpi0 pci_link2: ACPI PCI Link LNKC irq 11 on acpi0 pci_link3: ACPI PCI Link LNKD irq 10 on acpi0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci3: ACPI PCI bus on pcib1 ohci0: OHCI (generic) USB controller mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: OHCI (generic) USB controller mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered atapci0: SiI 3114 SATA150 controller port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xac00-0xac03,0xa880-0xa88 f ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ata4: ATA channel 2 on atapci0 ata5: ATA channel 3 on atapci0 pci3: display, VGA at device 6.0 (no driver attached) fxp0: Intel 82551 Pro/100 Ethernet port 0xa800-0xa83f mem 0xfeafb000-0xfeafbfff,0xfeaa-0xfeab irq 18 at miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:41:62:0d isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci1: AMD 8111 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pc ata0: ATA channel 0 on atapci1 ata1: ATA channel 1 on atapci1 pci0: serial bus, SMBus at device 7.2 (no driver attached) pci0: bridge at device 7.3 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfc80-0xfc80,0xfc8f-0xfc8f miibus1: MII bus on bge0 brgphy0: BCM5704 10/100/1000baseTX PHY on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:41:62:4c bge1: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfc83-0xfc83,0xfc82-0xfc82 miibus2: MII bus on bge1 brgphy1: BCM5704 10/100/1000baseTX PHY on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:41:62:4d pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci1: ACPI PCI bus on pcib3 pci0: base peripheral, interrupt controller at device
Re: dual bge nics slow transfer - no transfer
On Mon, 20 Mar 2006 09:55:29 -0800 (PST), in sentex.lists.freebsd.questions you wrote: I have a tyan k8wd with dual bge nics but they are painfully slow on transfer rates. Is there something I need to put in the hints file to fix this?? Thanks! Hi, There are a lot of fixes to the bge driver in 6.1, as well as other things. I would try there first and if there is still an issue, post more details to the list on how you are testing. ---Mike Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 [EMAIL PROTECTED], (http://www.tancsa.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to properly set-up multiple NICs?
Hi, I have a short and surely straightforward question: I want to set-up two NICs on two of my FBSD 5.x servers. Each server will have a dedicated NIC for all outside world traffic, and between the two machines I want to set-up a 192.168.1.x local network via a cross-wire cable, dedicated to local syncing of both machines. I am assuming the proper way to do this is to simply (using sysinstall) configure one NIC with the real live IP address, gateway, mask setting etc., hooked up to the outside world, and the other one with a 192.168.1.x IP address, directly connected to the other machine's similarly (though with a different IP address, of course) configured 192.168.1.y IP address over a cross-wire. Correct, or am I missing something? Also: when not using sysinstall: is /etc/rc.conf the only location where such settings need to be made, or are there other files as well that need to be manipulated for multiple NICs? Note: Normally I would simply test this myself and make it work, but tomorrow I'll have to add my new second server to the production environment and my current live machine is one of the two machines that need to be reconfigured. As I'll have preciously little time allocated for the installation, I want to get as much anticipated in advance as possible... Cheers, and tnx for any and all replies! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to properly set-up multiple NICs?
On 10/12/05, Olaf Greve [EMAIL PROTECTED] wrote: Hi, I have a short and surely straightforward question: I want to set-up two NICs on two of my FBSD 5.x servers. Each server will have a dedicated NIC for all outside world traffic, and between the two machines I want to set-up a 192.168.1.x local network via a cross-wire cable, dedicated to local syncing of both machines. I am assuming the proper way to do this is to simply (using sysinstall) configure one NIC with the real live IP address, gateway, mask setting etc., hooked up to the outside world, and the other one with a 192.168.1.x IP address, directly connected to the other machine's similarly (though with a different IP address, of course) configured 192.168.1.y IP address over a cross-wire. Correct, or am I missing something? Also: when not using sysinstall: is /etc/rc.conf the only location where such settings need to be made, or are there other files as well that need to be manipulated for multiple NICs? Note: Normally I would simply test this myself and make it work, but tomorrow I'll have to add my new second server to the production environment and my current live machine is one of the two machines that need to be reconfigured. As I'll have preciously little time allocated for the installation, I want to get as much anticipated in advance as possible... Cheers, and tnx for any and all replies! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I don't think you've missed anything. In /etc/rc.conf you can add something like: ifconfig_rl0=inet 192.168.17.1 netmask 0xff00 ifconfig_lo0_alias0=inet 172.17.0.1 netmask 0x ifconfig_vge0=dhcp ...to give you the general idea. It's enough to bring the NICs up and running, but then consider DNS and other issues that provide for a networking environment. Good luck, Andrew P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to properly set-up multiple NICs?
Hi, Tnx for the reply! I don't think you've missed anything. Good! That's what I also thought, but I just wanted to be sure. :) In /etc/rc.conf you can add something like: ifconfig_rl0=inet 192.168.17.1 netmask 0xff00 ifconfig_lo0_alias0=inet 172.17.0.1 netmask 0x ifconfig_vge0=dhcp ...to give you the general idea. It's enough to bring the NICs up and running, but then consider DNS and other issues that provide for a networking environment. Yes, the main entry, i.e., the one for the outside world is set-up like this: ifconfig_rl0=inet 123.45.67.89 netmask 255.255.255.0 defaultrouter=123.45.67.1 hostname=abcdef.nl My other two NICs are identified as re0 and sk0. When setting up one of them, say re0, for the local network I guess I only have to add an entry to /etc/rc.conf like: ifconfig_re0=inet 192.168.1.1 netmask 255.255.255.254 (note: the above gives a very restrictive netmask, as I'll only need the addresses 192.168.1.1 and 192.168.1.2). Would the above be correct, or should there also be an additional defaultrouter entry, next to the one for the outside traffic (e.g. defaultrouter=192.168.1.1)? This wouldn't really make sense to me, as I guess that one would then become 'the' defaultrouter for all traffic (be it local or outside world)... Cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to properly set-up multiple NICs?
On 10/12/05, Olaf Greve [EMAIL PROTECTED] wrote: Hi, Tnx for the reply! I don't think you've missed anything. Good! That's what I also thought, but I just wanted to be sure. :) In /etc/rc.conf you can add something like: ifconfig_rl0=inet 192.168.17.1 netmask 0xff00 ifconfig_lo0_alias0=inet 172.17.0.1 netmask 0x ifconfig_vge0=dhcp ...to give you the general idea. It's enough to bring the NICs up and running, but then consider DNS and other issues that provide for a networking environment. Yes, the main entry, i.e., the one for the outside world is set-up like this: ifconfig_rl0=inet 123.45.67.89 netmask 255.255.255.0 defaultrouter=123.45.67.1 hostname=abcdef.nl My other two NICs are identified as re0 and sk0. When setting up one of them, say re0, for the local network I guess I only have to add an entry to /etc/rc.conf like: ifconfig_re0=inet 192.168.1.1 netmask 255.255.255.254 (note: the above gives a very restrictive netmask, as I'll only need the addresses 192.168.1.1 and 192.168.1.2). Would the above be correct, or should there also be an additional defaultrouter entry, next to the one for the outside traffic (e.g. defaultrouter=192.168.1.1)? This wouldn't really make sense to me, as I guess that one would then become 'the' defaultrouter for all traffic (be it local or outside world)... Cheers! Olafo You'll only need one router, as the neighboring server will be directly accessible (via ethernet). Good that your brought the topic of subnetting up. I'm not going to explain it (any networking book will), for 2 hosts you'll probably need netmask 255.255.255.252. Subnet address will be 192.168.1.0, servers will have xxx.1 and xxx.2, and the broadcast address will be xxx.3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GbE NICs besides em (recommendation wanted)
On 8/31/05, Emanuel Strobl [EMAIL PROTECTED] wrote: Hello, I'm quiet disappointed with the em nics and wanted to try some other GigaBit NICs (1000baseTX only). AFAIK there are re, sk, bge driven cards. Which doesn't saturate a [EMAIL PROTECTED] at 200mbit/s with interrupt load (like em does)? I heard that the re is way better than the not so well rl and although much cheaper than em more efficient. What about bge? Or sk? Any comments welcome, also if I missed a supported family (TX only) I have a gigabit card managed by re and sk drivers at home IIRC ([EMAIL PROTECTED], [EMAIL PROTECTED]). I can run some tests for you this weekend if you wish. -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GbE NICs besides em (recommendation wanted)
Am Mittwoch, 31. August 2005 10:51 CEST schrieb Dmitry Mityugov: On 8/31/05, Emanuel Strobl [EMAIL PROTECTED] wrote: Hello, I'm quiet disappointed with the em nics and wanted to try some other GigaBit NICs (1000baseTX only). AFAIK there are re, sk, bge driven cards. Which doesn't saturate a [EMAIL PROTECTED] at 200mbit/s with interrupt load (like em does)? I heard that the re is way better than the not so well rl and although much cheaper than em more efficient. What about bge? Or sk? Any comments welcome, also if I missed a supported family (TX only) I have a gigabit card managed by re and sk drivers at home IIRC ([EMAIL PROTECTED], [EMAIL PROTECTED]). I can run some tests for you this weekend if you wish. Thank you for the offer, but I thought people had some simple test results in mind. If you next time use rdump or large NFS transfers to another GbE connected (and fast enough) box just watch the system load (I use systat -vm 1) and see what card causes what interrupt load. em cards can't transfer (real files over FTP/NFS) more than 200mbit/s on a [EMAIL PROTECTED], at this level the system load is 100% of which ~80% is interrupt systemload :( Thanks, -Harry pgpGnrJvsz3fA.pgp Description: PGP signature
Re: GbE NICs besides em (recommendation wanted)
Emanuel Strobl wrote: Thank you for the offer, but I thought people had some simple test results in mind. If you next time use rdump or large NFS transfers to another GbE connected (and fast enough) box just watch the system load (I use systat -vm 1) and see what card causes what interrupt load. em cards can't transfer (real files over FTP/NFS) more than 200mbit/s on a [EMAIL PROTECTED], at this level the system load is 100% of which ~80% is interrupt systemload :( Would device polling help in this case? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GbE NICs besides em (recommendation wanted)
Hello, I'm quiet disappointed with the em nics and wanted to try some other GigaBit NICs (1000baseTX only). AFAIK there are re, sk, bge driven cards. Which doesn't saturate a [EMAIL PROTECTED] at 200mbit/s with interrupt load (like em does)? I heard that the re is way better than the not so well rl and although much cheaper than em more efficient. What about bge? Or sk? Any comments welcome, also if I missed a supported family (TX only) Thanks, -Harry pgpf9054Hk1UN.pgp Description: PGP signature
Re: GbE NICs besides em (recommendation wanted)
On 2005-08-31 00:46, Emanuel Strobl [EMAIL PROTECTED] wrote: Hello, I'm quiet disappointed with the em nics and wanted to try some other GigaBit NICs (1000baseTX only). AFAIK there are re, sk, bge driven cards. Which doesn't saturate a [EMAIL PROTECTED] at 200mbit/s with interrupt load (like em does)? I heard that the re is way better than the not so well rl and although much cheaper than em more efficient. What about bge? Or sk? Any comments welcome, also if I missed a supported family (TX only) I recently bought a re(4) NIC to replace the unsupported on-board NIC of a motherboard. I've only had access to 100 Mbit/s connections so far though, so I can't tell for sure how it behaves in Gbit/s links. FWIW, it works like a charm in the 100 Mbit/s network I've used it so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
