TAP device & ax25 call

Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed

* TAP device & ax25 call
@ 2016-05-31 17:58 folkert
  2016-05-31 18:54 ` Thomas Osterried
  2016-06-01 12:31 ` Alejandro Santos
  0 siblings, 2 replies; 6+ messages in thread
From: folkert @ 2016-05-31 17:58 UTC (permalink / raw)
  To: linux-hams

Hi,

While trying to use tap-devices for ax.25 I noticed some issues.
Biggest issue being that I could not get it to work. Now some guy on
stackoverflow dug a bit further and apparently something goes wrong
with the ssid.
http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
I thought you may wanted to know this.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: TAP device & ax25 call
  2016-05-31 17:58 TAP device & ax25 call folkert
@ 2016-05-31 18:54 ` Thomas Osterried
  2016-06-01 12:31 ` Alejandro Santos
  1 sibling, 0 replies; 6+ messages in thread
From: Thomas Osterried @ 2016-05-31 18:54 UTC (permalink / raw)
  To: folkert; +Cc: linux-hams

Hello,

I know of no kernel problems with ax25 over tap.
Actually, we use it for years, i.e. with ax25ipd.

I also thought you may wanted to know this ;)

vy 73,
	- Thomas  dl9sau


On Tue, May 31, 2016 at 07:58:02PM +0200, folkert wrote:
> Hi,
> 
> While trying to use tap-devices for ax.25 I noticed some issues.
> Biggest issue being that I could not get it to work. Now some guy on
> stackoverflow dug a bit further and apparently something goes wrong
> with the ssid.
> http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
> I thought you may wanted to know this.
> --
> 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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: TAP device & ax25 call
  2016-05-31 17:58 TAP device & ax25 call folkert
  2016-05-31 18:54 ` Thomas Osterried
@ 2016-06-01 12:31 ` Alejandro Santos
  2016-06-01 13:47   ` Thomas Osterried
  2016-06-01 14:16   ` Alejandro Santos
  1 sibling, 2 replies; 6+ messages in thread
From: Alejandro Santos @ 2016-06-01 12:31 UTC (permalink / raw)
  To: folkert; +Cc: linux-hams

Hi all,

I've just double checked this and I agree, I'm unable to set the SSID.

Also tried manually with ifconfig and axparms, the SSID is ignored:

em0 is a TAP device.

# axparms -setcall em0 "LU4EXT-15"
# LANG=C ifconfig  em0
em0       Link encap:AMPR AX.25  HWaddr LU4EXT
          BROADCAST MULTICAST  MTU:256  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

# ifconfig em0 hw ax25 "LU4EXT-15" mtu 256
# LANG=C ifconfig  em0
em0       Link encap:AMPR AX.25  HWaddr LU4EXT
          BROADCAST MULTICAST  MTU:256  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

73
Alejandro



On Tue, May 31, 2016 at 7:58 PM, folkert <folkert@vanheusden.com> wrote:
> Hi,
>
> While trying to use tap-devices for ax.25 I noticed some issues.
> Biggest issue being that I could not get it to work. Now some guy on
> stackoverflow dug a bit further and apparently something goes wrong
> with the ssid.
> http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
> I thought you may wanted to know this.
> --
> 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



-- 
Alejandro Santos

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: TAP device & ax25 call
  2016-06-01 12:31 ` Alejandro Santos
@ 2016-06-01 13:47   ` Thomas Osterried
  2016-06-01 13:50     ` Thomas Osterried
  2016-06-01 14:16   ` Alejandro Santos
  1 sibling, 1 reply; 6+ messages in thread
From: Thomas Osterried @ 2016-06-01 13:47 UTC (permalink / raw)
  To: Alejandro Santos; +Cc: folkert, linux-hams

