Jump to content

brwainer

Floatplane Pilot
  • Content count

    2,083
  • Joined

  • Last visited

Awards


1 Follower

About brwainer

  • Title
    Veteran

Recent Profile Visitors

1,395 profile views
  1. External Firewall for blocking Windows 10 spying.

    It has been proven that the Windows Telemetry (spying) features don't use the Hosts file at all. Also since the traffic doesn't all use HTTP based communication, a web proxy would have limited effect. I would have to reread to be sure, but I'm fairly certain that noone above said it couldn't be done at the firewall, just that it wasn't a good idea to do so because it can have unintended consequences such as disabling Windows Updates. While I agree that it seems suspicious that certain updates re-enable features that were purposely disabled, you can't safely stop all security updates.
  2. External Firewall for blocking Windows 10 spying.

    What about just using Spybot Anti-Beacon on each computer? https://www.safer-networking.org/spybot-anti-beacon/
  3. Then hopefully, if this is needed, the old router can get online with the new modem.
  4. My guess is that the DVR is statically set to the IP 192.168.0.92, and you will have to arrange a means of logging into it and changing it. You could either set a static IP on a computer directly connected to it, or you could reattach the DVR and a computer to the old router (don't worry about reconnecting the router to the internet) and then you would be able to access it on the old IP. If the IP address of the DVR can only be changed by the security company, then you will have to reconnect the old router (and possibly modem) to the internet, and then they can update it to the new subnet that the Google Wifi uses.
  5. so the cameras themselves aren't IP-based, they use normal video cable connections like composite, S-Video, Component, or HDMI?
  6. You need to find out what your new subnet is - if it isn't 192.168.0.0/24 (192.168.0.1-192.168.0.255) then the DVR's IP address will need to be updated to match the new subnet, and then the port forwards would have to go to whatever the new IP for the DVR is. To set up port forwarding on Google Wifi, see this: https://support.google.com/wifi/answer/6274503?hl=en BTW, your public IP may have changed also, and the security company may need to update their side with the new public IP.
  7. LTT Storage Rankings

    Something like this I'm assuming: https://www.amazon.com/Startech-19-Inch-Vertical-Mountable-Server/dp/B001YHYVEY Generally these are intended for switches and patch panels, but they can hold servers if you secure them to the wall properly.
  8. Router security options...

    With the new vulnerability, anything with TKIP or AES+TKIP can have traffic injected into the network, but anything using AES only can only snooped on. So TKIP, the attacker can join your network, AES they can only listen to traffic. Still scary, but even more reason to never use TKIP.
  9. Long cable vs Router train

    if you have a router doing switching (defined as traffic going between devices connected to LAN ports) then only the switch chip, which can be outside of the CPU or integrated into the SoC, is doing more work - the CPU doesn't ever see purely switched traffic. It does cause heat in the switch chip, and in an SoC you could argue that the heat is in the "CPU area", but its not technically the CPU heating itself up for switched traffic. However if you mean bridging, where you are using the WAN port as part of the LAN set (as is commonly available with routers that have a builtin AP mode) then yes the bridged traffic gets processed by the OS on the CPU and would cause load/heat. So I would recommend that you not use the WAN/uplink port on routers that are in AP mode (use the LAN ports only). The only exception is routers like those made by Mikrotik, where instead of 2 hard connections on the CPU to the WAN and LAN, they can actually reassign the WAN port to be part of the switched ports on the switch chip when you aren't using them for NAT/Firewall. For @kurtwism's case, I think using the routers as they already exist / are set up is fine, they are already doing much less work in the AP role than they would be as routers, regardless of whether the WAN/uplink port is being used or not.
  10. 'Fixing' a weird ZFS

    Assuming that no other drives die while resilvering, then yes you can do this EDIT: because another drive might die, best to have a recent backup
  11. Port Forwarding on Mobile Network

    networking wise, for what you want to do, I doubt a proxy would work. Proxies often just deal with HTTP and/or TCP traffic, and the things you mentioned wanting to do need UDP too
  12. Port Forwarding on Mobile Network

    I don't know how android works really, but my guess is that you need to root your phone, and then be able to install a NAT rule into the firewall (iptables or whatever it runs) EDIT: or possibly, the port forwarding apps required you to be rooted in order to work EDIT2: also, if the port forwarding apps require you to enter the IP for "your device", then you need to enter the public IP, not the local IP
  13. Port Forwarding on Mobile Network

    what do you mean by public IP, and local IP? do you mean that your phone gets a public IP, and then your computer is getting a local IP from your phone? If that is what you mean, then you would have to do theport forwarding on the phone itself.
  14. How to open a port on Digital Ocean VPS?

    That seems like a really dumb default, but DigitalOcean is free to make their own choices I guess.
  15. How to open a port on Digital Ocean VPS?

    Also you will probably have to open the port in the firewall of the VM - an OS like Ubuntu ships with a default firewall that blocks all incoming connections.
×