That's why I stay away from the starter scripts. Learning how to hand code your tables works much better. I tried a while ago to use the shorewall scripts and the RH firewall tools both really screwed up the rules I wanted set. It seems like they expect eth0 to be external and eth1 to be internal but mine are always the other way. I set my internal first before I let it the box hit the internet just seems like the smarter thing to do.
-----Original Message----- From: Vidiot [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2003 1:40 PM To: [EMAIL PROTECTED] Subject: Re: DHCP appears not to be working >Did the firestarter open the dhcp ports? I think it broadcasts on port 68 >TCP/UDP When I ran the firestarter wizard, I added DHCP to the list of stuff I run. After that it worked. Here are the $64,000 questions: 1) Why is firestarter setting up the firewall to block stuff from eth1, my internal lan, when I ran the wizard and gave it eth0 as the device? 2) Why is firestarter letting VRAS (the Philips VPN software, which I believe uses port 500) get through the system, or is that because I'm not trying to VRAS to my box, but having it port forwarded out of the box? Thanks. MB -- e-mail: [EMAIL PROTECTED] /~\ The ASCII \ / Ribbon Campaign [So it's true, scythe matters. Willow 5/12/03] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
