I would probably set up a static IP address for the PC to PC cross-over cable (one per host attached to the cable) that is on a different subnet than the rest of your internal network. NIC0 to internal network being 192.168.0.xxx NIC1 direct to other PC being 192.168.1.xxx NICn on other PC directly connected being 192.168.1.xxx+1 -Alain -----Original Message----- From: Johan Nielsen [mailto:yep@osterbo-net.dk] Sent: Monday, November 28, 2005 1:58 AM To: suse-amd64@suse.com Subject: Re: [suse-amd64] strategy for gigabyte dual nic board in 9.3 Mandag 17 oktober 2005 18:00 skrev Black, Alain:
Mark,
On my dual NIC systems under 9.3, I only configure the NIC that I want to use. Otherwise on boot the system will spend 20 seconds waiting for DHCP to timeout for the NIC that isn't plugged in.
I would recommend deconfiguring the NIC that you don't want to use at this time, and then only configure it when you're ready to use it.
-Alain.
Now if you wanted to use one NIC for external traffic and the other for internal traffic on the local lan how would one attack this given. 1. NIC connected to the same switch with other PC's that's behind a router (Zywall 5) 2. PC to PC with patched cable This would mainly/basicly be used to move large sets of data my "data" repository. Good suggestions is very welcome. Johan
-----Original Message----- From: mark pryor [mailto:tlviewer@yahoo.com] Sent: Friday, October 14, 2005 1:56 PM To: suse-amd64@suse.com Subject: [suse-amd64] strategy for gigabyte dual nic board in 9.3
hello,
SuSE 9.3 x86_64 system: Gigabyte ga-k8n ultra-9 Asus 6800 EN Nvidia pci-x video 1 GB Ocz 2-3-2-5 RAM hd: WD 2500JD SATA (JBOD nv_sata_0)
I'm having trouble setting up the two LAN devices in Yast network devices.
In the manual, it shows the LAN1 (Marvel) as connected to the (faster) pci-x bus. I only want to connect a single cable at this time. When I configure both devices, the system rolls over: I lose SAMBA and bootup behavior is inconsistent.
If you are going to setup both devices, what setting do you give "device activation" in the "detailed network settings" window? I tried hotplug for both (bad), "at boot" for LAN1 and hotplug for LAN2 (bad). I finally decided to disable LAN2 in the bios and delete it in Yast Network devices. Then LAN1 is set to activate at boot.
This solution (to disable LAN2) seems extreme. I'm guessing I ran into trouble since at one point I gave both devices the same settings. If I tried to change them something wouldn't reset.
This is the first board I've setup with dual onboard LAN -- what a head-ache.
thanks for your comments, Mark Pryor (the one with no political ambitions)
__________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com