WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Neverending story: Networking in domU

Hi,
i think i am one step further. 

I looked at the outout of ifconfig at dom0 (i am using routed networking):
eth0      Protokoll:Ethernet  Hardware Adresse 00:16:D3:27:32:9E  
          inet Adresse:192.168.1.15  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6 Adresse: fe80::216:d3ff:fe27:329e/64 
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4219 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4242 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:3734115 (3.5 MiB)  TX bytes:643767 (628.6 KiB)
          Interrupt:20 

lo        Protokoll:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:500 (500.0 b)  TX bytes:500 (500.0 b)

vif3.0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF  
          inet Adresse:192.168.1.137  Bcast:0.0.0.0  Maske:255.255.255.255
          inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:100 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

Usually vif3.0 should have the same ip as eth0.
I think the ip of vif3.0 is somehow random, because before the last reboot it 
was 192.168.1.16 ( maybe related to my dhcp-server, how assigns adresse 
starting from 192.168.1.15?)
What could be the reason for the differing ips?
How is the ip of vifX.0 determined? (As i said, i am using routed networking)

Thanks,
Julian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>