A few comments now :
First let me tell you all that I'm quite new to all this network
stuff that Linux lets the average person see.
I was much more used to the "out of the box" and "PnP" packages intended
to be used under Win95.
Of course Linux is much more fun to use !
In the first answer to my request, Julian Munoz Dominguez pointed me to
the ARP stuff that I only knew by its three letters :-)
Addind an arp entry combined with an 'arparms -route add ...' seems to
solve the problem for the host i wanted to contact in my example.
Some of you told me about the ax25rtd utility.
In fact, my machine is intended to be/serve as the first tcp/ip node in
the area as here no one has ever seen those protocols on radio before.
If i correctly understood the examples you gave me with the arp setting,
letting users access the services I'm starting to implement on my
machine would need adding a manual arp entry for each new user.
the job for me. In fact i actually expect It to learn from the ax25 heard
routes to let the system know how to route the arp requests (as I
know now what these requests are used to : learning the other's side
HW_Address !).
Well, I'll give a try to all of this taking great care to what will be
done.
I've been really impressed by the interest given to one more newbie
request.
THANK YOU ALL
Alex.
On Tue, 2 Jun 1998, Klaus Kudielka wrote:
> Richard Adams wrote:
> > If i understand your situation correctly then ax25rtd will help you out on
> > this one.
>
> IMHO ax25rtd is only helpful for tcp/ip nodes which are accessed by users
> via digipeaters (i.e. the digipeaters are not known a-priori and probably change
> with time). There may be other applications, but I don't recommend it for client
> machines.
>
> For the case mentioned in the original message, the following actions should be
> enough:
>
> * Add an IP route for the host you want to talk to on the right interface
> (this seems to be already ok, since ARP broadcasts are going out).
> * Add an ARP entry for the host you want to talk to (otherwise your machine has
> to
> use ARP broadcasts to find out the callsign, which doesn't work over
> digipeaters).
> The hw address type must be ax25.
> The callsign/ssid must be the one of the host you want to reach, NOT the one
> of the
> digipeater. For now, let's call it HOST-1:
> arp -H ax25 1.2.3.4 HOST-1
> * Add an ax25 route to HOST-1 via digipeater DIGI-1:
> axparms -route add ax0 HOST-1 DIGI-1
>
> I'm not 100% sure about the syntax, please check the man pages.
>
> 73 de Klaus OE1KIB
>
>
--- Alexandre FORNIELES 40150 Hossegor - FRANCE ax25 : F1CAY @ F1CAY.FAQI.FRA.EU EMail : wsuxau.zayfplxgb@sizsan.co.jp