Jerry,<br><br>I'll get the info on Monday and send it to you before I do anything else.<br><br>Thanks.<br>Gerald<br><br><div class="gmail_quote">On Sat, Sep 26, 2009 at 2:53 PM, Jerry Vonau <span dir="ltr"><<a href="mailto:jvonau@shaw.ca">jvonau@shaw.ca</a>></span> 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 class="im">On Sat, 2009-09-26 at 14:40 -0400, Gerald Ardito wrote:<br>
><br>
> Jerry,<br>
><br>
</div><div class="im">> I will try out what you suggested when I get back to school on Monday.<br>
> I'll let you know what happens.<br>
><br>
</div>Before you change anything please answer the questions below, I don't<br>
want to lead you on a wild goose chase...<br>
<div class="im"><br>
><br>
><br>
> That can be a problem, how is eth0 set? by dhcp from the<br>
> "regular<br>
> network"? Is the ip address in the 10.125.140.0 netblock? What<br>
> gateway<br>
> is the XS using? What is the output of "ip route ls"? Do both<br>
> eth0 and<br>
> eth1 plug into the same switch?<br>
><br>
<br>
</div>If your gateway is within <a href="http://10.125.140.0/23" target="_blank">10.125.140.0/23</a>, you will have to make some<br>
additional ip/routing changes in order to get to the internet from the<br>
XS box... Need that eth0 info..<br>
<br>
You have been warned...<br>
<font color="#888888"><br>
Jerry<br>
<br>
<br>
</font></blockquote></div><br>