On Mon, May 22, 2000 at 07:26:07PM -0400, Bruno Quesnel wrote:
> Now the problem that I have is that when trying to connect to the 44
> network, their is multiple transmit, then seems to wait, then receives
> the stuff or replies. Le tme give you an exmaple, when doing a ping
> with a 44 adress, their is multiple transmit (I can see the lights on
> TNC and I see with ifconfig TX packet increading) but nothing would ack
> the first ping.
Be sure to watch it with "listen" while doing this test... it's
slow enough you can see exactly what's going on. listen -at is
a good thing to leave running in an xterm at all times. (Or listen
-at -p rp0 to restrict it to one port, if you've got AXIP traffic
also it's distracting.)
When I've had this problem (packets not being acked) it was because
of radio problems... it was going "deaf" and not hearing the replies.
In that case you will hear a packet on the radio but not see the
TNC light that indicates data is being sent back to the PC. (Mine
has a green light for DCD, indicating that it's trying to decode a
packet, and another light that blinks when it actually decodes the
packet and sends it to the PC.)
Too short a TXD on the other end can do it too - your neighbor starts
transmitting before your radio's relay has quite flopped back over to
receive.
I did a bit of tuning on my Mitrek and am getting much better performance
now. 'course, at 1200 baud, it shouldn't be as critical.
--
_______ Shawn T. Rutledge / KB7PWD [EMAIL PROTECTED]
(_ | |_) http://www.bigfoot.com/~ecloud [EMAIL PROTECTED]
__) | | \________________________________________________________________
Get money for spare CPU cycles at http://www.ProcessTree.com/?sponsor=5903
