Setting up tunnels under Redhat Ver 6.0

1999-07-31 Thread Tony McClellan
Could anyone explain how to setup the tunnels in RedHat Ver 6.0. As there are major changes, could someone explain what has changed between 5.2 and 6.0 Tony

Re: CEPT callsigns

1999-07-31 Thread Geoff Blake
On Sat, 31 Jul 1999, Riley Williams wrote: > Also note that the following is a perfectly valid callsign which also > doesn't fit in the AX.25 spcification: > > PA/GM7GOD/MM > > That is the callsign that *I* would have to use if operating from a > ship sailing in tidal waters claimed by th

Re: Cept calls

1999-07-31 Thread Riley Williams
Hi Richard. > Thanks to all you made constructive comments and also included > forms for the application a German reciprocal. Nodz. > Callsign fields of greater than 6 chars need to be implemented , > albeit the ax25 protocol still states 6, but this has been > modified before. so a preced

Re: CEPT callsigns

1999-07-31 Thread Riley Williams
Hi Thomas. >> ie. bit 0 is set to say this is the end of the address field - >> by this means, AX25 (and X25 on which it is based) already >> support variable length address fields. >> That most implementations don't support it is another matter >> entirely!!! > Well, this is not exactly

Re: CEPT callsigns

1999-07-31 Thread Riley Williams
Hi Robin. >> To be honest, the AX.25 specification needs SERIOUS revision in >> this area, to allow for callsigns of any length or pattern to be >> used. However, it needs to be done in a manner compatible with >> the current standard. >> My suggestion would be to make it dynamic to suit th

Re: Using 2.2.? kernels

1999-07-31 Thread Riley Williams
Hi Karl. >>> ...under the 2.0.38 kernel. >> When was 2.0.38 released? I can't find it anywhere... > Sorry, That is a typo. I am using 2.0.36 now. No problem, just that you were the fourth person in as many messages to refer to 2.0.38 and I was beginning to get worried as a result... Best w

Re: CEPT callsigns

1999-07-31 Thread Robert Steinhaeusser
Hello Riley, > >> Also note that the following is a perfectly valid callsign which > >> also doesn't fit in the AX.25 spcification: > > >> PA/GM7GOD/MM > > >> That is the callsign that *I* would have to use if operating from > >> a ship sailing in tidal waters claimed by the Netherlands.

Re: Using 2.2.? kernels

1999-07-31 Thread Karl F. Larsen
Sorry, That is a typo. I am using 2.0.36 now. On Sat, 31 Jul 1999, Riley Williams wrote: } Hi Karl. } } > ...under the 2.0.38 kernel. } } When was 2.0.38 released? I can't find it anywhere... } } Best wishes from Riley. } } +

Re: Cept calls

1999-07-31 Thread Robin Gilks
- Original Message - From: richard bown <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 31 July 1999 21:00 Subject: Cept calls [snip] > No Robin contacting immigration wont stop me getting back !!! > As if I'd do such a thing Will you be writing up the 23cm radar interference

Cept calls

1999-07-31 Thread richard bown
Thanks to all you made constructive comments and also included forms for the application a German reciprocal. Callsign fields of greater than 6 chars need to be implemented , albeit the ax25 protocol still states 6, but this has been modified before. so a precedent has already been set. As far as

Re: CEPT callsigns

1999-07-31 Thread Thomas KE6CBR
On Sat, Jul 31, 1999 at 01:40:08PM +0100, Robin Gilks wrote: > ie. bit 0 is set to say this is the end of the address field - > by this means, AX25 (and X25 on which it is based) already > support variable length address fields. > > That most implementations don't support it is another matter > e

Re: Using 2.2.? kernels

1999-07-31 Thread Richard Adams
> > 2.0.38?? > > Possibly you should submit this to Linus. Editing /usr/src/linux/Makefile does wonders.. > > Bob > > On Sat, Jul 31, 1999 at 06:33:11AM -0600, Karl F. Larsen wrote: > > > > Hi Bob, I got your tarball thanks and will work with it. I will not use > > your ax25d.conf and

Re: Cept callsigns

1999-07-31 Thread Wayne Nakata
Hi here is the form you need to apply for a German license. 73 Wayne N1WPN I used to be DA2YD mstr_antrag.doc

Re: Using 2.2.? kernels

