Linux-Hams archive - April 1998: Re: update : ax25ipd question

Re: update : ax25ipd question

kd4zkw (izdejhv@caseta.com)
Mon, 6 Apr 1998 19:04:11 -0400 (EDT)


On Mon, 6 Apr 1998, Tomi Manninen wrote:
> You're not he only one Terry. I think Curtis himself is a little bit
> confused too. I've been reading all the postings from him and frankly they
> don't make much sense...
>
> Curtis could you please explain in simple terms what you try to achieve?
> Like in "I want to type XXX and get connected to YYY". From what I have
> gathered you might be confusing ax25 over ip and ip over ax25. And ax25
> and netrom. But then again I might be the one mistaken... :)

Yeah, I'm totally whacked. Anyays, what I wanted to do was to hook up
ax25ipd to port another gateway on a different freqeuncy into my node
using ax25ipd. I set up the node for his address which is 205.152.185.200
and we went for it, with no luck. What I think might have happened is
that I had him route to nme thru 44.98.2.22, instead of my commercial
address which is 209.4.65.28. Incidentally, his amprnet ip is 44.98.2.5,
and if you telnet to that, you will get his gateway. He has his commercial
IP named as w4bkx.ampr.org, so that's where the confusion is. But his
stuff works, and mine doesn't, so I'm not going to critique him.

Anyways, I have to check node.perms, as I might have it blocking the
commercial IP address here. I had it work for me one time, and it
worked instantly, like really well, just before the kernel routing
table totally fell apart. So, I rebooted, and tried the same thing,
again with no luck. Bummed me out, man. But I took a day off, and
am ready to try again.

The thing is, I had him coming into the node at KD4ZKW-5. When I try
to connect to him from the node, it's at KD4ZKW-1. He doesn't seem
to hear anything I send to him from KD4ZKW-1, but when it did work
it worked thru KD4ZKW-5, and the 'call axip FTLGW' program run from
the command line. As I was calling him, the node broadcast was coming
in, and it worked immediately. It also worked from the node at the
same time when I used 'c axip ftlgw' from the node. Again the ssid was
-5 instead of dash one, which is what it is when the node calls over axip
by using it's internal routing. The thing is, I really don't want users
making axip calls, unless the node is on the nodelist. I can route the
nodes I want having axip calls to the circuit using 'nrparms'. The reason
is that I am not a permanent gateway yet, and simply want to serve as a
bridge to w4bkx during peak usage hours. And maybe a few others, but not
a full blown gateway, as that is the function of w4bkx. And he does it
well. The gateway has maybe been down a total of one week in three years.
He has an excellent track record.

So, hopefully, I've explained myself. BTW, I get every single node
broadcast w4bkx puts out, and his mail beacon, etc. So him coming to
me is not a problem. It's me going to him, and for some reason, I just
haven't got it down quite pat. Sorry to trouble the list, I know one of
my worst habits is wanting something to work immediately when I try to
do it, and not having to wait for an answer. It's a terrible habit, one
I'm working religiously on breaking. And again, thanx for the help, and
the patience. I'll let you know how this one turns out.

____________________________________________________________
| Curtis D. Levin kd4zkw | lleyfdz.yuiwxmpk@hydris.com | QRP-L #1488 |
| qwk.scqr@mct.ne.jp | http://www.diaisdn.net/user/cdlevin |
| kd4zkw.ampr.org [44.98.2.22] Exp Ax25/Linux DPTNTv1.1a3 |
| amprnet e-mail : qmnt.ftmtd@roskapostia.tunk.net |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~