[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 27/01/16 11:42, Ben Whorwood wrote:
on my (x)ubuntu setups /etc/network/interfaces contains only loopback. ifconfig shows it as wlan0 when configured - when not configured a reboot brings it all back to life if restarting network fails. That is rare but sometimes we get a farmer contractor with a phone that takes out the networking and restarting networking from scratch is required. I blame redhat.On Debian (assume Ubuntu as well) network interfaces are defined in: /etc/network/interfaces Wireless interfaces could be additionally configured using other tools such as wicd. I'm not sure on the wlan0=wlan0 issue but don't experience it myself. My /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug enp0s25 iface enp0s25 inet dhcp # This is an autoconfigured IPv6 interface iface enp0s25 inet6 auto (Wireless network is managed by wicd.) On 27/01/16 10:57, Tom wrote:On 26/01/16 22:26, Matt Stevenson wrote:Yes Eion seems MS updates break and fix wired and wireless connections reliably. http://www.infoworld.com/article/3016955/microsoft-windows/cumulative-update-kb-3124200-for-windows-10-version-1511-may-fix-wi-fi-problem.html My Ubuntu 14.04 LTS. has been known to drop wired and wifi connections. May of been due to restarting the network manger. What is the preferred way to restart the network interfaces in Ubuntu ?sudo ifdown eth0 or your interface number sudo ifup eth0 or your interface number How does one find ones interface number and does using this stop that damned wlan0=wlan0 not found thing? Tom te tom te tom
Tom te tom te tom -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq