Project

General

Profile

Bug #27272

Prevent IPv6 from slowing down the console

Added by Andrew Miskell over 1 year ago. Updated 11 months ago.

Status:
Done
Priority:
Nice to have
Assignee:
William Grzybowski
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I'm attempting to use the serial console in order to configure LAGG on my system and the console is very slow to respond. It appears to be hanging up on something with IPv6 before displaying the URLs you can use to access the web UI.

Whenever it hangs, I see this message on the console.

Dec 15 08:45:16 storage uwsgi: [django.security.DisallowedHost:81] Invalid HTTP_HOST header: '[fe80::d250:99ff:fe19:29af%igb0]'. The domain name provided is not valid according to RFC 1034/1035.

Associated revisions

Revision 4a8989db (diff)
Added by William Grzybowski over 1 year ago

fix(netcli): filter interface from IPv6

Ticket: #27272

Revision a7239d2d (diff)
Added by William Grzybowski over 1 year ago

fix(netcli): filter interface from IPv6

Ticket: #27272

History

#1 Updated by Dru Lavigne over 1 year ago

Andrew: please attach a debug (System -> Advanced -> Save Debug).

#2 Updated by Andrew Miskell over 1 year ago

  • File debug-storage-20171215085304.tgz added
  • Private changed from No to Yes

Debug attached and changed ticket to private.

#3 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to William Grzybowski

William: passing to you first as it appears to be Django/networking related.

#4 Updated by William Grzybowski over 1 year ago

  • Status changed from Unscreened to 15

What/How is slow exactly? Can you explain further?

Are you talking about the "netcli", the console menu?

#5 Updated by Dru Lavigne over 1 year ago

  • Status changed from 15 to Closed: Insufficient Info
  • Target version set to N/A
  • Private changed from Yes to No

#6 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-storage-20171215085304.tgz)

#7 Updated by Andrew Miskell over 1 year ago

Yes, I'm talking about the netcli console menu displayed over the serial or graphics console of the server.

It displays all of the menu items (but not the prompt) and hangs for several minutes, displays the error in the description and then presents the URLs for accessing via network and the console prompt to enter a selection.

#8 Updated by William Grzybowski over 1 year ago

  • Status changed from Closed: Insufficient Info to Screened
  • Priority changed from No priority to Nice to have
  • Target version changed from N/A to 11.2-BETA1

Ok, thanks for the update

#9 Updated by William Grzybowski over 1 year ago

  • Status changed from Screened to Ready For Release

#10 Updated by Dru Lavigne over 1 year ago

  • Subject changed from Console extremely slow to respond to Prevent IPv6 from slowing down the console
  • Status changed from Ready For Release to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#11 Updated by Dru Lavigne about 1 year ago

  • Status changed from Done to Ready for Testing

#12 Updated by Nick Wolff 12 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Severity set to New

Doesn't seem to be any lagg in internal7

#13 Updated by Dru Lavigne 12 months ago

  • Status changed from Passed Testing to Done
  • Needs QA changed from Yes to No

#14 Updated by Stephen Griffiths 11 months ago

Andrew Miskell wrote:

I'm attempting to use the serial console in order to configure LAGG on my system and the console is very slow to respond. It appears to be hanging up on something with IPv6 before displaying the URLs you can use to access the web UI.

Whenever it hangs, I see this message on the console.

Dec 15 08:45:16 storage uwsgi: [django.security.DisallowedHost:81] Invalid HTTP_HOST header: '[fe80::d250:99ff:fe19:29af%igb0]'. The domain name provided is not valid according to RFC 1034/1035.

Nick Wolff wrote:

Doesn't seem to be any lagg in internal7

Did this Fix ever make it into any Release? I have IPV6 configured on my entire Network now as it provides massive amount if IP's. But now using the Console you constantly get this error message about django, bitching about my auto ipv6 address. Anyway we can fix this?

#15 Updated by William Grzybowski 11 months ago

Stephen Griffiths wrote:

Andrew Miskell wrote:

I'm attempting to use the serial console in order to configure LAGG on my system and the console is very slow to respond. It appears to be hanging up on something with IPv6 before displaying the URLs you can use to access the web UI.

Whenever it hangs, I see this message on the console.

Dec 15 08:45:16 storage uwsgi: [django.security.DisallowedHost:81] Invalid HTTP_HOST header: '[fe80::d250:99ff:fe19:29af%igb0]'. The domain name provided is not valid according to RFC 1034/1035.

Nick Wolff wrote:

Doesn't seem to be any lagg in internal7

Did this Fix ever make it into any Release? I have IPV6 configured on my entire Network now as it provides massive amount if IP's. But now using the Console you constantly get this error message about django, bitching about my auto ipv6 address. Anyway we can fix this?

Are you running BETA1?

#16 Updated by Stephen Griffiths 11 months ago

William Grzybowski wrote:

Stephen Griffiths wrote:

Andrew Miskell wrote:

I'm attempting to use the serial console in order to configure LAGG on my system and the console is very slow to respond. It appears to be hanging up on something with IPv6 before displaying the URLs you can use to access the web UI.

Whenever it hangs, I see this message on the console.

Dec 15 08:45:16 storage uwsgi: [django.security.DisallowedHost:81] Invalid HTTP_HOST header: '[fe80::d250:99ff:fe19:29af%igb0]'. The domain name provided is not valid according to RFC 1034/1035.

Nick Wolff wrote:

Doesn't seem to be any lagg in internal7

Did this Fix ever make it into any Release? I have IPV6 configured on my entire Network now as it provides massive amount if IP's. But now using the Console you constantly get this error message about django, bitching about my auto ipv6 address. Anyway we can fix this?

Are you running BETA1?

Build FreeNAS-11.1-U5
Current Train: FreeNAS-11-STABLE (...)

for some reason the Drop down to choose Trains is unpopulated

#17 Updated by William Grzybowski 11 months ago

Stephen Griffiths wrote:

William Grzybowski wrote:

Are you running BETA1?

Build FreeNAS-11.1-U5
Current Train: FreeNAS-11-STABLE (...)

for some reason the Drop down to choose Trains is unpopulated

The ticket says the target version is 11.2-BETA1, so you don't have the fix yet.

#18 Updated by Stephen Griffiths 11 months ago

William Grzybowski wrote:

Stephen Griffiths wrote:

William Grzybowski wrote:

Are you running BETA1?

Build FreeNAS-11.1-U5
Current Train: FreeNAS-11-STABLE (...)

for some reason the Drop down to choose Trains is unpopulated

The ticket says the target version is 11.2-BETA1, so you don't have the fix yet.

Thank you for pointing that out, IN my Trains I see FreeNAS-11-STABLE and FreeNAS-11.2-STABLE, but I am on the 11 train, should I change to the 11.2 stable train?

#19 Updated by William Grzybowski 11 months ago

Stephen Griffiths wrote:

William Grzybowski wrote:

Stephen Griffiths wrote:

William Grzybowski wrote:

Are you running BETA1?

Build FreeNAS-11.1-U5
Current Train: FreeNAS-11-STABLE (...)

for some reason the Drop down to choose Trains is unpopulated

The ticket says the target version is 11.2-BETA1, so you don't have the fix yet.

Thank you for pointing that out, IN my Trains I see FreeNAS-11-STABLE and FreeNAS-11.2-STABLE, but I am on the 11 train, should I change to the 11.2 stable train?

11.2 is still in BETA stage. We advise jumping to that train only after 11.2-RELEASE is out.

Also available in: Atom PDF