Rpi4 < $(community_build)

Thought I'd just add a comment on getting this community build working with the Eir's (Irish ISP) FTTH setup, since it might help other people. There's a few comments earlier on about how the Pi doesn't have the switch fabric, but they seemed to be in the context of LAN connections, not WAN connections. Eir require packets to be tagged on VLAN 10, and their provided VDSL2 modem is also able to take the ethernet feed from the optical network terminal, and handles the VLAN tagging.

Assuming the WAN interface is eth1 (say a USB dongle), then the following steps worked for me:

  • Go to Network > Interfaces > Devices
  • Add a new device configuration
  • Set the type to 802.1q
  • Alias it on top of eth1
  • Set the VLAN ID to 10
  • Save the new device
  • Go to Network > Interfaces > Interfaces
  • Add a new interface (or edit your existing one)
  • Set the type to DHCP client (no need for PPPoE, unlike their DSL offering)
  • Use the eth1.10 device (Software VLAN)
  • Make sure it's in the WAN firewall zone
  • Save
  • Repeat new interface steps, but set DHCPv6 client as the type (Eir offer IPv6)

The status of the interfaces should update to show IPs being assigned.

Without the VLAN 10 stuff, and using the base eth1 device, IPs don't get assigned.

Might help someone else with a different ISP that uses the same approach. How you find out your ISP needs VLAN tagging - no idea; I discovered that Eir do this by searching the 'net.

Edit:
Eir headend -> fiber distribution on pole -> termination point in house -> ONT (Huawei of some sort) -> Ethernet cable -> Pi USB dongle (WAN/WAN6) -> Pi (OpenWRT) -> Pi onboard Ethernet (LAN) -> Ubiquiti switch -> home network

2 Likes