<div class="gmail_quote">On 23 April 2011 02:20, Tim <span dir="ltr"><<a href="mailto:ignored_mailbox@yahoo.com.au">ignored_mailbox@yahoo.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Aaron Gray:<br>
<div class="im">> I want the laptop to serve as a gateway between the 192.168.0.x and<br>
> 192.168.1.x subnets, so it can serve BOOTP and TFTP to provide PXE<br>
> booting for diskless servers.<br>
<br>
</div>It doesn't *have* to be the gateway to do that. It can merely be a<br>
server on the LAN.<br>
<br></blockquote><div><br></div><div>It needs to be a DHCP server to serve the BOOTP protocol. Also I need to access HTTP to do netboot.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The only thing that has to be a gateway is that which sits between the<br>
two halves of the network. And I do mean *between*, as it's an<br>
obstacle, not just something else on the same network.<br>
<br>
If the computers on the 192.168.0 and 192.168.1 subnets are actually<br>
sharing a switch/router where they can directly talk to each other, then<br>
they don't need something acting as a gateway. And you could change the<br>
netmask to 255.255.0.0.<br></blockquote><div><br></div><div>Yes but it would not be separately serving DHCP on 192.168.1.x.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
It all depends on whether you're trying to enforce a segregation, or<br>
just get two different IP address ranges communicating together.<br></blockquote><div><br></div><div>Just to allow 192.168.1.x to have access to the internet. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
James Wilkinson:<br>
<div class="im">>> If, on the other hand, you’ve got a separate router (say an ADSL<br>
>> router), then what you’ve got is something like this:<br>
>><br>
>> Internet <—–> router <—–> 192.168.1/24 <—–> laptop <—–192.168.0/24<br>
<br>
> yep, but all on one physical network.<br>
<br>
</div>I have to wonder why do you want 192.168.XXX. subnetting, then?<br>
<br>
If it's not actually separated by hardware, you can't *enforce* separate<br>
networks just by putting in different IPs.<br></blockquote><div><br></div><div>I am not too worried about that its a temporary thing just to allow PXE booting. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
<br>
>> What you need to do is to tell everything on 192.168.1/24 to use a<br>
>> static route: packets to 192.168.0/24 should go to the laptop’s IP<br>
>> address.<br>
<br>
> ?<br>
<br>
</div>Anything on the 192.168.0 subnet has to go through the 192.168.0<br>
gateway, and *that* gateway has to have access to whatever it needs<br>
(e.g. the WWW, if necessary).<br></blockquote><div><br></div><div>Yep.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Likewise, everything on the 192.168.1 subnet has to go through the<br>
192.168.1 gateway, and *that* gateway has to have access to whatever it<br>
needs (e.g. the WWW, if necessary).<br></blockquote><div><br></div><div>This is what I need to know how to set up.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
It gets complicated if one of the gateways has to go through the other.<br>
<div class="im"><br>
>> You might find it easier to get this working with static IP addresses<br>
>> first, then replicate that with DHCP.<br>
<br>
> I need DHCP to serve the BOOTP protocol, so static IP's other than the<br>
> laptops don't really help.<br>
<br>
</div>In general, you give all your servers (computers, routers, whatever)<br>
fixed IPs, and one of them doles out the dynamic ones ones. So, I'm<br>
presuming you've already done that.<br>
<br>
Now, to test that your network actually works, before bashing your head<br>
against a brick wall in configuring your DHCP/BOOTP servers, try<br>
configuring some clients, by hand, with static IPs, and check that they<br>
actually work. If they don't, you've got a networking issue to resolve,<br>
first. If they do, it's only your DHCP/BOOTP servers you need to fix.</blockquote><div><br></div><div>Yep. </div><div><br></div><div>Thanks,</div><div><br></div><div>Aaron</div><div><br></div></div>