Routed ethernet + wifi with a Raspberry Pi 4

Installing and Using OpenWrt
1

Hi Guys,

I have exactly the same issue as described before.
Raspberry Pi 4 - eth0 is the ISP router, eth1 TP LINK usb ethernet dongle and I want to use wifi as well.
When I reboot the Pi, I get " Error: Unknown error (DEVICE_CLAIM_FAILED)" failure message in Luci.
issue

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd2d:78db:65fe::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'lanka'
	option proto 'static'
	option device 'eth1'
	option ipaddr '192.168.3.1'
	option netmask '255.255.255.0'
	option type 'bridge'
	option igmp_snooping '1'
	list dns '8.8.8.8'

config interface 'bridgelan'
	option proto 'dhcp'
	option device 'br-lan'

config interface 'wifilan'
	option proto 'static'
	option device 'phy0-ap0'
	option ipaddr '192.168.4.1'
	option netmask '255.255.255.0'
	option type 'bridge'
	option igmp_snooping '1'
	list dns '8.8.8.8'

When I restart the wireless service, the issue is gone and everything is good.

If you have any suggestions, please let me know. Appreciate it. Thanks.

2

Why is your wan bridged ?

3

Thanks for your quick reply.
I modified a bit, but now no Wifi internet - network connection work, but no internet. Wired network and internet work. The original failure is still there.

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd1d:88db:56fe::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'lanka'
	option proto 'static'
	option device 'eth1'
	option ipaddr '192.168.3.1'
	option netmask '255.255.255.0'
	option type 'bridge'
	option igmp_snooping '1'
	list dns '8.8.8.8'

config interface 'bridgelan'
	option proto 'dhcp'
	option device 'eth0'
	
config interface 'wifi'
	option proto 'static'
	option device 'phy0-ap0'
	option ipaddr '192.168.3.5'
	option netmask '255.255.255.0'
	list dns '8.8.8.8'
4

There's a lot wrong with this configuration -- I would suggest that you reset to defaults and start fresh. We can help you with that, but it would be best if you could describe your goals (rather than simply saying you've experienced the same issue described).

Beyond that, I'd like to move your issue to a new topic because you've bumped a 2 year old thread which is very likely different than your issue once we get into the specifics. Once I know your goal, I'll be able to split this with an appropriate title for the new thread.

5

Okay, sorry for confusing you, and thanks for your patience and willingness to help.

I just would like to use my Pi as a wired and wireless router. My Pi connects to a router (192.168.1.1) via eth0 onboard Ethernet. This is my WAN connection.

I would like to set up a LAN connection to access the internet, and the hosts can see each other via the Pi.
The current configuration is:
eth0: connected to the 192.168.1.1 router.
eth1: USB Ethernet dongle connected to my desktop PC.
Wireless: I am using the Pi's Wi-Fi because the distance is small; it is just a small room.
The client on the eth0 to get an IP if I use my IP as a traveling router.
On eth1, I would like to use this range: 192.168.3.1-192.168.3.xx.
On wireless connection, I wanted to use 192.168.4.1-192.168.4.xx range. But if I could use 192.168.3.1-192.168.3.xx range for both interfaces, which is also good. My only goals are to see the host each other and have internet connections.

Currently, on the eht1 USB dongle, the Ethernet network works well.
The issues come when I reboot my Pi and the wireless connection cannot get IP.

First, I used LUCI's Wireless settings and created a Wifi. After that, I created a WiFi interface and assigned the previously created WiFi interface. After rebooting, I saw the failure message ( Error: Unknown error (DEVICE_CLAIM_FAILED). The SSID of the wireless network is visible, my wireless devices are trying to get IP, without success.
But when I manually restart the system in LUCI, the wireless network is up and running.

I need a couple of days to check with a fresh config.

Thank you again,

6

This sounds like a near-default type configuration. You should start over from scratch. You'll need to ensure that the eth1 usb dongle has the driver package installed -- you can do that a few different ways -- let us know if you need help with that part of the process.

This is the built-in ethernet. No problem here.... you just need to reassign the ethernet port to be used as a wan.

It is most straightforward to use the same subnet for both wifi and ethernet devices. It's absolutely possible to use different networks, but unless you have a specific reason to do so, I'd recommend that you use the same.

Your config has a large number of problems. That's why you should start from scratch.

If you need specific help, post the default configuration from your pi and we can show you how to make the modifications required -- it's really quite simple.

7

If you search forum for raspberry pi 4 you’ll find a bunch of posts from me doing all kinds of little projects with openwrt.

Basically reassign the lan to wan, use the physical console to opkg update && opkg install the correct kmod

Reassign eth0 back to lan and eth1 to wan and reboot.

Enable WiFi and done.

Please note that the onboard wifi is awful

8

Thanks for your help; I will try these steps soon, but I need a few days.
I will get back to you with what I found.

9

Hi All,

small update only. I grab another Pi (4 with 8Gb, the previous was Pi 4 1GB) and started from scratch, installed the USB dongle driver only, but this issue was seen on that Pi as well. After manually restarted the wireless, this issue is gone. I also tried to use eth0 as wan and eth1 as local connection. No change. Used different Pis, different PSUs

I will try one more time and make some notes, what I did. My plan is to use eth0 as WAN and don't connect USB Ethernet dongle.

