Yet again Ethernet mod

I followed FAQ and several post here to try connecting an Ethernet based payload and get access to it from ground through herelink radio link

I’ve build this setup

And it works great I’ve well fing both eth0 on ground and air units

optimus:/ $ ifconfig
br-vxlan  Link encap:Ethernet  HWaddr b8:8d:f1:ff:85:03
          inet addr:192.168.144.11  Bcast:192.168.144.255  Mask:255.255.255.0 
          inet6 addr: fe80::ba8d:f1ff:feff:8503/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:33 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:94 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:1820 TX bytes:19918 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0 
          inet6 addr: ::1/128 Scope: Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:116795 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:116795 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1 
          RX bytes:6631247 TX bytes:6631247 

eth0      Link encap:Ethernet  HWaddr 00:0e:c6:86:d8:67
          inet6 addr: fe80::20e:c6ff:fe86:d867/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:94 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:92 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:6263 TX bytes:19228 

lmi40     Link encap:UNSPEC  
          inet addr:192.168.0.11  P-t-P:192.168.0.11  Mask:255.255.255.0 
          inet6 addr: fe80::d196:9657:f759:a2a/64 Scope: Link
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1550  Metric:1
          RX packets:16550 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:98053 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:500 
          RX bytes:864963 TX bytes:5447009 

vxlan1    Link encap:Ethernet  HWaddr d2:a3:f9:9d:e7:72
          inet6 addr: fe80::d0a3:f9ff:fe9d:e772/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:33 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:285 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:1820 TX bytes:58824 

wlan0     Link encap:Ethernet  HWaddr 00:18:07:51:85:03
          inet addr:192.168.9.130  Bcast:192.168.9.255  Mask:255.255.255.0 
          inet6 addr: fe80::218:7ff:fe51:8503/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3368 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:2206 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:580646 TX bytes:181345 

optimus:/ $

and for air unit

$ ifconfig
lmi40     Link encap:UNSPEC  
          inet addr:192.168.0.10  P-t-P:192.168.0.10  Mask:255.255.255.0 
          inet6 addr: fe80::f5ef:57ed:1189:8605/64 Scope: Link
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1550  Metric:1
          RX packets:15737 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:2686 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:500 
          RX bytes:920705 TX bytes:142663 

eth0      Link encap:Ethernet  HWaddr 00:0e:c6:86:d7:7d
          inet6 addr: fe80::20e:c6ff:fe86:d77d/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:2578 TX bytes:20826 

vxlan1    Link encap:Ethernet  HWaddr a2:6e:b1:c8:2d:74
          inet6 addr: fe80::a06e:b1ff:fec8:2d74/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:240 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:55384 TX bytes:2116 

br-vxlan  Link encap:Ethernet  HWaddr b8:8d:f1:ff:34:69
          inet addr:192.168.144.10  Bcast:192.168.144.255  Mask:255.255.255.0 
          inet6 addr: fe80::ba8d:f1ff:feff:3469/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:261 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:57916 TX bytes:760 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0 
          inet6 addr: ::1/128 Scope: Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:7658 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:7658 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1 
          RX bytes:480534 TX bytes:480534 

br-vxlan:0 Link encap:Ethernet  HWaddr b8:8d:f1:ff:34:69
          inet addr:192.168.42.10  Bcast:192.168.42.255  Mask:255.255.255.0 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

$ 

I can ping 192.168.0.10 or 11 and 192.168.144.10 or 11 from both air and ground units
I’ve fixed payload (192.168.0.20) and pc (192.168.0.50) ip’s
but I can’t ping any thing from or outside herelink units
i’ve also try to fix both IP in 192.168.144.xx range with same result
I’m not a big master in busy box but I was surprised to see no v4 ip on eth0 so I tryied to add an inetv4 addr on eth0

$ su 
# ip addr add 192.168.0.15 dev eth0

but It doesn’t change anything
if you have any king of test or ideas to get me a bit further that would be greatly appreciated
I’ve also try to draw an ip addr map :

if you can confirm or correct me that would be very kind be cause a get a bit lost betwenn bridge / devices / loopbacks ip etc
to be a bit more clear I can ping from herelink units ip in red but in or outside herelink units blue ip are not reachable
I would greatly appreciate also more details on difference between interface
bx-vxlan : guessing is the radio bridge
lmi40 : is unit on virtual lan between units
but what is vxlan for ?
thank’s for any tiny bit of info
ps someone said me to include @Michael_Oborne in my message so I’m doing it
thanks again and sorry for disturbing

