Re: dhcpd gateway settings

2011-04-23 Thread Tim
Tim: >> It doesn't *have* to be the gateway to do that. It can merely be a >> server on the LAN. > Aaron Gray: > It needs to be a DHCP server to serve the BOOTP protocol. Also I need > to access HTTP to do netboot. Yes, but it doesn't actually have to be the gateway. The DHCP server on

Re: dhcpd gateway settings

2011-04-23 Thread Aaron Gray
On 23 April 2011 02:20, Tim wrote: > > Aaron Gray: > > I want the laptop to serve as a gateway between the 192.168.0.x and > > 192.168.1.x subnets, so it can serve BOOTP and TFTP to provide PXE > > booting for diskless servers. > > It doesn't *have* to be the gateway to do that. It can merely be

Re: dhcpd gateway settings

2011-04-23 Thread James Wilkinson
I asked: > Do you have forwarding turned on on the gateway? Aaron replied: > No I said: > That might be a good place to start. Aaron replied: > Okay is that IPTables or routing ? Both, really. Since you’re behind a router, I’d start by turning iptables off, and then echo 1 > /proc/sys/net/ipv4/

Re: dhcpd gateway settings

2011-04-22 Thread Tim
Aaron Gray: > I want the laptop to serve as a gateway between the 192.168.0.x and > 192.168.1.x subnets, so it can serve BOOTP and TFTP to provide PXE > booting for diskless servers. It doesn't *have* to be the gateway to do that. It can merely be a server on the LAN. The only thing that has to

Re: dhcpd gateway settings

2011-04-22 Thread Rick Sewill
On Friday, April 22, 2011 01:58:35 PM Aaron Gray wrote: > On 22 April 2011 19:37, Rick Sewill wrote: > > On Friday, April 22, 2011 12:11:38 PM Aaron Gray wrote: > > > I am trying to set up a network and gateway on 192.168.1.x that I am > > > > using > > > > > for BOOTP'ing servers. > > > > > >

Re: dhcpd gateway settings

2011-04-22 Thread Aaron Gray
On 22 April 2011 21:45, James Wilkinson wrote: > Aaron Gray wrote: > > I am trying to set up a network and gateway on 192.168.1.x that I am > using > > for BOOTP'ing servers. > > > But I cannot seem to get HTTP or other services to work on 192.168.1.x > > > > I have the existing 192.168.0.x netw

Re: dhcpd gateway settings

2011-04-22 Thread James Wilkinson
Aaron Gray wrote: > I am trying to set up a network and gateway on 192.168.1.x that I am using > for BOOTP'ing servers. > But I cannot seem to get HTTP or other services to work on 192.168.1.x > > I have the existing 192.168.0.x network and was wondering how gateway > requests should get from 192.

Re: dhcpd gateway settings

2011-04-22 Thread Aaron Gray
On 22 April 2011 19:37, Rick Sewill wrote: > On Friday, April 22, 2011 12:11:38 PM Aaron Gray wrote: > > I am trying to set up a network and gateway on 192.168.1.x that I am > using > > for BOOTP'ing servers. > > > > dhcpd.conf > > ~~~ > > allow booting; > > allow bootp; > > ddns-update-s

Re: dhcpd gateway settings

2011-04-22 Thread Aaron Gray
On 22 April 2011 19:28, James Wilkinson wrote: > Aaron Gray wrote: > > I am trying to set up a network and gateway on 192.168.1.x that I am > using > > for BOOTP'ing servers. > > > But I cannot seem to get HTTP or other services to work on 192.168.1.x > > > > I have the existing 192.168.0.x netw

Re: dhcpd gateway settings

2011-04-22 Thread Rick Sewill
On Friday, April 22, 2011 12:11:38 PM Aaron Gray wrote: > I am trying to set up a network and gateway on 192.168.1.x that I am using > for BOOTP'ing servers. > > dhcpd.conf > ~~~ > allow booting; > allow bootp; > ddns-update-style interim; > ignore client-updates; > subnet 192.168.1.0 netm

Re: dhcpd gateway settings

2011-04-22 Thread James Wilkinson
Aaron Gray wrote: > I am trying to set up a network and gateway on 192.168.1.x that I am using > for BOOTP'ing servers. > But I cannot seem to get HTTP or other services to work on 192.168.1.x > > I have the existing 192.168.0.x network and was wondering how gateway > requests should get from 192

dhcpd gateway settings

2011-04-22 Thread Aaron Gray
I am trying to set up a network and gateway on 192.168.1.x that I am using for BOOTP'ing servers. dhcpd.conf ~~~ allow booting; allow bootp; ddns-update-style interim; ignore client-updates; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option broadca