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

[point17]

I've a minor issue with the network since upgrading my Vu+ Duo4K SE to 6.7.001. I'm not sure if it's a bug or some configuration setting that I lost when doing the upgrade.

Issue: I have a daily PowerTimer set for the early hours of the morning to reboot the box. I've been using this for years without a problem. Since the upgrade to 6.7, I find that the box is not visible on the LAN after each reboot. It's mainly Samba I want but I've tried FTP, Telnet, etc. and they also have the same problem. Even ping does not find the box. However, if I go to the box and do a "Restart Network", everything is fine.

It's only a minor problem because there's a workaround - I can do that manual operation easily enough. It's just a pain to have to remember to do it each morning.

So, I'm wondering, did something change in 6.7 to cause this? Or is there maybe some configuration setting I lost as part of the upgrade, which could be restored if only I knew what it was? Any advice welcome.

Thanks,
Dan

 

[Joe_90]

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.

 

[Huevos]

Please update to the latest version and try again.

 

[Joe_90]

Please update to the latest version and try again.

What's changed?

 

[Huevos]

What's changed?

You want me to list every change between 6.7.001 and 6.7.005? Or just the ones related to network connections? Most changes are listed here. There were updates related to udev. Birdman changed some settings.

 

[Joe_90]

Sorry - I didn't twig that the OP was still on 6.7.001. It was me who kicked off the issue resolution initially with wifi problems and @Birdman changed the udev script so that the the ethernet interface was not UP'd by default. The new change can actually affect the ethernet interface unless it is specifically enabled.

 

[birdman]

The new change can actually affect the ethernet interface unless it is specifically enabled.

Why would it not be enabled if you want to use it?
Given the you can disable it, you must surely need to enable it for it to be brought up?

 

[Joe_90]

The change you made to the udev script UP's only the interfaces marked as "auto" IIRC. I'm not 100% sure the interfaces file from the built image comes with the ethernet interface marked as "auto". In my particular case it was the wlan0 interface that I was trying to enable, but the ethernet interface kept being UP'd also even though it had no connection. Your script change fixed that ok for me, but I found that on my other box (my Vu+ with ethernet only, no wifi) after a flash of the newer image and settings restore that the ethernet interface would not come UP automatically at boot. I had to go into Network settings and explicitly enable the ethernet interface. That changed the setting in the interfaces file to "auto" and after that the interface worked fine.

 

[birdman]

The change you made to the udev script UP's only the interfaces marked as "auto" IIRC. I'm not 100% sure the interfaces file from the built image comes with the ethernet interface marked as "auto".

They can't, as there is no known interface to set as such.

The Install Wizard should be doing it, though.

If it isn't, then that is where the bug lies.

 

[Joe_90]

...
The Install Wizard should be doing it, though.

If it isn't, then that is where the bug lies.

I suspect I had never used the network wizard on the boxes I use in the living room as they have always been ethernet cable connected and the connection just seemed to work in the default image config. So my flash and settings restore process always left the interfaces file as it was. The recent script change caught me out when I flashed the 6.7 dev version after it was implemented. My LAN connection just stopped working after the reboot following the settings restore/plugins download. I realised straight away what had happened, so I went into network config and enabled the LAN interface. Using the wizard would have done it also.

The script change might catch out other users who use the flash and restore process, so never use the wizard to set the interfaces properly. In the case of my wifi-connected boxes I usually go through the wizards as I'm testing new dev and release images.

 

[birdman]

Hmmmm....I suppose a workaround/fix would be to put an init script in at S99 which checks whether there is a non-local interface up and, if not, tries to start eth0.

EDIT: No, scrub that.
To bring an interface up it needs to have been configured (IP addr/mask/resolver or DHCP), and if it’s been configured it should be marked as auto.

Or is the expectation that if it hasn't been configured it defaults to DHCP? In which case it's still the FIW that should be setting this.

 

[Huevos]

Why does it have to be in FIW? So if I want to changes things later I have to reflash?

 

[Joe_90]

@birdman, @Huevos - Your posts ended up in an incorrect thread (about VLC shortcuts), so I moved them. I don't know if there was a disturbance in the matrix somewhere or just a mistake


The network setting to enable any interface works from FIW or from the local Menu/Settings/Network, so it's all good providing the user uses one or the other.

 

[birdman]

Why does it have to be in FIW? So if I want to changes things later I have to reflash?

No, reconfiguring your network already does the right thing.

 

[birdman]

@birdman, @Huevos - Your posts ended up in an incorrect thread (about VLC shortcuts), so I moved them. I don't know if there was a disturbance in the matrix somewhere or just a mistake

Probably my fault.
I seem to recall something odd happening at my end.

The network setting to enable any interface works from FIW or from the local Menu/Settings/Network, so it's all good providing the user uses one or the other.

So why has an update made it stopped working?
Something appears to be amiss.

 

[Joe_90]

I don't know what the behaviour was prior to 6.7, but when 6.7.001 (udev) was launched it UP'd the LAN interface by default (which was good for LAN users, not so good for wifi users). Then you fixed the script which only UP'd an interface with "auto" status (which was good for wifi users who had run the wizard or properly configured their interfaces). I don't think it's a big deal as most people will have used the wizard to set their interfaces properly. Any edge cases where LAN is not working we just need to advise users to check their config.

 

[birdman]

Any edge cases where LAN is not working we just need to advise users to check their config.

But you noted that:

The network setting to enable any interface works from FIW or from the local Menu/Settings/Network, so it's all good providing the user uses one or the other.

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

 

[Huevos]

So there is a report on Vu boxes that Wifi has to be set up in FIW and is impossible later.

 

[birdman]

So there is a report on Vu boxes that Wifi has to be set up in FIW and is impossible later.

Can't see how it would be specific to any one brand, given that it is the standard Vix python code that updates the interfaces file and adds the "auto" line for any enabled interface.

 

[twol]

The ( very specific) vu+ WiFi issue is fixed, just need to commit before I go away