Re: [Xen-users] Strange Networking Issue

[jez <jez@xxxxxxxxxx>]

Some things aren't adding up here. When your provider set up your
machine they configured 75.126.153.178/29 on eth0. But when they
allocated you your extra addresses, what did they say exactly - what did
they tell you the subnet mask was, did they mention an additional
gateway address, etc. 

Also, if I was to ask you to actually change the address on eth1, would
you still have access to the box via eth0?


On Sat, Mar 10, 2007 at 01:44:45PM -0500, Jonathon Jones wrote:
> jez wrote:
> >On Fri, Mar 09, 2007 at 07:08:28PM -0500, Jonathon Jones wrote:
> >  
> >Hi Jon, 
> >
> >your first post says that additional IPs on eth0 in Dom1 are /32 not /22 - 
> >which is it? 
> >  
> Tried it both ways and more.  I added it as /22 recently simply to show 
> that it is consistent with a working IP, .240
> >Also, can you fill in the details on the following:
> >
> >1. "ip addr show" on Dom0
> >  
> [root@trinity domU]# ip addr show
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>    inet 127.0.0.1/8 scope host lo
>    inet6 ::1/128 scope host
>       valid_lft forever preferred_lft forever
> 2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> 3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 4: vif0.1: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>       valid_lft forever preferred_lft forever
> 5: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>    link/ether 00:30:48:78:d6:07 brd ff:ff:ff:ff:ff:ff
>    inet 75.126.153.178/29 brd 75.126.153.183 scope global eth1
>    inet6 fe80::230:48ff:fe78:d607/64 scope link
>       valid_lft forever preferred_lft forever
> 6: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> 7: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 8: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> 9: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 10: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>    link/ether 00:30:48:78:d6:06 brd ff:ff:ff:ff:ff:ff
>    inet 10.10.16.2/26 brd 10.10.16.63 scope global eth0
>    inet6 fe80::230:48ff:fe78:d606/64 scope link
>       valid_lft forever preferred_lft forever
> 11: peth1: <BROADCAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>       valid_lft forever preferred_lft forever
> 12: sit0: <NOARP> mtu 1480 qdisc noop
>    link/sit 0.0.0.0 brd 0.0.0.0
> 13: xenbr1: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>    inet6 fe80::200:ff:fe00:0/64 scope link
>       valid_lft forever preferred_lft forever
> 14: vif1.0: <BROADCAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 32
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>       valid_lft forever preferred_lft forever
> 15: vif2.0: <BROADCAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 32
>    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
>       valid_lft forever preferred_lft forever
> >2. "brctl show" on Dom0
> >  
> [root@trinity domU]# brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr1          8000.feffffffffff       no              peth1
>                                                        vif0.1
>                                                        vif1.0
>                                                        vif2.0
> >3. "route -n" on Dom0
> >  
> [root@trinity domU]# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use 
> Iface
> 75.126.153.176  0.0.0.0         255.255.255.248 U     0      0        0 eth1
> 10.10.16.0      0.0.0.0         255.255.255.192 U     0      0        0 eth0
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
> 10.0.0.0        10.10.16.1      255.0.0.0       UG    0      0        0 eth0
> 0.0.0.0         75.126.153.177  0.0.0.0         UG    0      0        0 eth1
> >4. The vif configurations for Dom1 and Dom2 (from their config files)
> >  
> In Dom1:
> [root@secure network-scripts]# cat ifcfg-eth0
> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
> # for the documentation of these parameters.
> TYPE=Ethernet
> DEVICE=eth0
> BOOTPROTO=static
> ONBOOT=yes
> IPADDR=75.126.154.240
> NETMASK=255.255.252.0
> GATEWAY=75.126.153.177
> [root@secure network-scripts]# cat ifcfg-eth0-range0
> IPADDR_START=75.126.154.241
> IPADDR_END=75.126.154.243
> CLONENUM_START=0
> NETMASK=255.255.252.0
> 
> Note:  I have been using ip addr add/del to test the IP's out but for 
> simplicity I added them using the range config above.  Neither way is 
> working.  I also have my ISP checking on whether this is a routing issue 
> on their side, although I don't see hwo it could be when .240 and .244 
> are routing to Dom1 and Dom2 respectively.
> 
> In Dom2:
> [root@secure network-scripts]# cat ifcfg-eth0
> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
> # for the documentation of these parameters.
> TYPE=Ethernet
> DEVICE=eth0
> BOOTPROTO=static
> ONBOOT=yes
> IPADDR=75.126.154.244
> NETMASK=255.255.252.0
> GATEWAY=75.126.153.177
> 
> [root@secure network-scripts]# cat ifcfg-eth0-range0
> IPADDR_START=75.126.154.245
> IPADDR_END=75.126.154.247
> CLONENUM_START=0
> NETMASK=255.255.252.0
> >5. The settings for (network-script ...) and (vif-script ...) in your
> >   xend configuration file.
> >  
> In Dom1:
> vif = [ '' ]
> In Dom2: (as an experiment which didn't change anything)
> vif = [ 'ip=75.126.154.244' ]
> 
> Neither DomU has any other network settings in the config.
> >6. The version of xen you are running.
> >  
> xen-3.0.4_1-install-x86_32p.tgz is the file I downloaded form xensource.com
> uname reports 2.6.16.33-xen #1 SMP Mon Jan 8 14:39:10 GMT 2007 i686 
> athlon i386 GNU/Linux
> >Depending on what you come back with, I might have more questions. 
> >
> >Also, do you have any idea if you would prefer a bridged or a routed
> >setup?
> >
> >jez
> >
> >  
> I prefer bridged simply because it seems the most simple setup 
> normally.  I am open to suggestions but I am looking for the easiest to 
> maintain because I am frankly not a networking guru...although I am 
> learning a lot from this.
> 
> Thanks much!
> 
> Jon
> >_______________________________________________
> >Xen-users mailing list
> >Xen-users@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-users
> >
> >  
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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