I also use axdigi and it works well. But it needs one change -- it's
an all-or-nothing tool in that when it's running, it allows wide-open
digipeating from any port on the system to any other port. I've had a
few lusers do Very Bad Things to our network when they discovered, for
example, that they could digi from the slow 1200 baud port to the 19.2kb
port. We need a little config file that specifies allowable input to
output mappings.
Having said that, I *don't* commit to do the mods (though I might give it
a try in my spare time).
John N8UR
[EMAIL PROTECTED]
----
In message <002601bf2695$785ce640$[EMAIL PROTECTED]>, "Phil Maley" writes:
>Hi Chris
>
>I am using axdigi on a gateway system to digipeat between the RF
>ports and the axip wormhole port. It works very well. I guess it
>was a philosophical decision to remove a "user space" application
>from the kernel even though to me as a user it would seem to fall
>in the same category as kernel ip forwarding. I don't know of any
>alternatives to axdigi.
>
>73
>Phil VK6AD
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Ruffin
>> Sent: Thursday, 4 November 1999 13:50
>> To: [EMAIL PROTECTED]
>> Subject: axdigi vs. other methods?
>>
>>
>>
>> What is the best way to handle digipeating with linux? I've
>> looked at the linux-hams archive and it seems that there used to
>> be support for this in the kernel, but then there is axdigi,
>> which I find odd not to be in a debian package. I figure that
>> there would be axdigi in a package somewhere if there wasn't
>> kernel support for it. In fact, I saw on the archive where it
>> had been "taken out," which I don't particularly understand.
>>
>> So, before I install axdigi (I hate installing non-packagized
>> software)- is there another way to do this with the kernel?
>>
>> Chris
>> --
>> Chris Ruffin <[EMAIL PROTECTED]>
>> http://www.ece.msstate.edu/~ruff/
>>
>>
>>
>>
