Bug #6869: Diagnostics / Routes Truncates Destination and Gateway Names - pfSense - pfSense bugtracker

Actions

Copy link

Bug #6869

closed

Diagnostics / Routes Truncates Destination and Gateway Names

Added by Daryl Morse about 8 years ago. Updated almost 8 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

Web Interface

Target version:

2.3.3

Start date:

10/20/2016

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.3.2

Affected Architecture:

Description

When "resolve names" is enabled, resolved destination and gateway names are truncated to 18 characters (e.g., pfSense.localdomai).

When "resolve names" is not enabled, destination and gateway names are at least 28 characters (e.g., fe80::215:5dff:fe5c:e205%hn0).

Actions

Copy link

Updated by Phillip Davis about 8 years ago

That is a "feature" of the netstat command, which has annoyed me too. With "-W" it does output the full data in some columns, but not for reverse resolved names.

One way around this is to always just do the netstat command without name resolution, then parse the output and "manually" resolve each item that looks like an IP Address. This PR does that:
https://github.com/pfsense/pfsense/pull/3203

Actions

Copy link

Updated by Renato Botelho about 8 years ago

Category set to Web Interface
Status changed from New to Feedback
Assignee set to Renato Botelho
Target version set to 2.4.0
Affected Version set to 2.3.2

PR has been merged, thanks!

Actions

Copy link

Updated by Phillip Davis about 8 years ago

% Done changed from 0 to 100

Applied in changeset ed893ee55a248bea3a03d69a7e80b905a39a4f94.

Actions

Copy link

Updated by Phillip Davis about 8 years ago

Note: This fix has been applied to RELENG_2_3 to fix the issue on FreeBSD 10.3/pfSense 2.3.*

In FreeBSD 11.0 (upcoming pfSense 2.4) the wide output of netstat is improved, the whole text of a reversed-looked-up name is output, and passes through successfully to the GUI. So there is no need for any fix in pfSense master.

In FreeBSD 11.0, netstat has been enhanced to use the "libxo" output formatting, so it can output the data, for example, in JSON format, rather than a text block that has to be carefully parsed. pfSense code that parses and uses netstat output could be re-engineered to output JSON, transfer that to the GUI via AJAX calls... and then have the GUI easily format/display it. But that is an engineering refactoring issue, not this bug fix.

Actions

Copy link