USB to ethernet Dongle as LAN port

[Switzerg95]

I added a usb ethernet interface and created a bridge with that interface and the default lan veth, on the host machine running the container.

client behind usb dongle can reach internet, gets a dhcp address from the openwrt docker container, but it cant talk to anything else thats on some of my mesh nodes, but any mesh node LAN members (same l2) can reach each other fine.

Is there a different suggestion on how we could make this work?

The issue being that for some reason nothing on the LAN side of the clients can reach the location engine.

Wondering if thats something to do with the way I created the bridge. Is there a particular way to add the USB interface into OPENWRT? Maybe thats why its not working quite right?

Do we pass in through the LAN_IF / WAN_IF? Or do we pass in as USB device? Into the compose file.

[AlbrechtL]

Can you post your docker compose file, please? Even, it would be very nice if you add your OpenWrt IP configuration via console uci show network.

[Switzerg95]

I actually wanted to change the configuration and instead use the second ethernet port as the LAN port for the network.

So i'll use the USB to access the host.

Anyway, here is the docker compose file.

services:
openwrt:
container_name: openwrt
image: albrechtloh/openwrt-docker:latest # for latest OpenWrt stable version
#image: albrechtloh/openwrt-docker:openwrt-2410-snapshot # for latest OpenWrt 24.10 snapshot version
#image: albrechtloh/openwrt-docker:openwrt-master-snapshot # for latest OpenWrt master version
#image: openwrt-docker
build:
context: .
dockerfile: Dockerfile
args:
OPENWRT_VERSION: "23.05.4"
#OPENWRT_VERSION: "master"

environment:
  # Define which physical or virtual interfaces shall be attach direct to OpenWrt
  # If WAN_IF/LAN_IF is missing then "host" mode is selected
  # -
  #WAN_IF: "host" # Usage of container host Ethernet connection as WAN. WARNING: Bad performace because of user space Ethernet implementation.
  #WAN_IF: "none" # No WAN interface defined. This is useful if OpenWrt WAN acts a USB Wi-Fi client or as USB cellular modem
  #WAN_IF: "enx00e04c0407a6" # Use this option to define a specific physical Ethernet interface
  WAN_IF: "enp2s0"
  #LAN_IF: "host" # Usage of container host Ethernet connection as LAN. WARNING: Bad performace because of user space Ethernet implementation.
  #LAN_IF: "veth" # veth pair between OpenWrt and host system. The host Ethernet interface IP is fixed to 172.31.1.2/24
  #LAN_IF: "veth,nofixedip" # veth pair between OpenWrt and host system. No host Ethernet interface configuration
  LAN_IF: "enp1s0" # Use this option to define a specific physical Ethernet interface

  # Make LuCI OpenWrt web interface accessible via host LAN
  FORWARD_LUCI: "true" 

  # USB passthrough
  # Format <vendorID>:<productID> like 'lsusb' is given
  # Currently only two USB devices are supported
  #USB_1: "0b95:1790"
  USB_2: "148f:5372"

  # Define number of VM CPUs
  # If unset -> 1
  CPU_COUNT: 2

  # Define amount of VM memory in MB
  # If unset -> 256
  RAM_COUNT: 256

  #DEBUG: "y"

ports:
  # Port 8006 is console tty web VNC
  - 8006:8006
  # Port 8000 is available only when Docker WAN network is used.
  # Use script /usr/bin/fw_wan_open_http to open the port. Works only if WAN_IF=host
  #- 8000:8000
  # SSH
  # Use script /usr/bin/fw_wan_open_ssh to open the port. Works only if WAN_IF=host
  #- 8022:8022
stop_grace_period: 2m
restart: on-failure

# The following settings are mandatory to run the container
devices:
  - /dev/kvm
device_cgroup_rules:
  - 'c *:* rwm'
cap_add:
  - NET_ADMIN
pid: "host"
privileged: true
volumes:
  - /dev:/dev/
  - data:/storage/

volumes:
data:

[Switzerg95]

network.loopback=interface
network.loopback.device='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fd5e:0d3b:d693::/48'
network.@device[0]=device
network.@device[0].name='br-lan'
network.@device[0].type='bridge'
network.@device[0].ports='bat0' 'eth0'
network.lan=interface
network.lan.device='br-lan'
network.lan.proto='static'
network.lan.ipaddr='172.31.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.lan.dns='8.8.8.8'
network.wan=interface
network.wan.device='eth1'
network.wan.proto='dhcp'
network.wan6=interface
network.wan6.device='eth1'
network.wan6.proto='dhcpv6'
network.wan6.disabled='1'
network.wan6.reqaddress='try'
network.wan6.reqprefix='auto'
network.bat0=interface
network.bat0.proto='batadv'
network.bat0.routing_algo='BATMAN_V'
network.bat0.aggregated_ogms='1'
network.bat0.gw_mode='server'
network.bat0.log_level='0'
network.bat0.orig_interval='1000'
network.bat0.bridge_loop_avoidance='1'
network.bat0.network_coding='0'
network.bat0.hop_penalty='30'
network.bat0.isolation_mark='0x00000000/0x00000000'
network.nwi_mesh0=interface
network.nwi_mesh0.mtu='2304'
network.nwi_mesh0.proto='batadv_hardif'
network.nwi_mesh0.master='bat0'

[AlbrechtL]

Thanks for sharing.

I can't find an openwrt-docker related issue. I would guess an issue with B.A.T.M.A.N.. But I don't personally have experience with it.

Did you already ask the OpenWrt community at https://forum.openwrt.org/?

[Switzerg95]

I did post there, but didnt get any replies.

[AlbrechtL]

Can you post the link here, please?