Is there any command, which might help to find where the problems occur? With dmesg everythings looks fine or acceptable:

[    5.331714] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.340759] usbcore: registered new interface driver brcmfmac
[    5.346616] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
[    5.358283] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin
[    5.371030] kmodloader: done loading kernel modules from /etc/modules.d/*
[    5.448301] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
[    5.514865] r8152 2-1:1.0: load rtl8153a-4 v2 02/07/20 successfully
[    5.530304] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jul 29 2022 02:15:20 version 7.45.250 (70e9766 CY) FWID 01-e53e306b
[    5.559093] r8152 2-1:1.0 eth1: v1.12.13
[    6.617201] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
[    6.625779] bcmgenet fd580000.ethernet eth0: Link is Down
[    6.874267] brcmfmac mmc1:0001:1 phy0-ap0: renamed from wlan0
[    7.065582] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[    7.609450] hrtimer: interrupt took 14166 ns
[    9.448491] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[    9.455563] r8152 2-1:1.0 eth1: carrier on
[   10.807839] bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   10.816266] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
10

Okay,
Flash the sd card with the latest raspberry os and boot. go through the config pages and then wait a few minutes for it to fetch the time and update package list. Install updates; this will update the bootloader. and reboot for good measure and then shutdown.

Then ( you can use the same card) go here and choose Customize installed packages and/or first boot script (your posts are confusing you say you do want to use the USB ethernet then you say you don't) if you want to use the USB dongle add the driver at the end of the script, then request build. Might take a few minutes if server is busy.

When it is done click on FACTORY (SQUASHFS) to download the image. Flash it to sd card. The 1GB pi is fine; no need to waste the 8GB.

Boot the Pi and come back here and I'll get you through the rest. Do not try to config anything. Just come back here.
Also; do not plug in your USB ethernet dongle. Not yet.

11

Thanks for your help.

I followed your steps, now the Pi is booted up on SD Card, using the custom openWRT image, I didn't try config anything, USB Ethernet dongle not connected.

(Before I did this a made another check. Previously I used USB stick to for booting, and now I boot up from SD card. I added the USB Ethernet successfully, the wired network was up and running. But when I set the wireless, the issue popped up again.)

12

Well, I guess if we cannot get it working, you can start over, again, and not deviate from my instructions.

Show me a screenshot of Network in LuCI; just like you did in your OP.

13

Sorry for the misunderstanding, but I didn't deviate from your instructions. Before your steps, I made another test to make sure, that it isn't related to the USB pendrive/stick, which is my boot device (not the USB Ethernet dongle). When I could see the issue using microSD card too, I could say, that is not related to the boot device. Then Raspbian image, update, remove from the Pi, reimage with the openwrt and boot. All in all, the Pi is in that state now, what you asked.

I can send now the /etc/config/network file only, you can see that this is the original config. I can send the LUCI only a couple of days later, if the network file isn't acceptable.

1707318593711

Thank you.

14

I'm sorry:
I meant the interfaces with the red and green just below where you typed

But, let's look at what you have provided:
eth0 is in the lan interface with a static address when you say you want it in the wan interface with DHCP.

So, if you plug eth0 in the modem it shuts everything down because all the addresses are wrong.

15

Okay, thanks. Let me try from another view.

Well, please take a look at this /etc/config/network. This is the fresh config, when only the required things installed AND the failure appears. I have internet connection, but after reboot I have to restart the Wifi in Luci manually and the Unknown error is gone until the next reboot.

May I ask your kind help to check for bugs or typos, which can cause the Unknown error?

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd0c:f536:136e::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'wan'
	option proto 'dhcp'
	option device 'eth0'

config interface 'lan'
	option proto 'static'
	option device 'eth1'
	option ipaddr '192.168.5.1'
	option netmask '255.255.255.0'
	option type 'bridge'

config interface 'wifi'
	option proto 'static'
	option device 'phy0-ap0'
	option ipaddr '192.168.6.1'
	option netmask '255.255.0.0'

Another question. I have LAN (192.168.5.1) and Wifi (192.168.6.1). What should I do to have only one range (192.168.5.x) for both, wired and wireless connections? Should I just delete the Wifi part AND modify the LAN part by adding option device 'phy0-ap0' under option device 'eth1?

Thanks for your feedback and patient.

16

eth0 cannot be in the wan and lan.

When you set up the pi as I instructed the radio and eth0 are automatically bridged. After that we set up the lan and then it is trivial to move eth0 to wan and then add the dongle (eth1) to lan (br-lan).

No, the easiest thing to do at this point is to unplug the dongle and run firstboot and then reboot.

This should set up the bridge for us and we can config from there and then, after we get the lan set up create the wan interface, move eth0 into it and add the dongle (eth1) to the lan (br-lan).

:spiral_notepad: We are not going to set this up in CLI; we are going to do the setup in LuCI.

17

Okay, thanks for the detailed explanation, I will try again.
I can give status update not earlier then next Tuesday.

Thanks again all of your help and patient.

18

Okay, np. :ok_hand: :+1:

20

Hi, finally good news. Based on your help I understood what my problem is: I had to bridge the eth1 and the wifi...so simple now. :slight_smile:

Do you have a "buy me a coffee" account?

Thanks for your patient and kind help.

1 Like
21