Skip to contentSkip to conversation

ax25d not hearing incoming connection requests

DISCUSSION GeForce 3 participants 3 messages Jan 2, 2009

lore
Share & tools
lore

GeForce

author
#0 lore raw

Hi all, need a hand here if you would be so kind. I have ax25d running, with ax25d.conf looking like this:

[M3XYZ-1 VIA tncx]
default 1 * * * * * * root /usr/sbin/axspawn axspawn %u

Using the "listen" command I can see the incoming connection request packets, which look like:

tncx: fm M3XYZ-3 to M3XYZ-1 ctl SABM+

But ax25d seems to be doing nothing with them! ax25d is set to log, but there are no entries in the syslog related to the incoming connection. The only ax25d entries are "starting" and "loaded config successfully" ones.

I can transmit a packet using
beacon -s tncx "hello"
without any problems, so I know both stations can tx and rx correctly.

Anyone got any ideas as to why ax25d is not responding to the connection request?

Thanks,
Jon

Signature · 2 lines
View this message in context: http://www.nabble.com/ax25d-not-hearing-incoming-connection-requests-tp21253389p21253389.html
Sent from the linux-hams mailing list archive at Nabble.com.
#1 lore raw
Quoted 2 lines · GeForce

Anyone got any ideas as to why ax25d is not responding to the connection request?

It's been a while since I've played with that stuff, but I seem to recall that you need to send a line first so that the protocol is known to the AX.25 kernel-mode layer. Once the protocol is known then the packets start getting fed to whatever applications have registered to receive that protocol.

"Listen" is a special case in that it has registered to receive everything.

For instance a ROSE packet might get routed to one application, connected mode info packet to another (aprsd in this case). Extend this to APRS, NET/ROM, TCP, UDP, etc.

The connection packet itself doesn't specify the upper-level protocol being used, therefore there's nothing to send to the application at that point.

Send a blank packet immediately after the connect packet which should pass a LF or a CRLF off to aprsd. Aprsd should then respond.

That was one thing I had to get used to compared to similar non-Linux systems way back when: Sending an extra packet before the stuff would respond to me in connected mode.

Signature · 5 lines
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"
#2 lore raw
In reply to GeForce
Quoted 19 lines · GeForce

Hi all, need a hand here if you would be so kind. I have ax25d running, with ax25d.conf looking like this:

[M3XYZ-1 VIA tncx]
default 1 * * * * * * root /usr/sbin/axspawn axspawn %u

Using the "listen" command I can see the incoming connection request packets, which look like:

tncx: fm M3XYZ-3 to M3XYZ-1 ctl SABM+

But ax25d seems to be doing nothing with them! ax25d is set to log, but there are no entries in the syslog related to the incoming connection. The only ax25d entries are "starting" and "loaded config successfully" ones.

I can transmit a packet using
beacon -s tncx "hello"
without any problems, so I know both stations can tx and rx correctly.

Quoted 6 lines

Anyone got any ideas as to why ax25d is not responding to the connection request?

Thanks,
Jon

Jon,

My only use for ax25d these days is to steer Netrom connections to fpacnode. All other applications (ax25 and Rose) do their own listening so entries in ax25d.conf aren't needed.

If you wish to contact me off list I try to help you out.

Ray vk2tv