Re: [SLE] setting up routes

• Previous message: David T-G: "Re: [SLE] resizing ntfs partitions (un-SOLVED)"
• In reply to: Jan Elders: "Re: [SLE] setting up routes"
• Next in thread: Jan Elders: "Re: [SLE] setting up routes"
• Reply: Jan Elders: "Re: [SLE] setting up routes"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sun, 3 Aug 2003 14:11:07 -0400
To: "SuSE Linux (English) list" <suse-linux-e@suse.com>

Jan, et al --

...and then Jan Elders said...
%
% On Sunday 03 August 2003 00:59, David T-G wrote:
% >
% > My SuSE 8.1 laptop talks just fine over its wireless NIC, but can't talk
% > over its wired NIC because of [apparent] route problems (that's what is
...
% >
% > Now I'm trying to get my new Toshiba Satellite talking on the network. I
% > can manually ifconfig the eth0 interface and it happily talks to itself,
...
% >
% > Nothing I do, though, can get me off of the box. What do I need to do to
% > set up proper routing?(!!?)
%
% Your environment is a bit unclear to me.
% I assume that you have a wired-NIC and a wireless (PCMCIA) one. Right?

Sorry. I suppose that was a bit muddled. Let me try again:

My [old] Tecra 8000 running SuSE 8.1 will talk just fine over its cardbus
wireless NIC, which shows up as eth0. When I try the 3com or Compaq
cardbus wired NICs, though, which also each show up as eth0 (I only have
one in at any time), netstat's output looks right but it only says
"destination unreachable".

When running with that wireless NIC, I can ssh over to my gateway machine
on the same subnet but it, interestingly enough, cannot ssh back to me!
And netstat says the same sensible thing on it.

Now I have a new Toshiba Satellite and am getting SuSE (8.1 again) loaded
on it. Keeping things simple at first, I'm just trying to talk on the
built-in 10/100 eth0 port. Again I give it an address and bring it up,
and it can ping itself, but anything else even on the same subnet is
"unreachable".

% I suspect that your wired NIC is configured as eth0 and your wireless as eth1.
% If this is true, then your default gateway is pointing at eth0, which is your
% wired NIC -- hence no action via the wireless.

Sorry for the confusion :-)

% I had similar problems and solved them by disabling the wired NIC, enabling
% the wireless, and changing the default route to the wireless.
% Commands :
% ifdown eth0
% ifup eth-pcmcia-0 eth1
% route add default gw 192.168.42.254 netmask 0.0.0.0 dev eth1
% (You can make a little script for this)
% If I want to change to the wired NIC, I run :
% ifdown eth-pcmcia-0
% ifup eth0
% route add default gw 192.168.123.254 netmask 0.0.0.0 dev eth0

Hmmm... All I've ever tried is

  route add default gw 192.168.42.254

without the dev flag, so I'll try again. Meanwhile, now that I've done a
much better job of explaining myself, are there any other answers?

% Hope this helps.
% Greetings,

Thanks & TIA & HAND

:-D

-- 
David T-G                      * There is too much animal courage in 
(play) davidtg@justpickone.org * society and not sufficient moral courage.
(work) davidtgwork@justpickone.org  -- Mary Baker Eddy, "Science and Health"
http://justpickone.org/davidtg/      Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

• application/pgp-signature attachment: stored

• Previous message: David T-G: "Re: [SLE] resizing ntfs partitions (un-SOLVED)"
• In reply to: Jan Elders: "Re: [SLE] setting up routes"
• Next in thread: Jan Elders: "Re: [SLE] setting up routes"
• Reply: Jan Elders: "Re: [SLE] setting up routes"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]