| |
ZL3AI > APRDIG 28.08.06 23:10l 253 Lines 8397 Bytes #999 (0) @ WW
BID : 8674-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 26 #26, 2/3
Path: DB0FHN<DB0MRW<DK0WUE<DB0RES<TU5EX<IW2OAZ<ZL2BAU
Sent: 060828/2104Z @:ZL2BAU.#87.NZL.OC #:912 [Waimate] $:8674-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Message: 10
Date: Fri, 25 Aug 2006 17:36:18 -0500 (CDT)
From: wa7nwp_at_jnos.org
Subject: Re: [aprssig] JNOS Interface question
>Gudday
>
>I have JNOS ruinning and can do some basic tcpip over radio stuff.
>
>When i look at ifconfig in linux, i do not see the vhf interface.
>
>Is it only available in JNOS ?
>
>Perhaps I need to do ax25 support in LINUX instead ?
AX25 in Linux would be one option.
If you stick with JNOS, you'll have to use either the TUN driver or create
a pseudo-tty connection between JNOS and Linux to establish a TCP/IP
connection between them.
------------------------------
Message: 11
Date: Sat, 26 Aug 2006 08:44:15 +1000
From: "Andrew Rich" <vk4tec_at_tech-software.net>
Subject: [aprssig] SUSE LINUX AX25
Ok I have made the dicision I need to use the kernel ax25
I have suse linux and seem to have the ax25 installed.
How do I configure it ? how do i start it ?
I know there is some stuff on google but it is giving me a headache.
I need a simple step by step to get me going.
Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_tech-software.net
web: http://www.tech-software.net
Brisbane AUSTRALIA
------------------------------
Message: 12
Date: Sat, 26 Aug 2006 08:57:40 +1000
From: "Andrew Rich" <vk4tec_at_tech-software.net>
Subject: [aprssig] RE: SUSE LINUX AX25
Ok here is what I did
1) Run YAST in SUSE and enable ax25 libraries
2) edit /etc/axports
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
1 VK4TEC 1200 255 2 144.675 MHz (1200 bps)
3) linux:/usr/sbin # kissattach /dev/ttyS1 1 192.168.1.105
4) Gets me this in ifconfig from linux
ax0 Link encap:AMPR AX.25 HWaddr OH2BNS-1
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MTU:255 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
*** sorry i had the other persons callsign left over ***
now what ?
Route ?
Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_tech-software.net
web: http://www.tech-software.net
Brisbane AUSTRALIA
------------------------------
Message: 13
Date: Fri, 25 Aug 2006 18:01:32 -0500 (CDT)
From: wa7nwp_at_jnos.org
Subject: Re: [aprssig] SUSE LINUX AX25
>Ok I have made the dicision I need to use the kernel ax25
>
>I have suse linux and seem to have the ax25 installed.
Which version of SUSE and which Kernel - that's a big issue.
The (mostly) official instructions:
http://www.tldp.org/HOWTO/AX25-HOWTO/
73
Bill - wa7nwp
------------------------------
Message: 14
Date: Thu, 24 Aug 2006 19:37:46 -0700
From: "Keith - VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] rotate2.aprs.net down?
I wrote...
>My conclusions... [re] "T2MCI" (using rotate.aprs2.net:14580)
>Looks like there is a snag with that server...
I later heard from Joe KA3NAM that central.aprs2.net (T2MCI) underwent a
firewall upgrade about 11:30 AM Central today. This may or may not have
been why Brad VE3BSM was having a problem with rotate.aprs2.net:14580. The
T2MCI server looks OK now.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 15
Date: Fri, 25 Aug 2006 20:18:17 -0500
From: "Tim Cunningham" <tim_cunningham_at_mindspring.com>
Subject: Re: [aprssig] Delayed packets (yet again)
There was a delayed packet discussion specifically concerning IGates
recently. We did a through study into the problem in my area and isolated
the problem to a UI-View station operating as an IGate. Since that
discussion there were a few other folks across the country who wrote
off-line that they experienced the same issue with UI-View in their areas.
This issue was specifically limited to a UI-View IGate that was injecting
packets greater than 1 minute later than another IGate using APRS+SA. Many
of the packets were time stamped to verify the delay. It was not a
digipeater delay because we could see two IGates hearing the same packet
from the same digipeater being injected into the APRS-IS greater than one
minute apart.
IGates that are experiencing delays should consider using filtered port
14580 and limit their data to under 100 to 200km using the m/100 to m/200
qualifier. When an IGate tries to process the full feed they are going to
run slower depending on their computer configuration and whether they are
using a dial-up feed or a high speed link.
There are many sources of delays that also include digipeaters. The first
step is to identify if the delay is the USB to serial converter which
should be fairly easy by visual observation on how long it takes a decoded
packet to appear on the screen. Then, it becomes only a measure of time
from that point to when it appears on the APRS-IS.
73's,
Tim - N8DEU
Huntsville, Alabama
------------------------------
Message: 16
Date: Fri, 25 Aug 2006 23:03:50 -0400
From: "Wes Johnston, AI4PX" <wes_at_kd4rdb.com>
Subject: Re: [aprssig] Delayed packets (yet again)
Recently kc4pl and I saw enormous delays on RF. We've seen igate delays
from ww6jc in a nearby town running ui-view. At anyrate, kc4pl is running
TNC-x and an ax.25 stack connected to javaaprs. What we saw was /were
delays on the order of 60 to 90 seconds. I was sending packets that were
uniquely numbered so we'd know which got thru and which didn't.
We suspected that perhaps TNCx was hearing too many packets on frequency to
TX, so he QSY'ed the radio. I send a few more packets. Then it dawned on
us that he wasn't seeing the packets I send for 60 to 90 seconds. As soon
as he saw them appear in the ax.25 stack, they were digipeater. In the
process of reaching under the desk, he may have reset or momentarly
interrupted the power to the TNCx.... so we're not sure if the tnc-x is the
problem or the ax.25 stack in linux. Or maybe some part of the system
needed a break. At this time, we're waiting for the delays to happen again
so we can figure out if it's TNC-x or ax25 stack.
Possible theories include that TNCx may have a memory leak... tncx may
spend so much time servicing interrupts in a busy channel that it can't
deliver data to the serial port. ubuntu ax25 may have a problem.
Really don't know anything difinitive at this point.
Wes
------------------------------
Message: 17
Date: Sat, 26 Aug 2006 08:23:08 -0400
From: "Ron Wenig" <ny3j_at_comcast.net>
Subject: [aprssig] ISS
Good Morning All,
I just read Steve WB8IMY Ford's article in this month's QST on APRS and ISS
and decided to give it a try. I followed the instructions in the article
and set up the receive frequency for 145.800. I have a prediction program
running and listened for packets with UI-View when the ISS was in site but I
couldn't even hear a slight signal from it. Before I beat my head against
the wall too many more times is the packet station turned on and should I at
least be able to copy packets from the ISS.
Thanks and 73,
Ron ny3j_at_comcast.net
------------------------------
Message: 18
Date: Sat, 26 Aug 2006 08:18:35 -0500
From: Mark Cheavens <mcheavens_at_usa.net>
Subject: Re: [aprssig] Delayed packets (yet again)
In various parts of the country I have also narrowed it down twice to two
different RF issues.
1. I found a TNC/Radio combination that was not using DCD, but was instead
using squelched audio for the TNC to decode. When the squelch was left
OPEN, the TNC would not transmit until it's internal buffer got full and
then DUMPED the entire contents of it's buffer in one continuous stream.
2. Similar issue as above, but the root cause was a digi that routinely
heard a continuous stream of packets from so many other digi's that it
would also que all the messages until it's buffer got full and then would
do a DUMP of it's contents. (It could hold about 2 minutes of continuous
packets when it did transmit).
In both cases above these happen to be on KPC-3's. I have never bench
proven if this could occur with other TNC's/Firmware versions.
I have seen delays from I-Gates as well cause the problem, but have never
PROVEN whether it was a slow computer/local connectivity problem, or a
problem with the APRS server it was attached to.
Mark Cheavens
KC5EVE
------------------------------
Read previous mail | Read next mail
| |
