Request for support / IOT connection setup

[Greg Oliver]

On Mon, Apr 1, 2024 at 4:31 AM <christian.kaiser at messagerie.de> wrote:

> Dear community,
>
> This is my
>
> Setup:
>
> I am on debian bookworm, uname -r: 6.6.20+rpt-rpi-v8 with NetworkManager
> –version:  1.42.4
>
> My wwan device is a ID 1e0e:9001 Qualcomm / Option SimTech SIM7000 with
>
> udev rule: ACTION=="add", SUBSYSTEM=="net", ATTR{qmi/raw_ip}=="*",
> ATTR{qmi/raw_ip}="Y"
>
> The NetworkManager connection
>
> nmcli connection add type gsm ifname '*' con-name 'test' apn 'iot.1nce.net'
> \n
>
> connection.autoconnect yes \n
>
> connection.lldp 0 \n
>
> ipv6.method disabled \n
>
> gsm.mtu 1200
>
> is successful: Connection successfully activated (D-Bus active path:
> /org/freedesktop/NetworkManager/ActiveConnection/8)
>
> and ifconfig reports:
>
> wwan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1200
>
>         inet 10.238.250.1  netmask 255.255.255.252  destination
> 10.238.250.1
>
>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen
> 1000  (UNSPEC)
>
>         RX packets 0  bytes 0 (0.0 B)
>
>         RX errors 0  dropped 0  overruns 0  frame 0
>
>         TX packets 1028  bytes 426040 (416.0 KiB)
>
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> After setting up the appropriate routing table – not shown here – I can
> send and receive udp datagrams.
>
>
>
> This is my
>
> Problem I am asking for help:
>
> tcpdump -vv  -i wwan0 shows this output (excerpt):
>
> ….
>
> 22:50:22.477131 IP (tos 0x0, ttl 1, id 54018, offset 0, flags [DF], proto
> UDP (17), length 419)
>
>     10.238.250.1.2053 > 239.2.1.1.2053: [udp sum ok] UDP, length 391
>
> 22:50:32.481315 IP (tos 0x0, ttl 1, id 54239, offset 0, flags [DF], proto
> UDP (17), length 419)
>
>     10.238.250.1.2053 > 239.2.1.1.2053: [udp sum ok] UDP, length 391
>
> …
>
>
>
> Some “process” is sending every 10 seconds traffic over wwan0.
>
>
>
> How can identify the “process”  and stop the traffic?
>

netstat --help
        -p, --programs           display PID/Program name for sockets

So - `netstat -p | grep 2053 | grep 239.2.1.1` will give you the pid of the
program sending traffic to 239.2.1.1 on port 2053



>
>
> Regards
>
> Christian
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/networkmanager/attachments/20240401/54d5f50c/attachment.htm>