New Pi 5.24 SD Card Image

I was just doing some testing of the new ‘pi’ SD card (purchased at the Wakefield show) and noticed that it gave a ‘Warning from Netsurf’ on start up saying that ‘No domain name servers are configured, so only browsing local files will be possible. Use ’Configure’ to set your name servers.’. Testing before this, I was using a wired network connection, which was fine.

My Pi is connected (using DHCP) via an Asus WL-330N wireless bridge to my network.

It is not simple to set the name server as you have to set the server, start up, accept the error message and then unset the server. Start ups then give no error on running Netsurf.

Nearly ditto – also testing new Pi and new SD. Got the same message about domain servers from NetSurf.
Ifconfig a gave an ip address of 169.254…. instead of the usual 192.168…
After pressing the RJ45 plug in firmly the problem went away :)

That’s odd. DHCP should handle all of this automatically (and I can confirm that it works – over Ethernet – on both of my Pis with 5.24). Is this behaviour different from RC15?

Is this behaviour different from RC15?

I don’t think so, except that RC15 was beta and this is stable.

Has DHCPExecute set the DNS servers passed via DHCP? If not, does it set them if you manually run DHCPExecute again?

I do not know what has been passed via DHCP. The status page shows ‘Gateway: Unset’.

My normal work around is to set the gateway to 192.168.1.1 (the IP address of my router), restart, accept the error ‘Machine has not completed successfully Route add net default gateway 192.168.1.1 Network is unreachable.’ [it cannot cope with the gateway being set manually and using DHCP], press cancel, reset the gateway to blank, restart. That no longer works.

DHCPExecute needs a parameter on my machine (Raspberry Pi model 3B+) and just gives a ‘Syntax:’ message.

DHCPExecute wants the interface name, which will usually be ej0.

DHCPExecute ej0 is accepted but the gateway still shows ‘unset’ and Netsurf cannot resolve a site name.

It sounds like you’re suffering from a long known about issue with DHCPExecute and the only workaround is to use a fixed IP.

That said, we did manage to get the TP-LINK WiFi nano router working on the pi-top, which I seem to recall needed configuring in a specific way.

It sounds like you’re suffering from a long known about issue with DHCPExecute and the only workaround is to use a fixed IP.

Yes. Or just use wired networking. Many thanks.