|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] No network at all in Kubuntu 8.04
On Saturday 10 May 2008 19:39:30 Todd Deshane wrote:
> > Okay, now I have the local network back, but what now? This is the
> > current state:
> >
> > irrlicht@home:~$ ifconfig -a
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:55 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:4155 (4.0 KB) TX bytes:4155 (4.0 KB)
> >
> > peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60
> > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> > inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link
> > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> > RX packets:20196 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:14388 errors:0 dropped:0 overruns:0 carrier:2
> > collisions:0 txqueuelen:1000
> > RX bytes:21625055 (20.6 MB) TX bytes:1178441 (1.1 MB)
> >
> > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > If I start /etc/xen/scripts/network-bridge start I get back the
> > "tmpbridge" and the messages:
> > irrlicht@home:~$ sudo /etc/xen/scripts/network-bridge start
> > ifdown: interface peth0 not configured
> > RTNETLINK answers: Device or resource busy
> >
> > That doesn't kill my network anymore, but what to do next?
>
> Are you using network manager?
Yes, KNetworkManager, may that be a problem?
> Did you try putting a manual entry in your /etc/network/interfaces file?
>
> See:
> http://ubuntuforums.org/showthread.php?t=651078
I don't have the lines discussed in the thread, probably because I use the
KNetworkManager:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
up ethtool -K eth0 tx off
The last line doesn't change the behavior, but I found that somewhere in the
net to help out of networking troubles with some newer cards...
> and also only similar problem that should already be fixed:
> https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/192294
That's fixed for me...
>
> Cheers,
> Todd
Cheers,
Daniel
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|