Bernard Pidoux

Hi Bernd, I downloaded 3.14-alpha ifconfig and it is working fine with AX25, NetRom and Rose devices with AX25 compliant callsigns. Too long calls would be rejected by librairies, So no fear about it. In the mean time I also ran netstat with --ax25 and --rose options. Everything goes well. Thanks. Bernard, f6bvp / ai7bg

Hi Bernd, I downloaded 3.14-alpha ifconfig and it is working fine with all ax25, NetRom and Rose devices with AX25 compliant callsigns. Too long calls would be rejected by librairies, So no fear about it. In themean time I also ran netstat with --ax25 and --rose options. Everything goes well. Thanks. Bernard, f6bvp / ai7bg

I ran ifconfig succesfully with following patch that wad tested with Ubuntu running stable kernel 6.15.10 --- netrom.old.c 2025-08-15 15:46:49.100721078 +0200 +++ netrom.c 2025-08-15 16:24:54.710824595 +0200 @@ -54,7 +54,7 @@ static const char NETROM_print(const char ptr) { - static char buff[8]; + static char buff[10]; int i; for (i = 0; i < 6; i++) { --- ax25.old.c 2025-08-15 15:46:49.099443771 +0200 +++ ax25.c 2025-08-15 16:25:10.447445233 +0200 @@ -49,7 +49,7 @@ static const char AX25_print(const...

In order to trigger ifconfig issue with NetRom interface Newly installed Ubuntu Linux version 6.14.0-27-generic (buildd@lcy02-amd64-120) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #27~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 17:38:49 UTC 2 ~$ ifconfig lo lo: flags=73<up,loopback,running> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Boucle locale) RX packets 290 bytes 27402...

There is a similar issue with NetRom callsigns leading to a buffer overflow for the same reason of buffer dimension. Linux version 6.14.0-24-generic (buildd@lcy02-amd64-010) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #24~24.04.3-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 7 16:39:17 UTC 2 issuing ifconfig command gives : nr0: flags=193<up,running,noarp> mtu 236 *** buffer overflow detected ***: terminated Abandon (core dumped)</up,running,noarp>...

As AX25 interface callsign cannot be longer than 6 character, the correct patch should be : - static char buff[8]; + static char buff[10]; that is enough space for 6 characters, '-' sign, two digits SSID, and null terminating string '\0'

I finally agree with Martin that printing AX25 callsign needs a 10 characters buffer. Presently none of the three stations are experiencing ifconfig craches. Their ax0 interface callsigns have no more than 5 characters plus SSID of one or two characters. F6BVP-8, F6BVP-10 and F6KKR-10. In order to test my own station I set ax0 interface callsign to maximum AX25 size (6 characters + 2 digits SSID) and it did not induce any crash (TM6BVP-10). System is a RaspBerry Pi ~$ cat /proc/version Linux version...

Hi Bernd, Once again the buffer overflow is clearly related to -O2 option while compiling ifconfig.c For some reason the compiler is taking some liberties in reducing the size of a buffer. Here are three /proc/net/ax25 files coming from three different active AX.25 neighbour node stations : 73s de Bernard, f6bvp / ai7bg Le 24/06/2025 à 18:14, Bernd Eckenfels a écrit : thanks for debugging, will make sure that buffer cant overflow in the future. can you maybe add your /proc/net/ax25 file for testing...