Well, I found 'set hint.run.0.disable=1' later on, after I was able to restore Internet connectivity at home :)
That's a good tip, but you have to be careful - if missed, booting and crashing caused many filesystem errors in my installation…
I understood you. Thank you for taking the time to find a solution to this problem! I very much hope that in future versions will be implemented to support the transfer H323 protocol to the fullest!
Try this:
http://wiki.pcbsd.org/index.php/Talk:Installation_Troubleshooting
I had to set HD access mode to LBA on a box here but you're not using a HD. Will that box not boot from USB then?
Steve
Seems like you hit some 'random weirdness' which is never a good thing.
Garbled serial output is very often a serial cable or adapter problem which may not be obvious.
Steve
I was able to get my networking working and the host can join the domain. I assume using the built in NAT from VMWare is enough and a firewall would not really benefit me any for this type of internal private network. Thanks for the help.
My own stupid fault. In the advanced pass through options I manually bound haproxy to port 80 to facilitate http > https redirection and specified the public ip of my production environment which is inaccessible from my test bench.
I am not a smart man.
1. Yes!
WPAD Autoconfigure for Squid
2. Squid will cache HTTP or HTTPS. Your hit ratio depend entirely on the sites that you visit and the frequency at which you visit them.4-8% is around the same ratio I get.
3. I have had limited success with dynamic content. Nobody seems to have a config that works well. All the various wikis etc say the same thing: play with it, see what happens, YMMV, but nothing concrete. That combined with the poor hit ratio has me thinking about deploying Squid just as a base for SquidGuard filtering.
Thanks heper for your quick response.
the NAT issue was actually me being too tired to do installations.
i only reseted the first router after configuring the NAT so NAT works great ( tested with different ports ).
the second issue is even more obvious.
as i have the default rule ( LAN net to get out ) it was higher then the rule of the change WAN for my ip.
this why you shouldnt deal with networking installation after 3:00AM
It looks like the driver is included:
[2.2-RELEASE][root@pfsense.fire.box]/root: kldstat -v | grep sas
256 pci/mrsas
It just needs to be given priority over the mfi(4) driver by setting that loader variable.
See: https://www.freebsd.org/cgi/man.cgi?query=mrsas&apropos=0&sektion=0&manpath=FreeBSD+10.1-RELEASE
Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.