We are trying to figure out a problem and maybe some of you can help us.
what we are trying to do is use SL/IP on a VaxStation 3100 running Ultrix
4.2 to connect a 286-AT running an amateur radio tcp/ip software package
called (KA9Q). Getting the link up is no problem. The 286-AT machine is
then linked on the radio interface (ax0) to a wireless TCP/IP network around
our region on the amateur radio bands. The VaxStation is called 'turing'
and its IP address is 161.45.1.14. It is on a LAN of other Ultrix 4.2
workstations connected via thinnet ethernet. There are no subnets present.
The entire ethernet is one network. The 286-AT is called 'w4efq' and has
an IP address of '161.45.63.4'. The wireless network is '44.34'. It is
not so much involved with the problem we are currently trying to figure out
so I will not really explain it further.
As I mentioned, the slip link is working fine between w4efq (286-at) and
turing (vaxtstation). From either end, you can telnet the other. Turing
is the SLAVE and w4efq is the MASTER in this arrangement (ie, w4efq logs
into turing and runs '/usr/new/slattach' as its login shell). W4efq has
all '44.34' addresses going out interface ax0 (radio) and all '161.45'
addresses going down sli0 (slip link to turing). Turing's route table
shows w4efq. If you run ifconfig (no args) it shows ln0 (the ethernet
with dynamic routing, and so on) and sl0 (slip to w4efq) as being POINT-TO-
POINT. We have the /etc/sliphosts file setup fine as best we can tell.
What our problem is, is that we cannot seem to get other workstations
on the ethernet to be able to access w4efq via the slip interface on turing
*UNLESS* we specifically add a route to the workstation in particular
that says
route add 161.45.63.4 161.45.1.14 1
ie, w4efq is via gateway turing. Then it works great!?!? w4efq has no
problem replying to say, 161.45.1.1, and 161.45.1.1 will reach w4efq as long as we manually add the route above. what we want it to somehow have turing
be "listening" for w4efq's address and say "ah, i know what to do with
this one" and send it up the sl/ip line. We don't want to have to go to
each and every workstation and add routes by hand. likewise, it seems to
me that one should not have to update every node in a network if you use
sl/ip to "bridge" another network in (as in my case); attaching it to just
one node in the main network (in my case, turing). Maybe I am wrong. :-)
I know I am confused! :-)
we played around with ARP on turing (no luck so far), and some other stuff.
So, bascially can what I have described be done the way I want it to? If
not, why? If so, how (from the beginning if necessary! :-)) ????
Ultimately, we would like any node in our 161.45 network to be able to
telnet 161.45.63.4 (w4efq) and get a prompt. Conversely, from w4efq,
we would like to telnet any of the other 161.45 nodes and get to them as
well. It is almost like some sort of subnet must be established on
turing, but I am really not sure how it would be done. Turing somehow
has to be listening and when it hears a request for w4efq, do something
about it (send it up the sl/ip).
Well, that is roughly what we are confronted with. Any help whatsoever
would be MOST appreciated!!! We have been trying to figure this for a week
or so and haven't gotten anywhere.
Thanks in advance!
Mark
P.S. email replies if you like (would), this really doesn't need to waste
anymore net bandwidth.
--
Mark J. Bailey, N4XHX _______/====X11====\_______
USMAIL: 511 Memorial Blvd., Murfreesboro, TN 37129 | JobSoft |
VOICE: +1 615 893 0098 | Design & Development Co.|
UUCP: ...!uunet!mjbtn!mjb, ...!raider!mjbtn!mjb | Murfreesboro, TN USA |
