@stephenw10: That looks like an issue entirely within VBox if it's between the host and the guest. That traffic never goes through pfSense. Try an iperf test between pfSense and the host on VLAN30 to confirm that. Steve you are right. iperf from and to the router is "fast" (in quotes because it's a gigabit line, but it does only 596 Mbit/s): [2.4.0-RC][admin@rutter.in.tern.al]/root: iperf -c 192.168.30.10 ------------------------------------------------------------ Client connecting to 192.168.30.10, TCP port 5001 TCP window size: 64.2 KByte (default) ------------------------------------------------------------ [  3] local 192.168.30.1 port 57809 connected with 192.168.30.10 port 5001 [ ID] Interval      Transfer    Bandwidth [  3]  0.0-10.0 sec  711 MBytes  596 Mbits/sec [2.4.0-RC][admin@rutter.in.tern.al]/root: So it's a VirtualBox problem. Thanks stephenw10!

strip_query_terms off Tried the above settings and I didn't get the result I needed. I can see the full address if i go to Squid proxy server / real time but the word/phrase thats been searched and user that searched it needs to be logged. Anyone got any suggestions?

It seems like the answer to this depends on the relative performance of your pfSense box vs. the RV340 and the cost of upgrading the former vs. purchasing the latter. It's hard to see how combining them would be advantageous unless your pfSense box is significantly underpowered for gigabit (but if that is true it's not going to be very good to use as a firewall)

You can do that, forward requests to the correct server based on the host-header, using Reverse Squid or HAProxy. HAProxy is more capable but potentially more complex: https://doc.pfsense.org/index.php/Haproxy_package Steve

Hi everybody, Someone have an idea to solve this problem? Thanks in advance Jack

It sounds like you have some sort of asymmetric route happening. You may be seeing an ICMP redirect that allows the traffic to pass until it times out. You need to trace where that syn/ack from the timeclock is going or if the syn ever reaches it. The first thing I would do though is check the pfSense firewall logs for blocked flagged or outbound traffic. Steve

Fixed.  Browser issue.

I'd start your toubleshooting with the  NICs: https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards Try searching the forum for your specific NIC or chipset

@dvs23: Well, buying a managed switch is no problem, I just cannot add a second wire to the APs… So I thought it would be unnecessary.. A VLAN to an access point is the usual method for multiple SSIDs.  A common configuration is to have the native LAN used for normal users and the VLAN for guests, who are only allowed to access the Internet.

OK, so how do we know that the Link Down/Up event was not a genuine event on the port?

I've applied this fix to my Atom N3150 box with 2 x Realtek NICs. Before, when I would push a lot of traffic (600+ mbps) through the system, either the LAN or WAN interface (or both) would crash. None of the fixes I found on the internet including disabling hardware checksum / hardware offloading under Advanced fixed this. But I'm happy to report that once I installed this driver, I can push a ton of traffic through the system without too much trouble!

@aGeekHere: just tested it again, it no longer works, oh well. I`d try it too - no effect ((( No ideas more? (

Ah, I see. Thanks for the info.

in windows open cmd as administrator and type netstat -ab. Also check this out https://forum.pfsense.org/index.php?topic=33833.0