🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.linux.misc
Article #1090

Re: Routing/LAN problems

#1090
From: John B. (Brent) Williams
Date: Tue, 01 Oct 1996 00:00
62 lines
2728 bytes
In article <52o8j7$6hf@robin.cqi.com>, cgill@cqi.com (C. Gill) wrote:

> [snip]
>
>So, I hooked Grass and Chimera up to each other using a crossover cable. 
>The ethernet cards ahve very nice green lights that come on when you have 
>a correctly wired conenction, and they came on. So, at least the cards 
>beleive they are correctly connected. I defined IP's broadcast, network 
>etc..using 192.193.194.* (grass is 1, chimera is 2, blade is 3). So, 
>here's the config fromm grass:
>
>IPADDR="192.193.194.1"
>NETMASK="255.255.255.0"
>NETWORK="192.193.194.0"
>BROADCAST="192.193.194.255"
>GATEWAY="205.252.44.251" (this is my provder. Teh other machines are set 
>to 192.193.194.1 ie: grass)
>
>then I implement a 
>
>/sbin/route add -net ${NETWORK} netmask ${NETMASK} dev eth0
>
>But grass can't ping chimera, and chimera can't ping grass. Teh SMC card 
>in chimera has an amber transmit light that, interestingly enought, 
>doesn't come on when I'm pinging, neither does the transmit light when 
>grass does the pining. 
>
>Yes, /etc/networks has a "localnet" entry, which is set to "192.193.194.0"
>

Make sure there is an entry for the host you are trying to ping in
/etc/hosts.  It should look something like this:

127.0.0.1         localhost
192.193.194.1     grass.somewhere.com grass
192.193.194.2     chimera.somewhere.com chimera
192.193.194.3     blade.somewhere.com blade


You may also want to setup static routes to each of your hosts:

route add -host [ IP address | hostname ] dev eth0

The following are equivalent if there is an entry in /etc/hosts for chimera:

route add -host 192.193.194.2 dev eth0
route add -host chimera dev eth0

Also, is this a permanent connection to your provider or is it a dialup? 
Are the IP addresses for grass, blade and chimera ones that were assigned
to you by your provider or did you just pick them?

If this is a dialup, are you connecting to a dynamic or static IP address?

--
+-------------------------------------------------------------+
John B. (Brent) Williams

forerunner@mercury.net      http://www.mercury.net/~forerunner/
forerunner@aol.com
afn32421@afn.org
Technical Details
Message-ID: <forerunner-0110961036180001@gnv-r0-mbs-d02.mercury.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <52o8j7$6hf@robin.cqi.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1103af,b772cd8affb1bb89
X-Google-Attributes: gid1103af,public
X-Google-Thread: 11663c,b772cd8affb1bb89
X-Google-Attributes: gid11663c,public
From: forerunner@mercury.net (John B. (Brent) Williams)
Subject: Re: Routing/LAN problems
Date: 1996/10/01
Message-ID: <forerunner-0110961036180001@gnv-r0-mbs-d02.mercury.net>
X-Deja-AN: 186470297
references: <52o8j7$6hf@robin.cqi.com>
organization: Mercury Communications, Inc.
newsgroups: comp.os.linux.misc,dc.org.linux-users