Messages

I have locked many dynamic IP addresses and this have never happen before and i have been running OPNsense for many years and before that pfSense.

Why should i lock a static IP address? It is already static set in the computer, so there is no need to lock it.

It is also called "DHCP Static Mappings". If this was only for static IP addresses it should only be called "Static Mappings".

If i lock a MAC address no other computer should be ably to get that IP address if it has another MAC address.

If you are saying it should be like this i have to live with that. I can't to anything about it anyway ...

That makes no sense.

The whole idea is to use dynamic IP address, but still be able to get the same IP address after every reboot.

If i use outside of the dynamic pool i have no use of "DHCP Static Mappings".

Computers I run as a server I always set a static IP address (DHCP Static Mappings for this interface).

This computer has always been using 192.168.2.110.

Yesterday i replaced the motherboard with a complete different brand and model, but when i looked in the "Services: ISC DHCPv4: Leases" i could see the old motherboard as a lease type static at 192.168.2.110 and the new motherboard as lease type dynamic at 192.168.2.110.
The static was offline (red) and the dynamic was online (green).

They both have different MAC addresses and i could connect to the new motherboard on 192.168.2.110.

I then edit the "DHCP Static Mappings for this interface" and changed the MAC address and the dynamic lease type changed to static and the dynamic was gone.

How is it possible that a computer with a complete different MAC address can get an IP address that is set to static?

After removing:

Code Select Expand

    <openvpn>
      <internal_dynamic>1</internal_dynamic>
      <enable>1</enable>
      <if>openvpn</if>
      <descr>OpenVPN</descr>
      <type>group</type>
      <virtual>1</virtual>
      <networks/>
    </openvpn>
from config.xml the OpenVPN is now gone from Firewall / Rules.

I have the exact same problem on my OPNsense 24.1.3_1-amd64.

I ran a site 2 site VPN and it is completely gone on one of my OPNsense, but not the other one.

I'm trying to get OPNsense_C (OpenVPN Client) to connect to OPNsense_S (OpenVPN Server) and make OPNsense_C use OPNsense_S to connect to the internet.

I have manage to connect them both with OpenVPN and the OPNsense_C can ping computers on the OPNsense_S , but whatever i do, it can't get OPNsense_C to connect to the internet through OPNsense_S.

It is a bit confusing if i should add rules on Floating, LAN, OpenVPN, S2S_VPN (the vpn interface) or the WAN.

I have tried to find some kind of help/guide, but i haven't manage to find any. :(

I know ASUS routers have an option for it (Client will use VPN to access: Internet and local network), so assume it is possible to get this to work on OPNsense too?

I haven't tried the new "Instances" in OPNsense, because it is giving me a headache. I don't see how this should make it easier to create OpenVPN servers and clients. It is way more confusing than the old way.

I did tried "Instances", but i gave up after a couple of hours.

I know it is hard to guide someone else's network, but some kind of guidance would be really appreciated.

First i need a rule on the Client to get the computers to use the VPN connection and i think i have manage to get that to work. :)

The problem is on the Server side, how do i get the computers connect to internet on the Server side?

All kind of help is appreciated, big or small.

Maybe you have manage to find some instructions or can point me in the right direction?

I'm not giving up that easy, but now I'm stuck here and need some help.

It seems that we are back to use User name and password on FreeDNS. So, now it is working  :D

Update: I was wrong... It is not working :(

FAILED: Could not get freedns update URLs from freedns.afraid.org

WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).

WARNING: file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''

I hope you will fix all the bugs before you remove the legacy version ...

I can't get the os-ddclient 1.3 to work with FreeDNS. After adding token to password field (as in the old plugin) it will disappear even if i save it. I have even tried adding it to user name. Here it will be saved but it will still not work.

I can't use ( or ) in the description field either. It will show this error message:
Description should be a string between 1 and 255 characters

Will there be a widget for this plugin too?

I'm also an old pfsense user and that separator was really really nice. When you have many entries it will be so much easier if it is possible to separate them. I really hope the devs reconsidering this and add a separator or at least something similar.