Project

General

Profile

Actions
Copy link

Bug #6075

closed

diag_dns.php creates invalid alias for long hostnames

Added by George Steketee about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Chris Buechler
Category:
Diagnostics
Target version:
2.3
Start date:
04/04/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

When attempting to enter "192-168-1-10.8ddbaeb8d2e446859c9d76e9474ee02a.plex.direct" as an alternate hostname in the advanced settings page for DNS rebinding, receive the following error:

/rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:26: table name too long, max 31 chars - The line in question reads [26]: table <192_168_1_10_8ddbaeb8d2e446859c9d76e9474ee02a_plex_direct> { 192.168.1.10/32 }

Because wildcards are not supported in this field, I have to disable rebinding checks entirely to get Plex to work properly in my local network.

Actions
Copy link
 #1

Updated by Chris Buechler about 8 years ago

  • Status changed from New to Feedback

That's not from adding an alternate hostname for DNS rebinding, that's from a pf table, which is unrelated to that. Looks like you have an alias with that name, which is too long (and the GUI normally wouldn't allow). How'd you configure the alias with that name?

Actions
Copy link
 #2

Updated by Chris Buechler about 8 years ago

  • Subject changed from Cannot enter "alternate hostname" for DNS rebinding checks that is longer than 31 characters to diag_dns.php creates invalid alias for long hostnames
  • Category set to Diagnostics
  • Assignee set to Chris Buechler
  • Target version set to 2.3
  • Affected Version changed from 2.2.x to All
  • Affected Architecture added
  • Affected Architecture deleted (amd64)

Pretty sure subject is where you ended up with the too-long alias name. Fixed that page to truncate hostnames that are too long.

You can fix yours going to Firewall>Aliases, edit the alias with that name, and shorten the name. The input validation on that page prevents it from being too long.

Actions
Copy link
 #3

Updated by Chris Buechler about 8 years ago

  • Status changed from Feedback to Resolved

works

Actions
Copy link
 #4

Updated by George Steketee about 8 years ago

Chris Buechler wrote:

Pretty sure subject is where you ended up with the too-long alias name. Fixed that page to truncate hostnames that are too long.

You can fix yours going to Firewall>Aliases, edit the alias with that name, and shorten the name. The input validation on that page prevents it from being too long.

Wow, that's really interesting. I didn't intend to manually configure any aliases, but when I looked there sure was one there. It looks like it was created from the "Create Alias from these entries" button in the DNS lookup utility (using the same too-long DNS name). It didn't immediately throw an error and the error seemed to reappear whenever I applied the settings in the advanced page with the too-long content in the alternate hostname field, but that must not have been the case.

Thanks!

Actions
Copy link

Also available in: Atom PDF