Quote:
Originally Posted by wholybee
My reply was going to be similar, that he needed to create a route on the Peplink for the UDP traffic. But he also shows a TCP dump from the mac, showing the UDP traffic is getting there.
We do see some UDP broadcast traffic, but we don't know if it is nmea data.
How is the YDWG set to UDP broadcast? iirc it only supports unicast, but i might be wrong.
I assume the YDWG logs into the peplink as a client? DHCP or static, and what is the gateway?
Can you view the routing table on the peplink?
|
The Peplink is setup to hand out a static IP address over DHCP.
I fired up Wireshark and did a packet capture when on the same subnet and then the different subnets. Note the YDWG prefixes the sentences with 'YD'. I can see the 'YDGLL' in both packets.
From 192.168.99.23 to 192.168.50.X - 2 packets of 192-byte and 430-byte
Sample of the 192-byte:
Frame 2: 238 bytes on wire (1904 bits), 238 bytes captured (1904 bits) on interface en0, id 0
Ethernet II, Src: Espressi_d8:03:67 (60:01:94:d8:03:67), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
802.1Q Virtual LAN, PRI: 0, DEI: 0, ID: 99
Internet Protocol Version 4, Src: 192.168.99.23, Dst: 255.255.255.255
User Datagram Protocol, Src Port: 10110, Dst Port: 10110
Data (192 bytes)
Data: 245944474c4c2c343734322e333336312c4e2c31323232332e 343332302c572c31383033…
[Length: 192]
0000 ff ff ff ff ff ff 60 01 94 d8 03 67 81 00 00 63 ......`....g...c
0010 08 00 45 00 00 dc 6f 06 00 00 ff 11 28 4b c0 a8 ..E...o.....(K..
0020 63 17 ff ff ff ff 27 7e 27 7e 00 c8 07 fa 24 59 c.....'~'~....$Y
0030 44 47 4c 4c 2c 34 37 34 32 2e 33 33 36 31 2c 4e DGLL,4742.3361,N
0040 2c 31 32 32 32 33 2e 34 33 32 30 2c 57 2c 31 38 ,12223.4320,W,18
0050 30 33 35 37 2e 37 36 2c 41 2c 44 2a 37 41 0d 0a 0357.76,A,D*7A..
0060 24 59 44 52 4d 43 2c 31 38 30 33 35 37 2e 30 30 $YDRMC,180357.00
0070 2c 41 2c 34 37 34 32 2e 33 33 36 31 2c 4e 2c 31 ,A,4742.3361,N,1
0080 32 32 32 33 2e 34 33 32 30 2c 57 2c 30 2e 33 2c 2223.4320,W,0.3,
0090 32 37 36 2e 30 2c 31 31 30 39 30 33 2c 2c 45 2c 276.0,110903,,E,
00a0 44 2c 43 2a 36 43 0d 0a 24 59 44 5a 44 41 2c 31 D,C*6C..$YDZDA,1
00b0 38 30 33 35 37 2e 38 33 2c 31 31 2c 30 39 2c 32 80357.83,11,09,2
00c0 30 30 33 2c 2c 2a 36 37 0d 0a 24 59 44 56 54 47 003,,*67..$YDVTG
00d0 2c 32 37 36 2e 30 2c 54 2c 2c 4d 2c 30 2e 33 2c ,276.0,T,,M,0.3,
00e0 4e 2c 30 2e 36 2c 4b 2c 41 2a 30 31 0d 0a N,0.6,K,A*01..
From 192.168.50.23 (same subnet) - 2 packets of 192-byte and 430-byte
Sample of the 192-byte:
Frame 369: 234 bytes on wire (1872 bits), 234 bytes captured (1872 bits) on interface en0, id 0
Ethernet II, Src: Espressi_d8:03:67 (60:01:94:d8:03:67), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.50.23, Dst: 255.255.255.255
User Datagram Protocol, Src Port: 10110, Dst Port: 10110
Data (192 bytes)
Data: 245944474c4c2c343734322e333335392c4e2c31323232332e 343239332c572c31383030…
[Length: 192]
0000 ff ff ff ff ff ff 60 01 94 d8 03 67 08 00 45 00 ......`....g..E.
0010 00 dc 6c d8 00 00 ff 11 5b 79 c0 a8 32 17 ff ff ..l.....[y..2...
0020 ff ff 27 7e 27 7e 00 c8 4f eb 24 59 44 47 4c 4c ..'~'~..O.$YDGLL
0030 2c 34 37 34 32 2e 33 33 35 39 2c 4e 2c 31 32 32 ,4742.3359,N,122
0040 32 33 2e 34 32 39 33 2c 57 2c 31 38 30 30 33 32 23.4293,W,180032
0050 2e 37 35 2c 41 2c 44 2a 37 42 0d 0a 24 59 44 52 .75,A,D*7B..$YDR
0060 4d 43 2c 31 38 30 30 33 32 2e 30 30 2c 41 2c 34 MC,180032.00,A,4
0070 37 34 32 2e 33 33 35 39 2c 4e 2c 31 32 32 32 33 742.3359,N,12223
0080 2e 34 32 39 33 2c 57 2c 30 2e 31 2c 31 34 32 2e .4293,W,0.1,142.
0090 39 2c 31 31 30 39 30 33 2c 2c 45 2c 44 2c 43 2a 9,110903,,E,D,C*
00a0 36 31 0d 0a 24 59 44 5a 44 41 2c 31 38 30 30 33 61..$YDZDA,18003
00b0 32 2e 38 35 2c 31 31 2c 30 39 2c 32 30 30 33 2c 2.85,11,09,2003,
00c0 2c 2a 36 31 0d 0a 24 59 44 56 54 47 2c 31 34 32 ,*61..$YDVTG,142
00d0 2e 39 2c 54 2c 2c 4d 2c 30 2e 31 2c 4e 2c 30 2e .9,T,,M,0.1,N,0.
00e0 33 2c 4b 2c 41 2a 30 42 0d 0a 3,K,A*0B..