Public IP to Client
-
Hello,
you can create Alias IPs on your WAN Interface and then 1:1 NAT them to the internal servers.
Kind reagards
-
for this i have to use private ip in internal server and then NAT 1:1 .. but actually i directly want to give public ip to internal server tht will be routed through pfsense
-
Well if the netblocks are actually routed to you.. Then just create the routed netblocks and networks behind pfsense, and then all you have to do is all the traffic in the firewall
So take one of those /29 or all 4 of them and put them on networks on the lan side of pfsense.
So for example change pfsense lan interface to x.x.x.1/29 and then your clients on this network could be .2 - .6
Or create a new optX network where this /29 will be connected behind pfsense.
-
https://www.netgate.com/docs/pfsense/firewall/virtual-ip-address-feature-comparison.html
-
@johnpoz said in Public IP to Client:
optX netwo
when i try to put my public ip on lan interface i got this error
"A valid interface to track must be selected."
"This IPv4 address is the network address and cannot be used" -
So what are you entering as the interface address and netmask?
-
@derelict said in Public IP to Client:
So what are you entering as the interface address and netmask?
public ip and the subnet mask 29 for example x.x.x.x/29
-
Ah. When you set that set IPv6 to none.
If you still get an error you are at least going to have to give us the last octet of the address there.
-
@derelict said in Public IP to Client:
Ah. When you set that set IPv6 to none.
If you still get an error you are at least going to have to give us the last octet of the address there.
this error comes now
IPv4 address 167.114.2x.232/29 is being used by or overlaps with: WAN (167.114.21x.84/1)
This IPv4 address is the network address and cannot be used -
@problemmaker said in Public IP to Client:
167.114.21x.84/1
So you have to find where that is configured.
Diagnostics > Routes might show you. That /1 netmask might appear as 128.0.0.0.
-
@derelict said in Public IP to Client:
@problemmaker said in Public IP to Client:
167.114.21x.84/1
So you have to find where that is configured.
Diagnostics > Routes might show you. That /1 netmask might appear as 128.0.0.0.
actually if i dnt use /1 netmask in wan side my wan ip does not response .. because my provider give me 255.255.255.255 mask and gateway is other subnet .
-
Not sure what to tell you there. That is unlike any ISP shenanigans I have seen before.
Maybe someone else knows.
-
@derelict said in Public IP to Client:
Not sure what to tell you there. That is unlike any ISP shenanigans I have seen before.
Maybe someone else knows.
it is an OVH
https://docs.ovh.com/gb/en/cloud/dedicated/network-bridging/
https://docs.ovh.com/gb/en/cloud/dedicated/network-ipaliasing/ -
@problemmaker What settings does your ISP propose? Ask them to come up with a decent solution (starting with your gateway).
Don't try to hack something together that might seem to work now. It will byte you in the long run.
BTW, you usually get a /32 mask with PPP links.
I have something like
111.2.3.4 /32 GW 111.9.8.7
on my WAN, and always had. Revert to that first and see why it doesn't work in your scenario. Once you figured that out the rest should be easy. -
Forget it, Jake. It's OVH.
