[opensuse] Suse 10.2 +two network cards
How does one get two networking cards to go at the same time in Suse Linux 10.2? I have eth0 which is wired network, and eth1 which is Wireless. If I connect to the wireless using network manager, it disconnects the eth0 network, connects to the wireless eth1 for a few seconds, disconnects eth1, then goes back to the eth0. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Art Fore
How does one get two networking cards to go at the same time in Suse Linux 10.2? I have eth0 which is wired network, and eth1 which is Wireless. If I connect to the wireless using network manager, it disconnects the eth0 network, connects to the wireless eth1 for a few seconds, disconnects eth1, then goes back to the eth0.
If you want them connected both at the same time, use the traditional method. NetworkManager only handles one network card at a time. The "connects for a few seconds" looks like a bug - otherwise NM behaves as designed, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 01/10/2007 Art Fore wrote:
How does one get two networking cards to go at the same time in Suse Linux 10.2? I have eth0 which is wired network, and eth1 which is Wireless. If I connect to the wireless using network manager, it disconnects the eth0 network, connects to the wireless eth1 for a few seconds, disconnects eth1, then goes back to the eth0.
I have two wired network cards on separate networks. I can switch back and forth between them and the connections stay stable. I'm with you I would like to know if there is a way to get both active at the same time. Something like the old dual line modems. Do you have some apps configured to use a certain connection? That might make the connection change. -- (o:]>*HUGGLES*<[:o) Billie Walsh The three best words in the English Language: "I LOVE YOU" Pass them on! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-01-10 at 19:45 -0600, Billie Erin Walsh wrote:
On 01/10/2007 Art Fore wrote:
How does one get two networking cards to go at the same time in Suse Linux 10.2? I have eth0 which is wired network, and eth1 which is Wireless. If I connect to the wireless using network manager, it disconnects the eth0 network, connects to the wireless eth1 for a few seconds, disconnects eth1, then goes back to the eth0.
I have two wired network cards on separate networks. I can switch back and forth between them and the connections stay stable. I'm with you I would like to know if there is a way to get both active at the same time. Something like the old dual line modems.
Are you trying to put both interfaces on the same network (both have the same net mask)? That is problematic. Otherwise there is no trouble with multiple cards. My wireless network is different from my wire one, so it 'just works'. with two cards. In fact, in our products, we always have two cards - and two different networks. Having said that, there is one small issue with YasT that has been this way for years. It will not let you give different names to the cards. After assigning the system name, it is applied to both cards. So, you need to edit /etc/hosts and give one card (IP address) a different name. That is the only issue I have ever had. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
Having said that, there is one small issue with YasT that has been this way for years. It will not let you give different names to the cards. After assigning the system name, it is applied to both cards. So, you need to edit /etc/hosts and give one card (IP address) a different name. That is the only issue I have ever had.
Host names refer to the computer, not the NIC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 11 January 2007 18:42, James Knott wrote:
Roger Oberholtzer wrote:
Having said that, there is one small issue with YasT that has been this way for years. It will not let you give different names to the cards. After assigning the system name, it is applied to both cards. So, you need to edit /etc/hosts and give one card (IP address) a different name. That is the only issue I have ever had.
Host names refer to the computer, not the NIC.
If you want to get really precise, DNS names can resolve to one or more IP addresses, so they need even not refer to a single host. Here's a typical example: % host www.google.com www.google.com is an alias for www.l.google.com. www.l.google.com has address 66.102.7.147 www.l.google.com has address 66.102.7.99 www.l.google.com has address 66.102.7.104 www.google.com is an alias for www.l.google.com. www.google.com is an alias for www.l.google.com. % host google.com google.com has address 64.233.167.99 google.com has address 64.233.187.99 google.com has address 72.14.207.99 google.com mail is handled by 10 smtp4.google.com. google.com mail is handled by 10 smtp1.google.com. google.com mail is handled by 10 smtp2.google.com. google.com mail is handled by 10 smtp3.google.com. Here's another: % host amazon.com amazon.com has address 72.21.203.1 amazon.com has address 72.21.206.5 amazon.com has address 72.21.210.11 amazon.com mail is handled by 10 smtp-fw-0102.amazon.com. amazon.com mail is handled by 10 smtp-fw-2102.amazon.com. amazon.com mail is handled by 10 smtp-fw-6101.amazon.com. It's also allowed and not uncommon to associate more than one IP address with a given NIC. And naturally, a given host can have any number of NICs installed. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-01-10 at 19:45 -0600, Billie Erin Walsh wrote:
On 01/10/2007 Art Fore wrote:
How does one get two networking cards to go at the same time in Suse Linux 10.2? I have eth0 which is wired network, and eth1 which is Wireless. If I connect to the wireless using network manager, it disconnects the eth0 network, connects to the wireless eth1 for a few seconds, disconnects eth1, then goes back to the eth0.
I have two wired network cards on separate networks. I can switch back and forth between them and the connections stay stable. I'm with you I would like to know if there is a way to get both active at the same time. Something like the old dual line modems.
Do you have some apps configured to use a certain connection? That might make the connection change.
-- (o:]>*HUGGLES*<[:o) Billie Walsh The three best words in the English Language: "I LOVE YOU" Pass them on!
No, I am not using any Linux applications that are configured for a certain connection. I want WinXP under Parallels to access the wired corporate network, but have Linux access the internet via the wireless connection that is not connected to the corporate internet proxy. It is usually much faster and I can get my private email from it where I can't via the corporate network. Anyhow, I got them both working. I setup Yast to use traditional control, then set the eth0 as it was default from the installation. Then set eth1 DNS servers etc. so DHCP would not update them. Then executed the command route add gw 192.168.99.1. I could then access the wireless network via Linux with not change in WinXP. Only remaining problems are how to get ifplugd to start the wireless at boot. eth1 was added to the ifplugd.conf file, but probably needs more time or something. Also have figure out where to put the route command so it will be executed automatically during boot. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Art Fore wrote:
Anyhow, I got them both working. I setup Yast to use traditional control, then set the eth0 as it was default from the installation. Then set eth1 DNS servers etc. so DHCP would not update them. Then executed the command route add gw 192.168.99.1. I could then access the wireless network via Linux with not change in WinXP.
Only remaining problems are how to get ifplugd to start the wireless at boot. Change it in Yast to startup at boot instead of on cable connection (Network Devices, Network Card, Edit your card, General Tab). eth1 was added to the ifplugd.conf file, but probably needs more time or something. Also have figure out where to put the route command so it will be executed automatically during boot.
Under Address tab, Routing -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2007-01-12 at 07:33 +0800, Joe Morris (NTM) wrote:
Art Fore wrote:
Anyhow, I got them both working. I setup Yast to use traditional control, then set the eth0 as it was default from the installation. Then set eth1 DNS servers etc. so DHCP would not update them. Then executed the command route add gw 192.168.99.1. I could then access the wireless network via Linux with not change in WinXP.
Only remaining problems are how to get ifplugd to start the wireless at boot. Change it in Yast to startup at boot instead of on cable connection (Network Devices, Network Card, Edit your card, General Tab). eth1 was added to the ifplugd.conf file, but probably needs more time or something. Also have figure out where to put the route command so it will be executed automatically during boot.
Under Address tab, Routing
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64
That appears to have done it. Will find out for sure Monday when I go back to work. Art
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2007-01-12 at 20:19 +0800, Art Fore wrote:
On Fri, 2007-01-12 at 07:33 +0800, Joe Morris (NTM) wrote:
Art Fore wrote:
Anyhow, I got them both working. I setup Yast to use traditional control, then set the eth0 as it was default from the installation. Then set eth1 DNS servers etc. so DHCP would not update them. Then executed the command route add gw 192.168.99.1. I could then access the wireless network via Linux with not change in WinXP.
Only remaining problems are how to get ifplugd to start the wireless at boot. Change it in Yast to startup at boot instead of on cable connection (Network Devices, Network Card, Edit your card, General Tab). eth1 was added to the ifplugd.conf file, but probably needs more time or something. Also have figure out where to put the route command so it will be executed automatically during boot.
Under Address tab, Routing
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64
That appears to have done it. Will find out for sure Monday when I go back to work.
Art
Tried the reboot this morning. Still no luck. Found that Ipv6 had to be enabled, enabled it, still no go. Still have to do a ifplugd -i eth1 then route add defualt gw 192.168.99.1 (or 192.168.11.1 as it was changed today). That sometime works and sometimes does not. Found that using rout del default gw 10.18.32.1 would then fix it but not affect WinXP under paralles which uses vnic0 tied to eth0. Would still like to automate this. Here is the output of route after all is said and done route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.37.129.0 * 255.255.255.0 U 0 0 0 vnic0 10.18.32.0 * 255.255.255.0 U 0 0 0 eth0 192.168.11.0 * 255.255.255.0 U 0 0 0 eth1 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.11.1 0.0.0.0 UG 0 0 0 eth1 Before I done the route del there were two default gateways. Here is the output to the /var/log/messages file after I issued the above commands. Jan 15 18:20:14 linux-latitude ifup-dhcp: Jan 15 18:20:14 linux-latitude SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. Jan 15 18:20:14 linux-latitude SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Jan 15 18:20:14 linux-latitude ifplugd(eth1)[17564]: Program executed successfully. Jan 15 18:20:14 linux-latitude SuSEfirewall2: batch committing... Jan 15 18:20:14 linux-latitude SuSEfirewall2: Firewall rules successfully set Jan 15 18:20:14 linux-latitude syslog-ng[3264]: SIGHUP received, restarting syslog-ng Jan 15 18:20:14 linux-latitude kernel: klogd 1.4.1, ---------- state change ---------- Jan 15 18:20:15 linux-latitude syslog-ng[3264]: new configuration initialized Jan 15 18:20:22 linux-latitude kernel: eth1: no IPv6 routers present Jan 15 18:23:26 linux-latitude kernel: ALSA sound/pci/hda/hda_intel.c:574: hda-intel: send_cmd timeout: IRS=0x1, val=0x270650 Jan 15 18:23:26 linux-latitude kernel: ALSA sound/pci/hda/hda_intel.c:574: hda-intel: send_cmd timeout: IRS=0x1, val=0x220011 Jan 15 18:23:26 linux-latitude kernel: ALSA sound/pci/hda/hda_intel.c:574: hda-intel: send_cmd timeout: IRS=0x1, val=0x270600 Jan 15 18:23:26 linux-latitude kernel: ALSA sound/pci/hda/hda_intel.c:574: hda-intel: send_cmd timeout: IRS=0x1, val=0x220000 Any other suggestions? Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Andreas Jaeger -
Art Fore -
Billie Erin Walsh -
James Knott -
Joe Morris (NTM) -
Randall R Schulz -
Roger Oberholtzer