Bill Vodall WA7NWP wrote:
> Xastir does need SUID, but not because of the serial port. Xastir
needs SU
> privileges in order to open the eoc ax.25 port.
That's a bit strange. Is the ax25 Listen command SUID? I know it
(Listen) works once the associated serial port is set RW for the
regular
> Xastir does need SUID, but not because of the serial port. Xastir needs SU
> privileges in order to open the eoc ax.25 port.
That's a bit strange. Is the ax25 Listen command SUID? I know it
(Listen) works once the associated serial port is set RW for the
regular user. Maybe Listen is doin
> chmod 4755 /usr/local/bin/xastir
Thanks. I'll try that right away this evening.
Thanks again - it worked. It appears Xastir is going to make a very
handy gateway for this other packet channel.
Adding a pop-up warning dialog for the ax25 setup should be a good
beginner exercise in t
On Mon, 16 Jul 2007, J. Lance Cotton wrote:
> Xastir does need SUID, but not because of the serial port. Xastir needs SU
> privileges in order to open the eoc ax.25 port.
Yes. This is a Linux kernel driver limitation, so we can't work
around it. Xastir has code in it to drop to regular user pri
on 7/16/2007 10:40 AM Bill Vodall WA7NWP said the following:
> The only problem is that the AX25 Interface isn't working. I set up
> an interface, put in the name of the AX25 device ("eoc") clicked start
> and nothing happens. No debug messages, no errors, nada.
>
> What's the trick here?
> PS.
Hi,
This weekend I started up Xastir initially with the intent of just
watching the local traffic. Then I realized that I might as well use
it with the AX25 (packet on Linux) connection to both view and Igate
on another local packet channel. It should be very fun and even
useful.
The only prob
On Sun, 4 Mar 2007, Lance Cotton wrote:
> Xastir needs to be set SUID so that it can open an ax.25 socket.
>
> try a `chmod 4755 /usr/local/bin/xastir` first
Yes. This will get you around possible permissions problems with
the ports _and_ the kernel requirement that network protocol access
requ
That took care of it, thanks a mil!
Stephen
N1VLV
On 3/4/07, Lance Cotton <[EMAIL PROTECTED]> wrote:
Xastir needs to be set SUID so that it can open an ax.25 socket.
try a `chmod 4755 /usr/local/bin/xastir` first
-Lance KJ5O
Stephen Brown Jr wrote:
> I'm in the process of setting up Xastir
Xastir needs to be set SUID so that it can open an ax.25 socket.
try a `chmod 4755 /usr/local/bin/xastir` first
-Lance KJ5O
Stephen Brown Jr wrote:
I'm in the process of setting up Xastir to use an AX25 interface and for
some reason I get this when I try to connect to it:
[EMAIL PROTECTED]:~$
On Mar 4, 2007, at 11:18 AM, Stephen Brown Jr wrote:
I also looked at the permissions
for the pty port:
crw-rw-rw- 1 root tty 2, 0 2007-02-24 19:51 /dev/ptyp0
I think these things come in pairs - ptypX and ttypX. If it's a
permission problem, you may need to check/change both.
-Jason
I'm in the process of setting up Xastir to use an AX25 interface and for
some reason I get this when I try to connect to it:
[EMAIL PROTECTED]:~$ socket: Operation not permitted
Sun Mar 04 12:12:27 EST 2007:
Interface Error! Error opening interface 1 Hard Fail
I am running Ubuntu 6.06 an
11 matches
Mail list logo
