On Fri, 2003-08-01 at 07:45, Sean Vincent wrote: > >Or do as 1,000s of other Shorewall users have done and add the 'dhcp' > >option to the eth1 entry in your /etc/shorewall/interfaces file. > > > > > >-Tom > >-- > > OK. Sorry if I overlooked the obvious. Like I said, it is actually > configured with a static ip, like every other client on my network. These > dhcpdiscover packets are bizzare artifacts resulting from one OS being > built on top of a different OS inside the RTV. The RTV can even lock up on > occasion if it can't find a dhcp server....even when configured as > static. By forcing a fixed address in the dhcp server, I keep the RTV from > assuming two separate addresses. It has worked very well for me for a > while now. Since that part was working so well, I wasn't sure if the > rejection of port 68 and 67 traffic was a bad thing or a good thing. >
Regardless of whatever arcane reason you have for doing so, you are running a DHCP server on your firewall and you need to let Shorewall know which interfaces that server is handling DHCP requests on. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
