dhcpd gateway settings

[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/ip_forward 
as root (I believe).

Aaron said:
> I need DHCP to serve the BOOTP protocol, so static IP's other than the
> laptops don't really help.

You will need bootp finally: understood. But for the moment, it means
you’re trying to fix way too much at the same time. A basic principal of
troubleshooting is to minimize the complexity of what you’re working
with at the moment.

If you’ve got anything else that can take a static IP address, give it
one on the 192.168.1/24 network, turn off firewalls (except on the
Netgear), and check that you can get between that device and the
Netgear.

You may want to use the route command to check: on the 192.168.1/24
network, everything (*apart* from the laptop) should have a default
gateway of 192.168.1.142 (*IF* that is the laptop).

On the 192.168.0/24 network, things are more complex. Most of them will
have a default gateway of 192.168.0.1 (for the Netgear). The Netgear
itself will need to know that 192.168.1/24 is behind 192.168.0.140. On
my Netgear, that’s set under Advanced -> Static Routes. The Destination
IP Address should be 192.168.1.0, the IP Subnet Mask will be
255.255.255.0, the Gateway IP Address will be 192.168.0.140, and it
really doesn’t matter what the Metric is.

You will also have to set something similar on any other 192.168.0/24
devices which will need to access the 192.168.1/24 subnet. In
NetworkManager, there’s an Edit button per interface, an IPv4 Settings
tab behind that, and a Routes button.

Hope this helps,

James.

-- 
E-mail:     james@ | Just remember: 1 virus         3 viriii
aprilcottage.co.uk |                2 virii         4 viriv
                   |     -- Matt S Trout