thebros35

I started playing Destiny 2 last night when it came out on PC. The coop is super fun, me and a friend played for almost four hours straight. It felt like barely an hour . Other than that I've been playing League of Legends and PUBG.

I've got that one at home, been using it for about a year. Its basic and works just fine, I would get it.

OK, I was thinking that was what you meant. But you don't really need QoS... have you tried this setup without QoS? Usually that is just used for priotrizing data in a large enterprise with many different data streams of different media types. If you are just doing this at home, QoS is overkill from what I understand. Someone please correct me if I'm wrong, I would like a second opinion as well.

Port prioritization? I don't know what exactly you are talking about...everything should work automatically. Why would you have to prioritize that traffic? I'm confused.

Only bad part about that is the TP-Link switch, they make OK products but not too great ones. If you are OK buying used, I would look on EBay for a used HP ProCurve. They have fire-ass warranties and are built like tanks.

Right now anyway...I wonder how much money you could make from a YouTube video about setting money on fire... Then pay for your 10 Gb network with it!

It could be driver related. I had the same thing happen with a friend's PC at a LAN event - it was giving the yellow caution flag. I downloaded some drivers for him and it worked like a charm after that. Driver's are fucking weird. If you have an motherboard with a Killer NIC, OP, I bet its a driver related issue. Download the drivers from the manufacturer and install them on your PC and come back at us.

I would go with the proposed picture, but I wouldn't plug the router into the server. Let your router route, and let your server serve . Running Windows Server in a VM would do fine. dnsmasq is super fine if you don't mind text files, but if you want a GUI and already plan on doing Windows Server run DHCP and DNS on there. Its trivial and doesn't take up very many resources, and if shit goes haywire you can let your router do DHCP and DNS. The access points are always a good idea. I would also agree with upgrading to a PoE switch for your cameras and AP's, just to save some space. They aren't too expensive, and its nice having less wires . Really, its kind of silly to roll your own DNS. Its possible, but rather pointless.

When you plug it in, is there any lights on the PC's ethernet port that light up? Almost every ethernet port lights up when you plug it in. You could get a PCIe network adapter or a USB to check that as well.

I was wondering this today, why aren't people on IPv6? This applies to home, to work, to school, to any network you can think of. My home isn't on IPv6 because I'm a lazy bastard. Everything supports IPv6, the only thing I haven't tested is my Cisco 2960-S I bought off of eBay. Even my ISP supports IPv6! I'm just a lazy prick so I turned off IPv6 from my DHCP server so now everything is IPv4 at home. What are your reasons?

So what you need to do is this: Make your pfSense VM have two network cards. The first one is a bridged adapter connected to your ethernet port, and the second one is an internal network. The name should be intnet, this is fine. Then, boot up pfSense. Set your em0 adapter (your WAN connection, which should be your bridged) to DHCP, and set your em1 adapter (your LAN connection, which is the intnet) to an IP of 192.168.100.1, with a subnet mask of 24. This makes pfSense be a true router. Now, create a Linux or Windows VM. Set the network adapter to be on internal network, with the name intnet. This means that this VM is essentially connected to a virtual switch with the router. Set the static IP of the Linux or Windows VM to 192.168.100.2, subnet mask of 255.255.255.0. The gateway needs to be 192.168.100.1. Logically, think of it like you have a switch, and the router is plugged into one port, and the PC plugged in right beside it. The router has another port that is connected to "The Internet". When the PC looks for a network, it goes to 192.168.100.1, which is the router's IP address on that port. The router knows to send all traffic out to the WAN port, which essentially tunnels the traffic out to your router. I have this set up at home, and am able to run an entire domain of Windows Servers, Linux Servers, and desktops using this setup. If this seems a little confusing, I can upload a video later today or post some screenshots or something. Last time I explained this setup I used a whiteboard Just quote me if you have questions, I've rambled on for long enough.

How hot does yours run? I have it on the default fan curve, and the only time I really notice the noise is when I've been playing PUBG or BF1 for a little while.

I need to start OC'ing, mine's been stable at 1350 since I bought it without touching the voltage. It stays pretty cool too, usually maxing out at 65 C in my hotter than hell case where my CPU runs at 80 C under load.