Wired and Wireless with a notebook

Dazed_75 lthielster at gmail.com
Thu Apr 20 01:20:39 MST 2006


On 4/19/06, Jared Anderson <pluggedIn at thegoldenedge.com> wrote:
> On Tuesday 18 April 2006 5:12 pm, Dazed_75 wrote:
> > My laptop (Toshiba 5105-S701) has both wired ethernet and built-in
> > 802-11b.  At home I normally plug in the wired ethernet.  The Wireless
> > is used when I have the laptop away from the computer room (wheter
> > home or away).  The issue seems to be that when I bring up the system
> > (Ubuntu 5.10) with the ether cable plugged in it finds both
> > interfaces, leaves both enabled and refuses to resolve URLs until I
> > use [menu] System/Administration/Networking to de-activate the
> > wireless.
> >
> > Note that both wireless and wired interfaces are being issued separate
> > IPs (e.g. 192.168.1.106 and 107) by the same Linksys router (which
> > also contains the AP) and should be issuing the same DNS IPs from my
> > ISP (/etc/resolv.conf only contains the usual pair).  One would think
> > the system could use EITHER interface succussfully.  Something is
> > getting in the way and I would love to learn how to avoid this issue.
> > BTW, this issue is not unique to me.  I have talked to several people
> > with the same problem including at least one other PLUG member.
> >
> > Suggestions or references anyone?
>
> While at home, before disabling one of the interfaces, can you run of the
> following commands and then post the results?
>
> netstat -rn
> -or-
> route -vn
> -or-
> cat /proc/net/route
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
Interestingly, my netstat (Ubuntu 5.10) does not seem to have a -m
option.  Also, I realize you said "OR" but too much is better than not
enough and since they produced slightly different output, Here is all
of it:

$ netstat -i
Kernel Interface table
Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0   1500 0       113      0      0      0       78      0      0      0 BMRU
eth1   1500 0        36      0      0      0        5      0      0      0 BMRU
lo    16436 0     15546      0      0      0    15546      0      0      0 LRU
$ netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     *               255.255.255.0   U         0 0          0 eth0
192.168.1.0     *               255.255.255.0   U         0 0          0 eth1
default         myrouter        0.0.0.0         UG        0 0          0 eth1
default         myrouter        0.0.0.0         UG        0 0          0 eth0
$ route -vn
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth1
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
$ cat /proc/net/route
Iface	Destination	Gateway
	Flags	RefCnt	Use	Metric	Mask		MTU	Window	IRTT
eth0	0001A8C0	00000000	0001	0	0	0	00FFFFFF	0	0	0
eth1	0001A8C0	00000000	0001	0	0	0	00FFFFFF	0	0	0
eth1	00000000	0101A8C0	0003	0	0	0	00000000	0	0	0
eth0	00000000	0101A8C0	0003	0	0	0	00000000	0	0	0
$ cat /etc/resolv.conf
search ph.cox.net
nameserver 204.127.203.135
nameserver 216.148.225.135

NOTE: the "search ph.cox.net" is from when I use the laptop at a
different location.

Just to reconfirm, this is following a powerup with the ethernet cable
plugged an and the wireless turned on.  At that point I was unable to
access the internet (ping yahoo.com even failed).  Interestingly after
capturing this info, moving to this desktop to do the email, I went
back to the laptop to try pinging the DNS server by IP address and
found that worked and learned the traffic went over the wireless.  I
then tried pinging Yahoo.com again and it worked (also via the
wireless).  This is getting even wierder.

--

Nothing is really work unless you would rather be doing something else.
  - James M. Barrie


More information about the PLUG-discuss mailing list