Re: [opensuse] Suse 10.2 +two network cards (Not yet solved)

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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: DNS or network problem
    ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ... The first thing that leaps out at me is the fact that eth0 and eth1 ... Because all your routes passes through eth1, and not eth0, I ...
    (Fedora)
  • Re: Linux is Driving me $#@!!!! nutz!!!
    ... :Doing a route call from terminal ... via nic card on eth0. ... time since I had to configure a PPP connection, ... from the command line. ...
    (rec.crafts.metalworking)
  • Re: Cant send packets via WiFi (possibly route issue)
    ... which means that the gateway needs a host route. ... > With that you should be able to ping any 192.168.0.x address on ... the only IPs I could ping were IPs of eth0 and eth1. ...
    (comp.os.linux.networking)
  • Re: Proper routes for linux machine with two network ports to same network
    ... I run a Fedora Core 4 system with two network devices eth0 (assigned ... interface is working or sort of, and choose the correct route? ...
    (comp.os.linux.networking)
  • two nics to one lan
    ... Whatever happened caused the eth1 route to be non-functional, ... but all traffic bound to 172.16.59.0/24 was being routed through eth1. ... Unfortunately I don't have the routing table from then, ... was down) there was one well-configured route via eth0 for that subnet. ...
    (comp.os.linux.networking)