Hi, all -- I have seen this problem before and it's still biting me. 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 *really* weird here). Another box I have has route problems as well, but I marked it as suspect because it's an LFS build. 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, but I cannot get it to talk off the box (even though I have a link light on this known-good link). Although it should be able to talk anywhere in my home 192.168.42.0 without a default gateway, I added one with route add default gw 192.168.42.254 and my routing table, per `netstat -rn`, looks sensible: # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.42.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.42.254 0.0.0.0 UG 40 0 0 eth0 Nothing I do, though, can get me off of the box. What do I need to do to set up proper routing?(!!?) 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!
On Sunday 03 August 2003 00:59, David T-G wrote:
Hi, all --
I have seen this problem before and it's still biting me.
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 *really* weird here). Another box I have has route problems as well, but I marked it as suspect because it's an LFS build.
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, but I cannot get it to talk off the box (even though I have a link light on this known-good link). Although it should be able to talk anywhere in my home 192.168.42.0 without a default gateway, I added one with
route add default gw 192.168.42.254
and my routing table, per `netstat -rn`, looks sensible:
# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.42.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.42.254 0.0.0.0 UG 40 0 0 eth0
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? 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. 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 Hope this helps. Greetings, ---- Jan Elders Nuenen the Netherlands
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!
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". Jan E : Did you configure /etc/pcmcia/atmel.conf (or equivalent, for your card) correctly to identify the appropriate driver for this card ? Are there no errormessages in /var/log/messages related to the device ?
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. Jan E : Beats me ! :-(
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". Jan E : What does the output of the command route look like ?
% 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.42.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? Jan E : Have you also tried <route del default> before giving the <route add etc.> ? I'm not sure but maybe that is madatory (I believe it is implied in the ifdown commands that I am using). Greetings, -- Jan Elders Nuenen
On Sunday 03 August 2003 20:11, David T-G wrote: the Netherlands
Jan, et al -- ...and then Jan Elders said... % % On Sunday 03 August 2003 20:11, David T-G wrote: % > % > ...and then Jan Elders said... % > % % > % On Sunday 03 August 2003 00:59, David T-G wrote: % > % > ... % > % > 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". % Jan E : % Did you configure /etc/pcmcia/atmel.conf (or equivalent, for your card) % correctly to identify the appropriate driver for this card ? % Are there no errormessages in /var/log/messages related to the device ? I didn't; I'll remember to do that. I haven't seen any messages when I went looking, but next time I'll look specifically. I can't switch to that card to check because I don't have that card at the moment :-) % > % > 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. % Jan E : % Beats me ! :-( It turns out that it was a route thing. % > % > 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". % Jan E : % What does the output of the command route look like ? This was the key! On my SuSE laptop it is davidtg@lake:~> route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0 default locks 0.0.0.0 UG 0 0 0 eth0 (where locks is the hostname of my gateway address and all is well) but on canal it said davidtg@canal:/home/davidtg$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0 default locks 0.0.0.0 UG 1 0 0 eth0 with a different metric! Sure enough, a manual root@canal:/home/root # route del default root@canal:/home/root # route add default gw locks metric 0 now lets me see my own machine :-) :-) :-) So why did it have "metric 1" in it? How do I make this fix permanent? % > ... % > 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? % Jan E : % Have you also tried <route del default> before giving the <route add etc.> ? % I'm not sure but maybe that is madatory (I believe it is implied in the ifdown % commands that I am using). I did del the route before adding it, but it is always up with a default route when I log in and find troubles anyway. % Greetings, % -- % Jan Elders % Nuenen % the Netherlands Thanks & 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!
On Monday 04 August 2003 21:57, David T-G wrote:
Jan, et al --
//CUT
% > 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". % Jan E : % What does the output of the command route look like ?
This was the key! On my SuSE laptop it is
davidtg@lake:~> route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0 default locks 0.0.0.0 UG 0 0 0 eth0
(where locks is the hostname of my gateway address and all is well) but on canal it said
davidtg@canal:/home/davidtg$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0 default locks 0.0.0.0 UG 1 0 0 eth0
with a different metric! Sure enough, a manual
root@canal:/home/root # route del default root@canal:/home/root # route add default gw locks metric 0
now lets me see my own machine :-) :-) :-)
So why did it have "metric 1" in it? How do I make this fix permanent?
I don't know why you have it, but I suggest that you make a little script with the commands above and add it in your boot sequence ( in /etc/rc.d ). That way you don't have to worry about it. ;-)
% > 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? % Jan E : % Have you also tried <route del default> before giving the <route add etc.> ? % I'm not sure but maybe that is madatory (I believe it is implied in the ifdown % commands that I am using).
I did del the route before adding it, but it is always up with a default route when I log in and find troubles anyway.
As I suggested, circumvent it with a boot script. Greetings, -- Jan Elders Nuenen the Netherlands
Jan, et al -- One little bit that I want to go back and cover here, with some extra added in... ...and then Jan Elders said... % ... % 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 Since the wired NIC on my new laptop is built in and the wireless is a card (I wish that I had built-in WLAN but that just wasn't to be), I will have to choose between TP and WL interfaces. Meanwhile, at home I want to be static so that other machines in my network can always find me, but when I drop in at an office or someone's house I want to be dynamic. How have other people already solved the problem of picking profiles with changes like these? Thanks again & 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!
participants (2)
-
David T-G
-
Jan Elders