Re: RF transmission problem
On Thu, 10 Aug 2000, Steve Stuart wrote: > Yes, I did edit ax25d.conf (smile). You can be confident that I'm not > bootlegging your callsign. ;-) > The radio baud rate is 9600, and I'm pretty sure the serial baudrate is as > well. This is easy to check via minicom. > How do I reset kiss mode without rebooting my pc? Entered "kissparms -x -p > ax0", but minicom says /dev/ttyS0 is locked? Kissparms -x takes the TNC out of KISS mode but it's kissattach that locks the tty. You need to kill it. Probably easiest with "killall kissattach". -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: RF transmission problem
On Thu, 10 Aug 2000, Steve Stuart wrote: > I've just installed the ax-25 stuff, >node-0.3.0-1.i386.rpm, > libax25-0.0.7-1.i386.rpm > ax25-tools-0.0.5-1.i386.rpm > ax25-apps-0.0.4-1.i386.rpm > on RedHat 6.2 system (2.2.14-5.0) with a pentium 133 and 80M > ram. Recompiled/installed the kernal (and modules) with ham > radio stuff enabled. Then set up /etc/ax25/axports with the > line: "ax0 W8AN-4 9600 255 2 144.050 MHz (9600 baud)". Modprobe Wild guess: your TNC serial line bit rate is not 9600 but something else? That 9600 at the speed field of axports is used for the serial bit rate, not the radio bit rate. > mkiss successful. > Next "kissattach /dev/ttyS0 ax0 44.70.161.132" followed by > "/etc/rc.d/init.d/ax25d start". Even setup a couple routes to Just to be on the safe side: Ax25d is not needed for outgoing connections or tcp/ip over ax25. And if you do want incoming connections, you did edit /etc/ax25/ax25d.conf right? Otherwise you'll be using my callsign... :) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: GW-List - Mkiss and Polled BPQ
On Tue, 8 Aug 2000, Albert D. Lawson wrote: > The mkiss docs say that to use it with TNC's that have the polled kiss > proms by G8BPQ that you use the -c and -p arguements. I have three > TNC's on one serial port with BPQ polled kiss proms, the addresses are > C, D, and E. So far, only one TNC is being polled, and it's not on > the "port" it was assigned to be on. Are there any additonal > arguements to pass the addresses of each prom onto mkiss so it knows > what TNC's are there...??? No. Mkiss starts the addressing from TNC 0 and goes up from there depending on how many pty interfaces you define on the command line. I don't remember how the BPQKISS addressing goes but if it starts from A then you could try and define two dummy ports and then the three "real" ones. If the address is a hexadecimal number then I'd try to find an EPROM programmer... > Has any one made this work before... Run mkiss and BPQKISS with polling and checksum enabled? Yes, that is what I wrote the support for. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: smdiag
On Fri, 4 Aug 2000, Leif Mattsson wrote: > One:I found a patch:ax25-tools-0.0.5-oh2bns.patch. How am I supposed to > handle that? Is it a executable program which corrects the earlier > compiled binaries or is it supposed to correct the sources? First see "man patch". Quick instructions for this particular case: $ tar zxf ax25-tools-0.0.5.tar.gz $ patch -p0 < ax25-tools-0.0.5-oh2bns.patch patching file `ax25-tools-0.0.5/netrom/nrparms.c' patching file `ax25-tools-0.0.5/user_call/user_io.c' $ Then you recompile. > Two:when I should try my soundcard with smdiag I can't find it! I do > find smmixer but not smdiag. How come? IIRC smdiag was removed from the tools as it depended on a non-free X widget library. This was however rectified later and ax25-tools-0.0.6 should include smdiag. (the above patch should also be unnecessary for 0.0.6). You can get 0.0.6 at: http://hams.sourceforge.net/ -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: aiee, killing interrupt handler?
On Thu, 3 Aug 2000, Stephan Loges wrote: > > > I don't know whether it's an 2.0.x issue, but I remember a ax25-bug where > > > the kernel oopses when you ifconfig'ed down your ax25 network interface > > > (or was it axctl ...-kill ??) while there was an ax25 connection open. > > > Reason was a forgotten timer that wasn't stopped when it should. > > > > That was a 2.2.x bug and fixed in 2.2.1x somewhere. The exact cause was a > > NULL pointer dereference at the time the heartbeat timer expired the last > > time (see ax25_timer. > > kernel is 2.0.38. Was the bug there too? As far as i can remember, no. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: EPP adapter woes
On Wed, 2 Aug 2000, Jens David wrote: > > Once the > > interface is up, packets never come out the h/w even > > though listen -a shows them going. > > This is not so good. Check that in BIOS setup EPP version 1.9 > is selected and/or check for a BIOS upgrade. In addition to that > (this might sound a little but funny) change the cabling. The > drivers have different timings (this is quiet critical). I have no experience with DOS but under Linux I too have noticed that the cabling is really critical. For example even a rather short length of flat cable can totally ruin the communication. This seems to make it a bit difficult with the older AT motherboards where the D-connector is not directly on the board... BTW I'm talking about the EPPFLEX hardware. Don't know if this is applicable to the older EPP adapter. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: aiee, killing interrupt handler?
On Sun, 30 Jul 2000, Thorsten Kranzkowski wrote: > On Sun, Jul 30, 2000 at 03:13:59PM +, Stephan Loges wrote: > > On Sun, 30 Jul 2000, Richard Adams wrote: > > > I must say the trace does ring some bells with me, i seem to remember more > > > about a ax25_timer problem, as to what it was or a answer to HOWTO solve > > > it i am at a loss at the minute. > > Maybe, would be good to have more information on it. > > I don't know whether it's an 2.0.x issue, but I remember a ax25-bug where > the kernel oopses when you ifconfig'ed down your ax25 network interface > (or was it axctl ...-kill ??) while there was an ax25 connection open. > Reason was a forgotten timer that wasn't stopped when it should. That was a 2.2.x bug and fixed in 2.2.1x somewhere. The exact cause was a NULL pointer dereference at the time the heartbeat timer expired the last time (see ax25_timer.c). -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: KPPP problems
On Fri, 28 Jul 2000 [EMAIL PROTECTED] wrote: > And once upon a time ham operators were helpful people > Could I refer you some of the Linux Hams to the Amateur Code as > published in the ARRL handbook for many years. > The Radio Amateur is > CONSIDERATE > LOYAL > PROGRESSIVE > FRIENDLY > BALANCED > PARRIOTIC. > > A couple of replies to Marks VK3JMA plea for help certainly did not > meet the critera needed to be an Amateur. Ok. Maybe the correct answer to the original plea would then be: "Mark, this list is not meant for such questions. Please consider subscribing to linux-newbies and asking there. Or perhaps Red Hat might be able to answer your question; there should be pointers to the correct place to ask somewhere in your distributions documentation." How does that sound? > I am like Mark becoming involved with Linux simply to apply the > new skill to my entertainment in amateur radio. This is the only > group to which I subscribe and had assumed if I had a Linux > question my fellow amateurs may be able to assist. Obviously you assumed wrong. Perhaps you are also a newbie in Internet? The purpose of this mailing list was sent to you when you subscribed. After a few years of Internet experience you will understand why it is rather important to stick to the meant purpose of a mailing list. > Another point I get the feeling you guru's just what your private little > club, well consider the demise of the RF side of the hobby primarily > because of such attitudes. How many amateur controlling bodies > are in a growth mode.?? No clubs here. It's a question of simple practicalities. I receive ~100 emails a day from several mailing lists. Some get more. If the signal to noise ratio drops too low on a list, I simply have to unsubscribe. Maybe I wouldn't be such a loss to this list but it would be yet another one, possibly having answers to relevant questions, off the list. A few off-topic posting every now and then doesn't really hurt, but they should be firmly discouraged. Believe me, a lot of the real guru's have already unsubscribed. And not because they feel they're somehow superior to you. It's because of practicalities. > Let remember the Amateur code maybe even dust of the old > handbook and reread it might make you all think to engage brain > before tapping the fingers. I remember the time when the Internet used to be a place for educated and conciderate people. The code used to be "listen before transmitting". The so called netiquette (which almost was required reading before getting access to the Net) was truly understood and obeyed. Everybody would carefully observe if a given mailing list or news group was really the one to ask his or her question. Oh, those were the days. Sounds familiar? It should. The only difference is that here you can not transmit over someone else. But you can transmit in a completely wrong place. The consequences are just as "bad". -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Soundmodem problem
On Mon, 24 Jul 2000, Rich Hall wrote: > I tried this route too. No workie.. Also the docs on several of the web > sites state that the ax-utils do not work with 2.2.x kernels.. I am totally > confused on this. The site at http://meow.febo.com/linux-ax25/index.html > shows the ax25-utils as a 2.0.x based support package and the ax25-tools as > a 2.2.x package. > > I am starting over this morning with the install of the previously > mentioned ax25-tools and support stuff and will see what goes from there. > > I also found ax25-tools-0.0.6.tar.gz which is not on the "official site" at > ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/ as that site has the latest > version as ax25-tools-0.0.5.tar.gz. Should I use this? Anyone care to comment? The lib/tools/apps are now in sourceforge.net somewhere. Ax25-tools-0.0.6 is the latest but I'm not sure if you need to upgrade. I haven't. For Red Hat I'd go to the nearest RH mirror site, and get the libax25, ax25-tools, ax25-apps and node RPMs that are included in the PowerTools. Ax25-utils might work with a 2.2.x kernel but it's asking for trouble IMO. > This is almost enough to make me want to run a Windoze box for the packet > stuff. But not yet.. I have a working and very stable CLX system that I > want to interface here. > > BTW how is the 2.2.16 kernel? I had a ton of trouble with crashing network > stacks on about 20 machines in our network when we went to that. Never seen any trouble here but then again I don't run a big network... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: NEWQPSK tests
On Mon, 24 Jul 2000 [EMAIL PROTECTED] wrote: > Why don't you guys just go to 20m, around 14.070, and tune around? > There's dozens of PSK31 signals there just about 24 hours per day, > with the band being open... I've made many good contacts with guys > running 3W output power and a dipole, both sides running DigiPan... > Why reinvent the wheel when there's worldwide PSK31 stuff coming in on > 20M most of the day/night? NEWQPSK has _nothing_ to do with PSK31. Instead it has much more to do with MT63. (both were "invented" by the same person, Pawel SP9VRC) NEWQPSK (aka Q15X25) is an AX.25 modem using 15 parallel (OFDM) tones modulated with DQPSK. Symbol rate with 8000sps is 83.333baud which translates to 2500 bits per second raw bit rate. There are three different levels of FEC that reduce the payload down to 833.3 bps. The modem takes about 2000Hz of bandwidth so it is something you definitely do NOT want to run on 14.070 !!! My code is a port of the original Motorola 56k assembler code to Linux and C. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: NEWQPSK tests
On Sun, 23 Jul 2000, Hamish Moffatt wrote: > Well, I was going to arrange a time and frequency where we could > try to make contact. If nothing else I might leave a beacon running > one day this week, if there's anyone hear who would try to copy it. > > I would be running Tomi's NEWQPSK modem for Linux, transmitting > AX.25 packets using the 'beacon' program. Would anyone try to decode > this if I set it up? Unfortunately I'm now back from my vacation and HF antennas are a problem but I might try to set up something. By the way if anyone here in EU is trying to connect to Joni's NEWQPSK station at 3590.0kHz LSB, it's now running 2500bps (8000sps), interleave=8 and fec=3. After some tests we decided that the 3000bps (9600sps) mode is too wide for most ham rigs and the high and low carriers are unnecessarily attenuated and performance thus degraded. 2500bps is much better at least in that sense. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: KISS over psuedo TTY
On Sun, 23 Jul 2000, Charles Brain wrote: > > What I am getting in my own task at the slave tty is sort of KISS data in that > > What I am actually receiving is 0x00 0xCC 0x07 everytime I ping. Strange. And somewhat hard to figure out without more info about what you are doing. If you want you can send me (off list) your config scripts and maybe a code fragment of your modem so I can see if I can find the problem. > Is it me or is this listserver taking a couple of hours to reflect each message? The listserver. Vger is under a rather heavy load I'd think. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: KISS over psuedo TTY
On Sat, 22 Jul 2000, Charles Brain wrote: > I am trying to set up a kiss link over a psuedo TTY without much luck. > I can do it with slip not not it seems with KISS. I am trying to set up > a link to my own application. > > the Kernel is 2.2.12-20 and I am using apps-0.0.4 and tools 0.0.5 > > Anyone have any ideas? How exactly does it fail? It should work just fine with the versions you mention (though upgrading to the latest wouldn't probably hurt). -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: soundmodem
On Fri, 14 Jul 2000 [EMAIL PROTECTED] wrote: > Before I go into a longish talk about transforms, I's, and Q's, is there > anyone out there that regularly runs newqpsk? I'm loopback testing the > modem on vhf fm and I get a 50% error rate. I run it somewhat regularly... :) Sorry that I didn't answer to your direct email, but I'm currently on a summer cottage 200km away from home and using GSM dada is a bit expensive. I'll reply later. That error rate is probably due to a somewhat ugly feature of the original modem desing. You see, after the symbol sync is acquired and the modem switches to data mode it just starts to feed the symbols through the (self synchronising) de-interleaver. However there is no way of knowing when avctually the sync sequence is over and valid data starts so there is bound to be several symbols worth of garbage at the beginning of every transmission. There is no way of counting the _real_ FEC errors... I've been thinking about reimplementing part of that but it'll mean that compatibility with the original modem is broken. > I've used the afsk1200 baud modem in the linux kernel, I've also written a > packet modem that works with the 'newqpsk' userspace soundmodem code. > Both the modulator and the demodulator work on the air, but they're mainly > a learning tool. Tom has already written modems for all the modes that the kernel driver handles. But as you said, writing them is good way of learning. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
ANNOUNCE: newqpsk-0.0.4
Hi all, just uploaded a new version of my newqpsk package, a NEWQPSK/Q15X25 implementation for Linux and soundcard to hes.iki.fi: http://www.hes.iki.fi/pub/ham/unix/linux/ax25/newqpsk/ In addition to the usual tarball there are source and i386 binary RPMs as well. >From the ChangeLog: 2000-07-02 Tomi Manninen <[EMAIL PROTECTED]> * Version 0.0.4 * RPM spec file * Changed the default channel access parameters 2000-03-11 Tomi Manninen <[EMAIL PROTECTED]> * Some reordering in rxdata() * Implemented frequency and sync tracking in data phase * Implemented data carrier S/N reporting * Hopefully fixed the "modulate_calib error" problem -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Letters?
On Fri, 30 Jun 2000, [Windows-1252] Håkan Larsson wrote: > I have moved all my yapp mapps from DFBB to XFBB. All the filnames are now > with bigg letters. This is not OK for users how want to yapp this files. I have to > rename all the filenames but there are aboute 2500 off them... > > Any one how can tell me how to do this in a easy way? > Not one by one...hi There are probably better ways but you could try this: for i in *[A-Z]*; do mv -i $i $(echo $i | tr [A-Z] [a-z]); done And don't blame me if you lose all your files with that... :) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Converse Bridge for RH6.1 (2.2.13) ?
On Mon, 26 Jun 2000, John F. Feist wrote: > I was wondering where I can find the source files for Converse Bridge > (TPP, HTPP...?) that will compile under RedHat 6.1 (2.2.13 kernel). > RPM's will be fine as well. > Thank you in advance, John http://www.hes.iki.fi/htpp/ -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Kernel IP routing bug
On Sat, 24 Jun 2000, Robin Gilks wrote: > On Thu, 22 Jun 2000, you wrote: > > > > The reason it doesn't work is because TCP/IP does not work that > > way. TCP/IP is based on the assumption that every computer on a > > network segment (NOT subnet) can hear all of the other computers > > on the same segment. > > It worked fine up to 2.0 series kernels and then it stopped. Every other IP > stack that I've tried that supports routing also works as expected. > > IP is a routing protocol - it should make NO assumptions of the lower layers > (eg. segments etc) - any stack that does is IMO broken. I agree. Yes the IP stack should send an ICMP redirect at least optionally but it should _not_ drop the original frame. Currently it does the worst - does not send a redirect and drops the original... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Kernel IP routing bug
On Tue, 20 Jun 2000, Arno Verhoeven wrote: > Robin Gilks wrote: > > > > Has anyone found a fix yet for the routing bug in 2.2 kernels that I > > highlighted about 5 months ago? > > Funny... Last weekend I saw the very same thing on our packet radio > node. I was just about to send a question about this to the mailing > list. > > I don't have a sollution for it, but I'm very interested in any ideas > for a sollution. The solution is for someone to dig in the kernel networking code and find out what is going on. I once did that but as the networking code is rather confusing and the bug doesn't currently affect me, I soon lost interest. The other solution is to wait for SomeOne Else (tm) to do that.... Use the source Luke, that's why you have it. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: kissparams & mkiss
On Thu, 8 Jun 2000, Richard Adams wrote: > I belive Tomi has said before, you can ignore them, but for the record my > comments. > BTW; just about all of my ax25 stuff is modules. > > > Jun 8 19:00:25 gb7cip kernel: kissparms uses obsolete > > (PF_INET,SOCK_PACKET) > > I have serveral machines all running kernel ax25 netrom, drivers include > mkiss scc dxlmodem, i also get the obsolite message for; > netromd and mheardd, but not from kissparms, further more i cant say i have > seen your problem. The message can come from any program that uses the packet capturing interface the old way. These include kissparms, listen, netromd, mheardd, xfbbd... However the kernel only prints the warning once after a boot so what you see in your system logs depends on how you set up your AX.25. Anyway, once again, the message is completely harmless. It just warns us that sometime in the future this backwards compatibility feature will be removed and the program will stop working. All this has already been taken into accound in recent versions of ax25-tools/apps (if someone sees this message when using the very latest tools/apps please let us know). -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: SCC causes kernel crash
On Wed, 7 Jun 2000, Paul Lewis wrote: > gb7cip:root /var/log # cat /proc/net/ax25 > > Segmentation fault > > gb7cip:root /var/log # tail syslog > Jun 7 12:48:28 gb7cip kernel: Unable to handle kernel NULL pointer > dereference > Jun 7 12:48:28 gb7cip kernel: current->tss.cr3 = 00a06000, %cr3 = > 00a06000 > Jun 7 12:48:28 gb7cip kernel: *pde = > > On the console screen I get the memory dump related to the segmention. > Can not seem to save that to a file. Other than write out the screen to > paper for input on my internet connect PC. You seem to have somethign odd in /etc/syslog.conf or the kernel default message level. Try to fix that so you get the full register dump to your log file (hopefully with symbols resolved). Otherwise writing it to paper and running through ksymoops is the only way... The register dump with symbols resolved is the information were interested in. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: SCC causes kernel crash
On Wed, 7 Jun 2000, Paul Lewis wrote: > Like others, I have been suffering with a problem since December 1999 > when I switched from 2.0.35 kernel +ax25 to the new 2.2.13, 2.2.14 to > the current 2.2.15. > > The problem I have is with the Ax25 code. (maybe nothing wrong with the > code - I still have a problem to solve) > > The AX25 interface(s) normally one of the very busy ax25 interfaces. > (they all run TCP/IP,AX25,NetROm over them) stop working decoding for > AX25 data, yet the TCP/IP stack continues to work over the interface. Next time this happens, could you try "cat /proc/net/ax25" and if it succeeds send the output here. Also do you see anything strange in the system logs? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: New install of linux
On Fri, 2 Jun 2000, Shane Deering wrote: > I might leave RH 6.2 for a while or make an extra partition for it and have > it as a boot option while working with 6.1. I wouldn't do that. I'd just go with RH6.2 and apply all the updates (that is what you should do anyway with any distribution). Applying the updates is very easy. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: About SQUID (dnsserver) ...
On Thu, 18 May 2000, r00t the LiNuXeRRR wrote: > We resolve our problem with the cache dir. Now we have another > problem ... Please solve that on some other list than linux-hams and stop crossposting to several mailing lists... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Sun, 14 May 2000, Stewart Wilkinson wrote: > Gerd wrote: > > > > > > Do you have a case where this leads to actual problems so we can see if > > > something needs to be fixed? > > > > Yes, I am aware of such a case. You run into problems when a > > user enters a node on L2, goes out on L2 again on the same port > > to another node where he also enters and goes out on a L2 > > connection. If everything here happens on the same port the > > second node sends out frames that seem to come from the original > > user (i.e., they have the same SSID as the user). If the user's TNC > > receives such a frame by accident, it either sends out DM- or > > reports protocol errors (FRMR). > > But that applies for other NODE software too. As the SSID gets > inverted twice. (ie: -0 > -15 > -0 ) Exactly. I guess I could come up with some other scheme for the SSID change but then it would probably cause problems elsewhere. Not worth the trouble IMO... > I recall sometime ago, having another problem (perhaps in earlier > versions), whereby Linux NODE used the wrong callsign in outgoing > connects. > > (I seem to recall this occured when one Linux NODE linked to another > at L3/4 and then on again at L2, but I am not currently able to > reproduce the problem). Never heard of such a problem. If you can reproduce it please send me a bug report. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Tue, 2 May 2000, Kjell Jarl wrote: > bpq can be set up to give welcome text to the node call as well, usually > set off though. Some thenet nodes also gives welcome texts, debending on > the set up, also over long distance (already established link level). Ok, maybe I shouldn't have stressed this issue too much, it's not the point. The fact is that traditionally those systems have avoided sending welcome texts, and the reason (or one of the reasons) is what I explained. I know some systems do send them and that those systems also do things like check the list of known NET/ROM neighbours to see if the connectee is a user or not. That last mentioned thing is something you will never see on Linux, it is just too ugly and even as such it's not at all foolproof. Some implementations wait for the first information frame from the user before deciding what to do (the frame will have a protocol ID so the system knows exactly what it is for). Now this hack could be implemented at kernel or ax25d level I think and it wouldn't be all that ugly. Maybe some day... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
RE: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Tue, 2 May 2000, Richard Bown wrote: > While on the subject of SSID's being used, and while there is plenty of > responses. > Has there been a fix in this release to decrement the SSID of a either a L2 > or L3 connection to the node, i.e. I login as g8jvm on someone else's > system then do an outgoing L2 connection to another > station what I see going out is g8jvm and not g8jvm-15, as I understand it > should be. > What it does cause problems with is , if someone logs into a neighbouring > BBS running linux node, this appears on my mheard list as a direct connect. > Has this been fixed?, if so can someone point me in the direction of the > fix. This of course has nothing to do with the kernel implementation of AX.25, it's a LinuxNode "problem". LinuxNode only inverts the callsign if the user is coming in via a L2 connection and going out again on a L2 connection and on the _same_port_. In all other cases users callsign-ssid is left untouched. When I coded this I tried to think of all the possible cases and only saw inverting necessary in that one particular case. Do you have a case where this leads to actual problems so we can see if something needs to be fixed? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Mon, 1 May 2000, Charles E. Gelm wrote: > "c 4 ctnode-9 > DAYLAN:NC8Q-1} Connected to CTNODE-9 > r > CTNODE:N8PS-2} Routes: > Port Neighbor Node Call Quality Dests HeardDigipeater(s) >3 DAYLAN:NC8Q-1 192 31 20:04 > Node cmd? > c3 daylan-9 > CTNODE:N8PS-2} Connected to DAYLAN-9 > Welcome to NC8Q's Packet Switch in Dayton > Type ? for list of available commands.New I message 4/6/97" > > I think that the two lines above is my welcome message. I use BPQ. Try doing the same connecting to the node _callsign_, not the alias. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Log Program for Linux
On Mon, 1 May 2000, Brian Hall wrote: > Anybody know if there is any provision for computer control with this library > with the ICOM 745 ? I have my IC-745 sitting there beside my computer but I don't think there is a way to computer control it? Is there a add on kit perhaps for that? > On 30-Apr-2000 Hamish Moffatt wrote: > > On Sat, Apr 29, 2000 at 07:08:44PM -0500, Nate Bargmann wrote: > >> Also, mentioned in this thread was rig control. IIRC, some months > >> back a post was made to the list of someone writing a library for ICOM > >> rig control. Perhaps this could be extended to other models. I think > >> it would be a good idea to develop such a library so that any programmer > >> doesn't have to re-invent the wheel each time rig control is needed. > > > > I have recently been thinking about do exactly that. > > > > ICOM's protocol is well documented; I have the CI-V manual in PDF > > format here. I now use a Yaesu though and haven't investigated the > > protocol there yet. I do know that ICOM's is very similar between > > radio models, while Yaesu's differs a lot between models. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Mon, 1 May 2000, Kjell Jarl wrote: > I do the same, have both netrom and port call the same, and letting node > respond to ax.25 user connects to the same SSID. > It seems to work, and makes it obviuos for users what to connect to. > Maybe some one could elaborate on why not to do it? If you let an application like LinuxNode answer to L2 requests with the same callsign that is used for internode NET/ROM traffic you can have problems like this: Your neighbor node wants to send NET/ROM traffic to you. It needs to open a L2 connection to you and it uses the callsign shown on your NODES broadcasts (== first nrports callsign == HWaddr for nr0). But now you have configured ax25d to listen for that callsign and to lauch "node". Linux has no way of knowing so it does what it is told and node is lauched. Node then sends it's welcome text and the trouble begins... What happens next depends on what is at the other end of the connection (the neighbor) and it ranges from a minor inconvenience through lots of L2 disconnetions and lost L3 frames to an avalanche of "invalid command" messages flooding the band. Ever wondered why node software like BPQ and TheNet never send a welcome message...? :-) (And no, just dropping the welcome text from LinuxNode is not a solution though I have been thinking of adding that as an option to node.) The same thing applies to AX.25 interface callsigns (those in axports) if you expect to have incoming TCP/IP traffic using Virtual Circuit mode. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Question, was; [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Sun, 30 Apr 2000, Charles E. Gelm wrote: > I thought Naylor & Manninen said that it is 'dirty' code to allow > L3 & L2 connect requests to the same CALLSIGN-SSID. > I thought this couldn't be done in linux. Nope. Never said that. It would be 'dirty' to add that kind of hackery to Linux which allows an application answer on the same callsign that is used for the two NET/ROM 'entities' to talk to each other. In linux that would be the callsign used for the first nrports entry (== the one shown with "ifconfig nr0"). Actually Linux allows you to do that but you _SHOULD_NOT_ do that unless you are completely aware of the consequences. The way around this is the "dummy node" setup well explained on John's web page. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Log Program for Linux
On Fri, 28 Apr 2000, Geoff Blake wrote: > On Fri, 28 Apr 2000, Wilbert Knol wrote: > > > 4. An incrementing number field for contests: "AA1BC 5nn 001" > > For contesting should the automatic entry be 599 rather than 5nn - > because IME n is always = 9 :-) But 9 in reports is most often abreviated N so Wilbert had it right I think... :-) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Thu, 27 Apr 2000, Jens David wrote: > > The later will use the netlink interface, I don't know > > how to fix net2kiss for the new DDI, and listen can easily be tweaked > > to work with all kernels. > > As I said, listen is already done, but net2kiss really puzzles me. > Maybe AF_AX25, SOCK_DGRAM orientated? Umm.. What is it that is difficult with net2kiss? Taking a quick look it receives a packet from a network interface, KISS encapsulates it and writes to a pty. Definitely a PF_PACKET thing, (PF_AX25, SOCK_DGRAM) won't give you enough of the received packet. Am I missing something here? Oh, BTW, rxecho also needs to be fixed. > > Well, those are for "node" and similar programs to view the > > connection status of other processes. What's wrong with that? > > Even if they were always updated to match the current kernel > behaviour (i.e. formatting), or through libax25 I still think > this would be a performance issue. Doesn´t the kernel for example > disable all interrupts while a proc file is accessed (composed) or did > I get this wrong? I have understood so but at least node doesn't use them in a way that would cause any performance issues. > I do not yet understand why an application programmer (e.g. terminal program > writer) has to access the axports file at all. Why not use the socket interface > and ioctl()s as AF_INET applications do? They do not require a ipports file > either, don´t they? > As I understood it the axports file was created to give kernel-ax25 a little > bit the touch of a NOS-app? The original reason for axports was that interfaces could only be differentiated by the interface callsign. There was no way to tell the kernel to "open a connection through device ax0". It needed to be done by telling the kernel to "open a connection through the interface having hardware address N0CALL". And this still is the default method. This would obviously have been very cumbersome to the users without an abstraction layer of some sort and as long as that was needed, symbolic names were easy to add. Now we have bind-to-device and settable interface names so we can start thinking whether all this is needed. (This btw raises another question: with the current state of things do we still need unique interface HW-addresses? If we could get rid of that restriction, it would help a lot.) The question is how will the old functionality be phased out and whether the [ax|nr|rs]ports files still have a place for some other reason. That needs to be discussed. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Wed, 26 Apr 2000, Jens David wrote: > please calm down and let us deal with this on the facts. It was definetely > not my intention to start another flamewar when I did that announcement. Neither did I. Sorry if I seemed a little too exited earlier. > Fact is, nobody else but Jan and Joerg came up with any concrete, factual > ideas/founded bug reports/patches. This is _very_ irritating, especially > if you spend most of your spare time on this stuff while the download > counter reaches the "100" mark. I really need more feedback. Exactly. Pardon me but the way you presented things in your previous posts on this subject didn't exactly prompt me to contribute. Again, I buy many of the arguments you give. That channel access stuff etc. is self-evident. I just feel that these things should be discussed before making hasty decisions. Especially as it seems you want to drop things that are concidered important by others. You are of course entitled to do as you please but if the real world isn't taken into account, I fear your valuable work ends up something only your "group of high standards" knows about... Anyway we now have discussion and that is good. > I my opinion only configuration should be in /proc. That´s settings, port > status, ax25 circuit list (for reading only of cause) etc. That´s mostly > what it consists of now, so it should stay there. What I have a bad feeling > about is that terminal programs begin scanning /proc/net/ax25 to find out > about L2 state of "their" sockets just to display them. They IMHO ought to > use the ioctl() interface. As I said, that /proc reading stuff was written for node. Jonathan then thought it should be moved to the lib so others could use it. In node it is only used to give the user information about what is happening in the system. I don't see what's wrong in that. Oh, and it's also used to get the NET/ROM routing info from kernel in order to do mnemonic->callsign translation. Currently there is no other way and I see little reason to change that. We have seen wrongful uses of the stuff but (now that the ioctl interface is powerful enough) they have been rectified. I'm not buying it should be removed just because someone could use it for wrong purposes. > Another thing is trying to find ax25-Interfaces. Some apps scan the proc > entries instead of using ioctl()s. They break when proc format changes. > In my opinion procfs should be reserved for user interaction with standard > tools such as "cat", "grep" etc, applications and tools should use the > ioctl() interfaces. What apps? That's seems just plain stupid. Anyway in my opinion "when proc format changes" is entirely analogous to "when the kernel api changes". If something changes in the API the apps break just as if they would when a proc file format changes. That should just be avoided! And if it cannot be avoided then it should be hidden behind a library anyway. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Wed, 26 Apr 2000, Jan Wasserbauer wrote: > I have to support Jens since I think nex-Ax25 support is much better (and > what is done so far greatly proves that). > > Have in mind we're talking about Ax25 for 2.5/2.6 kernels .. (or patched > 2.2/2.4 of course) so compatibility issues are not that important. I wasn't talking about compatibility issues (which are important also of course) or which implementation is better. I was talking about attitudes. (Actually the new-ax25 stuff looks very nice, I do believe it's better in many ways and I'm sad that I haven't had time to test it.) > Some developers talk, some actually develop something .. :) > (just my opinion about new-ax25 discussion .. > don't take personaly (anyone)) Yeah, right. And some people think they know all the answers and never need any advice/comments/suggestions/input. What I would have liked to see is something like: "I think feature X in the current implementation is somewhat suboptimal. I was thinking of rewriting/reimplementing/modifying it by implementing feature Y. What do you folks think? I'm going to start writing it now but am open to suggestions." ...and then really be open to the suggestions. This was _exactly_ what we saw when Matthias first started to write new-ax25! Now all I see is: "the old stuff is crap, let's dump it." > > The /proc reading stuff was somethign I hacked quickly together to support > > node. I don't think anyone else uses it. Would you care to elaborate on > > what exactly is so evil about that. > > Someone was asking here what is so conceptionally wrong about old-ax25 > .. so just one example .. And I still don't see an explanation of exactly _what_ is conceptionally wrong about that. Explain it and I'm happy. (If the explanation makes sense that is.) > > > I know that this will pose a lot of administrative problems. But I will > > > not accept any performance-compatibility tradeoffs here, except perhaps > > > the binary compatibility with the old socket interface. > > > > > > Comments? > > > > Good luck getting other developers interested in your (apprently personal) > > crusade to save us from the evil of the old implementation. > > Oh .. should we do it like Win95 ? (DOS compatibility) > Old implementation is working but that's just about all to tell about it. > If new-implementation was only frame-collector and adaptive timers it > would be better .. and new implementation is much more than that .. BZZZT. Wrong answer! Again. My point is that Jens doesn't seem to give a damn about what other people think about this. Jens of course has the right to do what he want's but I wouldn't that suprised if with the current attitude the stuff wouldn't catch fire. And that would be a shame in my opinion. Nobody wants DOS-like backwards compatibility. But the current approach seems like sticking your head in a bush and hoping the real world goes away. It won't. If all else fails Linus and Alan make sure it won't. > And it does not allow users to set parametrs but after some years on PR I > exactly understand why .. there are just too much people who have special > ability to misconfigure anything .. And this, my friend, is exactly what is so repulsive about FlexNet thinking. If all Linux developers shared that notion, we would have a reimplementation of Windows with all the plug'n'pray stuff and people at Redmond knowing much better what we want. That kind of thinking just doesn't fit into Linux! But let's drop this FlexNet issue here and now. It won't be productive. Apologies for getting caught by that flame bait... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
On Wed, 26 Apr 2000, Jens David wrote: > My future plans are the following: > I will mostly rework the complete packages. There is a lot of conceptionally > wrong stuff in there like dependencies on the stupid axports file and > /proc/*-Entries. > > Also, I will remerge ax25-tools and -apps (I do not see the reason to have > two packages here) and call the resulting package ax25-utils again. The > library will have to be completely reworked, too. I do not like those > proc-scanning functions and axports stuff at all. I think I am going to > call this libax25-2, but I´m not yet completely sure about this. Oh, how nice of you to discuss all of this with the other developers and giving constructive critisism/feedback to those of us who have written the old code! The /proc reading stuff was somethign I hacked quickly together to support node. I don't think anyone else uses it. Would you care to elaborate on what exactly is so evil about that. > I know that this will pose a lot of administrative problems. But I will > not accept any performance-compatibility tradeoffs here, except perhaps > the binary compatibility with the old socket interface. > > Comments? Good luck getting other developers interested in your (apprently personal) crusade to save us from the evil of the old implementation. > Remember the flexnet slogan?: "It´s like re-inventing the wheel, and doing > it the right way this time." Are you referring to "doing everything under secrecy and without discussing with others" when you talk about the "right way" á la Flexnet? Give us a break... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Twpsk
On Sun, 23 Apr 2000, Dirk Koopman wrote: > > On 22-Apr-2000 Jose R. Marte A. wrote: > > I agree with Tomi about the gpsk31 of Luc (LX2GT) > > this it syntonizes very quick an station using the spectrum analyzer > > and it works very well, both they are good, but I recommend the gpsk31 > > I have it, both in RPM > > Erm... > > Where is it located please? ftp://db0bm.automation.fh-aachen.de/pub/incoming/lx2gt/ -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: About ARPSD..!!
On Sun, 23 Apr 2000, Hamish Moffatt wrote: > > socket: Invalid argument > > > > and it exit, I was looking in the file sockets.ccp > > in the following line: > > > > / * Create the receive socket * / > > if ((rx_socket = socket(AF_PACKET, SOCKET_PACKET, htons(proto))) == -1) > > > > if I change the AF_PACKET for the AF_INET, the program works in TX > > via RF Link but non RX in the RF Link, in RedHat 6.1 as AF_PACKET yes > > it works using the ax25 tools in RX > > > > My main Question is your patch works for the RedHat 5.2 ?? > > AF_INET is for TCP/IP and not for AX.25 though. I think the problem > is that you are not running aprsd as root -- it must be run as root > to create the AF_PACKET socket if I recall correctly? (Just as > "listen" must be run as root -- and listen is where I got the above > code from originally.) (AF_INET, SOCK_PACKET) was the old way of getting a packet capture socket that worked with 2.0.x kernels. (AF_PACKET, SOCK_PACKET) only works on 2.1.x and newer. Jose are you possibly running a 2.0.x kernel in the RH5.2 box? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Twpsk
On Sun, 23 Apr 2000, Hamish Moffatt wrote: > On Fri, Apr 21, 2000 at 05:49:29PM -0600, Bryan Curl wrote: > > Hope all is well. > > Question. Why does my Twpsk receive screen jump to the top all the time? > > I t only odes this after I scroll back, once, then try to go to the bottom. > > At the end of each received line it jumps to the top. > > Just a note: Also notice that CTRL functions dont work if numlock is on. > > Another PSK31 program you might like to try for Linux is 'phaseshift.' Or, even better: 'gpsk31' by Luc, LX2GT BTW Luc, I have some patches to it if you are interested. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: ax25-tools-0.0.6
On Sat, 22 Apr 2000, Sandor Dibuz wrote: > Hi Jose, > > On Sat, 22 Apr 2000, Jose wrote: > > > Please, where is "ax25-tools-0.0.6". > > I have 0.0.5 > > Go and get it at ftp.hes.iki.fi You won't find 0.0.6 there. The lib/tools/apps packages are now somewhere on www.sourceforge.net. Good luck finding them... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: sendmail problem
On Mon, 17 Apr 2000, Aaron Sethman wrote: > What I do is on my systems is allow mail to be relayed from any 44.0.0.0/8 > address. I don't know if sendmail supports this, but I do know that > postfix does. Now all I need to do is hack LZW support into postfix, and > I'll be happy :). Long time ago I did that to ZMailer but only on smtp server (incoming). If you want I could try to find the code. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: sendmail problem
On Sat, 15 Apr 2000, Shawn T. Rutledge wrote: > On Sat, Apr 15, 2000 at 08:17:28PM +0200, ron jochems wrote: > > > Can the 'nslookup' program be used without DNS running ? Can he retrieve > > names without DNS running ? > > No. Just so there will be no misunderstandings, you _can_ use nslookup without a _local_ DNS running but you of course need to have a DNS server reachable somewhere nearby. Normally when you run nslookup it will check /etc/resolv.conf to see what name server to use but you can also specify the server IP address on either the command line or in interactive mode with the "server" command. Splitting hair? Yes, but that's better than someone getting the wrong idea... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: net-tools bug
On Sat, 15 Apr 2000, Jeff Johnson wrote: > But it has crossed my mailbox. I'll forward to Phil (if you haven't > already :-) Actually I haven't because I thought I saw a problem with ifconfig. However that was partly me fumbling and partly something I already fixed. So go ahead. :-) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: net-tools bug
On Sat, 15 Apr 2000, Leszek A. Szczepanowski wrote: > Dnia 15 kwietnia 2000 o godzinie 19:39, Tomi Manninen napisa³(a): > > > BTW the bug is not Red Hat specific so other distributions > > might be affected too. > > So, maybe mailing this bug to net-tools authors or > maintaners would be good solution for future?:) Gee, that never crossed my mind. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
net-tools bug
Hi all, the net-tools version (1.54-4) coming with Red Hat 6.2 distribution has a bug that makes it impossible to set a permanent ARP entry for NET/ROM making IP over NET/ROM impossible to do. Other protocols and parts of the net-tools might be affected too. I did a quick patch and rolled my own src and binary RPMs that can be downloaded at: ftp://ftp.hes.iki.fi/pub/ham/unix/linux/ax25/packages/libc6/rpm/ The RPMs have not been tested very thoroughly so if something breaks you get to keep both pieces... However my fix is rather obvious so I feel safe distributing it. :) BTW the bug is not Red Hat specific so other distributions might be affected too. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Unproto Path in AX25
On Wed, 12 Apr 2000, Hamish Moffatt wrote: > On Mon, Apr 10, 2000 at 09:23:19AM -0500, John Gorkos wrote: > > Unfortunately, with APRS being a UI-only protocol, my beacons don't get > > propagated through the APRS system. I need to be able to do something > > like this: > > beacon -d "APRS via WIDE,WIDE,WIDE" ... > > That should work fine, use "v" instead of "via". Both should work fine. It's the comma signs that are the problem... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Unproto Path in AX25
On Mon, 10 Apr 2000, jerome schatten wrote: > John... I went through this years ago running a 1278 in kiss mode on > an fbb bbs. As soon as it receives a string which is the same as > the KISSOFF command, it drops out of kiss mode. I can't remember what > the hex sequence was, but it was reproducible. No-one was able to > fix it, and it seemed true across all 1278's in this area. The "kiss off" sequence in hex is 0xC0 0xFF 0xC0 and it can never appear in a valid kiss data flow. So there must be more than that to it if it really was happening in response to serial data to the TNC. Long ago I had a problem with a Symek TNC2S with the TAPR firmware that came with it. It would just reset itself after a while. But IIRC it stayed in KISS mode, it flashed the LEDs three times and forgot the channel access parameters... Anyway it was a bug in the firmware. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Unproto Path in AX25
On Mon, 10 Apr 2000, John Gorkos wrote: > Background: I am running APRSdigi on my RedHat 6.1 box, with a MFJ-1278 > hanging on ttyS0. I am using the modified AXtools from Alan Crosswell, > N2YGK. Everything is working well (aprsmon allows TCP/IP connections, > beacons are sent, etc.). What is "modified AXtools from Alan Crosswell" ? > Problem 2: The beacon command I use looks like this: > beacon -d APRS -t 15 ax0 '' > Unfortunately, with APRS being a UI-only protocol, my beacons don't get > propagated through the APRS system. I need to be able to do something > like this: > beacon -d "APRS via WIDE,WIDE,WIDE" ... > Is there an axparm that I'm missing in the documentation that will allow > me to do this? Thanks. Have you tried beacon -d "APRS v WIDE WIDE WIDE" ... That should work. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Node query
On Mon, 10 Apr 2000, Robin Gilks wrote:
> > > The line in my node.conf that is affected is:
> > > Alias CONVers "telnet %{2:gb7ipd.ampr.org} 3600 \"/n %u %{1:160}\""
> > >
> > > and its the bit in the quotes at the end that don't work no more...
Actually you'll probably find that the first part won't work either. You
won't be able to specify another convers server at runtime...
> > What does work is;
> >
> > 'telnet %{2:gb7ipd.ampr.org} 3600 "/n %u %{1:160}\n/w *"'
>
> Changing the double quotes to single quotes and removing the escape character
> from the double quotes fixed it!!
>
> Not an obvious problem!!
The reason is that those %-escapes get processed twice: first when the
configuration file is read and later when the alias is actually executed.
The problem is that positional parameters (%1 and %2 in this case) don't
really have a meaning when the configuration file is read. They only have
a meaning when the alias is executed. So you need to be able to enter the
alias definition so that the %-escapes are not processed while reading the
config but only at alias execution time. That required a slight change in
the config syntax. The change is documented (see the HISTORY file,
node.conf(5) manual page and the sample files) but probably very easy to
miss...
The way it works is probably easiest explained with the example included
in the sample file:
ExtCmd TIme 1 nobody /bin/echo echo %N Node session started at %I, current time is \%I.
The %N will be expanded to the NodeId (at startup so NodeId needs to be
specified above this). %I will be the current time again at the time the
config file is read. The second %I has the percent sign escaped so it will
be expanded only when the extcmd is executed. (The same effect would have
resulted from enclosing it in single quotes: '%I')
I know this may sound confusing (I certainly was first confused when
trying to code it) but IMHO when you understand it, you'll see that it is
the only clean way of implementing it.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Attention UK netrom users
On Mon, 10 Apr 2000, Robin Gilks wrote: > The other problem is, using 2.0.36 kernel, how do I get the netrom broadcast to > send the alias as well as the netrom call. I've set nrports the same as a 2.2 > kernel box which works OK. An adjacent node adds the call to its node list but > no alias :-(( The sending node alias is part of every NODES broadcast sent by the node. It should work the same with regardless of the kernel version. Have you watched the 2.0.36 box sending the broadcasts? With listen -a on that box? >From another box over the radio? Is there perhaps something strange in the nrports file on that box? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Split port ax25
On Sat, 8 Apr 2000, Robin Gilks wrote: > I have a very vague recollection of someone saying that its possible to > operate an ax25 connection (eg. for netrom) over a split port - ie. one that > TXes on a different interface to the RX. Something like an internal tunnel? > > I can't find anything on the docs and as I recall it was a rather obscure > facility anyway. I of course find I need it!!! You mean "axparms -forward" ? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Kernel based AX25 on Sparc?
On Fri, 24 Mar 2000, Geoff Blake wrote: > I may be going off at "half cock" but during a spare moment at work today > I was looking at compiling an "AX25 aware" kernel on a Sparc 10. I was > doing about a dozen other things at the time, but it appeared that > Menuconfig did not offer the same options as the usual i386 config. > > Should the Sparc Linux kerne source tree include the same AX25 utilities > or is the RedHat 6.1 (2.2.12) distribution a stripped down version? (I > did not have a recent kernel tree to hand nor did I want to d/load one > over a 28K link!) An excerpt from the announcement of Alan's 2.2.15pre1 kernel: ... o Use amateur radio drivers on Sparc (Tom Sailer) ... Seems they were accidentally left off at some point. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: OT: T4 terminal program?
On Sun, 26 Mar 2000, Gerd wrote: > sorry for being offtopic, but here at the list for me there was the > only place the T4 packet radio terminal program was mentioned. I > could not find it in the Internet, however. > Does anyone know where to get it from? ftp://ftp.funet.fi/pub/ham/Finnish/oh2mkp/ I'm not sure if newer versions can be found anywhere on the net. The latest is something like 1.5a24. After that Mikko lost interest in it... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: VC and datagram mode?
On Fri, 24 Mar 2000, Thomas Sailer wrote: > "Wilson G. Hein" wrote: > > > Is this a part of the current implementation of linux ax25 and x1j nodes? > > It's not in the stock kernel, however part of the DG2FEF/DG1KJD patch. > No idea about x1j. It works in Flexnet and Xnet. Wampes also has > some h2h ack code. > > In theory, you could also use net/rom to achieve this, but this adds > overhead (net/rom header), a window size problem (if you don't > use mod128 sequence numbers), and the original net/rom routing > protocol is quite broken (INP is said to solve this though). On the other hand both Linux (current implementation) and X1J are capable of IP routing and support Virtual Circuit mode so if configured to do that the whole problem disappears. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: VC and datagram mode?
On Tue, 21 Mar 2000, Arno Verhoeven wrote: > "Jose R. Marte A." wrote: > > > > In datagram mode, IP packets are encapsulated in AX.25 > > (UI frames) and transmitted without any other link level mechanisms, > > such as connections or acknowledgments. > > > > In vc (virtual circuit) mode, IP packets are encapsulated in AX.25 > > (I frames) and are acknowledged at the link level according to the > > AX.25 protocol. Link level (i.e. AX.25) connections are opened as > > necessary. > > > > Isn't this the other way around? > Datagram is the default mode, and I've never seen UI frames after the > connection has been established. But maybe I'm mistaking. No, Jose has it right. > The next question that pops up is; > If this setting determines the AX.25 connection type, It defines how _IP_traffic_ is carried over AX.25. > then what is the > difference with the parameter set in > /proc/sys/net/ax25//connect_mode ??? This defines the type of incoming AX.25 connections allowed. Zero means no connections are allowed (only incoming UI frames are processed), one means connected mode is allowed to carry upper level protocol frames (like IP or NET/ROM) and two means everything is accepted (including no-L3-protocol frames or text mode). -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: AX.25 packet length parameter
On Tue, 21 Mar 2000, Arno Verhoeven wrote: > I have a question about the parameter set in > /proc/sys/net/ax25/interface_name/maximum_packet_length > > Is this parameter determining the total AX.25 frame length (including > flags, address, frame-number, etc)? > Or is it the length of the payload within this AX.25 frame? Payload. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Syslog message: pg uses obsolete (PF_INET,SOCK_PACKET)
On Mon, 20 Mar 2000, Bent Bagger wrote: > I am hunting an error in PG (the program for upload of files to the > Microsats) and I have turned socket debug information on by doing a > 'setsockopt(s, SOL_SOCKET, SO_DEBUG, &opt, sizeof(opt)' call. When > I inspect the system log, I now find this message: > > pg uses obsolete (PF_INET,SOCK_PACKET) This shouldn't depend on having SO_DEBUG on. You probably just haven't noticed it before. Also you only get it once after a reboot and it may be that you didn't see it because some other program has already got the complaint. So it depends on the order in which you run programs after a reboot. > Could somebody please shed some light on the significance of this > message, more specifically: what has been changed in the ax25utilities > since the days of kernel 2.0.35 (I'm now on kernel 2.2.13 with glibc 2.1 > and libax25 0.0 (?)) and what changes should I do in PG to make this message > go away? Nothing changed in the utils, it's the kernels generic packet capture interface that was changed. The message is completely harmless (other than a program causing it may stop working sometime in the future if not fixed). You can get rid of the message just by changing PF_INET -> PF_PACKET in the source. While that is actually also obsolete (see "man packet") I believe it will continue to work for some time still. I have not checked what it would take to properly use (PF_PACKET, SOCK_RAW) like suggested in the packet(4) manual page. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: ARP Timeout problem
On Sat, 18 Mar 2000, F. D. Johnson wrote: > Hi Folks, can anyone point me in tthe right direction ? > > My system (Suse6.3), when initiating any tcpip/radio session sends out 3 > very rapid ARP requests > then, more often than not, times out before the remote end has had chance > to reply. > > Can I lengthen the ARP timeout ? Yes, through the proc interface. See /usr/src/linux/Documentation/proc.txt section Network Neighbor handling. The parameter you want to adjust is retrans_time. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: DSP boards.
On Sun, 19 Mar 2000, Geoff Bagley wrote: > I had not realised that stand-alone DSP boards were getting scarce. The Motorola DSP56002EVM was discontinued some time ago. Newer models are of course available but there is no direct replacement. There was a discussion on this topic on the TAPR DSPSIG (or was it HFSIG?) so if anyone is interested you can check the archives on TAPR home page. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: newqpsk Activity?
On Mon, 13 Mar 2000, Luc Langehegermann wrote: > Thanks you for reading this. I have just compiled the newqpsk package and it > seems to work. Are there already stations operating this? If yes, where? .lu is Luxembourg right? You might want to try if you can hear Joni OH2NJR's station at 3590.0 MHz LSB. It is on 24h/day, there is a LinuxNode and a XFBB bbs listening. He uses an Alef Null DSP card 4 but the settings are compatible with the defaults in my package. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
ANN: newqpsk-0.0.3 (Q15X25)
Hi all, I have uploaded newqpsk-0.0.3.tar.gz to hes.iki.fi. There is nothing very special but a nasty bug that probably affected all OSS/Lite users should be gone. >From ChangeLog: 2000-03-07 Tomi Manninen <[EMAIL PROTECTED]> * Version 0.0.3 * The modem should now work with the standard kernel sound drivers as well (I use ALSA drivers...) * Added BCH(15,7) error correction code. See the supplied soundmodem.conf sample file for details. (The code is from Charles Brain G4GUO, I hope he doesn't mind...) * Minor changes in the documentation -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Q15X25 - newpsk.0.0.1
On Mon, 6 Mar 2000, Jörgen Overgaard wrote: > Is there any one who has successfully compiled and run the Q15X25 > (newpsk-0.0.1) package on RedHat 6.1?? Well, I still run RH6.0 but I really don't think there are any 6.1 spesific problems... > For me it all compiles well,but when i try to start it with > ./soundmodem it stops and shouts angry at me that threre is a problem > with TIOCSETD. Do you have MKISS support compiled in the kernel or if it is compiled as a module, is the module loaded? > After some VERY rude hacking in the code it runs a bit longer,but not much. > Now it says it cannot open PTY "". > (I understand that you cannot open "" nothing,but why is it trying) Better undo those hacks... :) Anyway there is a newqpsk-0.0.2 available in the same place you downloaded 0.0.1. There is nothing really new but the nasty tx-lockup bug mentioned in BUGS is fixed. Oh, and I should probably soon upload 0.0.3 as there is also a problem when running newqpsk with the standard sound drivers (I use ALSA drivers to develop). -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: QSSTV
On Sun, 13 Feb 2000, Richard Ferryman wrote: > I also tried and failed under 6.1. Has anyone got QSSTV to work on this RH > release? I just compiled qsstv_2_0_e under RH6.0 and it seems to work fine. Here is what I had to do: 1) I needed to upgrade my Qt libs because in RH6.0 they don't include libqimgio. There is are new RPMs in RedHat updates directory on their FTP site. Anyway I believe this is unnecessary in RH6.1 as it seems to use the upgraded RPM already (qt1x-1.44-4 and qt1x-devel-1.44-4). 2) The Makefile uses QTDIR environment variable to find includes and the meta object compiler "moc". So I had to type: export QTDIR=/usr/lib/qt-1.44 to have the variable point to the correct directory. 3) Then I needed to edit Makefile and replace the line: MOC = moc with: MOC = $(QTDIR)/bin/moc It's on line 18 of the Makefile. 4) Then I ran "make" and it produced a working executable without a single error message! Hope this helps. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: GW-List - kissnetd not working?
On Sat, 12 Feb 2000, Terry Dawson wrote: > Chris Smith wrote: > > > I run kissnetd /dev/ptyzf /dev/ptyze & > > Then kissattach /dev/ptyzf > > and get : kissattach: open: Input/output error > > kissnetd should be opening the slave end of the pty, and kissattach > should be opening the master end. > You've got them both opening the same end. Note that a long time ago when I experimented with kissnetd I noticed it doesn't want to work on the slave side. I don't know if this is still the case but at the time it certainly was. So the advise goes: kissnetd on the master side, kissattach on the slave side. Just a hint if all else fails... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Alias in ax25 util help
On Sat, 12 Feb 2000, Ron Stordahl wrote: > All of a sudden I have received a flurry of responses to my posting in > March 1999. I don't know what has caused this, but re-reading them > causes me to remember a few additional points. I had this too. Seems that a host in .cz re-posted every single message posted to linux-hams last year to all the recipients except linux-hams. So I received a lot of mail that either had me listed in To: or Cc:, or that were also cross-posted to xfbb or debian-hams... > I now recall why a 6 character alias caused problems. It was because I had > used a number as the 6th character. Specifically we had a node > STCDX:K0IR-7 and I added a node STCDX1:K0IR-2. Surrounding TheNet > X1J nodes would not deal correctly (yes I know that's pretty vague - I don't > remember the exact details) with STCDX1. I had to change it to STCDXA > at which point all was well. STCDX1 may be legal, standards wise, but it > appears the alias parser in TheNet or BPQ may be not up to the job. Strange. We have a lot of nodes with such aliases here. Right now I can find HYVI10, LOHJA2, LOHJA7, LOHJA8, LOHJA9 on my list. And in the past we used to use aliases of the style #8IP46 (oh2bns.ampr.org = 44.139.8.46). Those LOHJA nodes are TheNet nodes and BPQ and X1J are also used here. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: pa4ab
On Mon, 7 Feb 2000, Gregory Maxwell wrote: > On Mon, 7 Feb 2000, Ing. Jose A. Amador wrote: > > > On Mon, 7 Feb 2000, Tomi Manninen wrote: > > > > > Why not try Q15X25 (aka NEWQPSK). Download the package from > > > http://www.hes.iki.fi/pub/ham/unix/linux/ax25/ > > > and give it a try! > > > > I already got it, precisely from THAT URL, but have not compiled it > > yetIs anyone using it on HF ? > > Have I been out of the soundmodem loop too long or are all soundmodems now > implimented as very nice userspace daemons like this one? As explained in the README file, I used an early beta version of a userspace implementation from Thomas HB9JNX as the core of my Q15 code. I stripped all the other modulator/demodulator libraries from my package in order to avoid confusion. Unfortunately it seems Thomas is so busy with more important projects (read work) so he hasn't been able to finish the soundmodem code. The beta I have used works, but still has issues to be solved and probably wouldn't work too well on a busy VHF channel. So were stuck with the kernel soundmodem implementation at least for a while. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: pa4ab
On Mon, 7 Feb 2000, Ing. Jose A. Amador wrote: > On Mon, 7 Feb 2000, Tomi Manninen wrote: > > > Why not try Q15X25 (aka NEWQPSK). Download the package from > > > > http://www.hes.iki.fi/pub/ham/unix/linux/ax25/ > > > > and give it a try! > > I already got it, precisely from THAT URL, but have not compiled it > yetIs anyone using it on HF ? I only know about one station using it regularly here in Finland but that's on 80m so probably not of much interest to you. Anyway find someone interested thereabouts and start using it... :) BTW I uploaded a new version today that fixes a rather fatal bug. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: pa4ab
On Mon, 7 Feb 2000, Ing. Jose A. Amador wrote: > Certainly, 1200 could be used on 10 meters, or anywhere where the > regulations do not impede it if you don't have a path with heavy > multipath. Yesterday a good stretch of South America was copiable here on > ten...LW5's, PY2's, etc, on 28.180, 1200 baud. > > It is a pity noone has forwarded a solution to this. > Maybe a patch and plugging new figures > > Has anyone used the 4800 baud PSK over an SSB radio on HF ? It MIGHT get > thru...I have not tried, I am still using Kantronics TNC's in kiss mode. > But I am curious... Why not try Q15X25 (aka NEWQPSK). Download the package from http://www.hes.iki.fi/pub/ham/unix/linux/ax25/ and give it a try! -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: NetROM interface for TCP/IP ?
On Mon, 7 Feb 2000, Stephan Loges wrote: > Trying to get NetROM via TCP/IP up with kernel 2.2.13 (SuSE 6.3). > Until now without success. > After a ping from a remote machine, which frames are forwarded > by my NetROM neighbour, ifconfig nr0 looks like this: > slclx:~ # ifconfig nr0 > nr0 Link encap:AMPR NET/ROM HWaddr DB0SUE-9 > inet addr:44.130.127.141 Mask:255.0.0.0 > UP RUNNING MTU:512 Metric:1 > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:3 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > It received the 3 packets and answered them as they should, but they > are not visible at the ax0 port. > A ping from this machine to the remote end counts one error more. > > This is my routing table: > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > 44.130.127.141 * 255.255.255.255 UH0 00 nr0 This shouldn't be necessary. > 44.130.127.129 * 255.255.255.255 UH0 00 nr0 > loopback* 255.0.0.0 U 0 00 lo > > and this my arp entries: > Address HWtype HWaddress Flags Mask Iface > 44.130.127.129 netrom 88:84:60:A6:AA:8A:00CM nr0 I suppose 44.130.127.129 is the remote host you are talking about? The one that is pinging you? 88:84:60:A6:AA:8A:00 translates to DB0SUE-0 if I managed to do it right. Is that the correct NET/ROM address of 44.130.127.129 ? Also do you have a NET/ROM route to DB0SUE-0 ? Ie. if you run node, what does "nodes DB0SUE-0" command tell you? Or "grep DB0SUE-0 /proc/net/nr_nodes" from shell? > What im doing wrong, or does the current state of NetROM > interface with new kernel not support this ? I just verified, it works for me. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: API and driver interface
On Sun, 6 Feb 2000, Joerg Reuter DL1BKE wrote: > > > You can and should use 6PACK instead... > > Which doesn't work with the new AX.25 code... > Yet... > > Reminds me to give Andreas a kick in his ... um, nevermind. ;-) Exactly... :) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Kissparms on a wire link ?
On Sat, 5 Feb 2000, Stephan Loges wrote: > can someone tell me if and which parameter settings > of kissparms are active on a wire link ? None. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: API and driver interface
On Fri, 4 Feb 2000, Stefan Preuss wrote: > Gerd wrote: > > > Hmmm, are KISS TNCs still in use someplace (seriously)? > > > > What other chances do you have to work with a TNC under Linux other than in > > the KISS mode? I guess there are still a lot of TNC users out there (think of > > You can and should use 6PACK instead... Which doesn't work with the new AX.25 code... > bye Stefan -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: /dev/ttyS2 and /dev/ttyS3
On Fri, 4 Feb 2000 [EMAIL PROTECTED] wrote:
> > > Try this insteadworks here!
> > >
> > > ${SETSERIAL} /dev/cua0 uart 16550a port 0x3f0 irq 4 ^fourport
> > > ${SERSERIAL} /dev/cua1 uart 16550a port 0x2f0 irq 3 ^fourport
> >
> > Rubbish. (excuse me :) )
>
> Well genius, take a look at the SETSERIAL docs before you shoot your
> mouth off.
On a box with kernel 2.2 - /usr/src/linux/Documentation/Changes :
General Information
===
...
Also, please remember that cua* devices are now obsolete. Switch to
the corresponding ttyS* device instead (e.g., cua0 -> ttyS0, cua1 ->
ttyS1, etc.).
...
Recommending the use of /dev/cua* is not really sensible anymore. Even if
it happened to work for someone, it will cause unnecessary trouble the
next time they upgrade...
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04Amprnet: [EMAIL PROTECTED]
RE: Routing problem
On Fri, 4 Feb 2000, Robin Gilks wrote: > Does anyone have a 2.0 system they can check to see if it behaves the > same as 2.2 - be nice to know if this is a 2.2 problem only. If it is > its move back time 2.0 lets you route back to the interface the datagram came in. I can verify that anytime on my home system. > (despite other threads urging us to move on the bleeding edge). 2.2 is not bleeding edge... -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: Routing problem
On Sat, 5 Feb 2000, Hamish Moffatt wrote: > On Thu, Feb 03, 2000 at 07:36:57PM -, Robert A Jenkins wrote: > > For machines within the same subnet to work via an intermediate system, you > > must add specific routes to the target machines with the intermediate as a > > gateway. I set mine up in rc.local. > > Well, they are not really on the same subnet then if an active > intermediate is required. Can you change the subnet mask to the correct > value, which may even be 255.255.255.254? (I don't know that such > a mask is actually supported to be honest..) I'm not sure but I don't think the subnet / netmask issue is of relevance here. The main point of the problem is that Linux 2.2 seems to refuse to send out an IP datagram on the same interface it came in. At least with AX.25 interfaces. I tested this at home by setting up a route to certain host through my only radio port. I tested that the route works from my machine and from another machine on my home ethernet. I then went to another site that is on the same frequency as mine (actually I dialed it up but anyway) and set up the route there to point _through_my_box_. With older kernels, this would have worked. With kernel 2.2 my box just throws the datagram away. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: Routing problem
On Thu, 3 Feb 2000, Terry Dawson wrote: > Robin Gilks wrote: > > > Is there another parameter or does Linux strictly not allow routing back out > > the same port. If this is the case I've got some serious rethinking to do :-(( > > Robin, > I'm suffering precisely the same problem and have been for some time. > I'm completely baffled by it myself. I've suffered this problem for > months. > > I've tried walking through the kernel source to try and identify what > might be preventing it, and I'm stumped. > > What amazes me is that more people aren't seeing it. I just checked and I see this too. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: node dies with no errors
On Fri, 28 Jan 2000, Randy Smith wrote:
> Well, he sent me output from the strace. After all the initial normal
> system call type stuff, I can see where it connected to /dev/log, sent a
> message indicating the program started, then did an _exit() shortly
> thereafter. If there is nothing in the logfile regarding the exit (which
> doesn't look like there will be based on the strace), maybe some
> additional informational type messages need to be placed in the code.
> Just a thought. :)
Node doesn't send a message to syslog indicating it started!!!
You either get this:
tpm@oh2bns ~ $ strace node
execve("/usr/sbin/node", ["node"], [/* 44 vars */]) = 0
strace: exec: Operation not permitted
Or as root:
root@oh2bns /home/tpm # strace node 2>&1 | tail -5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
connect(5, {sun_family=AF_UNIX, sun_path="/dev/log"}, 16) = 0
send(5, "<187>Jan 28 15:14:05 node[1499]:"..., 68, 0) = 68
SYS_174(0xd, 0xb4e0, 0, 0x8, 0xd) = 0
_exit(1)= ?
And then:
root@oh2bns /home/tpm # tail -1 /var/log/messages
Jan 28 15:14:05 oh2bns node[1499]: No uid->callsign association found
Should be quite clear after that.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04Amprnet: [EMAIL PROTECTED]
Re: node dies with no errors
On Thu, 27 Jan 2000, Randy Smith wrote: > Try running it like this: > > strace /usr/sbin/node >~/node-strace 2>&1 That won't work. Node needs to be installed setuid root and a normal user can not strace a setuid program. And root can not run node at all... (there is a way around this, namely the -u option to strace but I don't think stracing would give any usefull information anyway) -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: node dies with no errors
On Wed, 26 Jan 2000, Peter Grace wrote: > Greetings all, especially Toni: > When I run node as in /usr/sbin/node > it dies with no errors. > > Any ideas why or how to diagnose? The first thing is to check your system logs (probably /var/log/messages) for an error message from node. There should be something. Most probably the problem is with uid/callsign association like Wilson already poined out. You should read the INSTALL file (and man axparms) that comes with the source distribution. Unfortunately it seems that this file was left out from the binary RPM. It should be in /usr/doc/node-0.3.0/. > RedHat 6.1 > kernel-2.2.14 > ax25-apps-0.0.4-1 > libax25-0.0.7-1 > libax25-devel-0.0.7-1 > ax25-tools-0.0.5-1 > node-0.3.0-1 (also tried node-0.3.0-8) Where did you find that? -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: IP over NET/ROM question
On Tue, 25 Jan 2000, Terry Dawson wrote: > Hans-Peter Zorn wrote: > > > (I think it would be rather annoying if 20+ stations at a user qrg > > would broadcast every 5 minutes?) > > Most networks I know use 30 minutes, not 5 minutes. Also, you can (should) set the verbose flag in nrbroadcast file to zero. That way you only advertise your own node and the broadcast packet will be very short. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: IP over NET/ROM question
On Tue, 25 Jan 2000, Terry Dawson wrote: > Hans-Peter Zorn wrote: > > > Why do I need a route to the interface ip address? Shouldn't that be > > a network route (which is set up automagically with 2.2) > > A nuance I missed the first time around. NetRom has no facility for > automatically mapping IP address to NetRom node (nothign like ARP for > example) so a network route is useless, you'll have to manually map each > IP address anyway. Actually you can use a network route and it's perfectly reasonable in many cases. But you still need to set up a manual ARP entry for each IP address separately. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: packets not making it out serial port
On Sun, 23 Jan 2000, Peter Grace wrote: > Thanks to Hans-Peter, > I cleaned out my old /etc/ax25 directory and removed the lines from my > rc.local > and used his method (http://1409.org/papers/ax25-config-howto.html) to > resetup ax25. I'm not getting any better results. > Packet seem to make it to the ax25 socket but don't make it out the > serial port - they aren't being shown on my tnc our going out my radio > (or incoming packets heard by my ax25d). Just a wild guess in case you haven't checked already. Is your TNC serial connection bitrate correct in both ends? The "speed" field in axports file is the serial bitrate, not the radio baud rate. I've made that mistake a couple of times in the past... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: compiling fbb for linux
On Sun, 9 Jan 2000, john Buxton wrote: > Hi list, > I now have RH6.0 with kernel 2.2.13. > I have compiled and installed ax25-apps-0.0.4, ax25-tools-0.0.4 and > libax25-0.0.7 > > I am attempting to compile fbb7.01b and have struck the following: > > cc -Wall -Wstrict-prototypes -O2 -g -funsigned-char -D__LINUX__ > -DPROTOTYPES -I../include -I/usr/local/include -c drv_sock.c -o > drv_sock.o > drv_sock.c: In function `opn_sck': > drv_sock.c:460: `SOL_AX25' undeclared (first use in this function) > drv_sock.c:460: (Each undeclared identifier is reported only once > drv_sock.c:460: for each function it appears in.) > drv_sock.c: In function `sock_connect': > drv_sock.c:1133: `SOL_AX25' undeclared (first use in this function) > drv_sock.c: In function `sock_stat': > drv_sock.c:1366: `SOL_AX25' undeclared (first use in this function) > drv_sock.c: In function `sock_connexion': > drv_sock.c:1561: `SOL_AX25' undeclared (first use in this function) > make: *** [drv_sock.o] Error 1 The best would probably be downloading xd701i.tgz which seems to fix this. It also has some new Y2K fixes. A quick and dirty solution might be just adding #define SOL_AX25 257 somewhere near the top of drv_sock.c. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: AX25 and Redhat 6.1
On Sun, 9 Jan 2000, Hamish Moffatt wrote: > On Sat, Jan 08, 2000 at 11:43:53PM +, Richard Adams wrote: > > Yes it is, for the simple reason, redhat-6.x uses kernels in the 2.2.xx > > range. Rh 6.x means 6.0 and 6.1. > > Its as easy as that. > > Don't you also need libc6.1 (glibc2.1) for the new tools? > That probably means RH6.1, not 6.0. The mentioned packages compile and work just fine on RH6.0. The binary rpm's I'm not 100% about but compiling from the source at least is definitely ok. On RH6.1 the binary rpm's is the way to go. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
RE: AX25 and Redhat 6.1
On Sun, 9 Jan 2000, john Buxton wrote: > I have the same problem with compilation. ax25-utils-2.1.42a.tar.gz > seems to be the latest version at > ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/. > > Where can I find a version that will compile with RH6.0? Nowhere. Please _read_ the message you quoted. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Tapio Sokura > Sent: Wednesday, 5 January 2000 9:47 > To: [EMAIL PROTECTED] > Subject: Re: AX25 and Redhat 6.1 > > > >Over the last couple of weeks I have been trying to get AX25 going on > Redhat > >6.1. I am unable to comple ax25-utils-2.1.42a.tar.gz on the base > system. > I get > > You are using a too old version of ax25 utils. The system has changed a > bit > for 2.2 kernels, you should download ax25-apps, ax25-tools libax25 from > ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/ and install them as instructed. > The ax25-howto is a bit outdated on the ax25 installation when you are > using 2.2 kernels. > > As for Samba, you should define the interfaces you want Samba to run on > in > your smb.conf (interfaces = ip-addr/mask). If you don't have an > interfaces > line, Samba will listen and broadcast on all network interfaces on your > machine. > > You can also probably configure most of the other packages to only use > certain interfaces. I think having an IP address is mandatory for a > network > interface in 2.2 kernel series. Kernel ipchains would probably be the > easiest way to disable all ip traffic on your radio interfaces. > -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Incoming connection to ???
On Thu, 6 Jan 2000, Chuck Hemker wrote: > I just noticed the other day that someone had connected to my computer. > (I noticed by the fact that the transmit relay in the radio was clicking) > I hadn't set it up to do anything so I didn't figure it would allow connects. > When I tested it myself though, I can connect to myself (going out to a local > node and back) and it seemed to eat everything I threw at it, but I have no > idea where it went. Does it accept connections and then ignore that data? > The only ax25 demons I have running are kissattach and mheardd. Yes, by default your system accepts incoming connections to the interface callsign. That is because there might be network traffic (IP, NET/ROM or ROSE) coming in. Any plain data (PID=Text) will be ignored. You can control that with /proc/sys/net/ax25//connect_mode. Setting it to 0 disables any incoming connections, 1 allowes only network connections and 2 allowes everything. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
RE: RE: AX25 and Redhat 6.1
On Wed, 5 Jan 2000, Hast, Chuck wrote: > Richard: > Thank you for the info, I am very new at this part of it. so new that > it is somewhat befuddling... I guess the biggest mess is in that the > docs are not up to date and trying to sort it all out is a bear. > > I see that in the RH 6.1 box there is a second CD that has a load of > AX25 stuff on it, but I assume that it is not all I need?? Yes it should be. I assume you mean the Powertools collection with the second CD. There are RPMs for libax25, ax25-tools, ax25-apps and node. Install those (remember to uninstall the obsolete ax25-utils RPM first!), configure and you should be ready to go. The samba problem was already addressed but I guess it doesn't hurt to repeat. I have these on my smb.conf: interfaces = 10.0.0.1/24 127.0.0.1/8 bind interfaces only = Yes That 10.0.0.1/24 of course corresponds to my ethernet interface (inet addr:10.0.0.1 Mask:255.255.255.0) and it is different from any radio ports. I'm not sure how you'd have to configure it if you want to use the same address on radio and ethernet interface. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: no more ipc channels
On Mon, 3 Jan 2000, Kjell Jarl wrote: > Thanks Tomi, yes kill -9 my.script has been performed regularly. Seems > to be a bad habit of mine, have to change it. Also, I may be doing wrong > in the expect script, node simply is left in the dark? Well sending SIGKILL to terminate node certainly doesn't give it any chance to free the IPC message channel. Besides using SIGKILL should always be the absolute last resort when trying to make a process terminate. If you can't get node to exit cleanly you can send a SIGTERM or a SIGQUIT to it. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
RE: Help - Display of link Retries
On Mon, 3 Jan 2000, R.A. Jenkins wrote: > unless it's been changed in a newer version, the Link command only shows the > instantaneous state of the Retry counter for the current frame (eg. 2 tries > from 15 max) - there is no 'accumulated total' of retries for a given link, > which is what I'm looking for. That would require the kernel to gather the statistics and currently it doesn't do that. It would be a nice addition though. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Linux FBB and Unproto list.
On Wed, 29 Dec 1999, Dirk Koopman wrote: > Because I wish to receive packets addressed to generalised, as it were, > "broadcast" addresses eg "DX", "ANN", "LINK" (these are examples, not > necessarily real) as well as to my callsign. I also may want to gateway UI > frames to callsigns that I know (by various higher level means) to be part of > "my" network (i.e to "digi" UI frames selectively across ports according to > heuristics under my control). > > The point of this that a reliable multicast protocol requires there to be > some group addresses, for DX cluster work there are several logical > groups that one could envisage including, but not limited to, "node-to-user" > things, "network" things, "inter-user" things and so on. As well as > multicast, there is a point to point message requirement that could be done > by "normal" connected mode but I would prefer, for orthogonality, to also be > done by a simple UI based, window=1, protocol. Some kind of braodcast/multicast method should probably be added to the AX.25 stack. But if you want that much flexibility it might be easiest to really use PF_PACKET. Sure you need root for that but only when calling socket(). > I was not envisaging a PF_PACKET based thing - I understand why this is a > problem. I was under the impression that we were talking about SOCK_RAW here > and that that required root as well. Calling socket(PF_AX25, SOCK_RAW, ...) doesn't require root but then binding the socket to any local address other than your own does require it. > Have you any sample code that does things with SOCK_RAW? I am perfectly happy > to generate raw AX25 packets (I can do that bit), it is the ioctl and > socket magic that I am confused (and cannot find any documentation for > SOCK_RAW) about. SOCK_RAW with AX25 seems to be just about the same as SOCK_DGRAM except that when you receive you get the PID byte as well. Thus I'm not sure if it's really very usefull. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: Error opening terminal
On Mon, 3 Jan 2000 [EMAIL PROTECTED] wrote: > I have two TNOS executables, the second just compiled for the y2k > bug. When I try to run the new exe I get the following message: > > Error opening terminal: linux Probably it doesn't find the terminfo database. I guess the executable was compiled on another machine? Running tnos with strace might reveal where it expects to find the database and then you can add a symbolic link there. For example on one box I had to do ln -s /usr/share/terminfo /usr/local/lib/terminfo to get some old stuff running after upgrading the system. Possible places for where the database is and/or where tnos searches for it are /usr/lib, /usr/share, /usr/local/lib and /usr/local/share at least. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: no more ipc channels
On Mon, 3 Jan 2000, Richard Adams wrote: > On Mon, 03 Jan 2000, Kjell Jarl wrote about, no more ipc channels: > > > > After using /usr/bin/node alot (I am learning script writing...) I am > > getting: > > > > [sm7gvf@pc2 test2]$ node > > LINUX:SM7GVF-5} ipc_open: Could not get an IPC channel: No space left on > > device > > This indicates that the partition on which the software operates is full. No it does NOT ! It means that the system is out of IPC channels. Kjell, have you by any chance been killing node with something like "kill -KILL" or otherwise made it terminate abnormally while testing your stuff? Node used to have a bug that caused it to leak IPC channels but that should be fixed (see the HISTORY file). Note that node not getting a free IPC channel is not a fatal bug. At least not to node. Only the the "TAlk" command is affected (disabled). Some other software on your system might however need a free channel too... > > RH 6.0, node 0.3.0 and alot of other stuff (clx/postgresql). Kernel > > 2.2.5. I seem to have vague recollection that clx has had problems with IPC channels as well. I'm not sure however as I don't run it my self. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: Linux FBB and Unproto list.
On Wed, 29 Dec 1999, Hamish Moffatt wrote: > On Tue, Dec 28, 1999 at 04:39:06PM -, Dirk Koopman wrote: > > Please would you answer the question? Why does it _actually_ need root > > privileges for ax25 protocol traffic? We are talking here about something > > which, whatever you do, is insecure. Anybody can program a TNC to be any > > callsign. Anybody can monitor anything using a TNC. Why does linux have to be > > different? > > Because Linux tries to integrate AX.25 with Unix, rather than Unix with AX.25. > It treats AX.25 like just another protocol; it should be as secure as IP. > Obviously it is trivially easy to imitate someone else's callsign if you > really want to, even with linux. But not without having root and/or hardware access to the system. Or that's how it is supposed to be. IMHO in this case root access doesn't have to mean a process running as root however. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: Linux FBB and Unproto list.
On Tue, 28 Dec 1999, Dirk Koopman wrote: > Please would you answer the question? Why does it _actually_ need root > privileges for ax25 protocol traffic? We are talking here about something > which, whatever you do, is insecure. Anybody can program a TNC to be any > callsign. Anybody can monitor anything using a TNC. Why does linux have to be > different? Well, I guess Tim said it. I might add that my understanding of the unix filosophy is that a normal user should not be allowed to do whatever he pleases, at least not without a permission from the super user. Remember that with PF_PACKET socket you can construct whatever packets you want, even completely malformated. Packets that could possibly crash other hosts on the network. Linux is a multiuser OS and everything is thought from that point of view. There is always the malicious user. That is probably the reason why a PF_PACKET socket is not allowed for a non-root user. Leszek talked something about a suser() call in af_ax25.c but frankly I don't know what he is talking about. PF_PACKET is handled in linux/net/packet/af_packet.c: if (!capable(CAP_NET_RAW)) return -EPERM; and that is for all protocols, not AX.25 alone. Tampering with that is definitely a bug! (BTW. that CAP stuff might be something worth investigating, I'm not quite sure how it works.) Note that we are talking about PF_PACKET socket here, not SOCK_RAW. At least I am (and that is what is used in FBB for unprotos). SOCK_RAW packets are actually allowed for normal users in Linux AX.25 (unlike IP). > > Generating UI frames as non-root is easy, just use a datagram socket. > > Receiving should be just as easy but I haven't tested. Of course you are > > then restricted to your own source call. > > Which is exactly the point, it isn't. For the record: I was able to create a program capable of sending UI frames to anyone and receiving UI frames from anyone. As non-root, and of course only with my own call. > I want to implement a UI based DX > Cluster protocol so that, finally, we can move on a bit, reduce some > bandwidth and maybe even achieve some experimentation. In order to do that I > need to be able to send UI frames from my callsign to any address, listen for > UI frames from any address, to any address and process the ones I am > interested in (only a few of which will be addressed to me) and maybe (for > experimental purposes) relay some frames from one interface to another. Explain me why you need to receive UI frames addressed to any address? FBB uses a UI based message system and copes well with only UI frames addressed to the box call. If you _really_ need that then use a SOCK_DGRAM socket and come up with a clever system to extend the uid->callsign association system so you are able to bind to those addresses you need. If that were controlled by root then I don't see a problem. Or then maybe implement some sort of AX.25 level broadcast/multicast method in the kernel. Or what ever, but do it in a way that is compatible with the unix way of thinking and the rest of the kernel. Not with a quick hack in microsoft style. > A good way to start this off would be to use another pid. However, I can't see > a way to use a specific pid on my UI frame without using a raw socket; there > doesn't seem to be a mechanism to handle pid specific traffic. There is no > concept of setting SO_BROADCAST on the socket. In fact there is no way AFAIK > to set a pid in any of the sockaddr structures available. So even 'normal' > things that you can do for IP, as a user, in this area are impossible. You can get/set the pid with SOCK_RAW at least. (Probably with SOCK_DGRAM also, I'm not sure if there really is a difference. I need to dig deeper into the code... :) And as I said, SOCK_RAW does not require root privileges. And if there is a valid feature missing in the kernel, that is probably because no-one has ever needed that. This is a community effort. You implement it. > potential security hole that needs watching), the main cluster process does > _NOT_ (and will _NOT_) run as root. I have already said that even if you use a PF_PACKET socket, there is no need to keep to root privileges after opening the socket. Just drop them and continue as a normal user. > I am just in the process of trying to see how this might be achieved by > studying the user_process stuff, but should you have any code available > (whether run by root or not) that can short circuit my learning the hard way, > it would be appreciated. Umm. I have to admit I don't know what you are talking about. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Linux FBB and Unproto list.
On Tue, 28 Dec 1999, Dirk Koopman wrote: > On 23-Dec-1999 Tomi Manninen wrote: > > On Thu, 23 Dec 1999, Leszek A. Szczepanowski wrote: > > > >> Is ANY posibility to use unproto list (raw socket), running > >> FBB as ordinal user, not root? I was looking in kernel > >> sources, and found in AF_AX25 there is one 'suser' function > >> checking if user has priviledges to open such a socket. > >> I think it is uneseseary there, security solutions in this > >> case aren't needed! What a stupid reason. If I'll make > >> patch, to open raw socket for AX25 by any user, it will > >> be placed on this list. > > > > Please don't distribute such bugs on this list. There are good reasons for > > why the unix security model is as it is. Besides, doing what you want > > (running FBB as non-root) would be fairly simple to do the right way. If > > you want to be usefull, just help Jean-Paul in doing that. > > Erm.. a "bug"? I am not at all sure that this is a "bug". I also cannot, for > the life of me, see why a "feature" of this sort cannot be discussed here. Well, of course it can be discussed. Maybe my reaction was too strong. > I would like to hear the reasons why this feature is "root only", especially > bearing in mind that computers running ax25 should be amateur use only. Amateur use only? Why? > Running ax25 stacks on "commercially sensitive" machines especially with > ax25 programs running as root (UI generating or not) strikes me a security > exploit waiting to happen! There is _NO_ need to have root privileges after opening the socket! Just drop them and suddenly you have 100% secure application. The stack it self should be secure. Unless some bright one decides to distribute a patch removing super user checks... > For the record, I too would like to be able to both receive and generate > UI frames from programs that are non-root. This is going to become an issue > during the course of the year with my DXSpider cluster program. Generating UI frames as non-root is easy, just use a datagram socket. Receiving should be just as easy but I haven't tested. Of course you are then restricted to your own source call. -- --- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
Re: AX25 T1 T2 T3 Timers
Hi again Paul ... :-) > In the previous system I ran 2.0.35, I use to change the values in > /proc/sys/net/ax25/interface_name/various timer param files with a > script file. (as reported many times over the past year or so) > Values I load in to t1_timer 70, t2_timer 10, t3_timer 18000 In 2.2.x kernels these values are expressed as 1/100th second values (or actually as the kernel native jiffies) instead of 1/10th second. Among others I have these lines in my startup scripts: case $(uname -r) in 2.0.*) echo 60> /proc/sys/net/ax25/ax0/t1_timeout echo 20> /proc/sys/net/ax25/ax0/t2_timeout echo 1800 > /proc/sys/net/ax25/ax0/t3_timeout ;; 2.[12].*) echo 600 > /proc/sys/net/ax25/ax0/t1_timeout echo 200 > /proc/sys/net/ax25/ax0/t2_timeout echo 18000 > /proc/sys/net/ax25/ax0/t3_timeout ;; esac I hope this one hits the nail too... :-) Oh, and BTW, Merry Christmas to everyone! -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: ax25-tools-0.0.5 + RIP98 Config file
On Sat, 25 Dec 1999, Paul Lewis wrote: > rip98d cannot locate the rip98.conf file I noticed the same a few weeks ago. The file is now called rip98d.conf even though all the documentation says otherwise... To be fixed in the next release I guess... -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Node-0.3-0 + telnet + http-1.22 EOL formatting
On Sat, 25 Dec 1999, Paul Lewis wrote: > I would like some advice on how to get the server when my users connect in to my Linux_node via the AX25 network. > They are using a non TCP/IP programs as their terminal program. > Use to work fine on my previous set-up. Your problem description is a bit vague but I guess the problem is that your AX.25 users get an LF as the end-of-line character whereas their packet terminal program expects (quite correctly) a CR. The reason for this is that over a telnet connection LinuxNode expects to see CR-LF or CR-NUL as the end-of-line sequence (most text based internet protocols use these). Conversd however sends only an LF and node doesn't think it as an EOL so it doesn't do any translation. IMHO this is really a TPP problem. I could add some sort of hack to node for this but I'm afraid it might break something else. I'd much rather fix HTPP, I need to ask Hessu for his opinion. > Also on the linux_node prompt line, I have Telnet Connect and at the > end of the prompt ZConnect ZTelnet > Has anyone else seen this and know how to remove these erroneous > commands Erroneous? Please read the node(8) man page. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25:[EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: Linux FBB and Unproto list.
On Thu, 23 Dec 1999, Leszek A. Szczepanowski wrote: > Is ANY posibility to use unproto list (raw socket), running > FBB as ordinal user, not root? I was looking in kernel > sources, and found in AF_AX25 there is one 'suser' function > checking if user has priviledges to open such a socket. > I think it is uneseseary there, security solutions in this > case aren't needed! What a stupid reason. If I'll make > patch, to open raw socket for AX25 by any user, it will > be placed on this list. Please don't distribute such bugs on this list. There are good reasons for why the unix security model is as it is. Besides, doing what you want (running FBB as non-root) would be fairly simple to do the right way. If you want to be usefull, just help Jean-Paul in doing that. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
Re: axconfig: port 1k2 not active
On Thu, 23 Dec 1999 [EMAIL PROTECTED] wrote: > I do #ifconfig bcsf1 hw ax25 ON1DOA-0 up > Then I try #ax25d > He tells me: > > axconfig: port 1k2 not active > ax25d:no AX.25 port data configured > > I tried to make it work to symlink the axports and ax25d.conf files to /etc > , /usr/etc/ax25 , but I got no positive result. I know that there are a few > people with the same problem, but none of them knows the answer. > > Is there someone who could give me a tip on how to fix this? You need to give the interface an IP address (using ifconfig). If you don't have your own, use something from the 10.x.x.x range. -- Tomi Manninen Internet: [EMAIL PROTECTED] OH2BNS AX.25: [EMAIL PROTECTED] KP20ME04Amprnet: [EMAIL PROTECTED]
