On Sat, 03 Aug 2013 11:50:28 -0700
Paul Munday <[email protected]> dijo:
>> Try connecting to em1. That's what my interface is named (it's on
>> the motherboard). You probably don't have an eth0 anymore. The new
>> enumeration scheme tries to name interfaces in a way that will tell
>> you where the interface is located. At least, I think that's the
>> idea.
>ifconfig -a should show you all the interfaces present regardless of
>state
ifconfig -a
eth0: flags=41663<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::21a:66bff:fed0:97f9 prefixlen 664 scopeid 0x20<link>
ether 00:1a:6b:d0:97:f9 txqueuelen 10000 (Ethernet)
(rest skipped because I have to type this manually)
lo; FLAGS=73<up,loopback,running> MTU16436
(rest skipped)
wlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:13:e8:b7:47:59 txqueuelen 1000 (Ethernet)
(rest skipped)
At a casual glance nothing looks wrong, except I wonder why wlan0 ends
in (Ethernet).
I also tried sudo ifconfig eth0 up. The command executed without error,
but I am still not connected.
>I've come across more than one instance of udev deciding to rename
>network interfaces on upgrades and the like.
>
>On Debian variants it does so
>in /etc/udev/rules.d/70-persistent-net.rules
>
>Its safe to delete/rename this file as it should get recreated on boot
>if needed.
Since I still have eth0 it appears that the upgrade did not rename my
network. I looked in /etc but I don't have a udev folder.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