1 Like

Your pc has to be in the 192.168.144.xxx subnet to ping your payload, that needs to be on the same 192.168.144.xxx subnet.

First attach your pc to the ground unit trough the ethernet adapter (make sure adapter is connected before you switch on the radio), and see if you can ping air unit at 192.168.144.10
If you can ping air unit from pc than try attach another adapter to the air unit and see if you can ping what is attached to it.

Make sure the adapters you got are recognized by air and ground unit.

1 Like

OK thanks !! sorry for that mistakes I was thinking the opposite
I tried
I modified in this way
PC connected to ground unit gets 192.168.144.20
fictive payload raspberry pi connected to air unit gets 192.168.144.25
when opening a shell on ground unit trough adb I can ping the payload

oga@oga-UX550VD:~$ adb shell
optimus:/ $ ping 192.168.144.10
PING 192.168.144.10 (192.168.144.10) 56(84) bytes of data.
64 bytes from 192.168.144.10: icmp_seq=1 ttl=64 time=31.9 ms
^C
--- 192.168.144.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 31.984/31.984/31.984/0.000 ms
optimus:/ $ ping 192.168.144.25                                                                         
PING 192.168.144.25 (192.168.144.25) 56(84) bytes of data.
64 bytes from 192.168.144.25: icmp_seq=1 ttl=64 time=35.9 ms
64 bytes from 192.168.144.25: icmp_seq=2 ttl=64 time=14.6 ms
^C
--- 192.168.144.25 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 14.630/25.291/35.953/10.662 ms
optimus:/ $

but from PC ground host even with right subnet

