<br><br><div class="gmail_quote">On Jan 8, 2008 5:22 PM, Joseph L. Casale <<a href="mailto:jcasale@activenetwerx.com">jcasale@activenetwerx.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div><div class="Ih2E3d">
<p><span style="color: rgb(31, 73, 125);">></span>Chris, <br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>I got the impression that the network
setup is as this example:<br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>Your laptop (192.168.1.x/255.255.255.0)<br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>Router (<a href="http://192.168.1.1/255.255.255.0" target="_blank">192.168.1.1/255.255.255.0</a>)<br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>Xen (192.168.1.x/255.255.255.0)<br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>Well, you can't route from one physical
network to another over a router where source and destination has a ip in the
same netmask area. Perhaps you only use the <span style="color: rgb(31, 73, 125);">></span>router
as a network switch since cheaper models have a built in switch... In this case
it's a switch rather then a router, some lousy home scale routers may rally
screw <span style="color: rgb(31, 73, 125);">></span>up things since they don't have
switches, rather a couple of network interfaces separated with bridging and
firewall rules in a embedded Linux or BSD environment..<br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span><br>
<span style="color: rgb(31, 73, 125);">></span>- Nicolas<span style="color: rgb(31, 73, 125);"></span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p></div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Nicolas,</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">I am following this thread with interest as a system I was about
to setup is using the same driver and in the same networking scenario! If in a
small segment with only one subnet and the default gateway on that subnet as
you describe above, the Xen machine even in bridged mode won't have
connectivity if Dom0 has an ip on the same subnet? Giving the Xen machine an IP
on a different subnet would make it tricky to connect from another machine in
this setup?</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks!<br>
jlc</span></p>
</div>
</div>
<br>_______________________________________________<br>CentOS mailing list<br><a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos
</a><br><br></blockquote></div><br>Joseph,<br><br>The only time I hit into this kind of problem is when using VPN sitting on the same subnet locally as on the other end of the tunnel so the VPN client is unable to route it over to the same subnet on the other side, this is quite expected behavior why one have to put another route between the client pc or change the ip range of the local network and then set up a VPN tunnel.. But on a local network where you have a Xen instance on
<a href="http://192.168.1.110">192.168.1.110</a>, the Dom0 host on <a href="http://192.168.1.100">192.168.1.100</a> (bridiging in between as default with Xen) with a gateway of <a href="http://192.168.1.1">192.168.1.1</a>
I don't see the problem, the clients on the network can access both last time I tested. I would be really surprised if this would have passed broken through RH and CentOS testing phases.<br>