Connect Linux box to the Internet via Linksys WRT54G router

Alex Beamish talexb-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Wed Mar 23 15:28:21 UTC 2005


On Tue, 22 Mar 2005 18:06:11 -0500 (EST), Michael L Yang
<lr1003-/E1597aS9LQAvxtiuMwx3w at public.gmane.org> wrote:
> Hello everyone, 
>   
> Good day! 
>   
> I have just purchased a Linksys WRT54G router for my home network (one pc
> and one windows laptop). The pc has both WinXP and Redhat 7.3 on it. The
> wired connection is as below: 
>   
>   
> PC ------------ 
>                   \ 
>                   WRT54G router ---- Rogers Modem ------Internet 
>                   / 
> Laptop------- 
>   
> Under windows XP, both computers can access internet no problem. But when I
> switch to RH on the PC, the networking is not working at all. I can not even
> ping the router (192.168.1.1). I have turned on dhcp via 'Network
> Configuration'. I wonder whether some one could point me to the right
> direction. 

Hi Michael,

I'm certainly not an expert, but here's something to get you started.

When dealing with networking problems, it's best to start at the
bottom; I'm presuming that you aren't unplugging some cables and
plugging others in when you re-boot to Red Hat. OK?

Once we're over that hurdle, you should get familiar with the
'ifconfig' command. On my home machine, it shows this:

[tab at bert tab]$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:88:F8:18:48  
          inet addr:192.168.5.4  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe88::250:8bf8:fef8:1f48/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2197224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2337516 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1095207556 (1044.4 Mb)  TX bytes:1049616572 (1000.9 Mb)
          Interrupt:20 Base address:0x4000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:19441 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:16962775 (16.1 Mb)  TX bytes:16962775 (16.1 Mb)

tun0      Link encap:Point-to-Point Protocol  
          inet addr:10.128.0.42  P-t-P:10.128.0.41  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:107409 errors:0 dropped:0 overruns:0 frame:0
          TX packets:112850 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:53203061 (50.7 Mb)  TX bytes:13334850 (12.7 Mb)

So there are three devices, eth0 (my LAN card), lo (the loopback
device) and tun0 (my VPN connection back to work). You should probably
have the first two, and it's eth0 that's the one that we need to get
working.

If it's not there at all, you have problems with Red Hat not
recognizing your card.

If it's there but not running, you need to issue something like a
'service network restart' as root to get it going.

If it's there, and running, but 'ping' still doesn't work, I'm not
sure what the next step is.

Let us know what you find out.

Alex
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list