ruby.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
If you are interested in the Ruby programming language, come join us! Tell us about yourself when signing up. If you just want to join Mastodon, another server will be a better place for you.

Administered by:

Server stats:

1.1K
active users

#R8000

0 posts0 participants0 posts today
GenghisKen Coar<p>Next rock continues..</p><p>Another, however, is that my main home <a href="https://ruby.social/tags/router" class="mention hashtag" rel="tag">#<span>router</span></a>, a <a href="https://ruby.social/tags/Netgear" class="mention hashtag" rel="tag">#<span>Netgear</span></a> <a href="https://ruby.social/tags/Nighthawk" class="mention hashtag" rel="tag">#<span>Nighthawk</span></a> <a href="https://ruby.social/tags/R8000" class="mention hashtag" rel="tag">#<span>R8000</span></a>, is now not getting access to the internet through the <a href="https://ruby.social/tags/ATT" class="mention hashtag" rel="tag">#<span>ATT</span></a> router. My phone says, &quot;Cannot provide Internet,&quot; and I haven&#39;t yet unlimbered my <a href="https://ruby.social/tags/laptop" class="mention hashtag" rel="tag">#<span>laptop</span></a> to actually log in to the routers to see what the hell is going on.</p><p>Just in case the old <a href="https://ruby.social/tags/DLink" class="mention hashtag" rel="tag">#<span>DLink</span></a>-645 (running <a href="https://ruby.social/tags/OpenWRT" class="mention hashtag" rel="tag">#<span>OpenWRT</span></a>) has lost it, can anyone recommend a good, inexpensive, 2.4GHz/5GHz home router?</p><p>Help?</p><p>Thanks!</p>
GenghisKen Coar<p>This week has been hellish. On Tuesday my main house router, a <a href="https://ruby.social/tags/Netgear" class="mention hashtag" rel="tag">#<span>Netgear</span></a> <a href="https://ruby.social/tags/R8000" class="mention hashtag" rel="tag">#<span>R8000</span></a>, decided that &quot;to avoid conflict with your <a href="https://ruby.social/tags/ISP" class="mention hashtag" rel="tag">#<span>ISP</span></a>, your router&#39;s IP address has been changed to 172.16.0.1.&quot; From something in 192.168.*.*. And the &quot;ISP&quot; was its uplink, in 192.168.1.0/24. So, no actual conflict. And the message only appeared on the R8000&#39;s Web screen after I figured out its new IPA. Futzing with it caused it to reset itself to 192.168.1.1 (actual conflict!), and 10.0.0.1, and.. Ghu!!</p>
GenghisKen Coar<p><span class="h-card" translate="no"><a href="https://ruby.social/@baweaver" class="u-url mention">@<span>baweaver</span></a></span><br />So I don&#39;t know whether to replace the <a href="https://ruby.social/tags/Linksys" class="mention hashtag" rel="tag">#<span>Linksys</span></a> <a href="https://ruby.social/tags/Nighthawk" class="mention hashtag" rel="tag">#<span>Nighthawk</span></a> <a href="https://ruby.social/tags/R8000" class="mention hashtag" rel="tag">#<span>R8000</span></a> with a higher-end and more capable <a href="https://ruby.social/tags/router" class="mention hashtag" rel="tag">#<span>router</span></a> (such as <a href="https://ruby.social/tags/Ubiquiti" class="mention hashtag" rel="tag">#<span>Ubiquiti</span></a>, if I could afford such), or go with <a href="https://ruby.social/tags/repeaters" class="mention hashtag" rel="tag">#<span>repeaters</span></a> (about the requirements of which I know nothing), or get an additional relatively low-end (read: <a href="https://ruby.social/tags/affordable" class="mention hashtag" rel="tag">#<span>affordable</span></a>) router and put the <a href="https://ruby.social/tags/IoT" class="mention hashtag" rel="tag">#<span>IoT</span></a> devices on a separate <a href="https://ruby.social/tags/subnet" class="mention hashtag" rel="tag">#<span>subnet</span></a> as originally ideated. Or something else. 🤔</p><p>Open to suggestions. Please. My <a href="https://ruby.social/tags/SBH" class="mention hashtag" rel="tag">#<span>SBH</span></a> is going spare about not being able to reach the printer.. 🙄🤪😔</p>
GenghisKen Coar<p><span class="h-card" translate="no"><a href="https://ruby.social/@baweaver" class="u-url mention">@<span>baweaver</span></a></span><br />As I said, I&#39;ve got no idea about the <a href="https://ruby.social/tags/network" class="mention hashtag" rel="tag">#<span>network</span></a> <a href="https://ruby.social/tags/hardware" class="mention hashtag" rel="tag">#<span>hardware</span></a>, and severely limited funds. If I could have gotten the <a href="https://ruby.social/tags/DLink" class="mention hashtag" rel="tag">#<span>DLink</span></a> running, I would have had it be <a href="https://ruby.social/tags/DHCP" class="mention hashtag" rel="tag">#<span>DHCP</span></a> <a href="https://ruby.social/tags/server" class="mention hashtag" rel="tag">#<span>server</span></a> for the <a href="https://ruby.social/tags/IoT" class="mention hashtag" rel="tag">#<span>IoT</span></a> devices in a separate subnet, since the <a href="https://ruby.social/tags/Linksys" class="mention hashtag" rel="tag">#<span>Linksys</span></a> <a href="https://ruby.social/tags/R8000" class="mention hashtag" rel="tag">#<span>R8000</span></a> isn&#39;t up to the combined task.</p><p>The R8000 logs don&#39;t even show <a href="https://ruby.social/tags/association" class="mention hashtag" rel="tag">#<span>association</span></a> requests for the devices not coming up, so I don&#39;t know if it&#39;s a <a href="https://ruby.social/tags/traffic" class="mention hashtag" rel="tag">#<span>traffic</span></a> issue or a router limitation.</p>
GenghisKen Coar<p><span class="h-card" translate="no"><a href="https://ruby.social/@baweaver" class="u-url mention">@<span>baweaver</span></a></span><br />I&#39;m disappointed that my first foray into <a href="https://ruby.social/tags/OpenWRT" class="mention hashtag" rel="tag">#<span>OpenWRT</span></a> came a cropper; the <a href="https://ruby.social/tags/DLink" class="mention hashtag" rel="tag">#<span>DLink</span></a> DIR-645 I <a href="https://ruby.social/tags/bricked" class="mention hashtag" rel="tag">#<span>bricked</span></a> with it was my main <a href="https://ruby.social/tags/Wifi" class="mention hashtag" rel="tag">#<span>Wifi</span></a> <a href="https://ruby.social/tags/router" class="mention hashtag" rel="tag">#<span>router</span></a> before I moved up to the <a href="https://ruby.social/tags/Linksys" class="mention hashtag" rel="tag">#<span>Linksys</span></a> <a href="https://ruby.social/tags/Nighthawk" class="mention hashtag" rel="tag">#<span>Nighthawk</span></a> <a href="https://ruby.social/tags/R8000" class="mention hashtag" rel="tag">#<span>R8000</span></a> 2.4GHz/5GHz one I&#39;m using now. (Which is having difficulty handling all my normal and <a href="https://ruby.social/tags/IoT" class="mention hashtag" rel="tag">#<span>IoT</span></a> devices, hence looking for alternatives. 😔)</p><p>Some <a href="https://ruby.social/tags/infrastructure" class="mention hashtag" rel="tag">#<span>infrastructure</span></a>-type things (like printers, <a href="https://ruby.social/tags/Raspi" class="mention hashtag" rel="tag">#<span>Raspi</span></a> devices, and <a href="https://ruby.social/tags/PlayStation" class="mention hashtag" rel="tag">#<span>PlayStation</span></a> <a href="https://ruby.social/tags/consoles" class="mention hashtag" rel="tag">#<span>consoles</span></a> 🤣) really *need* to be <a href="https://ruby.social/tags/hardwired" class="mention hashtag" rel="tag">#<span>hardwired</span></a>. 🙄😁🤪. <a href="https://ruby.social/tags/DHCP" class="mention hashtag" rel="tag">#<span>DHCP</span></a> is giving me the red-arse..</p>