see local network ip address on pfsense
-
Indeed. In a TLS/SSL OpenVPN tunnel all the routing and tunnel details are passed to the client by the server.
You do not need to set those details on the client.Steve
-
I should have added IPv4 continued to work, as I had the same subnet, but IPv6 broke, as the new hardware resulted in a new prefix.
-
@jknott @stephenw10
I give up I'm not able to connect opnvp I tried everything but nothing wrong something. I followed all the guides but one that worked and simple to do is not there. Now I restore the previous configuration thanks :-( -
@antonio-briguglio Maybe setting up an OpenVPN server is a bit over your current abilities:
@antonio-briguglio said in IP Pfsense:
Hi, in the SG-1100 the ip address is 192.168.1.1/24
Does this mean that the SG-1100's IP will have to vary between 192.168.1.2 and 192.168.1.24?
Exact?First you have to understand the basics. Setting up an OpenVPN server is not basic.
-
@antonio-briguglio
Have you tried using the Wizard? I've never bothered with it, but it apparently makes things simpler.
PfSense running on Qotom mini PC
i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
UniFi AC-Lite access pointI haven't lost my mind. It's around here...somewhere...
-
Yuo, I always use the Wizard for a RA server. Much quicker. You can easily make adjustments afterwards.
Steve
-
@jknott said in see local network ip address on pfsense:
Have you tried using the Wizard?
These are ment to be used by people who already know how it works.
Like : "stance out a frame work and fine tune afterwards".
Please don't tell me know that it is the other way around ... -
@gertjan @jknott @stephenw10 @jahonix It is absolutely not true that I don't have the basics to configure an openvpn.
The problem is not the configuration of an openvpn, but the configuration of the pfsense firewall which unf.ortunately I cannot understand which of the settings I have put in pfsense blocks the connection with the server.
Netgate does not provide a guide in which it says that to configure an openvpn some settings may conflict and I have not found anything about this on the net.
I conclude that the configuration I made is correct, the problem of conflicts remains -
What are you trying to do exactly?
http://docs.netgate.com/pfsense/en/latest/vpn/openvpn/configure.html
But as mentioned the wizard is the fastest easiest way to setup a road warrior setup.
You don't know what your local network is? As mentioned this would your lan network, or your other networks you setup on pfsense.
192.168.1.1/24 is not it - that would be a host address, not a network address.. If pfsense lan IP is 192.168.1.1/24 then your local network would be 192.168.1.0/24
This would tell your vpn client - hey you want to get to 192.168.1.0/24 come down the tunnel.
For your remote client to connect to pfsense - it would need the wan IP to connect to.. All of the info for your clients can be exported with the openpvn export package. Just pick your wan address. Unless your behind a nat on you pfsense wan?
-
@johnpoz pfsense's IP is 192.168.1.1/24, so the local network is 192.168.1.0/24.
The tunnel network I put 10.29.30.0/24
the three certificates have been activated, the profile burning too.
Then he imported the client configuration for android on the openvpn app I put username and password and it tells me wait for connection to the server and then it stops.
But is it because I have an access point connected in lan wifi that has another ip address? -
-
If pfsense is behind a nat router, then you would have to forward your vpn port to pfsense wan, if you want remote clients to be able to get to the vpn running on pfsense.
If your AP is actually wifi router and your natting again?
-
Yes, you are behind the Fritzbox and it is in router mode.
So if you are connecting from an external public IP the Fritzbox will need to be forwarding OpenVPN traffic to pfSense.
Steve
-
@stephenw10 Please tell me how should I do?
attach screenshots thanks -
You need to forward port 1194 (the default OpenVPN port) in the Fritzbox.
I can't make screenshots of that.
Where are testing from? What IP address does your Android client have?
Steve
-
@stephenw10
I on the Fritzbox I have activated the vpn
The access point is not reachable by vpn as the functions that require a public IP address (for example, port sharing and incoming VPN connections) may not be fully usable
Therefore the OPENVPN must access both the devices connected on the access point and the devices connected to the fritbox -
@stephenw10 With the openvpn app I connect from both tablet and android smartphone.
They have no fixed but dynamic public ip -
@stephenw10 So the openvpn server configuration is correct the problem and that the openvpn app does not connect to the server.
note the access point is configured with the same gateway as the fritz and active dhcp -
On the fritz you cannot forward port 1194 you can enable them for devices
https://en.avm.de/service/fritzbox/fritzbox-7490/knowledge-base/publication/show/34_Setting-up-port-sharing-in-the-FRITZ-Box/ -
@antonio-briguglio said in see local network ip address on pfsense:
On the fritz you cannot forward port 1194 you can enable them for devices
That's a non issue.
By default, an OpenVPN server listens on port 1194.You can have a OpenVPN server listening on your first router - on its WAN interface : your frits box.
You can have a OpenVPN server listening on your second router / firewall - on its WAN interface : your pfSense box.Now, the solution :
NAT on the frits box, on it's WAN interface, port ....... 1195 ( !) to the LAN IP (point of view : frits box) - to the IP of pfSense - and have the port mapped to 1194 (as pfSense us listening on 1194).
Or, even easier : instruct OpenVPN on pfSense to use port 1195.
And make a 1195 to 1195 (port ) classic NAT rule from Frit's WAN to LAN (IP of pfSense).Tell your VPN clients (edit the ovpn config file) that the port is now 1195.
Done.
Edit : NAT = Network Address Translation. But nearly always NAT can also do PAT : Port Address Translation.
