Oh ya
I have completely failed to take into consideration that there are no
virtual internal ethernet cross cables between the different VMs. Thanks for
pointing it out.
I will try it out with my hub tomorrow and also test with my laptop as an
external device.
On 7/30/07, Simon Hobson <[EMAIL PROTECTED]> wrote:
>
>
> >When I configured Dom 1 as
> ><http://192.168.1.2/255.255.255.0>192.168.1.2/255.255.255.0, I
> >couldn't ping Dom 1 from Dom 0. Similarly, I could not ping Dom 0
> >from Dom 1. I get Destination Host Unreachable error messages. Any
> >fix?
>
> Bear in mind I'm a Xen newbie as well ...
>
> Are the relevant ethernet cards all connected to the same switch ?
> Don't forget that the way you have this set up, inter-domain traffic
> will go out through one physical port, through an external switch,
> and back in via a different physical port. I would also test it for
> traffic between dom-0 or a dom-u and an external device - ie make
> sure you can ping between dom-0 and an external device, and between
> dom-1 and an external device, etc.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Shorewall-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
