LoTW and Linux

LoTW and Linux

[Petr Hlozek, OK2CQR]

Hello,

I have compiled tqsllib and TrustedQSL with wxWidgets 2.8 and have made
rpm packages for FC9 and openSUSE 11.0. Mandriva rpms will be added
soon. For the time being, you can use fc9 packages in Mandriva.

You can download it from  http://www.ok2cqr.com/?q=lotw-and-linux

73! Petr, OK2CQR

netromd + AF_PACKET/PF_PACKET

[cathrynham]

netromd is giving me an error "netromr: SIOCADDRT"

I just swapped AF_PACKET for PF_PACKET, SOCK_RAW and
that made the error go away, but I'm pretty sure that's not enough.

Is this correct, that AF_PACKET going away is the
source of this error?  If so, what are my options.  Has someone
fixed this code yet, or can I still recompile the kernel to include 
AF_PACKET?

Re: netromd + AF_PACKET/PF_PACKET

[cathrynham]

cathrynham wrote:
> netromd is giving me an error "netromr: SIOCADDRT"
>
> I just swapped AF_PACKET for PF_PACKET, SOCK_RAW and
> that made the error go away, but I'm pretty sure that's not enough.
>
> Is this correct, that AF_PACKET going away is the
> source of this error?  If so, what are my options.  Has someone
> fixed this code yet, or can I still recompile the kernel to include 
> AF_PACKET?
No, no, wait a second.  Sorry, I see other programs like listen
 are accessing AF_PACKET fine.  Maybe it's a config issue? Hmm.

Re: netromd + AF_PACKET/PF_PACKET

[Pidoux]

Hi,

Actually netromd was using obsolete PF_INET, SOCK_PACKET and I changed it
to PF_PACKET, SOCK_PACKET in ax25-tools.0.0.8.3 version.

Like you reported I can observe also netromr "bad argument"

Thus I added some modification in netromd code to make it display debuging log messages correctly.
This lead to version ax25-tools.0.0.8.4 that can be downloaded from hre :

http://f6bvp.free.fr/logiciels/ax25/ax25-tools-0.0.8.4src_f6bvp.tgz

Here is an extract from ChangeLog file :

  ax25-tools (0.0.8.4)
          * netrom debug info was not correctly reported.
            Starting netromd -lid will now
            write useful information into /var/log/messages

   -- Bernard Pidoux <f6bvp@amsat.org>

  ax25-tools (0.0.8.3)
          * kernel info (/var/log/kernel/info) tells PF_INET, SOCK_PACKET is
          obsolete. net/socket.c  says it should be replaced by PF_PACKET.
          This is done in hdrvcom.c, net2kiss.c, yamcfg.c
          * PF_INET = AF_INET. Thus (AF_INET, SOCK_PACKET) is also replaced by
          AF_PACKET in netromd.c, mheardd.c, rxecho.c and kissparms.c.
          ax25/ax25.4 file updated accordingly.

   -- Bernard Pidoux <f6bvp@amsat.org>


This is a listing of /var/log/messages when using ax25d version 0.0.8.4 :
...
Nov 22 20:45:00 f6bvp-11 netromd[4996]: netromr: add_node: route to me
Nov 22 20:48:04 f6bvp-11 netromd[4996]: Add Node : FE6BVP-1:FEBBS
Nov 22 20:48:04 f6bvp-11 netromd[4996]: Neighbour: VK2XB-14 device: ax0
Nov 22 20:48:04 f6bvp-11 netromd[4996]: Quality: 154 obs: 6 ndigis: 0
Nov 22 20:48:04 f6bvp-11 netromd[4996]: netromr: SIOCADDRT: Invalid argument
Nov 22 20:48:09 f6bvp-11 netromd[4996]: netromr: add_node: quality less than worst_qual
Nov 22 20:48:14 f6bvp-11 netromd[4996]: Add Node : F6BVP-3:BVPCLS
Nov 22 20:48:14 f6bvp-11 netromd[4996]: Neighbour: VK2XB-14 device: ax0
Nov 22 20:48:14 f6bvp-11 netromd[4996]: Quality: 154 obs: 6 ndigis: 0
Nov 22 20:48:14 f6bvp-11 netromd[4996]: netromr: SIOCADDRT: Invalid argument
Nov 22 20:54:47 f6bvp-11 netromd[4996]: netromr: add_node: quality less than worst_qual
Nov 22 20:55:03 f6bvp-11 netromd[4996]: netromr: add_node: route to me
Nov 22 20:58:00 f6bvp-11 netromd[4996]: Add Node : F6BVP-3:BVPDX
Nov 22 20:58:00 f6bvp-11 netromd[4996]: Neighbour: F6BVP-14 device: ax0
Nov 22 20:58:00 f6bvp-11 netromd[4996]: Quality: 254 obs: 6 ndigis: 0
Nov 22 20:58:00 f6bvp-11 netromd[4996]: netromr: SIOCADDRT: Invalid argument
Nov 22 20:58:05 f6bvp-11 netromd[4996]: netromr: add_node: route to me
...
Hope this will help finding the invalid argument received by netromd.


73 de Bernard, f6bvp



cathrynham a écrit :
> cathrynham wrote:
>> netromd is giving me an error "netromr: SIOCADDRT"
>>
>> I just swapped AF_PACKET for PF_PACKET, SOCK_RAW and
>> that made the error go away, but I'm pretty sure that's not enough.
>>
>> Is this correct, that AF_PACKET going away is the
>> source of this error?  If so, what are my options.  Has someone
>> fixed this code yet, or can I still recompile the kernel to include 
>> AF_PACKET?
> No, no, wait a second.  Sorry, I see other programs like listen
> are accessing AF_PACKET fine.  Maybe it's a config issue? Hmm.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

iptables versus ax25ipd

[cathrynham]

 I'm trying to setup axip, and when I turn on iptables/firewall in 
Fedora I stop
receiving any messages at all in axip. How do I  configure iptables so 
that it
works with axip at the same time?  

Re: iptables versus ax25ipd

[Steve Fraser]

cathrynham wrote:
> I'm trying to setup axip, and when I turn on iptables/firewall in 
> Fedora I stop
> receiving any messages at all in axip. How do I  configure iptables so 
> that it
> works with axip at the same time?  --
Assuming you have a default of 'drop or deny', then you need to allow 
the axip protocol through (the same applies to tunnelled ip).

To allow both, without restriction, something like this:

# encapsulation (IPIP=4, AXIP=93)
iptables -A FORWARD -p 
4                                                   -j ACCEPT
iptables -A FORWARD -p 
93                                                  -j ACCEPT

i.e. axip and ipip are separate protocols, just like tcp and udp are.

cheers

Steve

Re: iptables versus ax25ipd

[cathryn mataga]

John Ronan wrote:
>
> On 19 Nov 2008, at 06:31, cathrynham wrote:
>
>> I'm trying to setup axip, and when I turn on iptables/firewall in 
>> Fedora I stop
>> receiving any messages at all in axip. How do I  configure iptables 
>> so that it
>> works with axip at the same time?
> Hmm, is run over port 91? Our club machine is off so I can't check and 
> I don't remember.
>
raw        0      0 0.0.0.0:93                  
0.0.0.0:*                   7
        -

I set to 'ip' mode and it looks like it opens a socket for port 93 raw. 
  I assume
it's doing something slightly strange here.  I just went into the Fedora 
control panel
and naively turned on tcp/ip and udp for port 93, and that didn't 
work.   I'll
try the iptables that the other guy posted here this weekend, to see
if that works. 
.