I guess this is too many questions at once!
The first and main issue is:
If I add a second network interface to my existing linux box, how can grant access only to the web-server to traffic through this new interface. Is this best done with iptables configuration or routing or what?
Thanks for thoughts or links/references on this task,
/..
##----- original post follows:
Running RH9 and Apache 2.0.40
I have some web sites that I would like to share with several computers in wireless range. I bought a wireless router for like $9.00US. (that is cheap) I would like to add a second network card (eth1) to this box and serve the web using the wifi features of the router; it will not be connected to my lan, and its wlan/routing features are not needed either.
I believe that adding the NIC will not be too difficult, I have succeeded at this before. But I would like only to allow access to port 80(http) and possibly 443(https) and 21(ftp) through the wireless router and its interface (NIC). No connection to the samba server, mta, ssh, or any other daemon or process should be possible.
How can I achieve this? Is it enough to use features of the router? (Belkin F5D7230-4 v.2000) Is there some iptables configuration to consider? Are there various routes to set? Anything else?
In order to serve only part of the content that is normally available from this web server, what sort of modifications should I look to make in Apache's configuration? I have never approached this type of question before, so I'm a bit clueless; am I looking at a 'Virtual server' config based on the nic (mac or ip address)? Further, is it possible to use a per-user config, based perhaps on a logon & cookies (thru Apache) or by MAC address of the client, to allow various levels of ability -- such as access to more or different content?
thanks,
/..
