[Packet] Packet under Linux - port not active.

Doug Laidlaw laidlaws at hotkey.net.au
Tue May 9 03:34:31 EDT 2006


Here are the answers:

axparms -route list:
callsign  dev  mode digipeaters

ifconfig (ax0 only)
ax0       Link encap:AMPR AX.25  HWaddr VK3KDI-1
          inet addr:192.168.44.1  Bcast:192.168.44.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:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 b)  TX bytes:3975 (3.8 KiB)

At the moment I am running merely the computer and the modem.  My rig is deaf, 
and that is my next task.  Perhaps I need to do that before proceeding?

I don't know if the above results are normal, but they both look as though 
there is nothing obviously wrong.

Doug.

On Tue, 9 May 2006 05:21 am, you wrote:
> Doug,
>
> If you do an "axparms -route list" command, what does it bring back?
>
> What does "ifconfig" give you? Does it show the ax0 port?
>
> tim ab0wr
>
> On Sunday 07 May 2006 20:31, you wrote:
> > When the port is taken over, nothing can access it, not even minicom. 
> > The script i use puts the TNC in kiss mode.  I did it manually to make
> > sure, then ran kissattach, and the port was not active.  The problem
> > seems to be to make the ax0 port active and not to lock the COM port.
> >
> > Doug.
> >
> > On Sat, 6 May 2006 11:26 am, you wrote:
> > > Doug,
> > >
> > > Are you sure your MFJ1270B is in kiss mode? In mine I had to get a kiss
> > > only eeprom to make sure it always came up in kiss mode. Otherwise I
> > > had to use minicom to access the modem and put it in kiss mode before
> > > doing my kissattach.
> > >
> > > I suspect that if the tnc is not in kiss mode it is going to look to
> > > the computer like the vhf port is not working. It's been so long that I
> > > can't remember if that was the same symptom on my system or not.
> > >
> > > Something to check anyway. Use minicom to hit your serial port and see
> > > what you get for a reply.
> > >
> > > tim ab0wr
> > >
> > > On Friday 05 May 2006 17:07, you wrote:
> > > > Thanks Tim.  You are right. The TNC is set at 9600.  I had this right
> > > > earlier but abandoned the experiment.
> > > >
> > > > It is not the whole answer however.  I tried going back to a 2.4
> > > > kernel. With it, the ax0 port appears in GkrellM, but the VHF port is
> > > > still not active. That is about as far as I got last time.  With the
> > > > 2.4 kernel, my USB devices don't work, so it isn't really an
> > > > acceptable solution.
> > > >
> > > > Doug.
> > > >
> > > > On Saturday 06 May 2006 06:12, Tim Gorman wrote:
> > > > > In axports are you sure you have your tnc set to 1200bps?
> > > > >
> > > > > I thought the third parameter was the interface speed, not the
> > > > > tnc/radio speed.
> > > > >
> > > > > If you are using kissattach I think you can leave the interface
> > > > > speed in axports set to 0:
> > > > >
> > > > > vhf vk3kdi-1 0 255 2 144.925
> > > > >
> > > > > or try  You are right about the interface speed.  The TNC is set at
> > > > > 90600.
> > > > >
> > > > > vhf vk3kdi-1 9600 255 2 144.925
> > > > >
> > > > > tim ab0wr
> > > > >
> > > > > On Thursday 04 May 2006 21:07, Doug Laidlaw wrote:
> > > > > > I am running Mandriva 2006 with kernel 2.6.12 into a MFJ 1270B.
> > > > > > When trying to start packet, I got an error message:
> > > > > >
> > > > > > 	kissattach: Error setting line discipline: TIOCSETD: No such
> > > > > > device
> > > > > >
> > > > > > On googling, I found a reply in Debian-hams to somebody using
> > > > > > Ubuntu (also kernel 2.6.12) advising him to upgrade to kernel
> > > > > > 2.6.16, or at least 2.6.14. I downloaded kernel2.6.16 and that
> > > > > > seems to have dealt with that one.
> > > > > >
> > > > > > Now, when I start packet, the port  (COM2, /dev/ttyS1) is
> > > > > > assigned to ax0 and is promptly locked and made inaccessible.  In
> > > > > > a Linpac terminal and elsewhere, there is a statement that my VHF
> > > > > > port is not active and the computer port cannot be accessed. 
> > > > > > T+Relevant config files are as follows:
> > > > > >
> > > > > > axports:
> > > > > > # /etc/ax25/axports
> > > > > > #
> > > > > > # The format of this file is:
> > > > > > #
> > > > > > # name callsign speed paclen window description
> > > > > > #
> > > > > > vhf     VK3KDI-1        1200    255     2       144.925 MHz (1200
> > > > > > bps)
> > > > > >
> > > > > > ax25d.conf:
> > > > > > # ax25d.conf for VK3KDI - 04/05/06
> > > > > > # This configuration uses the AX.25 port defined earlier.
> > > > > >
> > > > > > # <peer> Win T1  T2  T3  idl N2 <mode> <uid> <exec>
> > > > > > <argv[0]>[<args....>]
> > > > > >
> > > > > > [VK3KDI-1 via vhf]
> > > > > > parameters 1    10  *  *  *   *   *
> > > > > > NOCALL     *     *  *  *  *   *   L
> > > > > > default    1    10  5 100 180 5   *    root  /usr/sbin/pms pms -a
> > > > > > -o vk3kdi
> > > > >
> > > > > ______________________________________________________________
> > > > > Packet mailing list
> > > > > Home: http://mailman.qth.net/mailman/listinfo/packet
> > > > > Help: http://mailman.qth.net/faq.htm
> > > > > Post: mailto:Packet at mailman.qth.net
> > > > >
> > > > > List Administrator David Barlitt (KF4AWU) mailto:kf4awu at qsl.net

-- 
Those who think that the rewarding tings in life are somewhere beyond the 
rainbow...
"Burn their toast a lot," said Pooh.
   - The Tao of Pooh.


More information about the Packet mailing list