Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bridge LAN doesnt work on omr vm #3768

Open
max93776 opened this issue Jan 16, 2025 · 4 comments
Open

Bridge LAN doesnt work on omr vm #3768

max93776 opened this issue Jan 16, 2025 · 4 comments
Labels
help wanted

Comments

@max93776
Copy link

Expected Behavior

I want to use 2 ethernet ports (eth0, eth1) bridged to access internet.

Current Behavior

I'm runnning OMR as a virtual machine in TrueNASScale and passthrought the NICs. I have eth0 and eth1 bridged on lan firewall zone and dhcp server enabled on eth0. Eth0 is working fine and if I plug in the cable in eth1 I get a IP from DHCP but no internet connection. There is also phy0-ap bridged with wifi but I already tested with it turned off. Any idea whats the problem here?

Specifications

  • OpenMPTCProuter version: v0.61-6.6 r0
  • OpenMPTCProuter VPS version: ?
  • OpenMPTCProuter VPS provider: openstack
  • OpenMPTCProuter platform: x86_64

My setup:
image
image
If I plug in my laptop in eth1:

root@OpenMPTCProuter:~# logread -f
Jan 16 12:17:48 OpenMPTCProuter daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.100.130 00:e0:4c:c6:94:ba
Jan 16 12:17:48 OpenMPTCProuter daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.100.130 00:e0:4c:c6:94:ba ***-Laptop

From both sides ips are not pingabel, tried already with different laptops. Wi-fi is working.
@Ysurac
Copy link
Owner

Ysurac commented Jan 16, 2025

What is the result of ip a and ip r via SSH on the router ? Same on laptop (or equivalent command if not Linux)

@max93776
Copy link
Author

Router:

root@OpenMPTCProuter:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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 proto kernel_lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP group default qlen 1000
    link/ether 00:a0:98:73:f7:46 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP group default qlen 1000
    link/ether 00:a0:98:4e:de:61 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:a0:98:5f:5b:a5 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:a0:98:66:6d:31 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.169/24 brd 192.168.10.255 scope global eth3
       valid_lft forever preferred_lft forever
6: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:a0:98:70:bb:9c brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.12/24 brd 192.168.11.255 scope global eth4
       valid_lft forever preferred_lft forever
7: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd :: permaddr aa19:5ab9:a68b::
8: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
9: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
    link/gre 0.0.0.0 brd 0.0.0.0
10: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN group default qlen 1000
    link/gre6 :: brd :: permaddr daac:dc80:e1dc::
13: teql0: <NOARP> mtu 1500 qdisc noop state DOWN group default qlen 100
    link/void
14: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:a0:98:73:f7:46 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fe80::2a0:98ff:fe73:f746/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
20: phy0-ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 2000
    link/ether e8:c8:29:76:c6:f9 brd ff:ff:ff:ff:ff:ff
21: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/none
    inet 10.255.252.3/24 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::126:3e80:a5fd:ee9c/64 scope link stable-privacy proto kernel_ll
       valid_lft forever preferred_lft forever
root@OpenMPTCProuter:~# ip r
default via 10.255.252.1 dev tun0
default via 192.168.11.2 dev eth4 metric 1
default via 192.168.10.2 dev eth3 metric 7
default via 192.168.11.2 dev eth4 metric 8
default via 192.168.10.2 dev eth3 metric 999
default via 10.255.252.1 dev tun0 metric 1500
10.255.252.0/24 dev tun0 proto kernel scope link src 10.255.252.3
10.255.252.0/24 dev tun0 scope link metric 1500
10.255.252.1 via 10.255.252.1 dev tun0
127.0.0.0/8 dev lo proto static scope link metric 5
192.168.10.0/24 dev eth3 scope link metric 7
192.168.11.0/24 dev eth4 scope link metric 8
212.********** via 192.168.11.2 dev eth4 metric 1
212.********** via 192.168.10.2 dev eth3 metric 999

Laptop:

>ipconfig

Windows-IP-Konfiguration


Ethernet-Adapter Ethernet 2:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:

Ethernet-Adapter Ethernet 3:

   Verbindungsspezifisches DNS-Suffix: lan
   Verbindungslokale IPv6-Adresse  . : fe80::f90b:91c8:940a:3779%19
   IPv4-Adresse  . . . . . . . . . . : 192.168.100.130
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.100.1

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:

Drahtlos-LAN-Adapter WLAN:

   Verbindungsspezifisches DNS-Suffix: combox.de
   Verbindungslokale IPv6-Adresse  . : fe80::96e7:5be1:7b:edad%5
   IPv4-Adresse  . . . . . . . . . . : 192.168.52.146
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.52.8
>route PRINT
===========================================================================
Schnittstellenliste
  6...00 ff 25 44 01 e8 ......Sophos TAP Adapter
 12...48 2a e3 b3 10 3d ......Intel(R) Ethernet Connection (13) I219-V
 19...00 e0 4c c6 94 ba ......Realtek USB GbE Family Controller #2
  9...8c 55 4a ca cf 61 ......Microsoft Wi-Fi Direct Virtual Adapter
 21...8e 55 4a ca cf 60 ......Microsoft Wi-Fi Direct Virtual Adapter #2
  5...8c 55 4a ca cf 60 ......Intel(R) Wi-Fi 6 AX201 160MHz
  1...........................Software Loopback Interface 1
===========================================================================

IPv4-Routentabelle
===========================================================================
Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0    192.168.100.1  192.168.100.130     25
        127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    331
        127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    331
  127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
    192.168.100.0    255.255.255.0   Auf Verbindung   192.168.100.130    281
  192.168.100.130  255.255.255.255   Auf Verbindung   192.168.100.130    281
  192.168.100.255  255.255.255.255   Auf Verbindung   192.168.100.130    281
        224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    331
        224.0.0.0        240.0.0.0   Auf Verbindung   192.168.100.130    281
  255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
  255.255.255.255  255.255.255.255   Auf Verbindung   192.168.100.130    281
===========================================================================
Ständige Routen:
  Netzwerkadresse          Netzmaske  Gatewayadresse  Metrik
          0.0.0.0          0.0.0.0      192.168.1.1  Standard
===========================================================================

IPv6-Routentabelle
===========================================================================
Aktive Routen:
 If Metrik Netzwerkziel             Gateway
  1    331 ::1/128                  Auf Verbindung
 19    281 fe80::/64                Auf Verbindung
 19    281 fe80::f90b:91c8:940a:3779/128
                                    Auf Verbindung
  1    331 ff00::/8                 Auf Verbindung
 19    281 ff00::/8                 Auf Verbindung
===========================================================================
Ständige Routen:
  Keine

note: I turned off wlan on my laptop for route PRINT because its better to read

if I use the working eth0, the routes in OMR and my laptop stay the same.

Maybe it has something to do with TrueNASscale?

@max93776
Copy link
Author

Hi!! Have you ever had similar experiences with such an error? If not then I'll close this issue :)

@Ysurac
Copy link
Owner

Ysurac commented Jan 22, 2025

No, I use bridge on one test platform without issues.
I would look in uci show network, uci show firewall and uci show dhcp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ysurac @max93776