Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards


About jasonvp

  • Title

Contact Methods

  • Twitch.tv
  • Twitter

Profile Information

  • Gender
  • Location
    Northern VA
  • Interests
    Big guns, fast cars, and fast computers.
  • Biography
    If *I* write this, doesn't that technically make it an *auto*biography?
  • Occupation
    Network Architect


  • CPU
    Intel 7900X (de-lidded, OC'd to 4.7GHz)
  • Motherboard
    Asus ROG Rampage VI Extreme
  • RAM
    Corsair Vengeance LPX 64GB (OC'd to 4GHz)
  • GPU
    2 NVidia 2080Ti FE (OC'd)
  • Case
    CaseLabs Magnum THX10
  • Storage
    Lots of SSDs and HDDs
  • PSU
    Corsair AX1500i
  • Display(s)
    Asus PG27UQ, 2 LG 4K/60Hz IPS
  • Cooling
    Custom water cooling
  • Keyboard
    Unicomp M "clone"
  • Mouse
    Logitech G502
  • Sound
    Sound Blaster ZxR card, Mackie DL32R mixer, Sennheiser HDV 820 amp and HD 820 cans
  • Operating System
    Windows 10 Pro (64 bit)
  • PCPartPicker URL

Recent Profile Visitors

1,586 profile views
  1. I'm both an audio nerd by nature, and a Network Architect by profession. That entire article in the OP just made me laugh. A lot.
  2. Ah, someone that hates Canon. Got it. The "anti"-fanboi. Check. Gotcha classified. OK, which Sony and/or Panasonic cameras are you referring to?
  3. I think that's an overly simplistic way to look at it. Resolution is at or near the top of your list of concerns based on what kind of output you're producing. Delivering in 1080p? Shooting in 4K gives you all sorts of fun re-framing options in post or very sharp 1080p output when the entire 4K is scaled down. Delivering in 4K? Well if you want the same options as before, you need a higher resolution video camera. This is where 6K and 8K cameras really help. IF Canon actually delivers a usable 8K/30 mirrorless that's affordable, it will change everything. This is a big deal for video guys. Specially since Canon's glass is basically second to no one's, other than the silly-expensive Zeiss stuff.
  4. I don't know that i'd go quite that far with the hyperbole. In the consumer space, we have a bunch of modern-day motherboards supporting 10GBASE-T right out of the box. The Aquantia 10GigE controller chip is cheap, and a bunch of MoBos are including it now. And have been for a couple of years, actually. So there's a good start. 10GigE NICs are also fairly inexpensive, depending on which model you buy, and how many ports are on it. Single and dual-port cards are readily available. The "expensive" ones from Intel will just work with any OS; the lesser expensive ones might need their specific drivers installed on Windows (Linux/FreeBSD will already have them). MicroTik(sp?) 4 x 10GigE switches aren't terrible. $131 at Amazon, without optics. An 8 x 10GigE from the same manufacturer is $240. All well within the reach of "consumers". All of this takes care of your LAN side, and does so relatively inexpensively and fairly easily. Plug'n'play. The WAN side becomes a bit more challenging because you need to go all-in with a Linux or FreeBSD (or NetBSD, or OpenBSD, or ...) solution on a home-built router. None of this is difficult to learn for someone willing to put forth the effort, but it will take some effort. The router itself wouldn't be expensive at all; a small motherboard, CPU, RAM, storage, and a PCI-E slot for a 2 x 10GigE card.
  5. Any self-built router with the appropriate NIC can handle 10GigE easily. But the result will be an OS that you need to configure manually: see Linux, FreeBSD, or the like. It'll be up to you to install the OS, configure the interfaces, and set up the filtering/NAT/etc rules.
  6. jasonvp

    10GBe Switch

    As the first reply pointed out: loud. Very loud. It's intended for a data center rack, not an office. So bear that in mind. Also, Arista isn't set up to deal with end users at all. You're not going to get any support whatsoever through them, and that includes code updates. So whatever code is running on it is all you're ever going to be able to use. And, that may be OK for your purposes, but it's something to keep in mind.
  7. If you considered that "whining" I'm not sure you understand what the word means. I wasn't even remotely doing so. I was pointing out how idiotic he is when he does those things, and laughing at (not with) him.
  8. Why are we "frequent(tl) plugging and unplugging" them? Set your networking stuff up and leave it the eff alone?
  9. Some day, maybe, Linus will grok the fact that neither Apple, nor the folks who use Mac Pros care about his price digs against it. He's adorable thinking they/we do actually care, though.
  10. The simplest thing to do is to get another WAP, run it to the switch, and make sure that port is on a different VLAN.
  11. Bear in mind that in the best case scenario, you'll get the switch to hash the PC<-->NAS over one of the PC's GigE links, and the PC<-->Intardwebz over the other GigE link. There's no guarantee that the switch will actually hash that way though, and you could be left with one of the GigE links in the bundle getting no traffic while the other is full. 802.3ad bundles are best used with a many-to-one. Those scenarios provide the switch far more to hash over and it's more likely you'll get an even distro across the links. Single 10GigE is the better solution. Mikrotic 5 x 10GigE switches are stupid-cheap, you'll just need to add some SFPs.
  12. Oh the Mikrotik switch we're referring to isn't rack mountable. It's pocket sized.
  13. Yep. But it doesn't come with any optics, so you'll need to either use a NIC with an SFP+ (and a DAC), or buy a few 10GBASE-T SFP+. They also run a bit toasty, too. Specially if you use 10GBASE-T.
  14. That's a 48-port GigE switch set up to live in a rack in a data center. What that means is the fans in it are small, very loud, and likely will be running at or near 100% all of the time. You'll get 2 10GigE ports on it, and that's it. THe 4948s are very old switches and I wouldn't bother.
  15. A couple of updates on this thread: 1. I did, in fact, get the MM cables run and installed. Turns out the hole I drilled in my floor was just large enough for the fully-assembled LC connector to slip through. As soon as I connected them up to the awaiting MM SFP+ optics in my switch, I had link. And we're done. Future updates will be fairly simple because QSFP+ LC MM optics do exist for 100GigE. 2. I found out what I was doing wrong with the Cat 7 (other than: using it). I had to ground the shielding properly, which I simply didn't understand at first. A quick application of some copper tape with conductive adhesive, and: bam, there's link. What the photo here is showing: I punched a single piece of Cat 7 down into both sides of the block, and you can see the copper tape through the little hole in said block. Basically, the ports are looped back on themselves. I added IP addresses to the two ports (9 and 10) on the switch, making them not switch ports; we don't want a loop! Then I connected both ports up to the block in my hand, using the two pieces of Cat 6 you see there. So that was the issue. Had I left the two 75ft runs of Cat 7 in place and re-terminated them with the help said copper tape, I likely could have gotten them to work. But, let's face it: fiber's better.