Messages

1

General Discussion / Monit specify ping interface

« on: July 15, 2024, 02:22:09 pm »

Hi all,

I have a Service monitoring using Monit with "Remote Host" type. I also have an OpenVPN Client setup, and would like to monitor a remote host via this tunnel. However, when I add the service, it goes through the WAN default route, instead of the OpenVPN client. I tried to force it via an explicit route, but it still the same. Do you know if there is any way to force monit to ping using a specific source iP? otherwise is there a workaround using some magic routing?

2

22.7 Legacy Series / monitor packet loss on interface and trigger action

« on: February 17, 2023, 10:55:48 am »

Hello,
I have an OpenVPN client tunnel interface (opt2) , under which I have a gateway configured with gateway monitoring enabled. Sometimes the VPN server from the provider side is overloaded, and that induces a packet loss. The packet loss is clearly seen in the RRD graphs. To fix the packet loss problem I simply need to restart the OpenVPN client, and get assigned to a new server pool that is not overloaded.

My question is the following: can I define a packet loss threshold that will trigger an action? the action would be to simply restart the OpenVPN client.

Thanks

3

Virtual private networks / Re: force Zerotier outgoing interface

« on: July 20, 2021, 09:49:23 pm »

Thanks Cerberus
I have reviewed the config manual, and found that I can do this

{
    "settings": {
        "interfacePrefixBlacklist": [ "ovpnc" ]
    }
}

4

Virtual private networks / force Zerotier outgoing interface

« on: July 14, 2021, 10:43:53 am »

Hello
I have installed zerotier plugin and everything is working as expected. In my OPNsense setup I also have OpenVPN clients connected to the outside world and assigned to interfaces. On the zerotier management portal I noticed that OPNsense is connected using one of the OpenVPN client IPs.
Is there a way to force it to use the WAN interface only? my WAN interface is vtnet1. I tried the following zerotier configuration without success.

{
  "settings": {
    "defaultBondingPolicy": "aggressive-active-backup",
    "policies": {
      "aggressive-active-backup": {
        "links": {
          "vtnet1": {
            "ipvPref": 4,
            "mode": "primary"
          }
        }
      }
    }
  }
}

5

20.7 Legacy Series / dnsmasq and dhcpd static entries not resolved

« on: October 12, 2020, 03:05:45 pm »

Hello guys,

I searched this forum before posting this message, so I hope I'm not duplicating this topic.
I have a very basic DHCP setup on my home network (see attachment dhcpd config). I wanted to add custom hostnames for some hosts on my network, like my android tv, so I would be able to resolve it as tv.mydomain.com

In order to do that, I have added static leases under the DHCP configuration for some hosts (see attachement dhcpd static entries).

My DNS server is dnsmasq with the needed options enabled (see attachement dnsmasq config).

Under DHCP leases (see dhcp leases), I see some hosts have been served and registered, with dynamic hostnames, like laptop-xxxx and when I query them using nslookup I get a good response. Same for the PTR record.

The problem happens, when I query a host with a static hostname set in DHCP configuration.

For now I have checked the /var/etc/dnsmasq-hosts and I can see the dynamic hosts being registered in this file and served by dnsmasq, however the static hosts are not in this file.

Under /var/dhcpd/var/db/dhcpd.leases I find the static defined hosts in that file, however without the "client-hostname" option

Under /var/dhcpd/etc/dhcpd.conf I can see my static hosts defined as part of the configuration

How can I proceed from here?