| |
ZL3AI > APRDIG 28.12.03 14:19l 228 Lines 9314 Bytes #999 (0) @ WW
BID : 2564-ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 26, 1/2
Path: DB0FHN<DB0RGB<DB0AAB<F6KFT<LX0PAC<DB0GH<F6KMO<ON0AR<ON0AR<WB0TAX<
N1UAN<ZL2BAU<ZL2BAU<ZL3VML
Sent: 031228/1133Z @:ZL3VML.#80.NZL.OC #:15485 [Chch-NZ] FBB7.00i $:2564-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Friday, December 26, 2003.
1. Re: UIView , Firewall
2. Re: TNC-X is Now Shipping -- Question on KISS mode....
3. WTB: Kenwood TH-D7A(G)
4. Re: -- Question on KISS mode....
5. Re: TNC-X is Now Shipping -- Question on KISS mode....
6. Re: -- Question on KISS mode....
7. Re: TNC-X is Now Shipping -- Question on KISS mode....
8. Source Code for TNC-X - Request for Comments before making a final decision
9. Re: KPC-3 does interesting things...
----------------------------------------------------------------------
Subject: Re: UIView , Firewall
From: KC7ZRU <kc7zru@arrl.net>
Date: Thu, 25 Dec 2003 23:16:54 -0700
X-Message-Number: 1
David Holland wrote:
>Hi
>
>I am looking for the way to set up UIVIEW when working from behind a
>firewall. I can't find info in the help files on where to set UIView up
>
>Regards David ZL2TAA
If you're using UI-View as a client only package, most firewalls will
allow outgoing connections just fine. That is, UI-view should have no
problem connecting up to a server. If that's the problem, you need to
talk to whoever it is that manages your firewall (firewall admin) or
learn about how to setup your firewall.
If you're the firewall-admin and you want to allow others to connect to
your UI-view, well there's a bit to be considered before doing this.
Hard to tell, but from the 'tone' of your message I'm assuming you're a
home user and you're asking about your own, personal firewall. In that case:
Take a quick look at this for some background on internet connectivity:
http://en.tldp.org/HOWTO/Unix-and-Internet-Fundamentals-HOWTO/internet.html
Last paragraph will talk about HTTP - the WWW and port 80.
After that, I'd take at least a quick look around at:
http://www.securityfocus.com/foundations
3 articles in the left colum - good start.
However, if I've assumed wrong and you're talking about a corporate or
business firewall - talk to your sys-admin.
73
----------------------------------------------------------------------
Subject: Re: TNC-X is Now Shipping -- Question on KISS mode....
From: WA8LMF2@aol.com
Date: Fri, 26 Dec 2003 05:53:38 EST
X-Message-Number: 2
I'm not intimately familiar with the inner working of KISS mode although I
realize that it offloads the task of interpreting a packet's data and path
information to the host computer.
Am I correct in assuming that connecting the RXD line of a purely-KISS
device like TNC-X to it's own TXD line would cause incoming packets to be
retransmitted exactly as-is? That is, no path changes, no digipeat hops
marked off as used, etc.
The reason I ask this is that if this does work, TNC-X might be the perfect
device as-is (i.e. no daughter boards for APRS-specific digipeating) for
inexpensively adding Mic-E capability to voice repeaters.
A dilemma I have pondered in the past working out Mic-E for voice repeaters
is that the standard approach of using a KPC+ or UI-DIGI TNC2 is that the
first hop of the path set into the user's packet burst will get "used up"
just passing into the voice repeater and out on 144.39. The result is that
if the user's radio / TNC / tracker is set for the customary pathing in an
area for operation directly on 144.39, it will be one hop short when
routed through a Mic-E voice repeater instead.
If my assumption about the direct KISS-RX-out to KISS TX-in connection is
correct, the voice repeater Mic-E operation would then become totally
transparent to the user's path, making no changes at all.
Any thoughts anyone ???
Stephen H. Smith wa8lmf (at) aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: Re: -- Question on KISS mode....
From: Bill Vodall - WA7NWP <wa7nwp@jnos.org>
Date: Fri, 26 Dec 2003 09:10:08 -0800 (PST)
X-Message-Number: 4
>Am I correct in assuming that connecting the RXD line of a purely-KISS device
>like TNC-X to it's own TXD line would cause incoming packets to be
>retransmitted exactly as-is? That is, no path changes, no digipeat
>hops marked off as used, etc.
That is correct. This technique has been used before for various
linking between channels.
73,
Bill - WA7NWP
----------------------------------------------------------------------
Subject: Re: TNC-X is Now Shipping -- Question on KISS mode....
From: wes@johnston.net
Date: Fri, 26 Dec 2003 14:08:18 -0500 (EST)
X-Message-Number: 5
The problem with this is that the Has Been Digi'ed flag never gets set...
so you end up with a potential infinity loop if two digipeaters such as
this are in the same area and on the 144.39 APRS network.
I've used this technique for 9600RX on repeater voice input to get a 9600
baud mic-e packet over to 1200 baud aprs channel. In this case, there is
never a chance for a loop b/c the RX frequency and mode are different than
the output. I have done it with two kpc3's, and a Spirit 9600 paccom and a
kpc3. Be aware that the if you use a TNCx it will be TX'ing blind... it
will have no way to know if it's QRMing another APRS station and the user's
packet will be lost.
I think a preferred method of doing this would be to come up with some
obscure frequency on 70cm or 23cm to link all the mic-e repeaters in the
area to someone's home or other digipeater on a dedicated link. I think
the chances of loosing a packet due to collision is pretty good if you TX
blind onto aprs frequency. However, the chances of loosing a packet on a
dedicated link is much much smaller. Let the user's home station IGATE the
packet or digipeat it out on 144.39.
Of course, the best way is to use a kpc3plus for the RX of packets on the
repeater input freq (and it's mute function), and serially link it to
another kpc3 (does not have to be a plus) on 144.39. This second kpc3 will
listen for other activity on 144.39 and hold off TX.
KPC3's will also CWID when in kiss mode. This is handy for ID'ing links.
TNCx will not CWID or inmode ID.... so it won't really be legal.
The TNCx has the true DCD mode, but I have seen it false... Pretty rare,
but it would be aggrivating to voice users to sporatically have their
voices muted...so it may be necessary to place the DCD in series with a 555
timer set for a 10ms delay to trigger any muting if you wish to use it.
WEs
ham callsign: kd4rdb
find me: http://wesvan.zapto.org
----------------------------------------------------------------------
Subject: Re: -- Question on KISS mode....
From: "Curt Mills, WE7U" <archer@eskimo.com>
Date: Fri, 26 Dec 2003 12:55:50 -0800 (PST)
X-Message-Number: 6
On Fri, 26 Dec 2003, Bill Vodall - WA7NWP wrote:
>>Am I correct in assuming that connecting the RXD line of a purely-KISS device
>>like TNC-X to it's own TXD line would cause incoming packets to be
>>retransmitted exactly as-is? That is, no path changes, no digipeat
>>hops marked off as used, etc.
>
>That is correct. This technique has been used before for various
>linking between channels.
Note that you have to have some other mechanism for automatic ID of
the repeater, such as turning the morse-code ID feature on. It's not
identified via AX.25 on each packet.
Also makes a cross-band repeater for putting special-event stations
(balloon, rally, walk-a-thon, etc) onto the main APRS frequency,
while allowing a clear channel for the event itself.
--
Curt, WE7U. archer@eskimo.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!"
----------------------------------------------------------------------
Subject: Re: TNC-X is Now Shipping -- Question on KISS mode....
From: Jeff King <jeff@aerodata.net>
Date: Fri, 26 Dec 2003 14:59:34 -0500
X-Message-Number: 7
What is being discussed is a packet bent pipe, aka a digital crossband
repeater. Of course, if you put it on the same frequency, you'll get a
feedback loop. Used as the author intended (from<>to a repeater to APRS) you
should not have this problem.
This method, along with direct packet regeneration, depends on both ends of
the pipe being on different frequencies. I've never seen this done right yet,
the ideal implementation would need some amount of intelligence, but nothing
a PIC couldn't handle. You give the voice users priority so you do need to
diddle the DCD lines to hold off any queued packets (which would be the
advantage of the KISS crossband as opposed to a packet regenerator).
A proper implementation of KISS implements DCD (I know this is a fact on the
TNC2), so it should not be transmitting in the blind. Can't speak on this
regarding the TNC-X.
BTW, anyone know the status of the TNC-X source code? open or closed? Was
holding off getting one until I knew the status.
--
Jeff King, jeff@aerodata.net on 12/26/2003
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
