• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle





  • “Gamers Nexus, on the other hand, thinks the issue is more deep rooted and originates from a foundry-level fault.”

    • The GN piece makes it very clear that this claim is not definitely true but is a line of inquiry.
    • Intel statement does not definitely exclude this hypothesis, the flawed CPU might need the lower voltage to work around the flaw.
    • The obvious question this article does not address is what will be the performance hit for the patched parts?

    That’s a bit annoying to see GN so grossly misquoted when Steve spends half the run time of the video explaining that they are not sure of anything at this point.









  • I’m not sure about the point of your setup but let’s ignore that :

    • Create a vlan “servers” on router B, assign a port (WITHOUT vlan tagging) to this vlan, patch a cable between this port and any port on rouer A
    • Put a static IP address 0.x on router B in this vlan
    • Enable routing between the default vlan and vlan “servers” on router B .
    • Configure router A to not distribute this IP address (by setting up a permanent DHCP lease for example)
    • On all your servers put a static route that says : “192.168.20.0/24 via 192.168.0.x”
    • If you can setup this route on A, things connected to A will work whether they have the route or not (it’s not a big deal but the routing would be assymetrical)

    If you can create a VLAN and a route on A, you can create a distinct “interconnect” VLAN and make all of that nice and clean without the extra static routes on the servers.