On Wed, Jun 01, 2016 at 02:31:00PM +0200, Alejandro Santos wrote:
> Hi all,
> 
> I've just double checked this and I agree, I'm unable to set the SSID.
> 
> Also tried manually with ifconfig and axparms, the SSID is ignored:
> 
> em0 is a TAP device.
> 
> # axparms -setcall em0 "LU4EXT-15"
> # LANG=C ifconfig  em0
> em0       Link encap:AMPR AX.25  HWaddr LU4EXT
>           BROADCAST MULTICAST  MTU:256  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> # ifconfig em0 hw ax25 "LU4EXT-15" mtu 256
> # LANG=C ifconfig  em0
> em0       Link encap:AMPR AX.25  HWaddr LU4EXT
>           BROADCAST MULTICAST  MTU:256  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> 73
> Alejandro
> 
> 
> 
> On Tue, May 31, 2016 at 7:58 PM, folkert <folkert@vanheusden.com> wrote:
> > Hi,
> >
> > While trying to use tap-devices for ax.25 I noticed some issues.
> > Biggest issue being that I could not get it to work. Now some guy on
> > stackoverflow dug a bit further and apparently something goes wrong
> > with the ssid.
> > http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
> > I thought you may wanted to know this.
> > --
> > 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

bpq0 is a tap device:

root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr LINUX-1
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10
root@db0fhn:~# axparms -setcall bpq0 TE1ST-15
root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr TE1ST-15  
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10  
root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr TE1STA-15  
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10  
root@db0fhn:~# uname -a
Linux db0fhn 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux

axparms / libax25: git master at http://git.linux-ax25.org/

vy 73,
	- Thomas  dl9sau

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: TAP device & ax25 call
  2016-06-01 13:47   ` Thomas Osterried
@ 2016-06-01 13:50     ` Thomas Osterried
  0 siblings, 0 replies; 6+ messages in thread
From: Thomas Osterried @ 2016-06-01 13:50 UTC (permalink / raw)
  To: Alejandro Santos; +Cc: folkert, linux-hams

sorry, just overseen forgot to paste the line where I increased the call sign length to 6(+ssid):

root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr LINUX-1
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10
root@db0fhn:~# axparms -setcall bpq0 TE1ST-15
root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr TE1ST-15
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10
root@db0fhn:~# axparms -setcall bpq0 TE1STA-15
root@db0fhn:~# ifconfig -a |grep bpq
bpq0      Link encap:AMPR AX.25  HWaddr TE1STA-15
bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10
root@db0fhn:~# uname -a
Linux db0fhn 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux


On Wed, Jun 01, 2016 at 03:47:29PM +0200, Thomas Osterried wrote:
> On Wed, Jun 01, 2016 at 02:31:00PM +0200, Alejandro Santos wrote:
> > Hi all,
> > 
> > I've just double checked this and I agree, I'm unable to set the SSID.
> > 
> > Also tried manually with ifconfig and axparms, the SSID is ignored:
> > 
> > em0 is a TAP device.
> > 
> > # axparms -setcall em0 "LU4EXT-15"
> > # LANG=C ifconfig  em0
> > em0       Link encap:AMPR AX.25  HWaddr LU4EXT
> >           BROADCAST MULTICAST  MTU:256  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:500
> >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> > 
> > # ifconfig em0 hw ax25 "LU4EXT-15" mtu 256
> > # LANG=C ifconfig  em0
> > em0       Link encap:AMPR AX.25  HWaddr LU4EXT
> >           BROADCAST MULTICAST  MTU:256  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:500
> >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> > 
> > 73
> > Alejandro
> > 
> > 
> > 
> > On Tue, May 31, 2016 at 7:58 PM, folkert <folkert@vanheusden.com> wrote:
> > > Hi,
> > >
> > > While trying to use tap-devices for ax.25 I noticed some issues.
> > > Biggest issue being that I could not get it to work. Now some guy on
> > > stackoverflow dug a bit further and apparently something goes wrong
> > > with the ssid.
> > > http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
> > > I thought you may wanted to know this.
> > > --
> > > 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
> 
> bpq0 is a tap device:
> 
> root@db0fhn:~# ifconfig -a |grep bpq
> bpq0      Link encap:AMPR AX.25  HWaddr LINUX-1
> bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10
> root@db0fhn:~# axparms -setcall bpq0 TE1ST-15
> root@db0fhn:~# ifconfig -a |grep bpq
> bpq0      Link encap:AMPR AX.25  HWaddr TE1ST-15  
> bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10  
> root@db0fhn:~# ifconfig -a |grep bpq
> bpq0      Link encap:AMPR AX.25  HWaddr TE1STA-15  
> bpq1      Link encap:AMPR AX.25  HWaddr DB0FHN-10  
> root@db0fhn:~# uname -a
> Linux db0fhn 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux
> 
> axparms / libax25: git master at http://git.linux-ax25.org/
> 
> vy 73,
> 	- Thomas  dl9sau
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: TAP device & ax25 call
  2016-06-01 12:31 ` Alejandro Santos
  2016-06-01 13:47   ` Thomas Osterried
