NAT and URL identifier
-
Hello,
I'm having a problem trying to make pfsense detect URL calls. I'll try to explain what I'm trying to do now…
1x pFsense
IP Public: 213.10.10.10 (ex)
2x Lan Computers:
–---- RDPSRV01 (rdp1.mysite.com)
–------- 192.168.1.200
------ RDPSRV02 (rdp2.mysite.com)
–------- 192.168.2.201So atm I have like this, I use the IP 213.10.10.10:3389 to redirect for RDPSRV01 and 213.10.10.10:3390 to redirect RDPSRV02. In Windows it's possible to use DNS and the windows will recognize he hosts several domains. (What I want it the upper quote)
Is it possible to this?
-
No, not really. There's no RDP reverse proxy or anything like this. Either get more IPv4s or get IPv6 working.
-
Well, it's not really a RDP reverse proxy, but more like web adress detection, rdp1.mysite.com goes to IP LAN 1, and rdp2.mysite.com goes to IP LAN 2…
Something like this.. I only said RDP to give a clear view... something like Virtual Host (apache)...
-
There is no generic hostname processor that directs traffic based on incoming host request that I know of. This is something that has to be supported by the server end and by the client. Web servers that support virtual hosts can detect the requested URL and direct the traffic to the specific server, but that's handled by the server itself using information provided by the client.
Instead of deciding on a particular course of action and then asking specific questions, perhaps you could tell us the big picture of what you're really trying to do and we might be able to give you a better solution.
-
I only said RDP to give a clear view… something like Virtual Host (apache)...
Wonderful… Kidding us, right? >:( There's no RDP "virtual host". As said above, describe what are you trying to do instead of wasting other people's time with nonsense.
-
@KOM:
There is no generic hostname processor that directs traffic based on incoming host request that I know of. This is something that has to be supported by the server end and by the client. Web servers that support virtual hosts can detect the requested URL and direct the traffic to the specific server, but that's handled by the server itself using information provided by the client.
Instead of deciding on a particular course of action and then asking specific questions, perhaps you could tell us the big picture of what you're really trying to do and we might be able to give you a better solution.
I think I haven't explain myself the way I want to.. For example, a computer with IIS, can "BIND" several URL to his IP ex: "www.google.com / www.yahoo.com". what I wanted to know if it was possible, was, with pFsense, do exactly the same thing, except, google.com goes to LAN-SRV1 and yahoo.com goes to LAN-SRV2 (pfSense is the external gateway). Sorry for all the confusion I've done..
I only said RDP to give a clear view… something like Virtual Host (apache)...
Wonderful… Kidding us, right? >:( There's no RDP "virtual host". As said above, describe what are you trying to do instead of wasting other people's time with nonsense.
I'm sorry that I make you feel like you are wasting your time, then please, don't reply.. I've been trying to explain what I want to do, apparently not in the correct way (I'm not english native). The last thing I want to do here, is a flame war in this topic.
-
pfSense can assume other IP addresses, but it can't assume domains. You still haven't rally explained what you're trying to do, but I assume you are wanting to internally route one or more services based on the requested domain. We all understand the concept of virtual domains, and all modern web servers support them. pfSense and other routing firewalls support virtual IP addresses but they are not concerned with domains. pfSense by itself has no idea about domains. You can install extra packages like HAProxy to do reverse proxying or load balancing, if that is what you want.