1999-07-31 Thread Bob Nielsen
2.0.38?? Possibly you should submit this to Linus. Bob On Sat, Jul 31, 1999 at 06:33:11AM -0600, Karl F. Larsen wrote: > > Hi Bob, I got your tarball thanks and will work with it. I will not use > your ax25d.conf and such because I have those that work fine for my setup > under the 2.0.38 ke

Re: Cept callsigns

1999-07-31 Thread Bob Nielsen
There was a ham with a French callsign running a BBS in Texas. He just used his F callsign for connecting and beaconed an I.D. with the w5/, as I recall. This may have been confusing to some, but is legal in the U.S., possibly elsewhere. Bob On Sat, Jul 31, 1999 at 09:25:54AM +0100, richard bo

Re: CEPT callsigns

1999-07-31 Thread Riley Williams
Hi Robert. >> Also note that the following is a perfectly valid callsign which >> also doesn't fit in the AX.25 spcification: >> PA/GM7GOD/MM >> That is the callsign that *I* would have to use if operating from >> a ship sailing in tidal waters claimed by the Netherlands. > AFAIK, th

Re: Using 2.2.? kernels

1999-07-31 Thread Riley Williams
Hi Karl. > ...under the 2.0.38 kernel. When was 2.0.38 released? I can't find it anywhere... Best wishes from Riley. +--+ | There is something frustrating about the quality and speed of Linux | | development, ie., the qualit

Re: CEPT callsigns

1999-07-31 Thread Robin Gilks
- Original Message - From: Riley Williams <[EMAIL PROTECTED]> To: Richard Bown <[EMAIL PROTECTED]> Cc: Linux Ham Radio <[EMAIL PROTECTED]> Sent: 31 July 1999 13:02 Subject: Re: CEPT callsigns [snip] > To be honest, the AX.25 specification needs SERIOUS revision in this > area, to allow

Re: CEPT callsigns

1999-07-31 Thread Robert Steinhaeusser
Hi all, On Sat, 31 Jul 1999, Riley Williams wrote: > > Hi all, as I will be working in Germany for the next year, no > > that doesn't mean you wont hear from me !, Would be bad, if German e-mail wouldn't make it around the world. Buh! Now how did I get here? :) > > I've come across a proble

[Fwd: No Ping Return]

1999-07-31 Thread Nate Bargmann
This is on behalf of a friend who accesses the list through a BBS mail reader through a service provided by the local university. He is subscribed to the list and can read your responses. Should you wish to reply direct, hs address is: [EMAIL PROTECTED] (JOHN BANDY) 73, de Nate >> JOHN BANDY w

Re: Using 2.2.? kernels

1999-07-31 Thread Karl F. Larsen
Hi Bob, I got your tarball thanks and will work with it. I will not use your ax25d.conf and such because I have those that work fine for my setup under the 2.0.38 kernel. I'm still concerned about the kernel configuration. This is because everything but "call" works fine right now. I have watche

Re: CEPT callsigns

1999-07-31 Thread Riley Williams
Hi Richard. > Hi all, as I will be working in Germany for the next year, no > that doesn't mean you wont hear from me !, Chuckle... > I've come across a problem common to linux node, jnos, tnos and > fbb and probally a few more as well. All of the above check for > valid callsigns , ie 6 c

Cept callsigns

1999-07-31 Thread Torsten Harenberg
richard bown writes: > So it looks like the only way around this is to apply to the German PTT > for a true reciprocal licence , and you know how pedantic the German s > can be !. > Or is it a case of so what we'll just wait til some country uses 7 char > callsigns, well that may not be too

Re: Cept callsigns

1999-07-31 Thread Thomas M.
On Sat, 31 Jul 1999, richard bown wrote: > now how about the followingdc/g8jvm a perfectly valid callsign > but the "/" is not accepted or any other delimiter. Isn't the ax25 protocol itself limited to 6 chars in the call?? I havent seen any tnc/programs that supports more than 6 chars

RE: Cept callsigns

1999-07-31 Thread Dirk Koopman
On 31-Jul-99 richard bown wrote: > So it looks like the only way around this is to apply to the German PTT > for a true reciprocal licence , and you know how pedantic the German s > can be !. > Or is it a case of so what we'll just wait til some country uses 7 char > callsigns, well that may not

Cept callsigns

1999-07-31 Thread richard bown
Hi all, as I will be working in Germany for the next year, no that doesn't mean you wont hear from me !, I've come across a problem common to linux node , jnos, tnos and fbb and probally a few more as well. All of the above check for valid callsigns , ie 6 characters and a number in it somewhere.