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 beersykins

  • Title

Contact Methods

  • Discord
  • Steam
  • Origin
  • UPlay
  • Battle.net
  • PlayStation Network
  • Xbox Live
  • Reddit
  • Twitch.tv

Profile Information

  • Gender
  • Occupation
    Network Engineer


  • CPU
    AMD Ryzen 3600
  • Motherboard
    Asus Crosshair VI Wi-Fi
  • RAM
    32 GB Gskill Trident Z RGB 3200
  • GPU
    EVGA 1080Ti SC2
  • Case
    Fractal Define C
  • Storage
    1 TB WD Black SN750 w/HS
  • PSU
    EVGA 1600G2
  • Display(s)
    Dell 144Hz 1440p
  • Cooling
    CoolerMaster ML240L
  • Keyboard
    Logitech K350
  • Mouse
    Logitech G502 Hero SE
  • Sound
    Logitech G930
  • Operating System
    Windows 10

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you get full speed directly connected to the modem then you can at least isolate the router as a slowly-forwarding-component. 23 isn't very much, I have 37 on my home network, although I would try to isolate IoT devices onto a separate wifi band than your main 'performance client' 5GHz SSID.
  2. That doesn't really make any sense unless you're using an ancient relic like a WRT54G
  3. Most of the concern is interference, the ISM (2.4 GHz) band only has three non-overlapping channels. If you have wifi neighbors then it gets congested quick. The UNII bands (5 GHz) have a lot more space for 20/40 MHz channels do you can have a more dense environment without being interfered with. There's also other non-wifi devices that contribute to interference in the 2.4GHz band. 5 GHz usually offers higher transfer rates, if there's no other wifi traffic around you, you probably won't notice a latency difference, although the throughput at 'normal' RSSI signal strength value
  4. I assume it's some issue with your DNS service on the router, try statically assigning that to or similar and see if that helps. Usually the 'no internet' notice is a failure to resolve DNS records. If you're just using the ISP ones sometimes they are pretty flaky.
  5. As above you can't forward the same port to multiple destinations. UPNP usually resolves this by dynamically opening different ports for each PC but it largely depends on the game. You'd also want to make sure UPNP doesn't listen on the WAN interface by doing something similar to the 'GRC ShieldsUp UPNP Exposure Test'
  6. You should be able to add your PPPoE credentials to the config of the device for the WAN side. After that it's all relatively synonymous with what you had before. The ATT box may have some weird dot1X features it's trying to use to join the network as well, as that provider forces client certificates on its devices.
  7. What router and wireless NICs do you have? If you're on single band N gear then dual band or powerline would perform better from a latency perspective. AC wifi usually beats out powerline pretty easily from a bandwidth perspective, but it depends on a variety of factors (interference from neighboring APs, signal loss through walls, the standard you're using, powerline wise the circuitry of the outlets you're communicating between plays a large factor, as well as the standard of powerline adapters you're using).
  8. The two eth0 entries are for different things. One is a next hop route to your ISP, and one contains the WAN subnet that interfaces with your ISP. If you're using the WAN interface of your second router then that's why you can't directly access it (also you're rolling double NAT behind router #2). The best solution is to assign it a static LAN address in the space, disable DHCP specifically on router #2 and then connect to the LAN port instead on router #2.
  9. You can change the route on the route table manually in command prompt, you'd just give the wired side a lesser-preferred value.
  10. Those are all private addresses before the ICMP filter segments, totally an ISP problem from the results you're posting.
  11. He's adding extra interference to his environment which will decrease performance. The OG PS4 only had a 2.4g adapter, your best bet is either wired or a 5ghz wifi bridge to wire your PS4 into that integrates into the rest of your network.
  12. Ah I was half expecting this to be like most threads where they are still using a WRT54G Do you have QoS enabled on the router? Usually that tanks any sort of performance on ARM style CPUs (such as inside the router).
  13. Whip out Wifi Analyzer on your phone and take a look at 2.4 g SSIDs from your neighbors. There's a very high probability it's just interference from another network or multiple networks
  14. 1) The vast majority of setups are/should-be modem-router-switch. Some more advanced setups with managed switches place the router on an outside vlan, so physically you'd modem-switch-router but logically it's still modem-router-switch. You need the router in front to be able to NAT the rest of your network behind the single IP the ISP gives you. 2) Anything unmanaged are pretty synonymous. You just would pick how many ports you want and if you need PoE. 3) For workloads or transfers that you want >125 MB/sec. Usually NAS or backup/bulk-data oriented.
  15. Wired or wifi? The original PS4 only had a 2.4g adapter.