text
stringlengths
7
369
[1598.26 --> 1600.58] He says, I put together a little 1U NixOS router.
[1600.92 --> 1605.04] It's got multiple LANs and Wi-Fi set up with DHCP and NF tables.
[1605.74 --> 1606.92] The Wi-Fi is wonky.
[1607.34 --> 1609.68] Client connections just stop randomly.
[1609.68 --> 1611.94] I wire guard proxy all of my traffic,
[1612.12 --> 1614.58] but when I turn it on, nothing routes.
[1614.98 --> 1615.76] It's probably my firewall.
[1615.88 --> 1616.64] Not sure how to debug.
[1617.26 --> 1618.62] I could use some tips.
[1619.00 --> 1623.12] Well, C-dubs, you got a lot going on on that one box, you know?
[1623.30 --> 1626.28] And so I feel like Wi-Fi wonky.
[1626.50 --> 1627.32] That's one issue.
[1628.14 --> 1630.92] Client connections stopping randomly could be related to the Wi-Fi.
[1631.00 --> 1633.56] That could be a third, or I'm sorry, a second issue.
[1633.90 --> 1637.12] And then wire guard not properly routing your traffic.
[1637.12 --> 1640.56] That's at least your third issue, if not your fourth issue.
[1641.06 --> 1645.62] I feel like where I would start is I would probably try to break down each one of those
[1645.62 --> 1648.04] into its own separate problem.
[1648.42 --> 1649.50] Like, I'd start with the Wi-Fi.
[1649.62 --> 1656.16] Like, what's the point of even fixing the routing and the firewall issue if your Wi-Fi isn't working?
[1656.16 --> 1658.14] So I'd probably start with the Wi-Fi.
[1658.78 --> 1660.10] Figure out what's going on there.
[1660.30 --> 1661.28] You know, check D-message.
[1661.58 --> 1663.08] Run journalctl-f.
[1663.28 --> 1664.38] Watch your log for a bit.
[1664.76 --> 1665.88] See if you can catch it happening.
[1666.94 --> 1667.36] I don't know.
[1667.38 --> 1668.06] You got any thoughts, Joe?
[1668.34 --> 1669.50] I think just what you said, really.
[1669.62 --> 1674.56] Try and break it down into systematic chunks that you can work on.
[1674.68 --> 1676.94] Don't try and work on the whole thing at once,
[1676.96 --> 1679.20] because there's too much going on to do that.
[1679.24 --> 1680.50] There's too many moving parts.
[1680.50 --> 1685.02] Let's try one of the moving parts at a time and just work through it logically
[1685.02 --> 1688.20] until you solve each problem, and then the whole thing will work.
[1688.68 --> 1695.52] I wonder, too, C-dubs, if you're on a later Linux kernel, like a 602 or later,
[1696.20 --> 1699.66] because I swear, man, I've been having wonky Wi-Fi issues
[1699.66 --> 1702.54] on the later, more recent 6-series kernels.
[1702.98 --> 1704.74] I don't know how long you've had that NIC system installed,
[1704.74 --> 1708.40] but if you could roll back to, like, 5.18,
[1708.40 --> 1712.92] I would give that a try and see what happens, too, for your Wi-Fi issues,
[1712.98 --> 1717.80] because I have a machine that actually have two laptops
[1717.80 --> 1720.64] that are having really wonky Wi-Fi.
[1720.74 --> 1721.92] One's not connecting reliably,
[1722.80 --> 1726.36] and the other is experiencing really long latency
[1726.36 --> 1729.44] at different parts of the network that just doesn't really make sense.
[1729.52 --> 1731.82] Like, sometimes several hops outside my direct land,
[1732.52 --> 1735.76] one laptop that's having Wi-Fi issues will have four, five,
[1735.82 --> 1737.30] 600 milliseconds on a route,
[1737.30 --> 1739.32] and all of the other machines on the LAN
[1739.32 --> 1742.16] have no problem with that one hop.
[1742.48 --> 1743.64] I'm having the weirdest problems,
[1744.02 --> 1745.86] and it's been since the later 6-series kernels.
[1746.36 --> 1748.14] Yeah, or you could just try Ubuntu or something,
[1748.30 --> 1750.06] rather than a fancy OS like NixOS.
[1750.62 --> 1751.78] Could always try a live session.
[1751.86 --> 1752.92] That's actually a pretty good tip.
[1753.72 --> 1754.60] Try a live session.
[1755.38 --> 1758.40] See if you have some of the same Wi-Fi issues
[1758.40 --> 1759.86] in the live session.
[1760.22 --> 1762.28] With a different OS, maybe an older kernel.
[1762.82 --> 1764.68] Yeah, or dig out an old SSD or something,
[1764.84 --> 1766.70] install it on that, and just boot off that temporarily.
[1767.70 --> 1769.70] Optimus Gray boosted in with some grandpa ducks,
[1769.78 --> 1771.72] 22,222 sats.
[1771.80 --> 1772.92] He says, I need your help.
[1773.54 --> 1774.50] I'm an anti-Googler.
[1775.08 --> 1777.32] I just don't like being the product of a company
[1777.32 --> 1779.04] that's like the thing that's being sold.
[1779.14 --> 1781.36] So when I hear this great tool is free to use,
[1781.80 --> 1783.02] and it makes everyone's life better,
[1783.02 --> 1784.52] my radar gets lit up.
[1785.06 --> 1786.18] Tailscale, a great tool,
[1786.86 --> 1788.48] but a company that's not looking to make money,
[1788.66 --> 1789.36] I don't understand.
[1789.48 --> 1791.74] P2P connects are very cheap, so they don't need much.
[1792.08 --> 1794.66] But my radar is up for something am I not seeing.
[1794.66 --> 1797.56] I just don't like connections to everything on my network,
[1797.64 --> 1799.18] so my radar is going off.
[1799.50 --> 1802.54] I know they sponsor JB, but I wanted your input.
[1802.92 --> 1803.86] That's a fair question,
[1803.92 --> 1806.52] and I think it's one that Tailscale gets enough
[1806.52 --> 1810.08] that they did a blog post about how they make money
[1810.08 --> 1813.06] and how they built their network
[1813.06 --> 1814.88] to make it sustainable,
[1815.04 --> 1816.44] because I think that's a common question.
[1816.96 --> 1818.90] So the short version is where they make money
[1818.90 --> 1821.06] is if you want to have more than 20 devices
[1821.06 --> 1823.20] that get connected to that LAN, you got to pay.
[1823.58 --> 1825.44] Yeah, which is a pretty good business model.
[1825.56 --> 1826.98] I mean, they sponsor my shows as well,
[1827.46 --> 1828.84] so I'm somewhat biased here,
[1828.90 --> 1832.14] but it seems like your classic business model,
[1832.26 --> 1834.38] give away just enough to get people hooked,
[1834.52 --> 1836.14] and then, you know, you're using it
[1836.14 --> 1838.62] on five, six, ten devices on your LAN,
[1839.14 --> 1840.24] and then you go into work
[1840.24 --> 1841.48] and talk about how great it is,
[1841.48 --> 1844.64] and then suddenly you're on two or three hundred devices.
[1845.16 --> 1847.04] Yeah, it's kind of the Dropbox idea too, right?