<482814C9.9010800@xxxxxx> <48284777.7090904@xxxxxx>
<200805121544.02186.daniel.spies@xxxxxxxxxxxx>
<fe9771a80805121249m1db7c564l811c3e62db24e16f@xxxxxxxxxxxxxx>
Message-ID: <cf9f4e818c7a3815e28395b72ae1bcfd@localhost>
X-Sender: daniel.spies@xxxxxxxxxxxx
Received: from 62.159.37.130 [62.159.37.130] with HTTP/1.1 (POST); Tue, 13 May
2008 08:45:35 +0200
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Hi Emre,
I did _disable_ the network manager already (KNetworkManager, as I'm using
Kubuntu (Ubuntu with KDE)), do you think I should remove it completely? If
yes, I'll give it a try later when I'm back at home...
Thank you!
Daniel
On Mon, 12 May 2008 21:49:46 +0200, "Emre ERENOGLU" <erenoglu@xxxxxxxxx>
wrote:
> Hi All,
>
> Ubuntu had this "Network Manager" component which messed up things with
> XEN
> for me in the past. Could you please remove the network-manager
> network-manager-gnome packages and try again to give the interface an IP
> address using the /etc/network/interfaces file?
>
> sudo apt-get remove network-manager network-manager-gnome
>
> Emre
>
> On Mon, May 12, 2008 at 3:44 PM, Daniel Spies <daniel.spies@xxxxxxxxxxxx>
> wrote:
>
>> On Monday 12 May 2008 15:34:47 Age_M wrote:
>> > Hi Daniel,
>> >
>> > Age_M schrieb:
>> > > Daniel Spies schrieb:
>> > >> On Monday 12 May 2008 11:24:16 Age_M wrote:
>> > >>> Hi Daniel,
>> > >>> Why does your peth0 has an ip-address?
>> > >>
>> > >> Good question, I don't know... What do you suggest me to do?
>> > >> Both, eth0 and peth0 have the very same configuration and IP
>> > >> addresses in "ifconfig -a".
>> > >>
>> > >> irrlicht@home:~$ cat /etc/network/interfaces
>> > >> # 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
>> > >> auto eth0
>> > >> iface eth0 inet dhcp
>> > >
>> > > Try using static ip instead of dhcp in dom0. Maybe this is messing
>> > > with your interfaces.
>> > >
>> > > _______________________________________________
>> > > Xen-users mailing list
>> > > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > > http://lists.xensource.com/xen-users
>> >
>> > I recently had a networking problem myself, where only pings came
>> > through from domU to the physical network. I had to turn off tx
> checksum
>> > offload with ethtool. I integrated it in the xen-network-common.sh
>> > script, so maybe this patch will help you too?!
>> >
>> > This patch modifies the last line in the "add_to_bridge ()" function:
>> >
>> > --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000
>> +0200
>> > +++ scripts/xen-network-common.sh.modified 2008-05-12
>> > 15:23:41.000000000 +0200
>> > @@ -124,5 +124,6 @@
>> > fi
>> > brctl addif ${bridge} ${dev}
>> > ip link set ${dev} up
>> > + ethtool -K ${dev} tx off
>> > }
>> >
>> > Hope it helps,
>> > Greetz Age_M
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-users
>>
>> This was the first thing I tried, but that doesn't change things for me.
> I
>> did
>> it via "up ethtool -K eth0 tx off" in /etc/network/interfaces...
>>
>> Thanks anyway!
>> Daniel
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>
>
>
> --
> Emre Erenoglu
> erenoglu@xxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|