Messages

1

24.1 Legacy Series / Re: Unbound DNS doesn't resolve names for un-named hosts

« on: August 20, 2024, 12:19:12 am »

On a whim, I booted the live version of OPNsense 24.7.  Its DNS served both my named hosts and my unnamed hosts.

After fiddling with my 24.1 installation's firewall rules and Unbound DNS configuration for most of a day, I gave up, upgraded to 24.7, and set up DHCP for my various hosts again.

2

24.1 Legacy Series / Re: Unbound DNS doesn't resolve names for un-named hosts

« on: August 15, 2024, 09:57:43 pm »

The output is nearly the same as above.  The only difference is that each host reports that it found one server.

From the host without a name:

Code: [Select]

talmage@otis:~$ dig @192.168.1.1 www.onespeeddave.com
;; communications error to 192.168.1.1#53: timed out
;; communications error to 192.168.1.1#53: timed out
;; communications error to 192.168.1.1#53: timed out

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> @192.168.1.1 www.onespeeddave.com
; (1 server found)
;; global options: +cmd
;; no servers could be reached

From the host with a name:

Code: [Select]

talmage@minerva:~$ dig @192.168.1.1 www.onespeeddave.com

; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> @192.168.1.1 www.onespeeddave.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15615
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.onespeeddave.com.   3600    IN      A       192.168.1.99

;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
;; WHEN: Thu Aug 15 15:53:38 EDT 2024
;; MSG SIZE  rcvd: 65


3

24.1 Legacy Series / Unbound DNS doesn't resolve names for un-named hosts

« on: August 15, 2024, 07:29:55 pm »

Please help me fix this problem: Unbound DNS won't resolve a name when the DNS query comes from a host without a name.

Unbound DNS works just fine when a DNS query comes from a host with a name.

All hosts on my network get an IP address from ISC DHCPv4, which is configured to not deny unknown hosts. ISC DHCPv4 gives each known host the same name each time they ask for a lease.  It recognizes a host by its MAC address.

Here's an example of dig's output on a host with no name:

Code: [Select]

talmage@otis:~$ !dig
dig www.onespeeddave.com
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> www.onespeeddave.com
;; global options: +cmd
;; no servers could be reached

Here's an example of dig's output for the same query on a host with a name:

Code: [Select]

talmage@minerva:~$ dig www.onespeeddave.com

; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> www.onespeeddave.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47178
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;www.onespeeddave.com.          IN      A

;; ANSWER SECTION:
www.onespeeddave.com.   2002    IN      A       192.168.1.99

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Aug 15 13:21:35 EDT 2024
;; MSG SIZE  rcvd: 65

Here is an example of the logging output of ISC DHCPv4 when a host without a name makes a DNS query:

Code: [Select]

2024-08-15T13:27:05-04:00 Notice unbound [34306:0] notice: remote address is ip4 192.168.1.205 port 56220 (len 16)
2024-08-15T13:27:05-04:00 Notice unbound [34306:0] notice: sendmsg failed: Invalid argument
2024-08-15T13:27:05-04:00 Notice unbound [34306:3] notice: remote address is ip4 192.168.1.205 port 53927 (len 16)
2024-08-15T13:27:05-04:00 Informational unbound [34306:0] info: send_udp over interface: 192.168.1.1
2024-08-15T13:27:05-04:00 Notice unbound [34306:3] notice: sendmsg failed: Invalid argument
2024-08-15T13:27:05-04:00 Informational unbound [34306:0] info: 192.168.1.205 www.onespeeddave.com. AAAA IN NOERROR 0.000000 1 38


I'm running OPNsense 24.1.5_3-amd64.

4

General Discussion / Re: Adding DHCP hosts from the CLI

« on: July 16, 2024, 11:45:58 pm »

Stipulating that editing /conf/config.xml is the right thing to do, https://www.reddit.com/r/opnsense/comments/16g5z62/how_to_update_config_via_cli/ says that

configctl dhcpd restart

will tell dhcp about my changes.

5

General Discussion / Adding DHCP hosts from the CLI

« on: July 16, 2024, 07:35:22 pm »

What's the way to add another host to isc-dhcp using the CLI?

My guess is that I can add a <staticmap> stanza for the new host to the <lan> section of <dhcp> in /conf/config.xml .

How do I tell Opnsense to re-read /conf/config.xml and reconfigure dhcpd?

Is this the right way?  Is there a better way via the CLI?

6

17.1 Legacy Series / Re: DLNA on two subnets

« on: August 06, 2017, 10:47:16 pm »

I reframed the query into a request for igmpproxy configuration examples.

Please see https://forum.opnsense.org/index.php?topic=5666.0

7

17.1 Legacy Series / simple igmpproxy configuration examples

« on: August 06, 2017, 10:44:36 pm »

I'm looking for simple examples for configuring igmpproxy.  I can't find any that I understand.

The specific example I want is how to enable a DLNA media renderer on one network to discover a DLNA media server on another network.  But feel free to post other examples here.

Given:
LAN1, 192.168.1.0/24
OPT1, 192.168.2.0/24

a DLNA media server on 192.168.1.10 sending SSDP messages on 239.255.255.250
a Roku4 media renderer on 192.168.2.102

What configuration for igmpproxy will let the Roku4 discover the DLNA media server?

8

17.1 Legacy Series / DLNA on two subnets

« on: July 09, 2017, 11:10:08 pm »

Please help me make my DLNA media server visible on both subnets in my network.  Someone asked for this information in the 16.7 Production Series forum (https://forum.opnsense.org/index.php?topic=3681.msg12592#msg12592) and received no answers.  I hope there is an answer for 17.1.

My DLNA media server is on the 192.168.1.0/24 subnet.  Media players on my 192.168.2.0/24 subnet can't see it.  Why is that?