OpenCpn in Linux not receiving WIFI data

[pendragon]

I set up an AIS transponder to transmit the received AIS data via an NMEA to WIFI bridge to a laptop in the cockpit.
This system works great for Windows 7 & 10 64 bit. It shows all the data in opencpn on screen eg : AIS targets, GPS position etc.. It is set up via Network UDP 192.186.x.x port 10110 (No filters)
The NMEA debug window shows the incoming data also , So this works great.
Now the problem:
Recently I set up as dual boot WIn 10 pro with linux Debian 9.
I set up Opencpn in Debian --> All working fine showing CM93 charts etc.
The setup again is via Network 192.168.x.x :10110 UDP No filters (identical as what I have in windows)
I confirmed that Debian is receiving the WIFI data via Firefox 192.168.x.x, all data are incoming (same as Windows)
The OpenCpn NMEA debug window is not showing any data, no AIS targets showing and no GPS position, iow Opencpn is not receiving any WIFi data.
Can anyone please help?

[Hakan]

pendragon..
In OCPN connections: Try to omit the IP address so that O use the default 0.0.0.0

[pendragon]

I tried UDP 0.0.0.0 port 10110 --> does not work
UDP 0.0.0.0 on deleting ports, it defaults to port 2947--> does not work either.

[verkerkbr]

Originally Posted by pendragon

I set up an AIS transponder to transmit the received AIS data via an NMEA to WIFI bridge to a laptop in the cockpit.
This system works great for Windows 7 & 10 64 bit. It shows all the data in opencpn on screen eg : AIS targets, GPS position etc.. It is set up via Network UDP 192.186.x.x port 10110 (No filters)
The NMEA debug window shows the incoming data also , So this works great.
Now the problem:
Recently I set up as dual boot WIn 10 pro with linux Debian 9.
I set up Opencpn in Debian --> All working fine showing CM93 charts etc.
The setup again is via Network 192.168.x.x :10110 UDP No filters (identical as what I have in windows)
I confirmed that Debian is receiving the WIFI data via Firefox 192.168.x.x, all data are incoming (same as Windows)
The OpenCpn NMEA debug window is not showing any data, no AIS targets showing and no GPS position, iow Opencpn is not receiving any WIFi data.
Can anyone please help?

are you allowed the receive the data ?


try:


sudo usermod -a -G dialout (user)

[pendragon]

there is no restriction on receiving AIS data, It's the same as receiving radio- TV broadcast. On the other hand Broadcasting AIS data is NOT allowed without a registered transponder.
To your suggestion:
1) I cannot enter this in the same Terminal window as "sudo opencpn "
2)In a second Terminal window I get a lot of Options.
So, I don't know what you mean or how to proceed

[bcn]

Verkerkbr is not talking about the radio signal.

You need to establish that the OpenCPN application (or the user who runs it) has the required permissions to receive from the network.

That's what the command he suggest shall reveal. You have to replace (user) by your real correct user who is running the application. user without brackets.

sudo adduser (theUser) dialout
would be an alternative ..

[pendragon]

Misunderstood --> been using windows for too long I guess. am new to Debian.
Ok, the result is:
Adding user adrian to group dialout
Done.
Than I started OpenCpn , but still no AIS data showing

[petter5]

Is your pc on the same network as the router ?


Try

ip addr show

What is the output ?
What is the ipaddress of your router ??

Originally Posted by pendragon

Misunderstood --> been using windows for too long I guess. am new to Debian.
Ok, the result is:
Adding user adrian to group dialout
Done.
Than I started OpenCpn , but still no AIS data showing

[pendragon]

I presume you could call it a router.
It is a NMEA to WIFI bridge, anyway both openCpn and the wifi bridge are set on the the same IP address 192.168.4.1 UDP port 10110
I also have a actual router for internet over wifi and wired connection, but it is currently being used via USB hard wired


The output of ip addr show is :


adrian@debian:~$ sudo ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether e8:e0:b7:7c:bf:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.2.200/24 brd 192.168.2.255 scope global dynamic enp0s25
valid_lft 85597sec preferred_lft 85597sec
inet6 fe80::eae0:b7ff:fe7c:bf5d/64 scope link
valid_lft forever preferred_lft forever
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:db:df:0a:ea:88 brd ff:ff:ff:ff:ff:ff
inet 192.168.4.2/24 brd 192.168.4.255 scope global dynamic wlp4s0
valid_lft 6323sec preferred_lft 6323sec
inet6 fe80::af03:70c0:1a9c:9822/64 scope link
valid_lft forever preferred_lft forever
4: wwp0s26u1u6i6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:80:37:ec:02:00 brd ff:ff:ff:ff:ff:ff

[petter5]

Try

