Or just plug it into the WAN and then it is zero config on the wirless/router device. The WAN port will get an "internal" address, and it will be a double NAT, but I think that would be easier then instructing people to disable this, change that, etc.
Robert On 8/30/07 4:34 PM, "Michael L Torrie" <[EMAIL PROTECTED]> wrote: > Joshua Draper wrote: >>> The reason is that with the fitlering, you are using a proxy which is >>> actually doing the talking for the client to the various servers. >>> It's a >>> middle man and as such needs to be able to send traffic and receive >>> traffic >>> which requires an IP. >> >> I was thinking something along those lines, but I was not sure. >> Thanks for the clarification. > > You're right of course. I've built plenty of bridging firewalls over > the years that actually were completely invisible. No IP address > whatsoever. But the machine only did packet filtering, not proxying. > > To get this working on a single-IP comcast network, what you'd want, > then, is to connect the box to the cable modem, then connect the other > interface to the wireless access point in one of the LAN slots, not the > WAN port. THis makes the WAP a mere switch. Configure the WAP to have > an address like 192.168.1.2, and make the filter box 192.168.1.1. Then > you turn off DHCP and all firewalling on the WAP. The filter box now > becomes the DHCP server, the DNS proxy, and the filtering proxy. > > Michael > > >> >> Joshua Draper >> Department of Civil and Environmental Engineering >> Brigham Young University >> >> >> >> >> >> >> -------------------- >> BYU Unix Users Group >> http://uug.byu.edu/ >> >> The opinions expressed in this message are the responsibility of their >> author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. >> ___________________________________________________________________ >> List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list >> > > -------------------- > BYU Unix Users Group > http://uug.byu.edu/ > > The opinions expressed in this message are the responsibility of their > author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. > ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list > Robert LeBlanc College of Life Sciences Computer Support Brigham Young University [EMAIL PROTECTED] (801)422-1882 -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
