Linpac Activity
Amateur Radio AX.25 chat and PBBS program using Linux's AX.25 stack
Brought to you by:
dranch
Activity for Linpac
-
Ken Hayden posted a comment on discussion LinPac discussion
When I first set up LinPac I would get an ax25 error in the bottom window. Maybe the listen window was actually working then but with the error I didn't try to connect. I read online somewhere that the -m got rid of the error so I tried it and then connected to a bbs no problem with LInPac just no listen. After giving root permission to listen everything works just starting with "linpac" . I was reading in LinPac manual, maybe just a guide, that some folder had to be set up for mail and I need to...
-
David Ranch posted a comment on discussion LinPac discussion
Good to hear you got things working though looking back in the thread, I never did see why you were starting Linpac with -m anyway. Btw, for the other mailbox error you're seeing, If you look at this other doc, see item #15: https://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi-setup.html#28c.configure-linpac I've added this missing step to the future ax25mail-utils README doc
-
After not being able to find the develop branch in git (I'm a rookie remember) I started checking for errors etc. and discovered that I no longer needed to start with the -m and lo and behold the listen window is now active when I just start with "linpac". So I guess it was giving it root access that was the fix and I just didn't know enough to stop using the -m to prevent the ax error. Thanks for your time and patience.
-
Yes, I highly recommend to build from the develop branch which will get you the nearly complete 0.29 version. It has mostly build fixes and other things but nothing for your listen issue. If you start Linpac from the terminal and the program loads, do you see any errors? If you then exit out of Linpac with the :sys command, do you see any errors there in the terminal program? Also check the $HOME/LinPac/error.log file for any errors too.
-
LinPac doesn't come in the 73Linux package unless he added it in the last couple of days. I downloaded 0.28 from SourceForge not knowing there was something newer. I ran the command and it said the file already exists. Should I try to get the 0.29 and can I just install it over 0.28? Just so you know how I'm doing this I'll explain how I start LinPac. In 73Linux there is the "Pat Menu" From there I click start modem which launches Direwolf in the -p mode. PatWinlink starts automatically but I close...
-
David Ranch committed [c1ec5b] on git
added copyright owner and date; updated the Linpac version number
-
David Ranch committed [44deaa] on git
added copyright owner and date
-
David Ranch committed [b8a15c] on git
added copyright owner and date
-
David Ranch committed [8209a3] on git
added copyright owner and date; updated the Linpac version number
-
David Ranch committed [150551] on git
updated copyright owner and date; cleaned out some stray DOS cr/lf chars
-
David Ranch committed [a7acc9] on git
Updated the date and denoted current vs. previous contributors
-
David Ranch committed [a561dd] on git
Refer users to the ChangeLog file for newer details
-
David Ranch committed [ca3a87] on git
Updated the date
-
David Ranch committed [45cb2f] on git
Updated the date
-
David Ranch committed [abb3a4] on git
Updated the date
-
David Ranch committed [a0f9b6] on git
Updated the date
-
David Ranch committed [99d392] on git
Added a mention for Linux distributions that use listen instead of axlisten
-
David Ranch committed [08c6f1] on git
Added fixes for the listen frame not showing heard AX.25 traffic
-
David Ranch committed [f208a8] on git
updated the update year, minor formatting changes
-
Ok, if you look at the permissions of the axlisten tool in your last screenshot, it's already SUID root (that's what the red probably means). Specifically, it shows: -rwsr-xr-x root root Since you're a new Linux user, I'll give some explanation. This file is owned by the user "root" and also have group ownership of "root". The permission area is broken into three areas: owner, group, other. The "root" owner here can (r)ead, (w)rite, and (s)execute this program with SUID permissions. Putting that...
-
One more time
-
Just realized I uploaded the wrong pic. Sorry
-
I ran the ls -la and the result is the attached screen shot. I'm sure you realize I'm a real rookie at all this. Looks like axlisten is in the root but I'm not sure. I started with a new mini pc and installed 73Linux from KM4ACK, configured Direwolf and tested by successfully sending and receiving email via PatWinlink. All of the ax25 stuff was installed and configured by 73Linux so I don't know where it came from other than that. I am on Mint because KM4ACK tested 73Linux on Mint and recommended...
-
The "ls" commands color coding can differ from OS to OS so that doesn't show what's wrong. Try running "ls -la" to see what it means. That said, it's probably a broken symlink which is easy to fix and NOT a 32bit vs 64bit file issue. Next, if Linpac+Linux AX.25 stack is showing the axlisten output when using one sound device but not the other, your problem isn't Linpac.. it's going to be the stack setup for the "broken" sound device. Finally, per the Linpac manual: " -m : disable monitor. When this...
-
Hi David, I tried to mark axlisten to "SUID root" and I think I did but it still didn't work. When I found axlisten in the the /usr/bin I found it's background red. Someone with an unrelated problem found that to mean the file was 32 bit and he was on a 64 bit system. I tried to install the 32 bit library as he did but it had errors and failed. Pretty old stuff I guess. The listen window works in LinPac on the DigiPi I assume because it's 32 bit? Also for anyone else following along, when you run...
-
The included Linpac documentation is lacking on this topic but I had covered this in my other Centos documentation. The issue here is that to display decodes of all AX.25 traffic in the bottom Linpac pane, axlisten needs root access to the kernel but this is generally considered poor security practice. I personally consider this low risk but there is one solution to fix this using the "ax25spyd" solution. It's old, unmaintained, and has been quirky in the past and I haven't tested it in years. I've...
-
Hi David, Since I couldn't get the Mail utilities to work in DigiPi I built up 73Linux with Linux Mint on a mini PC. Got LinPac installed on it and I got it working and connected to a Node and BBS but the bottom window is empty. I read a past discussion where you had them find axlisten and run a command. Tried that but no go. I also did try the :mail command and it opened the mail editor just fine. Empty of course and when I closed it the main window showed there was an error about accessing a mail...
-
Cody modified a comment on ticket #31
Hi David, I was able to compile and try the develop branch. This showed the same results - I did some additional testing. with :FIXPATH off I was able to send a file using :YPUT /home/cody/test From the remote machine //YPUT "/home/cody/test" note that quotes were required for the remote command to work but not necessary from the local terminal. Thanks, Cody edit: I misread the manual indicating that files are available in the /linpac/user directory, not the "home" directory of the user. When files...
-
Hi David, I was able to compile and try the develop branch. This showed the same results - I did some additional testing. with :FIXPATH off I was able to send a file using :YPUT /home/cody/test From the remote machine //YPUT "/home/cody/test" note that quotes were required for the remote command to work but not necessary from the local terminal. Thanks, Cody
-
Hello Cody, I will try to reproduce this but until then, you might want to try testing this with the "develop" Git branch of Linpac as there are various fixes in there.
-
Hi David, Thank you for the reply. I have tried with a LinPac to LinPac connection. One machine with debian 12 install running direwolf the other with linux mint serial connected kiss tnc. Either direction, I can connect and send keyboard to keyboard messages. //help shows :yput and :read. With a test.txt file in the home directory on either machine :yput or //yput does not creat any response, nothing is sent to start a yapp transfer. //YPUT TEST.TXT is sent across the radio but the remote machine...
-
When you look at the //help output, do you see either command? If there are permission issues, the desired command shouldn't show up. Can you also redo your test Linpac to Linpac so we remove any client compatibility issues for the moment?
-
Hi, I am having a similar issue with sending files using :read or :yput on linux mint. There is no update after entering a command ":Read test.txt" and having test.txt in the home directory. This was tried as a user and root user. Recieving a yapp file appears to work fine when Sent from qttermtcp, cannot send From LinPac. No errors shown in the terminal, just moves the cursor to the next line. yputtx is shown in the LinPac directory and listed in the commands file. Possibly a permissions error?...
-
This sounds like a broken Linpac install on your Digipi image. Looking at a 64bit Raspberry Pi install, I see: ls -la /usr/lib/aarch64-linux-gnu/liblinpac.so.6* lrwxrwxrwx 1 root root 18 Dec 31 2023 /usr/lib/aarch64-linux-gnu/liblinpac.so.6 -> liblinpac.so.6.1.2 -rw-r--r-- 1 root root 68304 Dec 31 2023 /usr/lib/aarch64-linux-gnu/liblinpac.so.6.1.2 -- Do you see these files in this specific path? Maybe Digipi is using a 32bit OS? Ultimately, it might be better to post your question at https://groups.google.com/g/digipi...
-
LinPac runs fine in the latest DigiPi. I can access messages on a BBS but if I try the mail command I get the error that liblinpac.so.6 is missing. Any way to get this into LinPac on DigiPi? Not a programmer but I'm comfortable running and installing stuff from the command line. DigiPi allows sudo remount so things can be installed and edited. The DigiPi guru said I should seek an answer here. Is this possible? Thanks.
-
David Ranch committed [2c303e] on git
script to assert a GPIO pin on a Raspberry Pi when a user leaves a new packet message
-
Chris posted a comment on ticket #35
Maybe over my Thanksgiving break coming up. I am pretty impacted with work right now. -73 de Chris KQ6UP On Fri, Nov 15, 2024 at 3:48 PM David Ranch dranch@users.sourceforge.net wrote: Ok.. after two fun packed days dealing with Slackware's rather weak installer, I was able to spin up a Slackware 15.0 VM, compile/install the VE7FET AX,25 repo and compile/install Linpac 0.29 (develop branch). I then upgraded/replaced the OS to Slackware-current, got it fully updated and again, was able to fully compile/install...
-
Ok.. after two fun packed days dealing with Slackware's rather weak installer, I was able to spin up a Slackware 15.0 VM, compile/install the VE7FET AX,25 repo and compile/install Linpac 0.29 (develop branch). I then upgraded/replaced the OS to Slackware-current, got it fully updated and again, was able to fully compile/install the VE7FET AX,25 repo (required some minor ncurses hacks), and compile/install Linpac 0.29 (develop branch). Please confirm if you're still seeing this issue.. if not, please...
-
Hello Christian, are you sure you are using the DEVELOP branch? This issue should have been fixed back in Dec 31, 2023. https://sourceforge.net/p/linpac/linpac/ci/5edcba8fda38b7735b91d7901750008aa228152c/
-
Christian Breitbarth posted a comment on ticket #35
This same issue has popped up for me as well, was there any resolution to this issue?
-
David Ranch committed [f30b4f] on git
Added various improvements
-
It seems either I missed several bugs reports or a whole bunch of issues just were released from limbo. Super sorry about the delay here. alt-x choice came from the original author and hasn't been any issue from anyone else. You can also use ":sys" which is what I personally use. Are you having an explicit conflict with this key sequence?
-
Sven Olaf Kamphuis posted a comment on ticket #33
there appears to be no check on the length of mon_line ;P (no that's not what the '1' in strncat does - that function has no total length limitation ;) so either mon_line itself is overflowed. or printf overflows at not seeing a terminating '0' to the overflowed string ;) windows.h: char mon_line[256]; /Downloads/linpac-0.28/src# less windows.cc if (ev.type == EV_NONE) { if (listpid >= 0) { char buf[512]; int rc = read(list, buf, 512); if (rc > 0) { int i; for (i=0; i < rc; i++) { if (buf[i] == '\r'...
-
Nope -- still fails. Had to do the autoreconf bit too. That was a first for me. Here is the output: g++ -DHAVE_CONFIG_H -I. -I../../.. -g -O2 -MT mail_screen.o -MD -MP -MF .deps/mail_screen.Tpo -c -o mail_screen.o mail_screen.cc mail_screen.cc: In function ‘void init_main_screen()’: mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’} 39 | maxx = stdscr->_maxx; | ^~ In file included from mail_screen.cc:13: /usr/include/curses.h:456:16: note: forward declaration...
-
Hello Chris, where did you get your Linpac source code? From the SourceForge .tar.gz file (master branch), from the Git Master branch, or the Git Develop Branch? Please try the Develop branch from Git at https://sourceforge.net/p/linpac/linpac/ci/develop/tree/ and let us know if that works.
-
Compile Failure Slackware-current
-
David Ranch committed [3ca649] on git
Marked segfault on missing axports file issue as resolved
-
David Ranch committed [ff6871] on git
updated the TXT version from the manual.html file
-
David Ranch committed [793f92] on git
updated the TXT version from the manual.html file
-
David Ranch committed [f4eefb] on git
update the packaging files to reflect the new version
-
David Ranch committed [570509] on git
Update the build details to reflect new build date, it's changes, etc
-
David Ranch committed [5edcba] on git
Changes to manage disruptive ncurses library change to make ncurses internal variables opaque aka not available for external use
-
David Ranch committed [3d6a55] on git
Updated version, copyright date
-
David Ranch committed [a042ee] on git
Updated the info when the axports file isnt found
-
John Wilson posted a comment on discussion LinPac discussion
Thank you David - that's done the trick.
-
Hello John, The files are stored in the "LinPac" directory of the user that started the Linpac process. So, if you were running it as root, look in /root/LinPac. If you want to completed start over as if Linpac was never run, run the command "rm -Rf /root/LinPac" and that directory and all contents will be removed.
-
Sorry for a very non-technical question but I've just installed LinPac on a Raspberry Pi Model B running Raspbian 11 (bullseye). I realised after starting LinPac that I put the wrong parameters in at this point. As a completely non-technical person, can someone tell me where the default parameters are stored and/or what file I can remove/rename in order to re-start LinPac from the beginning again? Thanks for your help.
-
Your newest post has nothing to due with Linpac and is a general Direwolf question. Please post that on the direwolf@groups.io email list and the team can help resolve that issue.
-
Maximo Barawid Jr. posted a comment on discussion LinPac discussion
I thought I have AX.25 stack installed. I edited /etc/ax25/axports; vhfp DU2UXH-2 9600 255 2 VHF Packet 1200 bps I did also run kissattach: $ sudo kissattach /dev/pts/2 vhfp AX.25 port vhfp bound to device ax0 $ sudo kissparms -p radio -t 100 -s 100 -r 25 Running direwolf: $ direwolf -t 0 -p Dire Wolf DEVELOPMENT version 1.7 E (Jun 14 2022) Includes optional support for: hamlib cm108-ptt Reading config file direwolf.conf Audio input device for receive: stdin (channel 0) Audio out device for transmit:...
-
That is correct. For your previous post above stating : "I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity when trying to connect to my bbs via the linpac." To use Linpac, you must configure Linux's AX.25 stack for it to function. The setup is radio --> direwolf --> Linux AX.25 stack --> Linpac. If you're looking for a complete setup...
-
I would recommend to join the direwolf@groups.io email list at https://github.com/wb2osz/direwolf where myself and others can better help you and stay on topic. In that post, please mention how your Linux computer is connected to your IC-7100, etc. Thanks David. So.. what you want to do is run: git clone git://git.code.sf.net/p/linpac/linpac linpac cd linpac autoreconf --install ./configure Ok, let me try that. Thanks again.
-
Hello Maximo, You are mixing discussions and your keying issue has nothing to do with LInpac. I would recommend to join the direwolf@groups.io email list at https://github.com/wb2osz/direwolf where myself and others can better help you and stay on topic. In that post, please mention how your Linux computer is connected to your IC-7100, etc. --David
-
It's looking like the README needs a cleanup as it's giving some misleading detail. The issue you're seeing here is that you're in the "~/Downloads/linuxax25" directory used for the AX25 stuff but then you're trying to follow the Linpac compilation instructions. They are very different things! The missing line is it was assumed you already have the Linpac sources and you're in that directory. That makes sense if you're reading the README from within the downloaded Linpac source directory but not...
-
Update: Looks like I got the linpac installed and working. How did I do it? Well, I followed different sites on installing linpac on raspberry pi until I got what I need to install BEFORE compiling linpac 0.29, or even 0.28. Having said that, I am still having problems keying my IC-7100. I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity...
-
Ok, I think I am getting there. It's trial and error process. So bear with me. Trying to learn. Max
-
Ok. I have read the README many times and, I did the following: pi@linpac:~$ git clone https://github.com/ve7fet/linuxax25.git. Then, pi@linpac:~/Downloads $ sudo apt install libax25 ax25-apps libncurses5-dev perl That went ok. Then, install of automake autoconf - done. Then, sudo apt-get install libtool libtoolize autoreconf --install pi@linpac:~/Downloads/linuxax25 $ autoreconf --install autoreconf: 'configure.ac' or 'configure.in' is required Question, am I installing only dependencies? Where...
-
Right.. per the README, you need to install the following other packages: libax25 ax25-apps libncurses5-dev perl I think I should also delete the INSTALL file as it's not very helpful here. --David
-
Hi. Thank you for the reply. It's past 9PM here and I will try it tomorrow and update you. Max
-
Jeb Baker posted a comment on discussion LinPac discussion
Howdy. I recently loaded this on a Raspberry Pi 4B. Ran into the same problem. Hit this link and read this install guide. It will tell you what Ncurses Library you need. https://sourceforge.net/p/linpac/linpac/ci/develop/tree/README Jeb
-
I am running Buster on a Raspberry pi 3B and trying to install linpac-0.28. Here is where it stops after ./configure. pi@bagiw:~/Downloads/linpac-0.28 $ ./configure checking build system type... armv7l-unknown-linux-gnueabi checking host system type... armv7l-unknown-linux-gnueabi checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking...
-
Hello Neil, There is the following Linpac bug report at https://sourceforge.net/p/linpac/bugs/31/ where I did some analysis and found one work around using YAPP but it's not perfect. That said, I would be great if both methods could be analyzed and fixed.
-
Neil posted a comment on discussion LinPac discussion
Hello all. I have a pair of LinPac instances that are communicating across the house to each other. I can send text, and it works perfectly. From what I can tell from reading the LinPac manual, to use YAPP to send a file through LinPac, I only need to use the yput command with a file. The peer will start downloading automatically. For example, my first test case is sending LinPac's manual.txt from my home directory. From a connected channel I type :yput /home/neil/manual.txt or :yput manual.txt and...
-
David Ranch committed [57ec2b]
Updated the Changelog based upon recent Git commit comments
-
David Ranch committed [7b4166]
new development version
-
David Ranch committed [a0ee36]
Updated version, copyright date, other contributors
-
Fix spelling errors
-
Fix segfault if /etc/ax25/axports not configured
-
Draft: build on docker
-
David Ranch committed [be1770]
Merge commit 'd838e60a576589a3808702cbafda9cf843cebbbc' into develop
-
David Ranch committed [3e58c9]
Fix segfault if /etc/ax25/axports not configured
-
David Ranch committed [1dd00b]
Merge commit 'f9f9bd831aedbecbb167b61495bfdce3e3668dad' into develop
-
dforsi created merge request #18
Fix spelling errors
-
BJnsn posted a comment on discussion LinPac discussion
Ahaaa wasn't that. I went through my whole file system and pulled all linpac stuff out, then reinstalled everything. This time I got a SELinux Alerts notification as soon as a connection attempt happened. Don't know how I missed the previous ones. Guessing all audio was pipped to RigBlaster and didn't hear it. It was nice of them to suggest the following because it worked. ***** Plugin catchall (2.93 confidence) suggests ************************** If you believe that linpac should be allowed read...
-
It sounds like you haven't configured Linpac to answer incoming connections. In the LinPac/macro/init.mac file under the ";; Callsign setup" area, what do you have? You need at LEAST one entry there such as "mycall@1 KI6ZHD". Also, what version of Linpac are you running. It's recommended to be running at least 0.28. --David
-
I spent a few hours digging in manuals with Ctl-F and google looking for why linpac will auto disconnect an attempt from another station connecting in. I noticed it once after I got up and running on HF. RK station, got kicked right way. Thought it was weird, but OK. Next I setup 2 VHF stations for playing and learning. One KPC3+ and one Direwolf Linpac. I can connect to the KPC3+, but get booted any time I try a connect with the linpac side. Any advice would be appreciated. BJ
-
according to the manpage on pipe() pipe's buffer size can simply be set to PIPE_BUF (mon_line=PIPE_BUF;) (#include<limits.h> as there appear to be 2 diffent ones one for posix (512) and one for gnu (4096) and then, at least with with O_DIRECT it'll never fail on that bit ;)</limits.h> Writes of greater than PIPE_BUF bytes (see pipe(7)) will be split into multiple packets. The constant PIPE_BUF is defined in <limits.h>.</limits.h> * If a read(2) specifies a buffer size that is smaller than the next...
-
works fine after changing mon_line to 512 in src/windows.h ... could be a bit overkill... the way it is done highly depends on pre-existing termios settings etc anyway. (as in if it even is one line of text at a time that gets read() in the first place ) think that whole part could well do with a rewrite... for one thing... instead of pipe dup2 exec ( axlisten )
-
axlisten seems to write() it actually line by line. (not just one write() with a lot of \n's in it ;) but how many bytes you get from a read() on a redirected terminal depends on the termios settings of that terminal. and is not per-se one line at a time... (especially not since it is also in non blocking mode ;) anyway the problem is in that strncat(bla,mon_line,1) bit which doesn't check the length of mon_line at all. just that it appends one byte at a time to it. ;) also the newlines, carriage...
-
axlisten seems to write() it actually line by line. (not just one write() with a lot of \n's in it ;) but how many bytes you get from a read() on a redirected terminal depends on the termios settings of that terminal. and is not per-se one line at a time... anyway the problem is in that strncat(bla,mon_line,1) bit which doesn't check the length of mon_line at all. just that it appends one byte at a time to it. ;)
-
works fine after changing mon_line to 512 in src/windows.h ... could be a bit overkill... the way it is done highly depends on pre-existing termios settings etc anyway. (as in if it even is one line of text at a time that gets read() in the first place ) think that whole part could well do with a rewrite... for one thing... instead of pipe dup2 exec ( axlisten ) (there is popen for that? , also it seems to dup both STDOUT_FILENO and STDERR_FILENO to the same filedescriptor ;) or actually just STDERR...
-
with axlisten broken on the box i tried to update that axlibrary stuff on at least it no longer crashes ;) no monitor tho. not that a monitor is needed per-se on a multi user multi tasking os... if they want axlisten they can just run one in another terminal.
-
with axlisten broken on the box i tried to update that axlibrary stuff on at least it no longer crashes ;) no monitor tho. not that a monitor is needed per-se on a multi user multi tasking os... if they want axlisten they can just run one in another terminal.
-
(and yes it is quite common for the linux ax.25 stack to receive and clearly also acknowledge a shitload of packets by itself before passing them onto recv() ;) thats why nothing is shown above. ;P funny part is. if your server closes() immediately afterwards they'll never get processed at all ;) you never notice that at 1200 baud ;) you do at 1000mbit/s or more ;) but then again gp isn't exactly 'real time multitasking' either ;) connect, server sends a shitload of packets, then it suddenly goes...
-
(and yes it is quite common for the linux ax.25 stack to receive and clearly also acknowledge a shitload of packets by itself before passing them onto recv() ;) thats why nothing is shown above. ;P funny part is. if your server closes() immediately afterwards they'll never get processed at all ;) you never notice that at 1200 baud ;) you do at 1000mbit/s or more ;)
-
it occurs at exactly 256 bytes. and yes in that silly old axports file it is also set to 256 (not 255). it doesn't -have- to be one of linpac's own connections. just 'seeing 2 other hosts do it on the network' in the monitor suffices. (so it's not related to linpac's own mtu). think it's purely in the parsing of the output of axlisten and displaying it. axlisten itself by itself works fine.
-
i'll just code an increment counter on it just sending packets until it crashes... should be able to see the last one it passed before the coredump ;)
-
Have you tried lowering your Linux /etc/ax25/axports MTU to a level that Linpac doesn't have an issue with? Yes.. Linpac should deal with with it but knowing the limit would be useful
-
can just test it yourself... kiss-tcp server at 208.109.9.123:8001 ... connect to 'MUTINY'.. it'll give a few short lines and then move on to transferring a huge blob of text 20 times in a row. it crashes on the first packet of that. source code for both the mutiny node as a kissattach for tcp here: https://github.com/cb3rob/CB3ROB-AX25-TOOLS-LINUX
-
so far for the attempt to just install that by running the ./ax25upd thing in his repository ;) (ubuntu 16 lts with all 'dev' stuff installed ;) - nope ldconfig didn't fix axlisten either ;) anyway. don't quite see the point in using that old ax25lib stuff -at all-... getifaddrs() will happily return all ax_25 interfaces AND their mtu's (which seriously should be 256 anyway, most definately not 255 such as in the default axports file ;)... SOCK_PACKET will happily give you a monitor (it needs to...
1 >