ping 192.168.4.1

Any reply ??


In opencpn try to set to 0.0.0.0 10110

Originally Posted by pendragon

I presume you could call it a router.
It is a NMEA to WIFI bridge, anyway both openCpn and the wifi bridge are set on the the same IP address 192.168.4.1 UDP port 10110
I also have a actual router for internet over wifi and wired connection, but it is currently being used via USB hard wired


The output of ip addr show is :


adrian@debian:~$ sudo ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether e8:e0:b7:7c:bf:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.2.200/24 brd 192.168.2.255 scope global dynamic enp0s25
valid_lft 85597sec preferred_lft 85597sec
inet6 fe80::eae0:b7ff:fe7c:bf5d/64 scope link
valid_lft forever preferred_lft forever
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:db:df:0a:ea:88 brd ff:ff:ff:ff:ff:ff
inet 192.168.4.2/24 brd 192.168.4.255 scope global dynamic wlp4s0
valid_lft 6323sec preferred_lft 6323sec
inet6 fe80::af03:70c0:1a9c:9822/64 scope link
valid_lft forever preferred_lft forever
4: wwp0s26u1u6i6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:80:37:ec:02:00 brd ff:ff:ff:ff:ff:ff

[transmitterdan]

The best way to distribute NMEA data via IP is to transmit to the broadcast IP (192.168.X.255). Then all devices on the same subnet can receive it. If you put an address like 192.168.X.10 as the UDP destination in the sender then it will only send to one device. Use 255 as the last number and data goes to all devices.

On the OpenCPN side set the UDP receive address to 0.0.0.0. Make sure the sending and receiving port numbers are the same. I use 10100 for both sender and receiver because it can’t be confused for a “preassigned” port.

[pendragon]

adrian@debian:~$ ping 192.168.4.1
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
64 bytes from 192.168.4.1: icmp_seq=1 ttl=128 time=1.18 ms
64 bytes from 192.168.4.1: icmp_seq=2 ttl=128 time=4.14 ms
64 bytes from 192.168.4.1: icmp_seq=3 ttl=128 time=2.83 ms
64 bytes from 192.168.4.1: icmp_seq=4 ttl=128 time=1.75 ms
64 bytes from 192.168.4.1: icmp_seq=5 ttl=128 time=2.23 ms

[pendragon]

Originally Posted by transmitterdan

The best way to distribute NMEA data via IP is to transmit to the broadcast IP (192.168.X.255). Then all devices on the same subnet can receive it. If you put an address like 192.168.X.10 as the UDP destination in the sender then it will only send to one device. Use 255 as the last number and data goes to all devices.

On the OpenCPN side set the UDP receive address to 0.0.0.0. Make sure the sending and receiving port numbers are the same. I use 10100 for both sender and receiver because it can’t be confused for a “preassigned” port.

I tried:
0.0.0.0 --- 0.0.0.0 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5125ms
rtt min/avg/max/mdev = 0.056/0.081/0.090/0.015 ms

and
--- 192.168.4.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.962/11.806/27.746/11.897 ms


Both Ip addresses seem OK, but no data on screen

Attached part screenshot (slightly edited for security reasons) of receiving AIS data, yet nothing shows in Cpn

[nohal]

Originally Posted by pendragon

I tried:
0.0.0.0 --- 0.0.0.0 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5125ms
rtt min/avg/max/mdev = 0.056/0.081/0.090/0.015 ms

and
--- 192.168.4.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.962/11.806/27.746/11.897 ms


Both Ip addresses seem OK, but no data on screen

Attached part screenshot (slightly edited for security reasons) of receiving AIS data, yet nothing shows in Cpn

Pinging stuff like broadcast addresses (the ones ending in .255) or listen all addresses (0.0.0.0), makes absolutely no sense.

UDP, which is what you seem to be trying to use is a stateless broadcast protocol, try to understand that it works the other way around than what you probably think - on the node that produces the data, you define the target audience to which it sends the data and on the clients you define that they are part of that audience, so there is not a "server" you might test by pinging it.

Pavel

[pendragon]

Originally Posted by nohal

Pinging stuff like broadcast addresses (the ones ending in .255) or listen all addresses (0.0.0.0), makes absolutely no sense.

UDP, which is what you seem to be trying to use is a stateless broadcast protocol, try to understand that it works the other way around than what you probably think - on the node that produces the data, you define the target audience to which it sends the data and on the clients you define that they are part of that audience, so there is not a "server" you might test by pinging it.

Pavel

Ok thanks--> this was suggested before.
The UDP protocol is the only choice in this NMEA to wifi bridge,
My initial question is: How do I get DEBIAN openCpn to receive the data? In windows it work perfectly, using the same identical settings ( see my previous messages)