BR LAN Issue …

So I am trying to set a bridge between my ONT and Router using br lan with the pi 5 I have eth 0 connected to the ONT and eth 1 to my router. Router sees the WAN IP from the ONT , but shows no internet access . I’ve set the br LAN protocol to unmanaged.

I’ve tested using my switch and pc , eth 0 is connected to my switch and eth 1 to my pc everything works here . Can anyone help ?

Why?

Then you don't have a bridge. What device do you intend to obtain an IP from the provider?

I’d like to see the contents of your /etc/config/network file, please, as well as the result of ifconfig.

And please confirm my understanding of your problem:

  • You’re still trying to use the Pi as a “transparent bridge doing SQM”.
  • You don’t want the Pi to actually hold a public IP address.
  • You don’t want the Pi to act as a router.
  • When you’re saying “Router sees WAN (…) but shows now internet access” you’re talking about a completely different router, not the Pi running OpenWRT.
2 Likes

No so currently I’m just trying to get the bridge up and running I don’t care regarding the sqm yet. I want the bridge to just take the ip provided by dhcp by the Fibre box that will connect to my WAN on my router .

Yes I am talking about a completely different router and I don’t want the pi to act as a router .

I think you're still completely misunderstanding the constructs here.

  • The bridge itself is an L2 device, and it does not take an address.
  • The L3 network interface (lan in this case) can have an address but you have set it with option proto 'none' which means that it is unmanaged -- no address.
    • if you want it to get an address via DHCP from your upstream Fibre box, you need to set the proto to dhcp instead.
  • In the case where the lan interface obtains an address from your Fibre box, it necessarily takes that address for itself. It does not have the ability to pass it to the next connected device (your other router).

Further, with your configuration as it is now, the router will (presumably) attempt to get an address from the upstream Fibre box via DHCP. This should succeed since you're currently not using the address from the ISP on the Pi, and the bridge, as I've said before, is just an expensive wire.

If you change the Pi to get an address via DHCP, the above (the router's ability to obtain an address) will probably fail (if the service only delivers a single DHCP lease/IPv4 address to each account; often the case for residential connections). Or it if succeeds, it would be another IPv4 address on the ISP's network that would not be related to some "passthrough" of the Pi's address to the ISP router.

It's also worth noting that if you set your Pi to get an address from the ISP network, you should make sure that it is assigned to a wan type interface... more specifically, you want to make sure that the firewall configuration with respect to that interface does not allow input to the Pi itself. This is the way that the OpenWrt wan firewall zone (to which the wan network interface is assigned)is configured by default. If you set the lan network interface to get an address via DHCP, because the lan is associated with the fully trusted lan firewall zone, the Pi would be completely exposed to the internet (this is a very bad thing).

So far, what you photographed is exactly what we expect to happen. You have neither a static address interface nor a DHCP interface, so there’s no IP to be had on eth0, eth1 or br-lan.

We now expect all L2 traffic coming in from the ONT on eth0 being passed out on eth1 to your router, because that’s what bridges do.

So now you should be at the stage of having a very expensive cable. That’s what psherman promised you in the last thread.

Could you please clarify: Does your other router fetch the IP address your ISP provides you with and is it able to communicate with the internet?

1 Like

Yes so my other router gets the WAN IP provided by my ISP but no internet access When connected to the pi .

Also I have tried setting the br lan to dhcp that doesn’t work also . Having same issue with both .

What happens if you restart both the ONT and the router?

If that doesn't fix the problem, is it solved by simply removing the Pi from the equation? (i.e. directly connecting the ONT to the router)

I have tried restarting both nothing works , I will try again now .

yes connecting straight to my router from the ONT works . but I know once my router gains access to internet through my PI I will 100% be able to apply sqm. I can prove this shortly after I get this part working .

does your ISP use a VLAN for connectivity to the upstream?

No isp doesn’t use vlan

For testing I have powered on a PlayStation wired straight to my router it shows internet access , IP obtained but DNS Failed .

On the Pi DNS and DHCP are disabled

What happens if you plug your Playstation directly into the ONT?

I’d put tcpdump on the Pi and go from there.

  1. Switch the Pi so it doesn’t sit between the ONT and your routers WAN port but at one of your routers LAN port.
  2. Change the lan interface from type “none” to type “dhcp”
  3. opkg update ; opkg install tcpdump
  4. Change the lan interface back from type “dhcp” to type “none”.
  5. Switch the wiring back so that the Pi sits between the ONT and your routers WAN port.

This will let you tcpdump -i eth0 and tcpdump -i eth1 to check traffic between the ONT and your router.

So my PlayStation works fine directly connected to the ONT

1 Like

Ok... try this in succession:

  • PS connected to ONT directly
  • Router connected to ONT (directly), PS connected to ONT
  • Pi connected between ONT and router, PS connected to ONT

Only problem with that is my ONT has 1 Ethernet port only

I understand that. The point is to adjust the topology each time (3 separate experiments):

1) ONT > Playstation
2) ONT > Router > Playstation
3) ONT > Pi > Router > Playstation

We can even run a 4th experiment:

4) ONT > Pi > Playstation

So 1 and 2 worked fine 3 and 4 failed

Try removing the ipv6 line from the br-lan definition. Then reboot all devices.