**I desire an application that would sit on my company router and receive the requests coming from the www. This application must then be able to extract the HOST request from the header. I would then like the application to forward the request to the correct internal computer, based on the configuration settings.
**
## Deliverables
>Continued from above
For example rule 1 would send users who requested [login to view URL] to the internal server on [login to view URL] on port 80. And rule 2 would send users who requested [login to view URL] to the internal server on [login to view URL] on port 8080. *(-h = host, -d = destination)*
*Rule 1:*
-h [login to view URL] -d [login to view URL]
*Rule 2:
*-h [login to view URL] -d [login to view URL]
The application must run from the command line, our only configuration of the router it using the telnet service from our internal network. We would like the console application to use the following commands (small variations are acceptable!). Lets assume the application was called *hostforward*
*For adding a rule:*
hostforward -add -h [login to view URL] -d [login to view URL]
hostforward -add -h [login to view URL] -d [login to view URL]
*For viewing all rules:(list of all rules would be shown)
*hostforward -view
*For deleting a rule:
*hostforward -delete 1
*For starting the service:*
hostforward -start
*For stopping the service:*
hostforward -stop
In regards to the command for deleting, I would like each rule to be assigned a number that I would be able to see listed when I performed the -view command. Therefore -delete 1 removes rule 1. Another important feature is the support of wildcards (*), but only specifically one usage i.e
hostforward -add -h *.[login to view URL] -d [login to view URL]
This rule would send all request for the domain [login to view URL] to the destination computer [login to view URL] on port 9090 if another specific rule for that host does not exist. So requests for _www.example.com_ would still reach [login to view URL] but a request for [login to view URL] that has not specific rule would use the wildcard rule. No other wildcard support is required.
The application should also ensure that the client IP address is forwarded in the header, so the requests appear to come to the internally networked computers not from the router/firewall.
Instructions on how to configure the iptables to work with your application is also appreciated.
I would like to run the application from the directory /usr/sbin/ and have any of the application config files in the directory /etc/rc.d/hostforward/
**I am willing to offer a bonus** for fast work and most importantly if all functionality is met. **I would appreciate bids that include a dumbed-down prototype application**, where I could sample your work.
Thank you,
Scott McArthur
* * *
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. With configuration settings to make it compatible with Linux iptables if applicable.
2) I would like the file to be package in a zip file not a [login to view URL] file. I will then extract these files on my windows computer and FTP them to the router.
3) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site).
4) The application must be console based - no graphical user interface. The application must be command based, and should therefore be able to be incorporated into my linux router startup script.
5) The application must be efficient and fast and should be no bigger than 2MB !
## Platform
Embedded Linux & IPTABLES compatible
- I can only access the os through TELNET. The app will be run as ROOT.
(The internal www servers use Windows but this should not effect the application development as far as I am aware)
---
Just another quick note to put forward my scenario:
I currently use IPTABLES to route my web server traffic to my internal network web server. This means that all the traffic for all my domains ends up in the one place, which is sometimes impractical. Another issue I had with using IPTABLES forwarding was all the external www requests appeared to be from the router, which was no use for my site security scripts.
So what I am trying to achieve is getting a program that will run at the router and send requests for certain domains (HOSTS) to certain internal computers. While also fixing the IP problem.
I hope this clarifies things. I know that a DMZ could be used but i dont wish to go down that route.