I have some strange wifi problem. I set up a wifi client, the problem is it isn't replying to LAN requests.
by inspecting with tcpdump I can see it's working and sending and receiving it's ntp messages, but almost any LAN request is ignored, the exception being it replies, with some delay to arp requests.
I have disabled the firewall...
And, if I reconnect an ethernet cable, all interfaces start working correctly as they should, including the wifi, then it's possible to ssh and everything. disconnect ethernet, and the problem is back. so basically now im stuck having to use an ethernet cable.
some more details about my setup:
the wifi interface isn't fully detected on boot, got a mac full of zeros,
but I could activate it manually with:
You don't typically need to define a gateway on the LAN interface; the LAN interface is the gateway. However, there are scenarios (e.g. "dumb AP" and similar) where having a gateway might be needed.
You have a wan firewall zone, but have removed the corresponding interfaces from the network configuration. This won't necessarily break anything, depending of course on your desired objective, but it is untidy and will cause unnecessary errors.
Your instance of OpenWRT has an active DHCP server operating on the LAN interface. Could it be conflicting with another DHCP server on your network, or is this one meant to be the only one?
The wireless interface in OpenWRT is disabled.
This is for using OpenWRT as an Access Point that clients can connect to; it's not for using OpenWRT as a wireless client. Are you sure you configured OpenWRT to be a wireless client?
I need the gateway, that's another router where the actual internet access is coming from. the other configs are mostly the defaults.
If I try to change disabled to 0, then wlan0 disappears,
and I only was able to recreate it with
iw phy0 interface add wlan0 type managed
the idea was to use this old router as a print server, which is all working, except that I can't use it in a wifi-only mode.
you're right that lan dhcp might be conflicting, I think it's a default too of openwrt , I will try to remove that and see if it helps.
Are you looking to establish the connection from OpenWRT to the primary router via an Ethernet cable, or via Wi-Fi? And, in turn, are you looking for OpenWRT to provide Wi-Fi connectivity to other devices, e.g. your printer?
If you want OpenWRT to connect to your main router via Wi-Fi then you'll need to reconfigure the wireless settings to behave as a client, not as an AP. This is possibly easiest to accomplish using LuCI (the web-based configuration).
Just spotted this. 19.07 is quite old. You may find upgrading to the current version might be beneficial. At the very least, there'll be bug fixes and security patches included.
Blockquote
Are you looking to establish the connection from OpenWRT to the primary router via an Ethernet cable, or via Wi-Fi? And, in turn, are you looking for OpenWRT to provide Wi-Fi connectivity to other devices, e.g. your printer?
No, I would like to connect to the primary router via wifi. Then p910nd is there on the openwrt router and should be available to the other lan computers. no need to share the connection.
I am now trying to reconfigure as client in the wireless settings. I have also disabled dnsmasq and the odhcpd service, but it didnt change anything.
p910nd is a print server program, it opens port 9100 and forwards traffic to the printer. So the openwrt router has to be available on lan to the clients on that port.
With these new configs the router starts the interfaces correctly, however, as before, as soon as I unplug ethernet, wlan becomes unreachable by ping, then if I plug ethernet again, wlan is back.
You've got two separate interfaces in the same subnet. You'd be better off bridging them.
First, try removing this section:
Then amend this line: option network 'wlan'
to:
option network 'lan'
Caveat: I haven't touched 19.07 in a long time. It's possible that some of this advice may not be applicable to 19.07, but would be fine on 22.03.5, for example.
that's ok, what matters is you're trying to help.
In fact, that change you propose goes back to how it was before. I have added this interface now, thinking it would help, but so far no change.
maybe it's a driver problem ? or mac address related... to me it's strange really.
I have a spare device buried somewhere, which I know can run 19.07. If upgrading to 22.03.5 is a non-starter then I might be able to fish it out and fiddle with the configuration directly rather than offering barely-remembered speculation.
b43 support for BCMA based wireless chipsets and BCM4321 is very, very, very limited, so there isn't much to be expected here (and the device being below minimum system requirements (4/32) and accordingly on an old/ EOL/ insecure version of OpenWrt doesn't help either).
Thanks everyone for the ideas, this is a forum where people actually try to help you, some other forums are like a desert. The only part I didn't like that much is the forum forces you to use updated browsers, some people, read: me, like to use older devices and browsers, so I had to use my woman's windows pc, eeew. have a good day all.