Messages

1

21.7 Legacy Series / OpenVPN server remote networks

« on: October 14, 2021, 06:16:51 pm »

I have problems with the routes to remote networks.
This is not an issue with spaces in the config.. :-)

My configuration consists of an OpenVPN server with IPv4 Tunnel Network 10.0.3.0/24 and "Address Pool" and "Topology" set.
So my first client gets 10.0.3.2.
When i set IPv4 Remote Network "10.144.16.0/22,10.0.200.0/24" in server settings and client specific overrides these routes get set:
10.0.200.0/24      10.0.3.2           UGS      ovpns5
10.144.16.0/22     10.0.3.2           UGS      ovpns5

Which of course is only valid if the client is the first client which connects.

In the client specific overrides I also set the IP of the client: Advanced: ifconfig-push 10.0.3.2 255.255.255.0;

How do I get the route set correctly?

Thanx for any help!

2

20.1 Legacy Series / Captive Portal Radius Access-Request missing Calling-Station-ID

« on: March 02, 2020, 06:35:20 pm »

Hi Team!

I would like to use the captive portal of OPNsense 20.1 and manged to configure it all right. So far everything is working but my radius-server (HP-MSM Controller) is dropping the access-requests because of missing the calling-station-id. I reviewed the packages with wireshark and there is no calling-station-id or called-station-id. Also the NAS-Identifier is some strange number.
Is there a way to set or populate this fields? As I understand most radius servers need this values to make some intelligent access-rules.

Thanks!
Jueregn

3

17.7 Legacy Series / Re: pptp reconnect needs filter reload

« on: October 14, 2017, 10:41:53 pm »

Hi Franco,

sorry for the delay, I did some more testing. 16.7 was an estimate, actually I have the Problem since my first install of OPNsense which was 16.1 (I found the install image on my ESXi).
To help debugging I did a fresh install of 17.7 followed by update to 17.7.5 without touching the firewall-rules. I just created the pptp connection and the problem is the same.
I can share the logs but first let me tell what the tests showed:
LAN is em0 (192.168.10.0/24)
ModemNet is em1 (10.0.0.140/24)
WAN is pptp0 (adddress *.*.*.* via pptp)
The modem sits on 10.0.0.138 and after restart or filter reload I can ping it from the firewall.
After pptp is established I can no longer ping 10.0.0.138 even when all packet filtering is disabled.
The routes are like this:
Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            217.25.113.2       UGS       pptp0
10.0.0.0/24        link#2             U           em1
10.0.0.140         link#2             UHS         lo0
10.0.3.0/24        10.0.3.2           UGS      ovpns1
10.0.3.1           link#8             UHS         lo0
10.0.3.2           link#8             UH       ovpns1
*.*.*.*      link#9             UHS         lo0
127.0.0.1          link#5             UH          lo0
192.168.10.0/24    link#1             U           em0
192.168.10.1       link#1             UHS         lo0
217.25.113.2       link#9             UH        pptp0

When I ping 10.0.0.138 from the firewall I get nothing back and pfTop-State shows:
icmp      Out *.*.*.*:11868                  10.0.0.138:11868                               0:0            00:01:56  00:00:10      229    19236      165   71 10.0.0.138:13083   

For me this looks wrong, as the modem can not know where *.*.*.* is, so there can be no answer.
But even if I specify the Interfave (ping -S 10.0.0.140 10.0.0.138) the output of pftop shows x.x.x.x as SRC.
BTW the tunnel shows up as:
gre       Out 10.0.0.140:0                                  10.0.0.138:0                                     MULTIPLE:MULTIPLE     04:09:29  00:01:00   501361  419039K                                 

which looks OK.

hmmm

Thanks,
Juergen               

4

17.7 Legacy Series / Re: pptp reconnect needs filter reload

« on: October 08, 2017, 01:31:25 pm »

Hi Bart,

I really mean PPTP. For some obscure historical reason nearly all ADSL-Providers in Austria use PPTP. Basically you create a V VPN to your modem which connects to your provider. Modems in Austria are provided by the internet-provider and not exchangeable....

I am using E1000 (emulated Intel card) for the WAN and LAN Ports and they are connected to a vSwitch. The VMware tools are installed.

There are no other problems beside the re-/connection problem. I am using NAT from the LAN to the WAN and some port forwarding.

My main problem ist that if the connection goes down and I am not on site I have no way of reestablishing the connection, so for a start some code to do a filter reload or pf restart via cli would help a lot. But I am willing to debug this fully.

Thanks!
 

5

17.7 Legacy Series / pptp reconnect needs filter reload

« on: October 07, 2017, 11:44:22 pm »

Hello!

I am running OPNsense 17.7.5-amd64 on vmware ESXi 6.5.
My WAN-connection is via PPTP on an ADSL-modem.

Problem:
Every time when the WAN-connection goes down (eg. modem reboot or provider resets the line) pptp can not reconnect to the modem. The modem sits on a separate interface(em1) and I can no longer ping it after the pptp comes up.
The Point-to-Point Log shows connection attempts but gets no answer from the modem. To reconnect I have to restart pf via the dashboard.
This problem is present since at least 16.7 and then my solution was to do a filter reload via cron-jobs and ifup/down, but filter reload is gone and I suspect this behavior is not expected.
Of course I checked my firewall rules but i am unable to spot an error.

Please can anyone help me with that?

Thank you very much!