OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of alesnav »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Topics - alesnav

Pages: [1]
1
18.1 Legacy Series / dyndns monitoring public IP behind NAT
« on: July 28, 2018, 01:45:47 pm »
Hello,

I am trying to config a dyndns with OVH DynHost, but being behind a NAT. So, my OPNsense does not see the public IP address directly.

There is an existing "OVH Dynhost" option, but I cannot choose to monitor something different than a local interface.

How should I do it? Is there any way to use "OVH DynHost" supported option of OPNsense to monitor the public IP not existing in a OPNsense interface?

I saw the "custom" service type, but it seems that it is linked to an interface, too. Anyway, I don't know how to test it with OVH DynHost, nor how to create a cronjob to check it every 15 minutes instead of linking it to a interface status change.

Thanks,
Best regards

2
18.1 Legacy Series / iodine install
« on: July 27, 2018, 09:44:42 pm »
Hello!

I am trying to install iodine to work as VPN over DNS server. I saw that iodine is in the OPNsense ports list but I am not able to install it using "pkg install iodine"

root@firewall:~ # pkg install iodine
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'iodine' have been found in the repositories
root@firewall:~ #

How can I install this package?

Thanks!

3
16.7 Legacy Series / Syslog TCP
« on: November 08, 2016, 07:09:16 pm »
Hello there!

It is not possible to send syslog messages using TCP from OPNsense, althought most syslog clients allow this option.

It could be implemented adding a new checkbox (enabled = TCP; disabled = UDP) next to each remote syslog server configured in "System > Settings > Logging" section.

The only thing to add would be an IF clause to set @IP if that checkbox is unchecked and @@IP if that checkbox is checked.

Many companies use some load balancers to manage the syslog traffic and it is better doing it via TCP. For example, the balancer included in OPNsense does not support UDP balancing :P . In addition, TCP gives more confidentiality to every log sent this way.

Thanks,
Best regards

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2