@ 2016-06-01 14:16   ` Alejandro Santos
  1 sibling, 0 replies; 6+ messages in thread
From: Alejandro Santos @ 2016-06-01 14:16 UTC (permalink / raw)
  To: folkert; +Cc: linux-hams

it seems I've found some kernel bug:

https://gist.github.com/alejolp/c96089059af378bffd3c0363d8a29b03

# ./a.out em1 "LU4EXT-15"
Creating TAP AX25 device name em1, call name LU4EXT-15
dev 3 name em1

# beacon -s LU4EXT hola

Message from syslogd@debian at Jun  1 16:11:24 ...
 kernel:[ 2589.973799] skbuff: skb_under_panic: text:ffffffffa0a36810
len:20 put:15 head:ffff880223282a00 data:ffff8802232829fe tail:0x12
end:0xc0 dev:<NULL>

The complete Kernel call trace from dmesg is in the gist




On Wed, Jun 1, 2016 at 2:31 PM, Alejandro Santos <alejolp@alejolp.com.ar> wrote:
> Hi all,
>
> I've just double checked this and I agree, I'm unable to set the SSID.
>
> Also tried manually with ifconfig and axparms, the SSID is ignored:
>
> em0 is a TAP device.
>
> # axparms -setcall em0 "LU4EXT-15"
> # LANG=C ifconfig  em0
> em0       Link encap:AMPR AX.25  HWaddr LU4EXT
>           BROADCAST MULTICAST  MTU:256  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> # ifconfig em0 hw ax25 "LU4EXT-15" mtu 256
> # LANG=C ifconfig  em0
> em0       Link encap:AMPR AX.25  HWaddr LU4EXT
>           BROADCAST MULTICAST  MTU:256  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> 73
> Alejandro
>
>
>
> On Tue, May 31, 2016 at 7:58 PM, folkert <folkert@vanheusden.com> wrote:
>> Hi,
>>
>> While trying to use tap-devices for ax.25 I noticed some issues.
>> Biggest issue being that I could not get it to work. Now some guy on
>> stackoverflow dug a bit further and apparently something goes wrong
>> with the ssid.
>> http://stackoverflow.com/questions/22465138/creating-a-tun-network-device-with-ax-25-encapsulation/37534385#37534385
>> I thought you may wanted to know this.
>> --
>> 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
>
>
>
> --
> Alejandro Santos



-- 
Alejandro Santos

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-06-01 14:16 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-05-31 17:58 TAP device & ax25 call folkert
2016-05-31 18:54 ` Thomas Osterried
2016-06-01 12:31 ` Alejandro Santos
2016-06-01 13:47   ` Thomas Osterried
2016-06-01 13:50     ` Thomas Osterried
2016-06-01 14:16   ` Alejandro Santos

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox