<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 12, 2015, at 10:26 AM, Jeremy Malcolm <<a href="mailto:jmalcolm@eff.org">jmalcolm@eff.org</a>> wrote:</div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><br>
<blockquote cite="mid:2E24D15D-3F71-45FC-A37C-D974B28EA1AF@selwastor.com" type="cite">
<div>
<div>Rather can you please explain the problem you are trying to
solve.
<div>Perhaps there is a way to achieve without large changes.</div>
</div>
</div>
</blockquote>
<br>
Here is what my network looks like:<br>
<br>
<tt>+---------+ +-------+ +-------+ <br>
|DSL modem+----+ Linux +----+ Apple | <br>
+---------+ | box | |airport| <br>
+---+---+ +-+----++ <br>
| | | <br>
| | | <br>
+--+--+ + + <br>
| VPS | eth wifi<br>
+-----+ <br>
</tt><br>
The DSL modem is currently in bridge mode which means it is
invisible to the network, the Linux box receives the WAN IP address
from my ISP and is currently doing the NAT and DHCP, and the Airport
is also in bridge mode and is only responsible for putting its
ethernet ports and wifi onto the same network as the Linux box.<br>
<br></div></blockquote><div><br></div><div>So the OpenWireless router is to replace the Apple airport, I assume. </div><div><br></div><div>How important is it that the ethernet ports and wifi be on the same network </div><div>as the linux box ? If it is not critical (if some thing breaks because of </div><div>additional networks for eth and wifi let me know, there are probably </div><div>relatively simple changes on the openwireless router that can fix</div><div>that). </div><div><br></div><div>Alternatively (and preferable from a security viewpoint) is to connect the </div><div>WAN port on the OW router to the DSL modem and let it get address from </div><div>ISP via DHCP and do the NAT. Then have your linux box connect to an </div><div>ethernet port on the OW router (possibly with additional NAT). That way </div><div>the openwireless traffic never comes inside your network -- going straight </div><div>to the ISP. We put in strong firewall rules to prevent OW users from </div><div>accessing anything on your internal network. If there are certain ports that </div><div>need to be opened on the OW router so services on the Linux box/VPS </div><div>are accessible, that is relatively easy to do. </div><div><br></div><div>Let me know if either of these options will work for you.</div><div><br></div><div>Ranga</div></div><br></body></html>