linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: f6bvp@free.fr, linux-hams@vger.kernel.org
Cc: List for the LINUX version of FBB <xfbb@f6fbb.org>,
	fpac@f6fbb.org, F3KT <f3kt@free.fr>
Subject: Re: [AX25] ipv6 incompatible with AX.25
Date: Tue, 25 Jan 2022 10:14:30 -0800	[thread overview]
Message-ID: <2394eae7-dada-f43e-40b9-fae929212913@trinnet.net> (raw)
In-Reply-To: <581f0c8e-f4fb-523d-df6e-7a973b506c34@sorbonne-universite.fr>


Hey Bernard,

When you saw the lines:

--
Jan 25 12:16:31 f6bvp-Ubuntu kernel: [ 6942.400016] IPv6:
ADDRCONF(NETDEV_CHANGE): ax0: link becomes ready
--

was the AX25 interface not up and usable for classic packet regardless 
of it's IPv6 state?  Generally speaking, I had been been disabling IPv6 
for the longest time but I've been leaving it enabled as all of us need 
to start embracing IPv6.  Anyway, on my Ubuntu 20.04 machine, I have 
IPv6 enabled with AX25 interfaces present though I only have a link 
local address on my primary Ethernet interface (no IPv6 on ax0).  It 
should be noted I do NOT use AXIPv4 and it wouldn't surprised me if 
AXIPv6 doesn't work. There are a lot of tools in modern Linuxes that 
don't even support all aspects of AX25, NETROM, ROSE, etc. in modern 
tools like "ip", etc.  Many of us have to resort to installing legacy 
tools like ifconfig and route to get the job done.

--
$ ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
     altname enp0s31f6
     inet 192.168.0.25/24 brd 192.168.0.255 scope global dynamic 
noprefixroute eth0
        valid_lft 66471sec preferred_lft 66471sec
     inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
        valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
state DOWN group default qlen 1000
     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
     altname wlp4s0
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
state DOWN group default qlen 1000
     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
        valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master 
virbr0 state DOWN group default qlen 1000
     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
11: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc fq_codel state UNKNOWN 
group default qlen 10
     link/ax25 xx:xx:xx:xx:xx:xx:xx brd a2:a6:a8:40:40:40:00
     inet 44.128.0.1/24 scope global ax0
        valid_lft forever preferred_lft forever
--


> I hope this will help and I have a question. Shall this line be 
> uncommented in sysctl.conf ?
>
> # Uncomment the next line to enable packet forwarding for IPv4
> #net.ipv4.ip_forward=1

I question if you really want this on as this should only be enabled if 
you what your LInux device to be a router (aka.. forwarding packets 
between one interface and another).  This is NOT used if remote stations 
just want to reach your machine via IP.  Fyi, this kernel /proc command 
alone isn't enough to get routing working.  You also need to setup 
forwarding policies using tools like iptables (legacy) or nftables 
(newest way).


> I actually have the following in my ax25start script :
>
> ax25start:echo 1 > /proc/sys/net/ipv4/ip_forward

Same point as above.

--David
KI6ZHD

  reply	other threads:[~2022-01-25 18:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B2CD772.1030106@upmc.fr>
     [not found] ` <4B2D1025.1020106@gmail.com>
     [not found]   ` <4B2E6729.1090102@free.fr>
     [not found]     ` <4B507FAA.8010007@free.fr>
2010-01-15 20:36       ` [PATCH net-2.6] ax25: netrom: rose: Fix timer oopses Jarek Poplawski
2010-01-16  9:04         ` David Miller
2011-06-16 20:23         ` [AX25] inconsistent lock state f6bvp
2011-06-17 13:28           ` Ralf Baechle
2011-06-17 13:36           ` Arnd Bergmann
2011-06-17 13:51             ` Ralf Baechle
2011-06-17 14:11               ` Arnd Bergmann
2011-06-17 15:31                 ` f6bvp
2011-06-25 15:51                 ` f6bvp
2011-06-25 16:39                   ` Ralf Baechle DL5RB
2011-07-01 13:00                     ` Bernard F6BVP
2011-07-01 21:28                       ` [PATCH] 6pack,mkiss: fix lock inconsistency Arnd Bergmann
2011-07-02  0:30                         ` David Miller
2012-10-21 15:18                   ` [NetRom] possible circular locking dependency detected Bernard f6bvp
2011-06-17 15:26               ` [AX25] inconsistent lock state f6bvp
2011-06-16 20:40         ` f6bvp
2022-01-25 11:46           ` [AX25] ipv6 incompatible with AX.25 Bernard Pidoux
2022-01-25 18:14             ` David Ranch [this message]
2022-01-31 12:04               ` [ROSE] rose socket destination address empty in connect tests Bernard Pidoux , f6bvp
     [not found]               ` <724d87c5-3029-702a-32c9-b64677a2da0e@free.fr>
2022-01-31 17:36                 ` [AX25] ipv6 incompatible with AX.25 Bernard Pidoux , f6bvp
2022-02-06 21:12             ` [AX25] unreleased sockets after disconnecting Bernard Pidoux , f6bvp
2022-02-20  9:18               ` Thomas Osterried
2011-07-07 13:31         ` Question with axudp Bernard, f6bvp
2011-07-07 21:43           ` Robert Thoelen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2394eae7-dada-f43e-40b9-fae929212913@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=f3kt@free.fr \
    --cc=f6bvp@free.fr \
    --cc=fpac@f6fbb.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=xfbb@f6fbb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).