Project

General

Profile

Bug #63234

Add Advanced Plugin Installation button to new UI

Added by Matt Johnson 3 months ago. Updated about 1 month ago.

Status:
Done
Priority:
No priority
Assignee:
Lola Yang
Category:
GUI (new)
Target version:
Seen in:
Severity:
Med High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

2 VLANs: 30 and 20. System gateway is defined on 30 (10.0.30.1). Created a plugin (deluge) unchecked DHCP and selected VLAN20 interface and set an IP of 10.0.20.12/24. immediately notice traffic on my firewall on VLAN30 from IP 10.0.20.12. It appears the plugin is disregarding my choice of interface.


Related issues

Has duplicate FreeNAS - Bug #69265: Plugin installation fails when configured to use VLAN interfaceClosed

History

#1 Updated by Matt Johnson 3 months ago

  • File debug-freenas-1-20181210193905.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne 3 months ago

  • Category changed from Services to Middleware
  • Assignee changed from Release Council to William Grzybowski

#4 Updated by Brandon Schneider 3 months ago

  • Assignee changed from William Grzybowski to Brandon Schneider
  • Reason for Closing set to User Configuration Error
  • Needs QA changed from Yes to No
  • Needs Merging changed from Yes to No

Make sure you set your vnet defualt interface under network. Otherwise it will use the default route on the system (vlan30 in this case)

#5 Updated by Matt Johnson 3 months ago

Brandon Schneider wrote:

Make sure you set your vnet defualt interface under network. Otherwise it will use the default route on the system (vlan30 in this case)

I'm looking under the menu item "network", looked through global / interfaces / IPMI / link aggregations / static routes / VLANS - and I did not see an option for a default interface. Am I looking in the wrong area?

#6 Updated by Brandon Schneider 3 months ago

  • Status changed from Unscreened to Closed
  • Target version changed from Backlog to N/A
  • Needs Doc changed from Yes to No

Yeah sorry if I wasn’t clear, this is a per jail option. You can see it during creation or changing the jails properties. You will need to set this for each jail you create.

#7 Updated by Dru Lavigne 3 months ago

  • File deleted (debug-freenas-1-20181210193905.txz)

#8 Updated by Dru Lavigne 3 months ago

  • Private changed from Yes to No

#9 Updated by Matt Johnson 3 months ago

Brandon Schneider wrote:

Yeah sorry if I wasn’t clear, this is a per jail option. You can see it during creation or changing the jails properties. You will need to set this for each jail you create.

So I found the setting vnet_default_interface and changed it to vlan20. I have tried with DHCP autoconfigure IPv4 on, and off + manually setting the IP + chosing VLAN20 for IPv4 interface. When on, it still pulls a 30 IP address, when off it is still sending data over vlan30.

The other issue is when deploying it as a plug-in, you are not given all these options. So we are forced to use the default interface to get the jail going and hoping editing the jail as I'm trying to above, works.

#10 Updated by Brandon Schneider 3 months ago

  • Subject changed from Plugin networking to Allow more properties in plugin creation (vnet_default_interface for instance)
  • Category changed from Middleware to GUI (new)
  • Status changed from Closed to Unscreened
  • Assignee changed from Brandon Schneider to Erin Clark
  • Target version changed from N/A to 11.2-U2
  • Severity changed from New to Med High
  • Reason for Closing deleted (User Configuration Error)
  • Needs QA changed from No to Yes
  • Needs Doc changed from No to Yes
  • Needs Merging changed from No to Yes

Matt: That is likely because your vlan30 is still on bridge0 on your host. Make sure to remove that from the cli now, or change all those jails and reboot your system.

Erin: Passing this ticket to your team as creating a plugin should allow these properties to be defined.

#11 Updated by Matt Johnson 3 months ago

Brandon Schneider wrote:

Matt: That is likely because your vlan30 is still on bridge0 on your host. Make sure to remove that from the cli now, or change all those jails and reboot your system.

Erin: Passing this ticket to your team as creating a plugin should allow these properties to be defined.

Brandon Schneider wrote:

Matt: That is likely because your vlan30 is still on bridge0 on your host. Make sure to remove that from the cli now, or change all those jails and reboot your system.

Erin: Passing this ticket to your team as creating a plugin should allow these properties to be defined.

So for fun I tried changing it from vnet0:bridge0 to vnet1:bridge0 which it finally pulled a 20 IP. I'm very new to the CLI, is there a manual or page I could refer to so I can play with editing the bridge. Thank you all for your help thus far.

#12 Updated by Brandon Schneider 3 months ago

Haha that is one way to do it! Sure man ifconfig on the CLI will let you start to learn the fundamentals on interface fun. To help you cheat in the future ifconfig deletem vlan30 is what you're looking for.

#13 Updated by Matt Johnson 3 months ago

Brandon Schneider wrote:

Haha that is one way to do it! Sure man ifconfig on the CLI will let you start to learn the fundamentals on interface fun. To help you cheat in the future ifconfig deletem vlan30 is what you're looking for.

Ohhh I thought you meant freenas specific CLI lol, I was thinking because of iocage and freenas there was some voodoo going on I'd need to do something specific. I went looking and I don't see it, was that only during freenas 10/corral?

Anywho thanks again, onward and forward. Sorry if these replies keep reopening the ticket, if so then this can be the last reply. Hopefully this thread helps somebody else stuck/confused.

#14 Updated by Brandon Schneider 3 months ago

It's fine :P

Yes that was the last one with a specific CLI. iocage in freenas should function just like freebsd, just a little more frozen since we can't have all the churn in freenas during release cycles.

#15 Updated by Erin Clark 3 months ago

  • Assignee changed from Erin Clark to Lola Yang

#16 Updated by Lola Yang 3 months ago

  • Status changed from Unscreened to In Progress

#17 Updated by Erin Clark 2 months ago

  • Status changed from In Progress to Ready for Testing

#18 Updated by Dru Lavigne 2 months ago

  • Subject changed from Allow more properties in plugin creation (vnet_default_interface for instance) to Add Advanced Plugin Installation button to new UI
  • Needs Merging changed from Yes to No

#21 Updated by Dru Lavigne about 2 months ago

  • Has duplicate Bug #69265: Plugin installation fails when configured to use VLAN interface added

#22 Updated by Timothy Moore II about 2 months ago

#23 Updated by Dru Lavigne about 1 month ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF