Re: Can't ping router.

David wrote:
*route add -net 192.168.0.0 192.168.0.11 -iface
add net 192.168.0.0: gateway 192.168.0.11

*inetstat -r -n
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif
Expire
default 213.120.208.131 UGSc 13 11 ppp0
127.0.0.1 127.0.0.1 UH 0 0 lo0
192.168 link#2 UCSc 0 0
213.120.208.131 link#3 UHC 37 9


Arse biscuits! Same as before, largely. I presume that pinging a
192.168 address still doesn't work?

And I've absolutely no idea what that might tell you.


I was hoping it would say "eh0" in the Netif column on the 192.168 row,
rather than just the obscure "link#2" under Gateway. (Why have two ways
to express the same thing, instead of being consistent?) Then I was
hoping that pinging would work, and the presence or absence of eh0 in
the table would predict that.

I'm basically stumped too - sorry.


Just guessing now, but maybe (a variation on other advice):

*route delete -net 192.168.0.0
*ifconfig eh0 down
*ifconfig eh0 192.168.0.11 netmask 255.255.255.0 arp up

The first command just makes sure that no conflicting route exists when
*ifconfig tries to add its own. (I shoved arp in for good measure,
though I'd expect it to be on by default.)


Another random thought:

You might be able to manually populate the ARP cache. (In earlier
posts, you showed that it had no entry for the router, and that there
was no corresponding activity on the link light when pinging.)

You'd need the MAC address of the router, the 6-byte hex number, usually
separated with colons - someone else may have an idea of how to get it;
might even be in the router web interface, as accessed by one of the
working machines (under "Gateway Status" => "LAN port"?). Then:

*arp -s 192.168.0.1 00:ab:cd:ef:98:76

(Obviously, supply your router's MAC address as the last argument,
instead of the one I've just invented.)

Assuming that you've got the routing table up as you've shown above, try
pinging 192.168.0.1 again. If it works, it means that the automatic
procedure for performing an ARP isn't working as expected, and that can
be investigated. If not, erm... Well, might be interesting anyway.



A final random thought:

Others have mentioned getting the things like the netmask the same on
all machines. I'm not convinced that such a discrepancy would cause a
failure, but it's an idea, and it occurs to me that your "*route"
command can't distinguish between ranges 192.168/16 and 192.168.0/24
because it only accepts 192.168.0.0, and assumes that the zeros imply a
netmask of zero (i.e. 255.255.0.0 or /16). (Anyone concur with that, so
far?)

The 192.168 route should be set up automatically when the interface
comes up, as controlled by *ifconfig, but it might not be able to
express to the routing table that it accesses 192.168.0/24 rather than
192.168/16. If that's the case, and no other avenue of investigation is
successful, perhaps you should configure your network to use the address
range 192.168.1/24 (in other words, 192.168.1.0 netmask 255.255.255.0),
and set the router to something in that range (say, 192.168.1.1; and
similarly for the other machines). Then, when the RiscPC routing table
is given 192.168.1.0 as a network address, it will correctly assume that
the netmask is 255.255.255.0.

But that might be such a faff to arrange, I'd leave it at the bottom of
your 'Things To Try' list. :-/ Anyone else comment on that? I have
little confidence in it...

--
ss at comp dot lancs dot ac dot uk |
.

Relevant Pages

  • Re: route trafic from external to internal adapter
    ... Routing is a two-way process. ... If the default gateway for 192.168.30.11 is to the RRAS router and the ... I have RRAS active on a SBS server and no firewall software I know of. ...
    (microsoft.public.windows.server.networking)
  • Re: 2 routers 2 network card
    ... The routing table will send all "undefined routes" ... router when the routing table specifics it to do so. ... comes in the second router (without the Default Gateway) the return traffic ... the difference between a "logical connection" and a "physical connection" ...
    (microsoft.public.win2000.networking)
  • Re: PIX VPN help.
    ... gateway's and the crypto maps on the Pix's. ... there is no routing you need to add. ... PC has the router as a default ... gateway, router has the Pix as the default gateway, crypto maps take care of ...
    (comp.dcom.sys.cisco)
  • Re: Simple Routing using FC2/3
    ... >> This silly routing thing is driving me buzzonkers. ... >> first email concerning the gateway address of the LAN PC. ... > the 192.168.213.x addresses back to your router box. ... > NAT on the router box you are describing so all of the 192.168.213.x net ...
    (Fedora)
  • Re: Simple Routing using FC2/3
    ... This silly routing thing is driving me buzzonkers. ... first email concerning the gateway address of the LAN PC. ... Router box route command. ... Internet (which would require NAT- but this isn't the case with these two ...
    (Fedora)