Project

General

Profile

Bug #40484

Add ability to customize default vnet interface to middleware

Added by Scott Finlon about 2 years ago. Updated almost 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Waqar Ahmed
Category:
Middleware
Target version:
Seen in:
Severity:
Medium
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 upgraded to Beta 2 to see if the fixes were in to remedy https://redmine.ixsystems.com/issues/30276 yet, and all of my jail/vm networking was broken for anything on the one bridge. Upon inspection LAGG0 was added to that bridge and shouldn't have been.
I tried pinging a jail, and host was down. I then removed the LAGG0 from the bridge and everything was available.

PING 192.168.254.2 (192.168.254.2): 56 data bytes
ping: sendto: Host is down
^C
root@nas:~ # ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:e6:d8:a2:2e:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 9 priority 128 path cost 2000000
    member: vnet0:4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000
    member: lagg0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 5 priority 128 path cost 10000
    member: vlan254 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 8 priority 128 path cost 2000000
root@nas:~ # ifconfig bridge0 deletem lagg0
root@nas:~ # ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:e6:d8:a2:2e:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 9 priority 128 path cost 2000000
    member: vnet0:4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000
    member: vlan254 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 8 priority 128 path cost 2000000
root@nas:~ # ping 192.168.254.2
PING 192.168.254.2 (192.168.254.2): 56 data bytes
64 bytes from 192.168.254.2: icmp_seq=0 ttl=64 time=0.054 ms
64 bytes from 192.168.254.2: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 192.168.254.2: icmp_seq=2 ttl=64 time=0.051 ms


Related issues

Related to FreeNAS - Bug #28627: Add the iocage host interface to the bridge and only rename if the default vnet0 interface is suppliedDone
Related to FreeNAS - Bug #34285: Failure to re-acquire DHCP address with link aggregation and jailsClosed
Related to FreeNAS - Feature #47642: Add vnet_default_interface field to Jails Advanced menu in new UIDone
Has duplicate FreeNAS - Bug #45633: lagg interface on bridge causes network issues.in jailsClosed

History

#1 Updated by Dru Lavigne about 2 years ago

  • Related to Bug #28627: Add the iocage host interface to the bridge and only rename if the default vnet0 interface is supplied added

#2 Updated by Dru Lavigne about 2 years ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Scott: please attach a debug (System -> Advanced -> Save debug) to this ticket to assist the dev in diagnosing why this is still happening.

#3 Updated by Scott Finlon about 2 years ago

  • File debug.tgz added

debug attached.

#4 Updated by Dru Lavigne about 2 years ago

  • Category changed from Services to OS
  • Assignee changed from Release Council to Alexander Motin
  • Reason for Blocked deleted (Need additional information from Author)

#5 Updated by Scott Finlon about 2 years ago

It appears to be part of the VNET networking setup for the iocage jails.

I stopped and then restarted the jail and lagg0 was added back to bridge, and no networking worked, once I did deleted the lagg0 membership it started working again.

# ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:e6:d8:a2:2e:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0:6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000
    member: vlan254 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 8 priority 128 path cost 2000000
    member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 9 priority 128 path cost 2000000
root@nas:~ # iocage restart plex
* Stopping plex
  + Running prestop OK
  + Stopping services OK
  + Tearing down VNET OK
  + Removing jail process OK
  + Running poststop OK
* Starting plex
  + Started OK
  + Configuring VNET OK
  + Starting services OK
root@nas:~ # ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:e6:d8:a2:2e:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0:8 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 2000
    member: lagg0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 5 priority 128 path cost 10000
    member: vlan254 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 8 priority 128 path cost 2000000
    member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 9 priority 128 path cost 2000000

#6 Updated by Alexander Motin about 2 years ago

  • Assignee changed from Alexander Motin to Brandon Schneider

Extra lagg0 interface added to the bridge sounds like a middleware issue.

#7 Updated by Dru Lavigne about 2 years ago

  • Category changed from OS to Middleware

#8 Updated by William Grzybowski about 2 years ago

  • Assignee changed from Brandon Schneider to Waqar Ahmed

Load-balancing with Waqar.

#9 Updated by Waqar Ahmed about 2 years ago

  • Status changed from Unscreened to In Progress

#10 Updated by William Grzybowski about 2 years ago

  • Target version changed from Backlog to 11.2-RC1

#11 Updated by Dru Lavigne about 2 years ago

  • Related to Bug #34285: Failure to re-acquire DHCP address with link aggregation and jails added

#12 Updated by Dru Lavigne about 2 years ago

  • Has duplicate Bug #45633: lagg interface on bridge causes network issues.in jails added

#13 Updated by Dru Lavigne about 2 years ago

  • File deleted (debug.tgz)

#14 Updated by Dru Lavigne about 2 years ago

  • Private changed from Yes to No

#15 Updated by Waqar Ahmed about 2 years ago

  • Status changed from In Progress to Ready for Testing
  • Severity changed from New to Medium

Iocage PR - https://github.com/freenas/iocage/pull/36

This PR enables the user to specify which default_vnet_interface they would like to use on the bridge with a jail. A new property has been added to iocage namely as vnet_default_interface with an example use

iocage create vnet_default_interface=vlan20 vnet=on interfaces="vnet0:bridge1" ip4_addr="interface|ip/23" defaultrouter="ip" -r 11.2-RELEASE -n n1

Now with this property vnet0 will be added to bridge1 and vlan20 will be added their as well. This will resolve the conflict which arose in earlier situations where default interface automatically got added. In case you would like to use the default interface, this property defaults to "none" and in that case it automatically uses the default interface.

Many thanks for reporting this!

#16 Updated by Dru Lavigne almost 2 years ago

  • Subject changed from FreeNAS-11.2-BETA2 - LAGG0 being added to bridge to Add ability to customize default vnet interface to middleware
  • Needs Merging changed from Yes to No

#17 Updated by Dru Lavigne almost 2 years ago

  • Related to Feature #47642: Add vnet_default_interface field to Jails Advanced menu in new UI added

#18 Updated by Dru Lavigne almost 2 years ago

  • Needs Doc changed from Yes to No

#19 Updated by Dru Lavigne almost 2 years ago

  • Status changed from Ready for Testing to Done
  • Needs QA changed from Yes to No

Also available in: Atom PDF