[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] noob tries to understand networking



Networking is working, it just doesn't look what
the docs I've been reading tell me.  Not
understanding how the pieces fit, I'm not sure
how to adapt iptables to the renamed interfaces
and copying of MAC and IP addresses.

First the specs.  I've probably left something
important out.  Sorry.

Single NIC computer, using xen bridging.

# cat /etc/debian_version
5.0.3 (lenny)

# uname -a
Linux fly 2.6.26-2-xen-amd64 #1 SMP Thu Nov 5 04:27:12 UTC 2009 x86_64
GNU/Linux

# xm dmesg | head -1
(XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi@xxxxxxxxxx) (gcc version
4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008

There are a million things I don't understand, but probably
the most fundamental is what the virtual pieces are, and
how they all fit together.  The only thing I changed in
/etc/xen/xend-config.sxp is to change (network-script
network-dummy) to (network-script network-bridge).

Everything I've read so far leads me to expect to find

  1) a bridge named xenbr0,
  2) a real interface called peth0
     with no MAC or IP,
  3) a virtual interface called eth0
     with a MAC and IP, and
  4) a vif<domID>.<domIF> for every
     domain.

But I appear to have a bridge and a virtual
interface called eth0, a peth0 with a MAC
and ip6 address, and no vif for dom0.

n# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:09:62:29:04
          inet addr:192.168.153.200  Bcast:192.168.153.255 
          Mask:255.255.255.0
          inet6 addr: fe80::211:9ff:fe62:2904/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14892 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1207077 (1.1 MiB)  TX bytes:2677763 (2.5 MiB)

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:104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13683 (13.3 KiB)  TX bytes:13683 (13.3 KiB)

peth0     Link encap:Ethernet  HWaddr 00:11:09:62:29:04
          inet6 addr: fe80::211:9ff:fe62:2904/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:14921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14110 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1422189 (1.3 MiB)  TX bytes:2678559 (2.5 MiB)
          Interrupt:20 Base address:0xa000

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:253 errors:0 dropped:104 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:39872 (38.9 KiB)

# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.001109622904       no              peth0
                                                        vif1.0

Can anyone help me to figure out how this is all
working together?

Thanks,

will
-- 
  
  whollygoat@xxxxxxxxxxxxxxx

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
                          love email again


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.