| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Strange Networking Issue
|
----- Original Message -----
Sent: Saturday, March 10, 2007 8:23
AM
Subject: Re: [Xen-users] Strange
Networking Issue
Hi,
2: eth0:
<BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
1000
link/ether 00:16:3e:3d:20:f0 brd
ff:ff:ff:ff:ff:ff inet 75.126.154.240/22 brd 75.126.155.255 scope global
eth0 inet 75.126.154.241/22 brd 75.126.155.255 scope global
secondary eth0:0 inet 75.126.154.242/22 brd 75.126.155.255 scope global
secondary eth0:1 inet 75.126.154.243/22 brd 75.126.155.255 scope global
secondary eth0:2 inet6 fe80::216:3eff:fe3d:20f0/64
scope link
valid_lft
forever preferred_lft forever
You can see that all IP's are
added in the same way yet only .240 is pingable. I can add the IP
manually to dom0 and get it to ping so I'm thinking there is some bug in
this latest version of xen. Does anybody else have any other
conclusion?
pingable means from outside, right. So are there any firewalls
between outside and xen?
have you tested any other service, like http? try
that.
does your xen box get/answer the ping? tcpdump -i eth0 icmp. Do you
see any echo/echo-replys generated from your box?
According to your first
mail, eth1 is the if with the public interface! Why are the addresses
configured on eth0?
There's been a lot of
previous discussions about setting up firewalls, especially iptables, for Dom0
to allow guests their necessary access. I'd still love to see a clear
walkthrough guide for this, though.
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home