Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Josh Cooper commented on FACT-2951 Re: Facter 3 bad network for VirtualBox or VPN network interfaces Thank you for reporting this issue. While we agree this is likely an improvement, we do not anticipate addressing this any time soon due to other issues demanding precedence. As such, this ticket will be closed as “Won’t Do”. We may revisit this at a later time, and if so, will re-open this ticket. If you are interested in submitting a patch to implement this issue, please open a pull request and re-open this ticket. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.15966.1650564360037%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Josh Cooper updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Josh Cooper Component/s: Facter 3 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.15965.1650564300040%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Claire Cadman updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Claire Cadman Labels: doc_reviewed known-issue-added knownissue Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.11084.1618565700030%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Claire Cadman commented on FACT-2951 Re: Facter 3 bad network for VirtualBox or VPN network interfaces I've added this as a known issue: https://puppet.com/docs/puppet/6.21/facter-known-issues.html Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.159102.1615191720034%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Claire Cadman updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Claire Cadman Labels: known-issue-added knownissue Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.158279.1614941340119%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network networking.interfaces ` with facter 3, i I get a different network on VirtualBox interfaces than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking. interfaces.vboxnet0. ip` matches the `facter networking.interfaces.vboxnet0. network`. `facter networking.interfaces.vboxnet0. network should show the correct network` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154683.1614673860041%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect. This can also be reprFacter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-20-42-413.png|width=222,height=201!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-21-03-365.png|width=285,height=149!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Also, when connected to a VPN, Facter 3 shows network incorrect.Facter 3 gets the network informations form here [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox comes empty.Facter 4 relies on `ifconfig` command and it works as expected. Add Comment
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava Summary: Facter 3 bad network for VirtualBox or VPN network interfaces Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154681.1614673080100%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN interfaces Change By: Dorin Pleava Summary: Facter 3 bad network forVirtualBox or VPN interfaces Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154679.1614672840080%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for Change By: Dorin Pleava Summary: Facter 3 bad network when connected to a VPN for Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154678.1614672840056%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN interfaces Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect. This can also be repr Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-20-42-413.png|width=222,height=201!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-21-03-365.png|width=285,height=149!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Mihai Buzgau Labels: knownissue Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154726.1614676380150%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154727.1614676380195%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava commented on FACT-2951 Re: Facter 3 bad network for VirtualBox or VPN network interfaces Claire Cadman I think this issue can be marked as a known issue for the moment. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.154685.1614674520024%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title
Dorin Pleava updated an issue
Facter / FACT-2951
Facter 3 bad network for VirtualBox or VPN network interfaces
Change By:
Dorin Pleava
When running `facter networking.interfaces` with facter 3, I get a different network on VirtualBox interfaces than running the same command with facter 4. This bug requires the following configuration in VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-20-42-413.png|width=222,height=201!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-21-03-365.png|width=285,height=149!This bug also reproduces when connected to a VPN, and comparing network interfaces used for VPN connection (utun0, utun1 ...).I think facter 3 gets the network informations form [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox are empty. Facter 4 relies on `ifconfig` command and it works as expected. {code:java} % puppet facts diff | jq{ "network_vboxnet0": { "new_value": "192.168.99.0", "old_value": "192.168.99.1" }, "networking.interfaces.vboxnet0.bindings.0.network": { "new_value": "192.168.99.0", "old_value": "192.168.99.1" }, "networking.interfaces.vboxnet0.network": { "new_value": "192.168.99.0", "old_value": "192.168.99.1"}{code}
Add Comment
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava The bug can be recreated without a VPN When running `facter networking.interfaces` with facter 3 , by using I get a different network on VirtualBox interfaces than running the same command with facter 4. This bug requires the following configuration in VirtualBox : # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-20-42-413.png|width=222,height=201!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-21-03-365.png|width=285,height=149! I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network.Also, This bug also reproduces when connected to a VPN, Facter 3 shows and comparing network incorrect interfaces used for VPN connection (utun0, utun1 . ..). Facter I think facter 3 gets the network informations form here [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox comes are empty. Facter 4 relies on `ifconfig` command and it works as expected. Add Comment This message was sent by
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Attachment: image-2021-03-01-16-21-03-365.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153815.1614608520049%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16- 03 20 - 50 42 - 857 413 .png|width= 263 222 ,height= 240 201 !3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16- 14 21 - 18 03 - 644 365 .png|width= 361 285 ,height= 188 149 !I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Attachment: image-2021-03-01-16-20-42-413.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153814.1614608460090%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-03-50-857.png|width=263,height=240!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-14-18-644.png|width=361,height=188!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-03-50-857.png|width=263,height=240!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-14-18-644.png|width=361,height=188!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network` with facter 3, i get a different network than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking.ip` matches the `facter network`. `facter network should show the correct network` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153747.1614596340030%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network` with facter 3, i get a different network than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking.ip` matches the `facter network`. Affects Version/s: FACT 3.14.1 On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava created an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Issue Type: Bug Assignee: Unassigned Created: 2021/03/01 2:34 AM Priority: Normal Reporter: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
