@bmeeks
Good to know!

@nicesub said in Pfsense refuses to boot on Hyper-V:

Few more things left to be fixed on it if possible:
It does not know what kernel is installed and when I go to "System update page" it does not know which version is installed. Also I get message there "Unable to check for updates".
In the package manager I cannot see the list of installed packaged as well and I cannot retrieve list of "Available packages".

That's fixed years ago 😊
You need the 2.6.0, not the ancient 2.5.2.

@chrisan I wasn't responding to you nor was I referencing your issue but rather responding to @JKnott's comments.

@optimus-prime
If he has an wifi AP you could connect it to your switch and configure a separate subnet for the guest wifi.

@johnpoz : I was originally using it as a bridge server, but the second side of that bridge server is not connected anymore and everything is on one side now.

I think my best bet at this point is to take a separate computer and a separate switch and connect those to a separate NIC on the Sinology NAS so that I can access the GUI. From there maybe I can rework the network and get it put back together.

To recap, when I installed the Netgate, I basically matched all of the networking. I wanted it all to be the same as it was in the sonic wall. Same, WAN, same, LAN, same port forwards.

Basically, everything worked out except for the NAS.

I crack into it more after the holiday.
Thanks for your response.

@viragomann
I tried it works great
Thank you so much

@nollipfsense that's almost what I was doing anyway, but then that again gets the printer on a different subnet from the PC, which puts the barrier between the UDP communication, which would make the printer not function.

That said, I think I may have figured out that the Canon driver potentially is only using UDP broadcast to initially find the printer if it's IP address is changed or it's a new installation. So, if I assign the printer a static IP on its network, and I temporarily move devices that need to print to it to the same network just for the driver install, then I can move the devices back to other subnets on the overall network and maintain functionality.

I'll have to test this through a few reboots and several days to confirm it does indeed work, that would suffice for now. I may eventually try to figure out which UDP ports I need to relay to get the Canon drivers to work without having to move devices around between the networks, if it becomes more problematic and this workaround doesn't hold.

Just wanted to post an update. Was able to get this unifi AP working on a different subnet by SSHing into the AP and pointing it with setinform to the controller on the other subnet.

@victor-2 said in Cannot ping pfSense:

ASRock A320M-HDV

Don't use the Realtek NIC if you have Intel NICs!
The Driver support is badly.

@furom you could always put in a feature request over at the pfsense redmine

https://redmine.pfsense.org/

edit: not widget but if your on the normal firewall log, you can put in a !WAN for the interface and get all interfaces that are not wan.

@stephenw10
The ping test could have been after ARP expiration.

Once the network failures were history, I tried switching to VirtIO, but speed was 35M even with offloading disabled. I set it back to Bridged, and got 250M with 4 CPUs. 2 CPUs in Virtualbox gave me over 500M. Not bad, but still ~50%.

Each reboot I would lose connectivity on the i211 LAN and the only way I could get it to work was to switch it promiscuous mode on/off while the VM was running. Crap...

I gave up on Virtualbox and moved it over to Hyper-V with 8 CPUs set. I got 30M, researched, and disabled RSC (even though it was already reported as disabled) via PowerShell with these commands:
netsh int tcp set global rsc=disabled
Get-NetAdapterRsc | Disable-NetAdapterRsc

Then I could get a solid 940M in Hyper-V, AND have the luxury of auto-start after host reboot. (Lessons for anyone reading this)

@nar94k the Google router will need to forward either the OpenVPN ports or all ports to pfSense. pfSense can allow access to the OpenVPN server ports on its WAN, or if you set up a dynamic DNS hostname you can allow that hostname.

@jwt @stephenw10 appreciate your feedback here. Truly do.

@stephenw10 Yeah, I read that but it doesn't really give case scenarios. I appreciate the help.

Yup, see: http://files.pfsense.org/jimp/BEGEMOT-PF-MIB.txt

The phase 2 entry for each device should use the IP address they specify in the 'NAT/BINAT translation' and the real address in the 'Local Network' field.

See: https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/phase-2-nat.html#example

You do not need an outbound NAT rule if you can add the route to the OpenVPN tunnel at Site1.

Steve

Ryan, I ordered directly from netgate.
Thanks all.

Thanks guys.

I normally shutdown properly but had an issue with power loss at home which was pretty regular. I have a UPS but it's just my Unraid that's plugged into that but I'll look at getting my pfSense hooked up to it too maybe. Power cuts were down to my Lava Lamp as it happens which I've now stopped using anyway.

Interesting stuff though.