Project

General

Profile

Bug #7100

IPv6 configuration fails in jails. Unable to configure and control plugins via GUI.

Added by Alex Mad almost 6 years ago. Updated about 4 years ago.

Status:
Closed: Not To Be Fixed
Priority:
Nice to have
Assignee:
John Hixson
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I am trying to run dual stack (ipv4/ipv6) on my FreeNAS.
I configured an IPv6 address on lagg0 interface of a freenas box and get an IPv6 connectivity to other networks, that is works fine.
After configuring IPV6 on lagg0 i loose the ability co configure and control installed plugins and get an errors in /var/log/messages

Here is the error message from my freenas (example)

https://[XXXX:1::241]/plugins/transmission/8/_s/treemenu

When i am clicking this link it shows me an error

URLError at /plugins/transmission/8/_s/treemenu
<urlopen error [Errno 50] Network is down>

Request Method: GET
Request URL: https://[XXXX:1::241]/plugins/transmission/8/_s/treemenu
Django Version: 1.6.1
Exception Type: URLError
Exception Value:

<urlopen error [Errno 50] Network is down>

Exception Location: /usr/pbi/transmission-amd64/lib/python2.7/urllib2.py in do_open, line 1184
Python Executable: /usr/pbi/transmission-amd64/bin/python2.7
Python Version: 2.7.6

....ommited

XXXX:1::241 - is an IPv6 address of FreeNAS gui
XXXX:1::201 - is an IPv6 address of transmission jail

There are 2 issues regarding IPv6 in jails.

1. I configured XXXX:1::201/64 for a jail manualy, but after a startup i have no ipv6 connectivity from inside of a jail. Ipv6 address is on an interface but

root@transmission_1:/ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:14:4a:00:10:0b
inet 172.24.100.201 netmask 0xffffff00 broadcast 172.24.100.255
inet6 XXXX:1::201 prefixlen 64
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

I have to execute a command ifconfig epair0b inet6 XXXX:1::201 prefixlen 64 to get an ipv6 connectivity. After that i can reach Ipv6 network (facebook.com for example).
And
root@transmission_1:/ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:14:4a:00:10:0b
inet 172.24.100.201 netmask 0xffffff00 broadcast 172.24.100.255
inet6 XXXX:1::201 prefixlen 64
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

2. I have no Ipv6 connectivity between XXXX:1::241 (freenas box) and XXXX:1::201 (jail). There is ipv4 connectivity between them and ip4/6 connectivity to other networks, but not IPv6 connectivity to each other

When i deleted an ipv6 config from freenas interface (lagg0 in my case) and reloaded a box i could configure a plugins and start/stop them? but IPv6 in jails is still not operational.
After configuring IPv6 addrees on freenas (lagg0) i loose ability to configure plugins and control them (with the same errors in log).

So we have an IPV6 issue in jails and depends on it plugin issuue.

Similar issues in bugs https://bugs.freenas.org/issues/6972 https://bugs.freenas.org/issues/7078 https://bugs.freenas.org/issues/7088

History

#1 Updated by Jordan Hubbard almost 6 years ago

  • Target version changed from 9.3-RELEASE to 111

It is a known problem that IPv6 and jails do not mix. This is hard to fix and on the roadmap for FreeNAS 10 next year.

#2 Updated by John Hixson almost 6 years ago

  • Status changed from Unscreened to Screened

#3 Updated by Jordan Hubbard about 5 years ago

  • Status changed from Screened to Closed: Not To Be Fixed

#4 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from 111 to N/A

Also available in: Atom PDF