/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Another way I've gotten this to work is to simply run DHCP on the internal interface. Avoids the bother of writing rules to forward DHCP requests between the interfaces. AJ On Wed, 2002-02-13 at 02:29, Tom Christensen wrote: > I've looked, and read, and I've come up empty. > Here's the situation. > external eth0 ip=166.70.187.225 > internal ip=10.0.0.254 > now, I want this machine to masq, but I also need to run DHCP (server) on it, > and hand out IP's in the 10.0.0.0 network to the internal clients. It works > with MASQ turned off (IE. no rules), however, when I put in the rules to > masq, I assume it just forwards all of the DHCP broadcasts from the 10.0.0.0 > subnet to eth0, and therefore the DHCP daemon never gets a chance to respond. Close but not quite. Normally broadcasts (255.255.255.255 in this case) are not forwarded. More likely your DHCP server is being blocked by the rules/policies that you are putting in place. I suggest you take a look at my script (http://www.asgardsrealm.net/linux/firewall). I have a few users that are doing exactly what you are trying to do. Jamin W. Collins _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
