How do I get WiFi working?

I had my Raspberry Pi 3B plugged into my Netgear Wifi extender (plugs into wall, has two antenna, and has an Ethernet port) via Ethernet cable. And was able to get online perfectly. Downloaded (or thought I did) the latest NetSurf browser for RiscOS. All was good… last night.

Tonight, I tried getting online and all I get is “Couldn’t resolve Host Name”, when I try to go to a web site. Nothing I’ve tried seems to make it work.

What are the EXACT Network settings I should have configured and saved for this setup? Is RiscOS prone to going wonky (forgetting or ignoring), conconcerning network settings or functionality?

You don’t say what build of RISC OS, or which distribution you’re running, which makes it a bit tricky to answer your question.

If you’re having network trouble, I recommend trying RISC OS Direct http://www.riscosdev.com/direct which contains new auto-config for networking on Pi, which can occur within the desktop. Additionally, it has programs like NetSurf et al ready-to-go.

At the very least, it’ll give you another point of reference – if it also fails, then it suggests something either fundamental or hardware related.

How do I get WiFi working?

You need a Raspberry Pi WiFi Hat → WiFi Hat or perhaps one of these tp-link TL-WR802N . An alternative to the tp-link is a Vonets device, see this thread

Native support for WiFi is on the To Do list.

Tonight, I tried getting online and all I get is “Couldn’t resolve Host Name”,

I, too, get this sometimes. My (horrible) solution is to set the gatway manually with DHCP selected and after the error ‘.. gateway … file exists’ reset the gateway to blank.

I recommend trying RISC OS Direct http://www.riscosdev.com/direct...

Do you have a zip file for the HardDisk 4 files only? (For those of us who gave up using troublesome partitioned SD cards some time ago.)

You need a Raspberry Pi WiFi Hat

On my reading of the original post, the Netgear range extender, which /is/ WiFi), is connected to the Pi by Ethernet cable. If I’m right, then internet connection won’t need a WiFi HAT, and should be very reliable.

What are the EXACT Network settings I should have configured and saved for this setup?

Jared, if you’re still struggling I can send a ‘how to’ sheet which reproduces my own settings.

George… I’d appreciate that “how to” sheet very much. :-D

Jared: email me at george d*t greenfieldbt at btinternet d*t com and I’ll attach it to the reply.

Ok, just sent you an Email…

Very strange… I reset my RiscOS Pi to default (Reset the firmware [whatever] via !Boot configuration option). Now, when I look at Network status, it shows a bunch of numbers (IP, Gateway, etc.) for about a minute or two…. and then it suddenly all changes to “Unset”, like it suddenly forgot everything! It’s set to DHCP, so why is that happening? I’d show pictures of what I’m seeing, but don’t know how to (if even possible) on the forums.

It is possible (one explanation) the lease time for your DHCP details is very short. AFAIK, RISC OS DHCP module doesn’t auto-renew DHCP details once the lease time expires.

But, there’s good news… The extra software in RISC OS Direct that I mentioned in the first reply, deals with this, and auto-renews DHCP details if they’re ever lost, without requiring a reboot. It is also set up automatically, so you literally just need to write the card with the RISC OS Direct image, and try it. No config necessary.

Again, I can’t promise that it’ll fix your problems, but please try it?

AFAIK, RISC OS DHCP module doesn’t auto-renew DHCP details once the lease time expires.

Of course it does. As long as the T1/T2 times from the server are sane, you can see when the next rebind or renew operation will be with

*DHCPInfo

Another possibility, if it’s a busy network or not set up quite right, is that there’s been an IP address clash. RISC OS will step back in that case in a sulk, though

*InetInfo

Another possibility, if it’s a busy network or not set up quite right, is that there’s been an IP address clash. RISC OS will step back in that case in a sulk, though

For info – experience of a multi-segment enterprise network suggests a prime candidate for generating IP clashes is any network device with a logo resembling a bitten apple.
I have considered dropping all such ignorant devices into a distinct VLAN so they can be kings of their own tiny little world. QoS the little gits into submission too…

… their own tiny little world.

Er, pots and kettles? :-)

Er, pots and kettles? :-)

Nah, Fixed connection stuff connects with an Apple OS only exists because I had my arm twisted and the relevant party has left. Treating it as a a pariah device is on the todo list – the problem is it’s a long list. Currently listed as “on sufferance, to be sorted”
To take you small reference to its obvious destination: The RPi devices (a handful) are also marked for segregation – mostly because the Rasbian OS is an unknown as far as AV is concerned.

Ok, I just discovered it’s the Netgear Wifi Extender that’s the fault (connecting to our Asus Wifi Router directly gave me instant, perfect Internet access). Question now is, do I do a factory reset or look at something in the firmware or…?

For a factory reset their is usally a small pin hole switcth that needs to be pressed for a certain length of time.

I’m connecting my ARM6x through a wifi extender, and at a private members club I have a few Raspberry Pis ruuning RISC OS through wifi extenders.

I found that you option you want is access point.

I found that you option you want is access point.

Should that be ‘I found that the option you want is access point’?