[VU+ Duo4K SE] Network restart needed after every reboot

[Joe_90]

But you noted that:

Are you suggesting that you can run through FIW without configuring the network at all?

No - when you have a backup you skip the FIW. In my initial case I had a problem with wifi on my AX61 and GB Quad Plus, which was resolved by your script change. Subsequently, I had an issue with my VU box on ethernet (not wifi) when I flashed and restored settings without going through FIW or Network wizard. I had to go into the Menu/System/Network/Settings and enable the LAN interface. After that all was ok.

 

[birdman]

So, as far as I can tell the only actual issue is the one reported in the OP, but which no-one else is reporting.

I've just had a look at the interfaces file in a standard et8000 image and it is:

# automatically generated by enigma 2 
# do NOT change manually! 

auto lo 
iface lo inet loopback 

auto eth0 
iface eth0 inet dhcp 
iface eth0 inet6 dhcp

which is fine for udev and will bring up eth0 even if FIW is never run.
If FIW is run then what you end up with should be what you choose - so any failing is down to the configurer.

 

[birdman]

However, if I go to the box and do a "Restart Network", everything is fine.

Odd. As all that does (as far as the network is concerned) is run "ifup -a", by calling /etc/init.d/networking.

And that is run as /etc/rc3.d/S10networking at boot time anyway (so udev bringing them up as well seems to be a bit of overkill).

If before choosing "Restart network" in the Network Setup menu you look at "Adapter settings", what does it show?

 

[joe1000000]

hate to say but network settings were simple on 6.6 and before,now a nightmair on 6.7 if it isnt broke dont fix it,my zgemmer boxes go to wlan and wont set on lan may have to go back to 6.6.13 and stay there

 

[Joe_90]

hate to say but network settings were simple on 6.6 and before,now a nightmair on 6.7 if it isnt broke dont fix it,my zgemmer boxes go to wlan and wont set on lan may have to go back to 6.6.13 and stay there

Network wizard and network menu settings are the same on 6.6 and 6.7 (current version). Just ensure that you enable the interface you want and disable the one you don't want.

 

[birdman]

if it isnt broke dont fix it

But it was broken, which is why it has been fixed.

If you have a problem report the details as "now a nightmare" is difficult to debug.

 

[Huevos]

hate to say but network settings were simple on 6.6 and before,now a nightmair on 6.7 if it isnt broke dont fix it,my zgemmer boxes go to wlan and wont set on lan may have to go back to 6.6.13 and stay there

If you helped debug the problem it might get fixed. Instead you want to go back to an old version that is about to have its feeds removed.

 

[joe1000000]

once again this morning 6.7.005 no picture box went back to none setup wlan from lan ?? went back to 6.4.... then to 6.7.05 picture back but this time in network wlan has an x beside it so hope this mean i am locked on lan...x never showed before ?

 

[Joe_90]

Please show screenshots of your network settings. Ideally, a debug log would help resolve your issue.

 

[point17]

Are you on a LAN (ethernet) connection or wifi?

Ensure that the connection you use is enabled in the network settings and the one you are not using is disabled. There has been a change in the udev script which activates the relevant network interface.

A belated update: I checked the above but it was set correctly (ethernet enabled, WiFi disabled), so that wasn't the problem. So I followed Huevos's suggestion and upgraded to 6.7.005. Since I did this 3 days ago I've not had the problem, so it looks like the latest version fixed it.

Thanks for the assistance.

 

[Joe_90]

A belated update: I checked the above but it was set correctly (ethernet enabled, WiFi disabled), so that wasn't the problem. So I followed Huevos's suggestion and upgraded to 6.7.005. Since I did this 3 days ago I've not had the problem, so it looks like the latest version fixed it.

Thanks for the assistance.

Ok, thanks. The udev script on 6.7.001 was subsequently changed and the behaviour fixed so that the enabled interface was brought up correctly.