network issue with no ethernet

[chrwei]

using 20160501.  boot up with no ethernet, connect wifi, and connections all fail

reason is that eth0 is setup in interfaces and for some reason if creating a default route to nowhere, and the wifi adds another default route, and I'm guessing the kernel routing table prioritizes the wired.

solution:  comment out the eth0 lines in /etc/network/interfaces and let network-manager handle it, the it can be manually disabled if needed.

[tkaiser]

using 20160501.

OMFG! Unbelievable. Since you're posting in the Debian forum I would assume you're talking about this: http://wiki.pine64.org/index.php/Pine_A6..._by_Pine64 or do you refer to any other 20160501 release?

Now the Pine64 folks start to modify OS images on their own and re-release them? While the wiki changes are in stealth mode and more and more changes disappear? http://wiki.pine64.org/index.php/Special:RecentChanges

Makes finding bugs or even getting the idea what the users are using/doing close to impossible. What an unbelievable mess...

BTW: Networking behaviour as expected in Debian/Ubuntu. Have a look into the documentation regarding 'auto' vs. 'allow-hotplug'. And here's the FAQ: https://www.pine64.pro/faqs-linux/

[chrwei]

if I got it somewhere else or it was a different distro I would have posted elsewhere.

this is NOT expected. it's a desktop OS release with network manager enabled by default, so interfaces should not be used by default. also when an interface doesn't get a DHCP address it also should not be setting any default routes, but maybe that's an upstream issue.

that FAQ page is blank.

[tkaiser]

if I got it somewhere else or it was a different distro I would have posted elsewhere.  

this is NOT expected.  it's a desktop OS release with network manager enabled by default, so interfaces should not be used by default.  also when an interface doesn't get a DHCP address it also should not be setting any default routes, but maybe that's an upstream issue.  

that FAQ page is blank.

Great, isn't it? A blank FAQ and an OS image that doesn't work as expected (an OS image that's based on longsleep's work with another rootfs and unknown settings and now modified/re-released again by 'Pine64' -- who should know who's responsible if things don't work as expected?).

But that's the expected result of 'featured' fragmentation.

You should be aware that I'm neither a friend of fragmentation of information 'sources' (pages with zero contents) nor 3rd party OS images. Unfortunately these and not the original one get featured by the Pine64 guys. And in the meantime they also start to modify others' OS images, re-release them and create further confusion.

It's really absolutely useless to continue with this here... but you can use the link above to get an idea about the real state of Linux support for Pine64. And maybe also here http://linux-sunxi.org/Pine64#Sunxi_support

And with every new released 3rd party OS image the situation will get more and more worse

[longsleep]

Any image which uses network manager should of course not have a automatic network configuration for any device in interfaces. Well, maybe except the wlan1 disable i have in my images.