OpenCpn in Linux not receiving WIFI data

[nohal]

Originally Posted by pendragon

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)

In your previous messages, I unfortunately see no useful information as you replace anything that could make some sense with x's... I also don't see you posting the "ip addr" output you have been asked for or the model of the "nmea to wifi bridge" you are using so that we may have a look at what it actually is capable of.
If you are worried about security, don't be, at least not the way you are now - those 192.168.0.0/16 are private, local addresses, not reachable over the internet, so knowing them is not going to help anybody to access your network in any way.

[bdbcat]

pendragon...

I do not understand this comment:

"I confirmed that Debian is receiving the WIFI data via Firefox 192.168.x.x, all data are incoming (same as Windows)"

How exactly did you do that?
Dave

[pendragon]

Originally Posted by nohal

In your previous messages, I unfortunately see no useful information as you replace anything that could make some sense with x's... I also don't see you posting the "ip addr" output you have been asked for or the model of the "nmea to wifi bridge" you are using so that we may have a look at what it actually is capable of.
If you are worried about security, don't be, at least not the way you are now - those 192.168.0.0/16 are private, local addresses, not reachable over the internet, so knowing them is not going to help anybody to access your network in any way.

The NMEA to WIFI bridge is Yakker by Yakbitz Australia
Set to IP 192.168.4.1 UDP port 10110, password set,
It receives data from Matsutec AIS transponder via wired connection and transmits same via WIFI.
As mentioned works great in Windows 7 10 64bit
------------------------------
Output for Ip addr 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

[pendragon]

Originally Posted by bdbcat

pendragon...

I do not understand this comment:

"I confirmed that Debian is receiving the WIFI data via Firefox 192.168.x.x, all data are incoming (same as Windows)"

How exactly did you do that?
Dave

The WIFI bridge contains a NMEA debug viewer.
This shows all the AIS + GPS data scolling past continiously.
This happens in Windows as well as in Debian, BUT no data showing on opencpn Debian.
In windows it shows all data in opencopn and works as expected.

[bdbcat]

pendragon...

Can you control the NMEA-WiFi bridge settings?

"The NMEA to WIFI bridge is Yakker by Yakbitz Australia
Set to IP 192.168.4.1 UDP port 10110, password set"

If so, change this address to 192.168.4.255

And what is the function of the password? Is that the WiFi Access Point p/w?

Dave

[bdbcat]

pendragon...

Documentation on Yakker is sketchy. It does not explicitly have a settable UDP target address.

Maybe it takes your set IP (192.168.4.1), and automatically sends UDP data to 192.168.4.255 ? Dunno without network analysis.

Have you tried TCP mode? In that case, the ip address uncertainty questions go away. Set OCPN connection parameters to (TCP) 192.168.4.1, with port = 23.

Dave

[sy_gilana]

Firewall blocking incoming?

[nohal]

Originally Posted by pendragon

The WIFI bridge contains a NMEA debug viewer.
This shows all the AIS + GPS data scolling past continiously.
This happens in Windows as well as in Debian, BUT no data showing on opencpn Debian.
In windows it shows all data in opencopn and works as expected.

The documentation of that bridge seems lacking information on how it actually sends the data, but I assume it might broadcasts to the /24 network derived from it's own IP address (192.168.4.1), so any device with a 192.168.4.* address should be able to receive it. The correct setting for the OpenCPN incoming UDP connection should then be IP address 0.0.0.0 and the same port number (10110 as you say, or maybe the default 2000?). Definitely it is not 192.168.4.1 in case you entered that.
If that does not work, there still is plenty of things that may cause that, varying from the firewall on your debian machine blocking the packets to the yakker actually not doing broadcast but multicast (that's what a well designed device would do) or (highly unlikely as then there would have to be some setting for the target in it's web interface) unicast.
The simple solution is, as Dave mentioned, switching to TCP where the settings to use are completely obvious.
Or having a look at the traffic, in which case we would like to see information about a few packets captured with

sudo tcpdump -i wlp4s0 udp port 10110

Pavel

[pendragon]

Originally Posted by bdbcat

pendragon...

Can you control the NMEA-WiFi bridge settings?

"The NMEA to WIFI bridge is Yakker by Yakbitz Australia
Set to IP 192.168.4.1 UDP port 10110, password set"

If so, change this address to 192.168.4.255

And what is the function of the password? Is that the WiFi Access Point p/w?

Dave

I can only control it if i have access to the source code. We tried to de-compile but no joy there.
The PW is to stop anyone on board with a tablet from accessing the wifi bridge

[pendragon]

Originally Posted by bdbcat

pendragon...

Documentation on Yakker is sketchy. It does not explicitly have a settable UDP target address.

Maybe it takes your set IP (192.168.4.1), and automatically sends UDP data to 192.168.4.255 ? Dunno without network analysis.

Have you tried TCP mode? In that case, the ip address uncertainty questions go away. Set OCPN connection parameters to (TCP) 192.168.4.1, with port = 23.

Dave

Last time I changed the mode to TCP 192.168.4.1:23 (using windows 10) I ended up resetting the wifi bridge to factory, Seemingly these 2 are not very good mates and nothing worked any more. Seeing UDP worked initially I set it back to original with win7.
Now you ask me to try TCP again...I give anything a go twice-- Used win 7 laptop to send TCP info to the Wifi bridge.Result -->Working on Win7, -->Reset the other laptops and android tablets. All are showing AIS -GPS data on screen. Yes even the Debian.
Many thanks Dave

[pendragon]

Many thanks to all contributors . Thanks to Dave's suggestion it's working in Linux Debian