Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve problems with IPv6 dpinger, VLAN Interfaces and long socket names #3027

Merged
merged 2 commits into from Jun 29, 2016

Conversation

@dhoffend
Copy link
Contributor

dhoffend commented Jun 28, 2016

For more details please see the ticket https://redmine.pfsense.org/issues/6505

  1. The use of underscores as delimiter conflicts with vlan interfaces names (which also contain underscors). --> switch to ~
  2. shorten long socket names so dpinger won't fail (this is not 100% failsafe due to the fact that the gateway name and monitor ip is actually used and presented in the status_gateway listing.
dhoffend added 2 commits Jun 28, 2016
Currently underscores are used to seperate gwifip, monitorip, etc, but
underscors are also used in vlan subinterfaces like em0_vlan10 and
therefore can't be used because the interface scope is appended to IPv6
link-local addresses.
dpinger stopps with an error when the socketname exceeds over
(around) 100 characters. The dpinger will not start and not deliver
monitoring results to the WebUI.

These long socket names can get created when using link-local addresses
and long gateway names / interface scopes.

See Ticket 6505
@dhoffend dhoffend force-pushed the dhoffend:ticket-6505 branch from 9efc66a to 40588fc Jun 28, 2016
@netgate-git-updates netgate-git-updates merged commit 40588fc into pfsense:master Jun 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.