Odd wifi install

[DareDrop]

Downloaded the new Raspbian Stretch and burned it to a newly formatted Micro SD card. On set up in the desktop this is what I found after I set up the wifi. Did this 2 times and got he same thing. makes it hard to set up a static ip. Any thoughts?

These all carry over to the ifconfig out put, not the normal names for wlan0

[pcmanbob]

I am guessing you have a USB wifi dongle as inbuilt wifi should still return wlan0.

so to set static IP for wifi you would use wlx000f55a867a6
in place of wlan0 in dhcpcd.conf like this

Code: Select all

interface wlx000f55a867a6
static ip_address=192.168.1.15/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1

or if you wanted to set static IP on wired interface

Code: Select all

interface enxb827eb350443
static ip_address=192.168.1.15/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1

making sure to copy the interface names exactly

[DareDrop]

So why would it be doing this, have been using it for several months and never seen it before?

[pcmanbob]

This is the new why the raspbian Stretch does the eth and wlan numbering.

Were as you were using raspbian Jessie before which used eth0 and wlan0

read some of the posts about Stretch on the forum it will give you more information.

there has been suggestion that it will change back to the old numbering on the next issue of stretch, but I can find it right now.


edit.
viewtopic.php?f=63&t=191010 read this post on page 4 &5 mentions going back to eth and wlan

[DareDrop]

I have to say I have not been happy with Strech, this is only the latest issue I've had with it. Yes I was using raspbian Jessie. Seems a VERY odd change, I think they need to roll back more than this.

Anyway

Thanks for the info, it helps.

[pcmanbob]

I can't say I am impressed with the roll out of stretch, I have only tried the lite version on a spare SD card just to see what people were talking about I plan to stay with Jessie until the next update of stretch then I might try it again before updating my pi's to it.

I think its a case of watch this space for now.

[jamesh]

You all need to remember, Stretch is Debian. RPF(T) just take it and add a few Pi specific bits. (well, quite a few bits TBH)

Most of the changes people are having issues with come from Debian, not from RPF(T). It's not our 'rollout' that is causing these things, it's Debian's.So don't blame us for decisions made by a completely different dev team!

We will try and make things as easy as possible however, where we can. Hence trying to go back to the earlier (but less reliable) device naming scheme.

[pcmanbob]

jamesh I was not putting the blame for the changes on anyone at RPF(T) , I am aware that you just take the Debian OS and adjust it for use on the pi.

What does surprise me is how many things have been found not to work correctly under stretch on the pi after it had been tested before release.
I am a strong believer in the fact that a user will always find a way to break something in a away not envisaged by the programmer so any testing must be through.

Having been involved in lots of software updates and OS changes on control systems at work I am well aware things can and do go wrong believe me its no fun when some in a control decides to update an OS remotely on systems scattered across the country resulting in remote access being lost and me having to visit each system in person to correct the problem, and they always want it all fixing like yesterday.

please accept my apology I did not intend to cause offence to anyone at RPF(T)