Re: another request to reach the router

From: David Efflandt (efflandt_at_xnet.com)
Date: 04/16/05 

Date: Fri, 15 Apr 2005 22:54:40 +0000 (UTC)

On 13 Apr 2005 16:00:20 -0700, ghilljr@satx.rr.com <ghilljr@satx.rr.com> wrote:
> I know that these questions have been asked several times but I
> followed all the suggested solutions I could find on this site and I
> still cannot ping my D-Link router or beyond from my
> RH ES 3.0 box. I am adding it to my network to act as a server for our
> company information database. A Sco box (see below) serves our
> internal business database functions and does not need internet
> acccess( I plan to move it out later!). We are small and have no
> professional IT guy. I thought I knew what I was doing!
> Currently, all of the WXP computers can access the internet (via the
> D-Link router connected to a T-1) and talk to each other as well as to
> the sco box using telnet on the LAN and ICE.ten on serial lines. I
> installed the RHES3 on a new Dell Server without difficulty but have
> not been able to configure it to get to the router. However, I can
> ping to the other computers on the system and telnet to the Scobox.
> The WXPboxes show up under samba as well.
>
> cat of /etc/hosts:
>
> 127.0.0.1 localhost.localdomain localhost
> 192.168.0.15 Bigiron.xxxxx.com(linux box trying to reach the router)
> 192.168.0.1 router
> 192.168.0.119 nod.xxxxx.com (hardwired laptop)
> 192.168.0.10 scounix(5.0.5)box current business data server
> 192.168.0.150 WXPbox1 \
> 192.168.0.139 WXPbox2 \
> 192.168.0.175 WXPbox3 > all assigned by router
> 192.168.0.111 WXPbox4 /
> 192.168.0.158 WXPbox5 /
>
> Output of route:
> Kernal IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
>
> Shouldn't the last line of the routing table start with
> "default"?

Yes, if you do not use the -n switch for route or netstat (but that takes
longer if IPs do not resolve).

> Oops, it is when I use netstat -r command!
> I have tried to remove the reference in the route tables to 169.254.0.0
> (which I think was added on failure to reach the router when I checked
> to use DHCP during the install) with route del 169.254.0.0 and get
> "SIOCDELRT: No such device." The current 192.168.0.15 address was
> assigned by me. Should I route -f to flush this and start over??

The 169... route is probably there for benefit of Win boxes that use that
range if DHCP fails.

> cat of /etc/resolv.conf:
> search 192.168.0.1
> nameserver 20X.XXX.XXX.X0 \ Primary
> nameserver 2XX.XX.XXX.X1 \ secondary
> nameserver 2XX.XX.XXX.XX3 / and tertiary DNS from telecom co.
> I read somewhere that these should not be used when assigning the IP
> address manually so I tried taking them out and it didn't change a
> thing!

Your 'search' line is incorrect. If that is included at all, it should be
one or more domains, NOT an IP (see 'man 5 resolver').

You do need nameserver(s). And if eth IP is manually assigned,
nameserver(s) have to be manually set in resolv.conf.

> output of ifconfig:
> eth0 Link encap: Ethernet Hwaddr XX:XX:XX:XX:XX:XX
> inet addr: 192.168.0.15 Bcast: 192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2695 errrors:0 dropped:0 overruns:0 frame:0
> TX packets:519 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0 txqueuelen:1000
> RX bytes:310171 (302.9Kb) TX bytes: 38142 (37.2 Kb)
> Interrupt:48 Base address:0xd8c0 Memory:dfce0000-dfd00000
>
> Lo Link encap: Local Loopback
> inet addr: 127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:10 errrors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0 txqueuelen:0
> RX bytes:700 (700.0 b) TX bytes: 700 (700.0 b)
>
> kudzu has Hostname = Bigiron.xxxxxx.com
>
>>>From XYZtelecom.com our "default inbound gateway" is 67.xxx.xxx.x17
> with available addresses from 67.xxx.xxx.x18 - 67.xxx.xxx.x22
>
> Pinging the router responds "Destination host unreachable. The man
> page says that happens until a static route is assigned. I thought
> that was done with the "add default 192.168.0.1 gateway."

The 192.168.0.0/24 network route allows you to access the 192.168.0.1 and
setting that as default route should allow you to access internet through
it.

> Finally, I have MAC filters set on the router for security but I have
> put this one in - else I would have no access to the LAN.

I doubt it. The switch of a router is usually just a simple switch (no
control between switch ports). MAC address limits only control what can
access router config or internet. So if you can access LAN and not
internet, the MAC filter would be first place to look for error (since
everything else appears to be mostly correct).

Relevant Pages

  • another request to reach the router
    ... all of the WXP computers can access the internet (via the ... D-Link router connected to a T-1) and talk to each other as well as to ... I have tried to remove the reference in the route tables to 169.254.0.0 ... I read somewhere that these should not be used when assigning the IP ...
    (comp.os.linux.setup)
  • Re: Cannot Share internet thru dual NICs
    ... "You will also need to add a route to your Internet router. ... You need to route traffic for 192.168.254 to the RRAS/NAT router. ... > do an ipconfig /release and ipconfig /renew on the clients to get the new ...
    (microsoft.public.win2000.ras_routing)
  • Re: XP unable to ping.
    ... I did a route print and saw nothing out of the ordinary. ... to go to the router address. ... >> system can ping the Internet DNS server any time. ... >> to route packets to the router for another private LAN. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Dialing into Internet with one PC and using that PC as gateway for rest of LAN
    ... > currently my only connectivity is dialup. ... /etc/resolv.conf and firewall not blocking internet access). ... Normally the only "default" route should be towards the internet, ... Any local routing that has to go through another local router ...
    (comp.os.linux.networking)
  • Re: [SLE] Routing issues with eth1(internal) & eth2(external)
    ... Let the router do the job it was designed for, ... >> from the internet you can then access all of the internal machines via ... Liberty1 is to be a development server. ...
    (SuSE)