Date: Tue, 11 May 93 04:30:13 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #121
To: tcp-group-digest
TCP-Group Digest Tue, 11 May 93 Volume 93 : Issue 121
Today's Topics:
Confused: ARP question....
Request
Routing & ARP (2 msgs)
subscribe
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Mon, 10 May 93 23:52:27 HST
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Subject: Confused: ARP question....
To: Jack Snodgrass <kf5mg@vnet.IBM.COM>
> I'm playing with a new Internet Gateway in our area and am a bit
> puzzled. I've got the following routes defined:
>
> route add 44.28.0/24 14567 # local 2 mtr ip
> route add 44.28.1/24 44430 # local 440 ip
> route add default 14567 dfwgate # dfwgate.ampr.org on 145.67
>
> Now when I ping uhm.ampr.org, my station sends out an ARP request for
> uhm.ampr.org locally. No one answers, so nothing else happens. I send
> a couple of ARP request for umh.ampr.org but eventually, it gives up.
> I'm pretty sure that the ARP request was not going to dfwgate for
> gateway routing.
First thing, you don't have to put in an explicit subnet route
statement if you have your subnet mask and broadcast address
setup properly for your two interfaces. Ie. you should have
something like:
ifconfig 14567 netmask 0xffffff00 broadcast 44.28.0.255
ifconfig 44430 netmask 0xffffff00 broadcast 44.28.1.255
But you do need the 'route add default' which looks correct. Since
you don't add on the 'ampr.org' make sure that your domain suffix
is set to 'ampr.org'. Also, ensure that there is an entry for
dfwgate.ampr.org in your domain.txt file (or your domain
initialization file). Depending on the version of NOS you may have to
terminate the 'org' with a period in domain.txt.
> Should the ARP request be routed through the gateway or should the
> gateway answer the ARP request or what? Thanks.
The gateway should answer the ARP request.
Tony AH6BW
------------------------------
Date: Mon, 10 May 93 19:37:27 PDT
From: kors@netcom.com (Richard Kors)
Subject: Request
To: TCP-Group@UCSD.Edu
I would appreciate being added to the TCP Digest mailing list. Send to
kors@netcom.com
Thank you again,
Dick Kors
km6ep
--
------------------------------
Date: Mon, 10 May 1993 12:43:01 -0600
From: ke9yq@ke9yq.ampr.org (Bob Van Valzah, ke9yq)
Subject: Routing & ARP
To: Jack Snodgrass <kf5mg@vnet.IBM.COM>
> I'm playing with a new Internet Gateway in our area and am a bit
>puzzled. I've got the following routes defined:
>
>route add 44.28.0/24 14567 # local 2 mtr ip
>route add 44.28.1/24 44430 # local 440 ip
>route add default 14567 dfwgate # dfwgate.ampr.org on 145.67
The purpose of a default route is to save you having to explicitly enter
routes for hosts or networks. It's *very* unlikely that you want a
gateway's default route pointing out a radio port--it should probably go
out your Ethernet port since that's where 99.9999% of the 1.7 million
Internet hosts will be reachable. Ask the administrator of the Ethernet to
which your gateway is connected for the IP address of a router for that
network. Then you'll want something like
route add default <your Ethernet interface name> <router's IP address>
Your earlier radio routes are fine, but you should note that the ifconfig
command will add them for you if you set the subnet mask to 0xffffff00. If
you have your IP address assignment set up for subnetting (and it looks
from your example that you do--kudos!), then I recommend using
ifconfig/netmask over an explicit route just because it's more clear what
the interface is good for and it saves a line in your autoexec because you
don't need the explicit route command.
In addition to these routes, you may wish for your gateway to have explicit
encap routes to other gateways to reduce the total number of Internet hopps
required when you address packets to other 44-net addresses. For example,
you might want these explicit route statements for reaching the folks I
serve thru my gateway:
route addprivate 44.46/17 ENCAP ke9yq.imsa.edu
route addprivate 44.72.0/18 ENCAP ke9yq.imsa.edu
route addprivate 44.72.248/21 ENCAP ke9yq.imsa.edu
route addprivate 44.72.75/24 ENCAP ke9yq.imsa.edu
This can be excerpted from the gateways file maintained by vk1xwt. Without
such encap routes, your traffic to other 44-net addresses will still get
thru, but it'll be delayed and subject to the availability of the
mirrorshades.ucsd.edu gateway.
So here's the bottom line: Your gateway must have explicit routes (or
ifconfig/netmask) for your radio ports; you may want to add encap routes to
other gateways for efficiency; and you must have a default route that
points out your Ethernet port at an IP router that knows how to reach the
Internet.
73, Bob, ke9yq
------------------------------
Date: Mon, 10 May 93 21:41:10 PDT
From: Bill Healy <healy@moriah.ee.unr.edu>
Subject: Routing & ARP
To: tcp-group@ucsd.edu (tcp-group)
> > I'm playing with a new Internet Gateway in our area and am a bit
> >puzzled. I've got the following routes defined:
> >
> >route add 44.28.0/24 14567 # local 2 mtr ip
> >route add 44.28.1/24 44430 # local 440 ip
> >route add default 14567 dfwgate # dfwgate.ampr.org on 145.67
>
> The purpose of a default route is to save you having to explicitly enter
> routes for hosts or networks. It's *very* unlikely that you want a
> gateway's default route pointing out a radio port--it should probably go
> out your Ethernet port since that's where 99.9999% of the 1.7 million
> Internet hosts will be reachable. Ask the administrator of the Ethernet to
> which your gateway is connected for the IP address of a router for that
> network. Then you'll want something like
Hold it, I think he's talking about a station he has on the air that he
wants to route through the gateway to everything that isn't local!!! If
that's the case then he has it right. The problem could be that for some
reason the default route isn't getting entered correctly, ie. dfwgate
isn't being looked up properly.
Bill N8KHN
healy@moriah.ee.unr.edu
------------------------------
Date: Mon, 10 May 93 18:22:44 CDT
From: Daniel Ortmann <ortmann@plains.NoDak.edu>
Subject: subscribe
To: tcp-group@ucsd.edu
subscribe
------------------------------
End of TCP-Group Digest V93 #121
******************************
******************************