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

[Xen-users] Re: DomU network configuration problem

Tej <bewith.tej <at> gmail.com> writes:


> > ---------------8<------------------
> >>
> >> You can do following steps:
> >>
> >> 1. Assign any private IP to your DomU
> >> 2. Assign the subnet gateway to the domU, above vuf configuration is
> >> fine i guess.
> >>
> >> 3. Now as dom0 is on different subnet, create the eth0 (i assume here
> >> that eth0 domU and eth0 of dom0 is connected to xenbr0 ) alias as a
> >> gateway for domU.
> >>     In dom0:
> >>     ifconfig eth0 add domU-gateway netmask.
> >> 4. Now that gateway should be pingable
> >> 5. Now add the forwarding rules
> >>     echo 1 >/procsys/net/ipv4/ip_forward
> >>    Now you should be able to ping the eth0 on dom0.
> >> 6. Add the masq rule as above.
> >>    iptables -t nat -A POSTROUTING -j MASQUERADE (use the eth0 address)
> >> 7. Now you should be able to ping google.com
> >>
> >> HTH
> >>
> >> -tej
> > -------------------8<--------------
> >
> > i tried these instructions but i could not proceed till step 4.
> > i was not able to ping the gateway from domU.
> 
> only one reason i could see xenbridge is not connecting dom0 and domU
> 
> ensure this connectivity using brctl show:
> 
> xenbr0           8000.xxxxx     no                vif0.0
>                                                                peth0
>                                                                vif<domU-id>.0
> if not eth0.0 will not be pingable.
> 
> try this if still problem  post following
> 1. domU ifconfig & route -n

ifconfig on domU gives the following output:
xentestl: # ifconfig 
eth8      Link encap:Ethernet HWaddr 00:16:3E:5D:1F:3D 
        inet addr: 192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0
        inet6 addr: fe80: :216:3eff:fe5d:lf3d/64 Scope:Link
        UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
        RX packets:0 errors:0 dropped:0 ouerruns:0 frane:0
        TX packets:8 errors:0 dropped:0 ouerruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:0 (0.0 b) TX bytes:592 (592.0 b)
        Interrupt : 177 Base address :0x2000
lo      Link encap:Local Loopback
        inet addr: 127.0.0.1 Mask:255.0.O .0
        inet6 addr: ::1/128 Scope:Host
        UP LO0PBACX RUNNING MTU:16436 Metric:1
        RX packets:50 errors:0 dropped:0 ouerruns:0 frame:0
        TX packets:50 errors:0 dropped:0 ouerruns:0 carrier:0
        collisions:0 txqueuelen:0
        RX bytes:7943 (7.7 Kb) TX bytes:7943 (7.7 Kb)

route -n on domU shows the following result:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth8
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth8
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

> 2. dom0 ifconfig & route -n

dom0 ifconfig has the following result :

dummy0    Link encap:Ethernet  HWaddr 52:B0:12:64:EA:DD  
          inet addr:10.33.195.40  Bcast:10.33.195.255  Mask:255.255.255.0
          inet6 addr: fe80::50b0:12ff:fe64:eadd/64 Scope:Link
          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
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)
 
eth0      Link encap:Ethernet  HWaddr 00:19:DB:51:BB:4A  
          inet addr:10.33.196.47  Bcast:10.33.196.255  Mask:255.255.255.0
          inet6 addr: fe80::219:dbff:fe51:bb4a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:101210 errors:0 dropped:0 overruns:0 frame:0
          TX packets:116297 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7828179 (7.4 Mb)  TX bytes:160785457 (153.3 Mb)
          Base address:0x3000 Memory:b8340000-b8360000 
 
eth0:0    Link encap:Ethernet  HWaddr 00:19:DB:51:BB:4A  
          inet addr:192.168.1.255  Bcast:10.33.196.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Base address:0x3000 Memory:b8340000-b8360000 
 
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:58768 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58768 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:305180714 (291.0 Mb)  TX bytes:305180714 (291.0 Mb)
 
tap0      Link encap:Ethernet  HWaddr 9E:A2:FE:02:92:1D  
          inet6 addr: fe80::9ca2:feff:fe02:921d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:592 (592.0 b)  TX bytes:468 (468.0 b)
 
vif10.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST NOARP  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:32 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 
xenbr0    Link encap:Ethernet  HWaddr 9E:A2:FE:02:92:1D  
          inet6 addr: fe80::f01a:3ff:fe74:43db/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:38 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:2304 (2.2 Kb)  TX bytes:0 (0.0 b)

route -n on dom0 is: 

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.33.195.0     0.0.0.0         255.255.255.0   U     0      0        0 dummy0
10.33.196.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.33.196.35    0.0.0.0         UG    0      0        0 eth0

> 3. brctl show
brctl on dom0 gives the following output:

xenbr0          8000.9ea2fe02921d       no              vif0.0
                                                        pdummy0
                                                        tap0
                                                        vif10.0

> 
> -tej
> 
> >
> > is there any method to know that the eth0 of domU is connected to xenbr0
> >
> > one more information that i missed out last time was that i am using full
> > virtualization. so i just want to confirm that are the above steps fine
> > for full virtualization as well?
> >
> >
> >
> >
> >> > _______________________________________________
> >> > Xen-users mailing list
> >> > Xen-users <at> lists.xensource.com
> >> > http://lists.xensource.com/xen-users
> >> >
> >>
> >
> >
> >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users <at> lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> 





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