SOLVED: No internet connection on X1000 using Prism2

[SteveH]

Following a power outage earlier this week which led to my router being re-booted, I can no longer get an Internet connection from my X1000 via wifi using the Prism2.device, which had worked fine for several years. The settings in SYS:Prefs/Internet seem fine and nothing has changed in ENV-ARCHIVE/SYS/Wireless.prefs
I am also unable to connect using Ethernet if I switch to the pa6t_eth.device
Can anyone suggest what I need to do to re-establish my connection?

[NinjaCyborg]

Power surges can fry routers, are you sure it's working OK?

[TribbleSmasher]

Maybe the router lost its settings or its firmware.

[SteveH]

Thanks for the suggestions, but I have multiple other wifi devices which have all reconnected without problem following the re-boot, so I am certain it is not the router.
[edit: It wasn't a power surge, as such - my fan oven heating element failed, tripping the main house fuse].

[nbache]

Is it possible that the other devices all use DHCP, but the Amiga had a fixed IP address, which for some reason is now taken by another device?

Best regards,

Niels

[SteveH]

Hi Niels,
I have tried both DHCP and assigning an (otherwise unused) static IP address to the Amiga, with no success.

[NinjaCyborg]

Can you share all the relevant config files?

Also, if you run C:WirelessManager or wpa_supplicant, whichever it's called in your version, in VERBOSE mode it will become clear.

[SteveH]

Hi,
I've attached the log from running WirelessManager in verbose mode, as suggested.
In wireless.prefs (Prefs/Env-Archive/Sys), the SSID of my router and its passkey are listed.
SYS:Prefs/Internet (v53.3) has prism2.device as the driver, set for DHCP and the hostname as the IP address of my router with packet type set to Default; for Routes, it has the IP of my router set as the default gateway address; for Hosts it has localhost set to 127.0.0.1; DNS servers are 8.8.8.8 and the IP of my router; and I haven't edited the Services or Servers section.
When I view my router dashboard, it shows the Amiga as connected.
I hope all this will help someone track down the problem.

[NinjaCyborg]

Well hostname should just be whatever you what the local hostname of your computer to be. 'amiga' or something. Don't set it to the IP of the router.

The log implies that the wifi is connecting. You still need to run 'addnetworkinterface' after the wpa_supplicant as well though too, you know that right?

A good way to do it in your network-startup is to have
run >NIL <NIL: wpa_supplicant (or wirelessmanager, depending on which version you're using) prism2.device
run wait 10 +
addnetworkinterface PRISM2

or sometihng like that

[SteveH]

I have the line

Code: [Select]

AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)in my S:Network-Startup
No, my local hostname isn't set to the IP address of my router. [Edit: Actually, yes it was - I see now that Hostname refers to the name of the local host, not the router - I will change it!].
The odd thing is, none of these settings have changed, which is why I can't work out why I can no longer connect

[NinjaCyborg]

The AddNetInterfaces needs to come after the wifi negotiation has connected, so unless you put a massive WAIT command in between the wpa_supplicant and the addnetinterface it won't work

[NinjaCyborg]

also if you temporarily remove the QUIET from addnetinterface you'll see it's output on the con. it will tell you if DHCP is successful or not.

[SteveH]

Thanks for the suggestions - I will try that in the morning. One odd thing I've noticed - although  I have set the Amiga's Internet prefs to use DHCP, my BT router shows the Amiga is connected via static address assignment ... but doesn't have an IP address (see attachments). Very confusing.
Also, I've not come across wpa-supplicant before, so I'm not sure what this is.

[SteveH]

Pleased to say this has now been resolved.
Not pleased to say that the reason was ... the line invoking WirelessManager was no longer in my Startup-Sequence
Such a stupid mistake, as I was sure this file hadn't been changed, but clearly I was wrong.
Thanks to all who tried to help!

[NinjaCyborg]

You'd be much better off putting it in network-startup. nothing will change it there. but system updates might overwrite your startup sequence.