oga@oga-UX550VD:~$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:b0:34:bc:df  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enx34298f908abf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.144.20  netmask 255.255.255.0  broadcast 192.168.144.255
        inet6 fe80::751a:27f1:a137:490b  prefixlen 64  scopeid 0x20<link>
        ether 34:29:8f:90:8a:bf  txqueuelen 1000  (Ethernet)
        RX packets 19  bytes 5257 (5.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 140  bytes 11066 (11.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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  (Local Loopback)
        RX packets 43303  bytes 3902037 (3.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43303  bytes 3902037 (3.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.9.138  netmask 255.255.255.0  broadcast 192.168.9.255
        inet6 fe80::3b61:efab:a24:1368  prefixlen 64  scopeid 0x20<link>
        ether 34:41:5d:a8:8e:73  txqueuelen 1000  (Ethernet)
        RX packets 1506170  bytes 966500548 (966.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1066359  bytes 578018198 (578.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I can’t reach anything

oga@oga-UX550VD:~$ ping 192.168.144.10
PING 192.168.144.10 (192.168.144.10) 56(84) bytes of data.
From 192.168.144.20 icmp_seq=1 Destination Host Unreachable
From 192.168.144.20 icmp_seq=2 Destination Host Unreachable
From 192.168.144.20 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.144.10 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3065ms
pipe 3
oga@oga-UX550VD:~$ ping 192.168.144.11
PING 192.168.144.11 (192.168.144.11) 56(84) bytes of data.
^C
--- 192.168.144.11 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9203ms

oga@oga-UX550VD:~$ ping 192.168.144.25
PING 192.168.144.25 (192.168.144.25) 56(84) bytes of data.
From 192.168.144.20 icmp_seq=1 Destination Host Unreachable
From 192.168.144.20 icmp_seq=2 Destination Host Unreachable
From 192.168.144.20 icmp_seq=3 Destination Host Unreachable
From 192.168.144.20 icmp_seq=4 Destination Host Unreachable
From 192.168.144.20 icmp_seq=5 Destination Host Unreachable
From 192.168.144.20 icmp_seq=6 Destination Host Unreachable
^C
--- 192.168.144.25 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7149ms
pipe 4

Thank’s a lot for your help
it helped a lot to move forward ( just a small move but forward :wink: )

ps : looks to be more an issue of PC side … but I’m a bit lost :

oga@oga-UX550VD:~$ nmap -sP 192.168.144.0/24
Starting Nmap 7.80 ( https://nmap.org ) at 2021-09-23 15:36 CEST
Nmap scan report for oga-UX550VD (192.168.144.20)
Host is up (0.00024s latency).
Nmap done: 256 IP addresses (1 host up) scanned in 3.34 seconds

we tried on several different pc / Linx / windows and always same result :cry:
:thinking:

C:\Sdk\platform-tools>adb shell
optimus:/ $ clear
optimus:/ $ ifconfig
br-vxlan Link encap:Ethernet HWaddr b8:8d:f1:ff:ba:01
inet addr:192.168.144.11 Bcast:192.168.144.255 Mask:255.255.255.0
inet6 addr: fe80::ba8d:f1ff:feff:ba01/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 TX bytes:17650

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope: Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 TX bytes:0

eth0 Link encap:Ethernet HWaddr 00:e0:4c:36:01:cd
inet6 addr: fe80::2e0:4cff:fe36:1cd/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:144 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15291 TX bytes:6484

lmi40 Link encap:UNSPEC
inet addr:192.168.0.11 P-t-P:192.168.0.11 Mask:255.255.255.0
inet6 addr: fe80::2de7:7916:d010:3dae/64 Scope: Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1550 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2490 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 TX bytes:187964

vxlan1 Link encap:Ethernet HWaddr 1a:3d:eb:a2:80:68
inet6 addr: fe80::183d:ebff:fea2:8068/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 TX bytes:52222

wlan0 Link encap:Ethernet HWaddr 00:18:07:64:ba:01
inet addr:192.168.137.7 Bcast:192.168.137.255 Mask:255.255.255.0
inet6 addr: fe80::218:7ff:fe64:ba01/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:360 errors:0 dropped:0 overruns:0 frame:0
TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50214 TX bytes:36927

optimus:/ $ /bin/busybox brctl show
bridge name bridge id STP enabled interfaces
br-vxlan 8000.b88df1ffba01 no vxlan1
optimus:/ $

cant connect my pc to herelink

Can you help me?

we cant see bridge(interface) eth0

it looks you have a well detected eth0 on the ground unit a least
I dont know what about the air unit but if you follow this Herelink Ethernet - #3 by Michael_Oborne
you should see also a eth0 on air unit
if you fix you pc and your payload IP in the 192.168.144.xx subnet you should be able to ping your payload from ground unit and you should be able to ping your payload from PC also that’s here I have an issue

when trying to make an arp request from PC on GCS

arp -an 192.168.144.11
? (192.168.144.11) at 00:0e:c6:86:d8:67 [ether] on enx34298f908abf

but 00:0e:c6:86:d8:67 is HW adress of Eth0 of GCS not the bx-vxlan one

when trying to ping from payload (192.168.144.25) to PC side
(192.168.144.20) it dont get’s to the end neither ( not surprising)
but the arp cache is showing

pi@raspberrypi:~ $ arp -an
? (192.168.144.20) at <incomplete> on eth0
? (192.168.1.184) at 34:41:5d:a8:8e:73 [ether] on wlan0
? (192.168.144.11) at b8:8d:f1:ff:85:03 [ether] on eth0

where b8:8d:f1:ff:85:03 is mac addr of br-vxlan on herelink ground unit
it looks that missing some routing table input to get connecttion between br-vxlan and eth0 on ground unit …
any one can helps me a bit I’m getting stuck and my boss start to look at me with black eyes !!

@Michael_Oborne

firstly, arp is not a routable protocol, its part of the broadcast domain.

br-vxlan is a bridge interface, with multiple interfaces under it. so i dont know what your intent is, i think might need to go back to basics.

dear @Michael_Oborne
It is possible to guide my problem Herelink Ethernet - #53 by Michael_Oborne

I’m ok with you just doing ARP requests to know on what interface I’m falling
speaking of basics I’m still stuck when trying to ping 192.168.144.xx from PC side …
despite everything looks ok and ping is ok between remote and payload
My goal is just to be able to do a simple ping bitweeen pc host hooked to remote and pâyload connected to air unit
PC(192.168.144.20) >> remote (192.168.144.11) >> … >> air unit (192.168.144.10) >> payload (192.168.144.25)
and back

It works if I connect PC over Wifi Acces point of remote

that in my opinion mean that it’s missing a link between br-vxlan bridge and eth0 this link is set for wlan0 interface but not for eth0 one

I have the same problem
but i cant connect to Rasperypi ( airunit )

the new ethernet interface is not automatically added to the bridge( GCS)

are you using an external power supply for you air unit lan interface adapter ?
do you have follow recommmendation for compatible adapters ? as explained here Herelink Ethernet compatible hardware
is your air unit ( and remote ) up to date ?
How To Update Firmware - CubePilot
if yes to all theses questions I can’t help you more it should work try anoter units

Yes, everything is correct