Hello chaps,
Note: This post includes (potential) questions on both - FreeNAS & Pfsense.
So a very curious issue. As some might be aware, recently setup a Pfsense box and started playing with Suricata (amongst other packages...its quite false-positive happy). My impression was there were no devices running in my network on IPV6. Hence, I unchecked the IPV6 box in Suricata (see the attached photo below). It turns out my LinuxMint VM was using IPV6 and now it wont connect.
Question: Is this new VM functionality developed to leverage IPV6 network by default? Or is it because it was available and enabled it used that instead of IPV4 to establish connection on my network?
Step taken to resolve:
Restarted FreeNAS server after turning off IPV6 in Suricata & disabled IPV6 network connection from within Linux Mint. Did this in hopes that Pfsense in conjunction with FreeNAS server will assign a IPV4 address using DHCP on restart - No go still.
Suggestions/comments/observations welcomed.
Many thanks in advance.
Note: This post includes (potential) questions on both - FreeNAS & Pfsense.
So a very curious issue. As some might be aware, recently setup a Pfsense box and started playing with Suricata (amongst other packages...its quite false-positive happy). My impression was there were no devices running in my network on IPV6. Hence, I unchecked the IPV6 box in Suricata (see the attached photo below). It turns out my LinuxMint VM was using IPV6 and now it wont connect.
Question: Is this new VM functionality developed to leverage IPV6 network by default? Or is it because it was available and enabled it used that instead of IPV4 to establish connection on my network?
Step taken to resolve:
Restarted FreeNAS server after turning off IPV6 in Suricata & disabled IPV6 network connection from within Linux Mint. Did this in hopes that Pfsense in conjunction with FreeNAS server will assign a IPV4 address using DHCP on restart - No go still.
Suggestions/comments/observations welcomed.
Many thanks in advance.