Menu

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.

Show posts Menu

Messages - dnll

#16
22.1 Legacy Series / Re: os-ddclient
July 23, 2022, 04:14:48 PM
Quote from: Jetro on July 23, 2022, 02:42:28 PM
Hello everyone,

I'm a os-dyndns and NoIP user: never had issued.

Now I'm trying to move to os-ddclient but I can't find a way to make it work.

Any suggestion?

Thank you,
I suggest your start your own thread and add more details about what you have tried so far and what error you are getting if any.

Sent from my Pixel 6 using Tapatalk

#17
22.1 Legacy Series / Re: os-ddclient
July 22, 2022, 06:34:02 AM
Quote from: bunchofreeds on July 21, 2022, 10:18:25 PM
What's the experience like now when using with Cloudflare?

e.g Is it all configured within the GUI and able to use an API Token (NOT the Global API)?

Thanks
Only works with the global API. It does from the webUI however.

Sent from my Pixel 6 using Tapatalk

#18
Quote from: pmhausen on July 17, 2022, 09:18:38 PM
You probably don't need a static lease, but you can use a host override. If it's a name that does not yet exist.
I'm just gonna change its hostname for opnsense a create a host override for "router" then. That should do the trick.

I wish there was a cleaner way to do this.

Sent from my Pixel 6 using Tapatalk

#19
Already tried an override in Unbound without success. I guess I'm going to create a static lease with a different hostname maybe... something like that. I'd rather stick with Unbound right now as it's only a minor inconvenience, and this wasn't an issue on pfSense so I'm sure it can configured somewhere.

Sent from my Pixel 6 using Tapatalk

#20
Quote from: pmhausen on July 17, 2022, 08:47:58 PM
That's a feature of the Unbound integration in OPNsense. I use BIND and manage my zones manually for that reason among others.
As I've self-taught myself through learning pfSense/OPNsense and network in general, could you walk me through the easiest way to have only 10.1.1.1 responds as router on all interfaces, or if it's easier whichever .1 from the subnet the DNS query is made from?

Sent from my Pixel 6 using Tapatalk

#21
I'm aware this thread is 2 years old but... is there any solution to this?

I did try to uncomment the following line an restart the service without any success:

[root@router ~]# grep -i pf /etc/snmpd.config
# pf(4) module
#begemotSnmpdModulePath."pf"    = "/usr/lib/snmp_pf.so"
#22
22.1 Legacy Series / Re: os-ddclient
July 17, 2022, 07:59:35 PM
Quote from: mightyi on July 17, 2022, 04:08:02 PM
Can someone direct me to a guide to configure GoDaddy in the new ddclient?  I've been looking everywhere, but so far found nothing helpful!
I'm new to OPNsense (migrating from pfSense) and what I did is install ddclient and use it for Cloudflare DDNS (it works fine after some toying around) and use de legacy dyndns plugin for GoDaddy which is still supported under the latest stable OPNsense version.

I am also looking for GoDaddy to be properly added to the WebUI of ddclient in OPNsense.
#23
My OPNsense hostname is "router" (I know, very original). I have a bunch of interfaces/VLANs... my problem is that pinging "router" is very inconsistent, and here is why (example coming from the 10.1.1.0/24 subnet):

vm-admin:~ # dig router

; <<>> DiG 9.16.6 <<>> router
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20656
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;router.                                IN      A

;; ANSWER SECTION:
router.                 3600    IN      A       10.1.100.1
router.                 3600    IN      A       10.1.200.1
router.                 3600    IN      A       10.2.30.1
router.                 3600    IN      A       10.2.20.1
router.                 3600    IN      A       10.2.10.1
router.                 3600    IN      A       10.1.1.1
router.                 3600    IN      A       10.2.1.1

;; Query time: 0 msec
;; SERVER: 10.1.1.1#53(10.1.1.1)
;; WHEN: Sun Jul 17 13:53:39 EDT 2022
;; MSG SIZE  rcvd: 163


Of course, on every interface/VLAN, the ".1" is OPNsense itself, however I'd like the DNS to reply either with 10.1.1.1 or whatever ".1" from the interface the request comes from.