text stringlengths 9 408 |
|---|
[1252.60 --> 1254.20] From there, that then |
[1254.20 --> 1256.00] points to a traffic |
[1256.00 --> 1257.12] instance that's running on |
[1257.12 --> 1257.94] the same server as |
[1257.94 --> 1258.28] Plex. |
[1259.00 --> 1260.22] And from there, it does a |
[1260.22 --> 1261.72] standard reverse proxy |
[1261.72 --> 1263.54] thing and just does the |
[1263.54 --> 1265.32] remote access as if I was |
[1265.32 --> 1267.16] going through port 32400 |
[1267.16 --> 1269.08] like I was last month. |
[1269.56 --> 1271.78] Very easy fix and I highly |
[1271.78 --> 1272.76] recommend you take a look |
[1272.76 --> 1273.16] into that. |
[1273.16 --> 1274.06] That's a great idea |
[1274.06 --> 1275.36] because Netscout said that |
[1275.36 --> 1276.30] after a scan they |
[1276.30 --> 1277.20] conducted, they found |
[1277.20 --> 1279.26] about 27,000 servers on |
[1279.26 --> 1280.06] the internet that can be |
[1280.06 --> 1281.08] abused this way. |
[1281.80 --> 1283.16] So it doesn't mean you |
[1283.16 --> 1284.00] have to shut off remote |
[1284.00 --> 1286.46] Plex, but it does mean |
[1286.46 --> 1287.18] you should probably take |
[1287.18 --> 1287.96] some steps to protect |
[1287.96 --> 1288.30] yourself. |
[1288.72 --> 1289.50] Yeah, just put it behind |
[1289.50 --> 1290.24] a reverse proxy. |
[1290.40 --> 1291.00] I mean, it doesn't have |
[1291.00 --> 1291.46] to be traffic. |
[1291.62 --> 1292.28] It could be Nginx. |
[1292.38 --> 1292.84] It could be whatever. |
[1293.22 --> 1296.02] But just don't open any |
[1296.02 --> 1296.84] ports in your firewall. |
[1296.96 --> 1297.96] You absolutely don't |
[1297.96 --> 1298.44] need to. |
[1298.92 --> 1300.18] Which actually brings me |
[1300.18 --> 1301.62] very nicely onto a very, |
[1301.76 --> 1302.48] very quick bit of |
[1302.48 --> 1303.14] follow up about the |
[1303.14 --> 1304.36] WireGuard rant I had |
[1304.36 --> 1306.08] last week on OpenSense. |
[1307.24 --> 1308.94] Turns out, like an |
[1308.94 --> 1312.02] idiot, I set a slash 16 |
[1312.02 --> 1313.96] subnet in my DHCP server. |
[1314.82 --> 1315.48] Now for those that don't |
[1315.48 --> 1316.60] know, what that means is |
[1316.60 --> 1319.96] every address from 192.168.0 |
[1319.96 --> 1323.70] all the way up to 192.168.255 |
[1323.70 --> 1326.56] was within my DHCP range. |
[1326.70 --> 1328.74] So I had 65,000 or whatever |
[1328.74 --> 1330.24] DHCP addresses available. |
[1331.24 --> 1332.92] The upshot of that was when |
[1332.92 --> 1334.24] I was trying to route through |
[1334.24 --> 1337.50] WireGuard, I was doing a 192.168.13 |
[1337.50 --> 1338.54] subnet. |
[1339.16 --> 1341.54] And so the remote servers were |
[1341.54 --> 1343.64] hearing that were receiving the |
[1343.64 --> 1344.88] commands from my laptop or my |
[1344.88 --> 1345.42] phone or whatever. |
[1345.92 --> 1347.66] But they didn't know how to route |
[1347.66 --> 1349.68] back to the client device because |
[1349.68 --> 1351.14] as far as they were concerned, the |
[1351.14 --> 1352.70] slash 16 overrode everything and |
[1352.70 --> 1353.72] it just thought everything was on |
[1353.72 --> 1354.08] the LAN. |
[1354.08 --> 1357.02] So what I did was I changed the |
[1357.02 --> 1360.12] subnet of the WireGuard VPN to a |
[1360.12 --> 1361.12] 10.something. |
[1361.74 --> 1362.94] So it was a completely different |
[1362.94 --> 1365.14] subnet and I reduced my slash 16 |
[1365.14 --> 1367.14] down to a more manageable slash 20. |
[1367.62 --> 1368.92] So I've only got a few thousand, like |
[1368.92 --> 1370.98] 4,000 addresses now instead of |
[1370.98 --> 1371.96] 65,000. |
[1372.08 --> 1373.38] I think that should tie me over for a |
[1373.38 --> 1373.72] bit, right? |
[1374.08 --> 1374.60] Nicely done. |
[1375.02 --> 1376.58] I definitely always suggest if |
[1376.58 --> 1379.30] people can, different subnets for |
[1379.30 --> 1381.68] the different VPN endpoints makes it |
[1381.68 --> 1383.90] so much simpler, you know, and I've |
[1383.90 --> 1385.40] tried, I've tried to do that myself |
[1385.40 --> 1387.84] so many times because it can solve |
[1387.84 --> 1390.76] you just a few simple problems and |
[1390.76 --> 1392.74] keeps it a little clear in your |
[1392.74 --> 1393.02] head. |
[1393.18 --> 1396.12] Like I know that the studio is .4 |
[1396.12 --> 1399.84] and home is .7 and the WireGuard |
[1399.84 --> 1401.42] network is actually a .10 network. |
[1401.54 --> 1402.50] It's all separated out. |
[1402.86 --> 1402.96] Yeah. |
[1403.02 --> 1404.20] So I just wanted to be absolutely |
[1404.20 --> 1406.16] clear that the problem was the user |
[1406.16 --> 1408.50] not OpenSense or WireGuard. |
[1408.60 --> 1409.80] It was totally my fault. |
[1409.80 --> 1412.92] And I owe a huge debt of gratitude to |
[1412.92 --> 1414.18] one of our listeners who reached out |
[1414.18 --> 1418.04] to me on Discord and did a screen |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.