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
