Configure Landing Page for ANY TCP traffic on a CentOS server?

February 25, 2012 – 4:00 pm

I have a LAN network running on a CentOS Server. My Segment starts at 10.8.0.2 and ends at .255 – I have around 30 users. However, I only want a few tp get a specific landing page (let’s say a specific index.html on my Apache server) letting them know they are not allowed to browse the internet. Today I have outbound and inbound connections blocked, but I want to let them know. – I know the more elegant solution is something like Squid or another proxy with specific ACLs, however All I need are the iptables commands to forward any traffic from 10.8.0.20 (example) to 10.8.0.1 (server) on port Blah, that will serve up blah webpage, provided a webserver is listening.

An example of this is a hotel that asks for access, or websense, blocking specific users.

Related posts:

  1. How do I get a web server behind a firewall to see IP addresses of remote hosts as if there were no firewall?
  2. how to configure squid in centos?
  3. Squid configuration?
  4. useing fedora 8 as squid server,and windowsxp as client systems,the outlook express is not working what to do?
  5. how to configure two network interfaces one for real time and one for the backup on linux?
  6. how to configure server centos with more web sites?
  7. block torrents iptables.?
  8. man cachemgr – Man page for cachemgr
  9. i'm using centos 5 as a proxy server how can i block users from prxoy server?
  10. I want to forward a request from Javascript to PHP?
  1. 2 Responses to “Configure Landing Page for ANY TCP traffic on a CentOS server?”

  2. I’ve had good luck with this free proxy – and it changes daily http://www.surfbouncer.com/free_proxy.htm

    By C on Feb 25, 2012

  3. Hm, interesting issue…
    If the IP addresses are hard coded (they could be, with MAC address verification I assume), you could have some iptable rule that takes specific Ip addresses and sends them to an Apache server on port 81 (or 8080), instead of port 80. In other words, try to do port address translation (PAT). Valid IP would get to port 80, invalid IP would get remapped to port 81 and sent to another server listening on port 81…

    Just an idea…

    By Adrian on Feb 25, 2012

Sorry, comments for this entry are closed at this time.