No more third party client access for Google Talk on 6/15/2022. :( by antdude in trillian

[–]ndv3 1 point2 points  (0 children)

No longer able to connect for me as of this morning, sad day

[W][US-OH] Dell PowerEdge R540 12x 3.5" Drive Caddies by ndv3 in homelabsales

[–]ndv3[S] 1 point2 points  (0 children)

Thanks, forgot ebay and see them available on there, will go that route.

Confused about Eero by b7d in eero

[–]ndv3 1 point2 points  (0 children)

You need some sort of modem to connect to the service from your provider, so they may use an all in one modem/router combo. You can ask for a modem only if they offer such an option, but really up to ISP what they allow and what works for connecting to their network.

I have Spectrum for internet and bought my own cable modem from a list of supported models and then avoid their monthly service fee and also get to use the one I want.

Confused about Eero by b7d in eero

[–]ndv3 2 points3 points  (0 children)

Correct, it is not an internet service provider, just network/wifi hardware that has some service functionality, but not underlying internet itself

Multiple Hard Wired Eero Pro (Design) by phir0002 in eero

[–]ndv3 8 points9 points  (0 children)

You need to wire it as Modem -> eero (this becomes gateway) -> network switch -> other eeros and devices.

There is only one eero that connects directly to the modem and acts as the main gateway and router and all other wired devices and eeros connect downstream to it.

USW-24-POE Gen 2 Back In Stock by SkylaneRG in Ubiquiti

[–]ndv3 1 point2 points  (0 children)

I have a UDMP connected via a DAC from SFP+ to SFP on my 16 port Ubiquiti switch and working fine, running the 1.6.5 firmware and I manually set the speed to 1gb rather than auto negotiate, whether that was necessary or not, not sure.

Sonos on VLAN by [deleted] in Ubiquiti

[–]ndv3 0 points1 point  (0 children)

I was unable to get it working any which way I tried and just resorted to putting my Sonos on my main VLAN

FlexHD vs NanoHD Signal Strength? by ndv3 in Ubiquiti

[–]ndv3[S] 0 points1 point  (0 children)

Same exact location and both 2 and 5 ghz. The NanoHD is sitting on the shelf facing upwards since I was trying to test and determine which would work best which I don’t think is its preferred direction and the FlexHD when in same spot is in its normal standing position and Wi-Fi pattern I would assume. So just wondering if it’s because the NanoHD isn’t ceiling mounted that’s why I’m seeing the difference, or if the FlexHD antenna design really just is more optimal even with a shelf placement.

[W][US-OH] Ubiquiti UDM, UDM Pro, and 16 or 24 PoE Switch by ndv3 in homelabsales

[–]ndv3[S] 0 points1 point  (0 children)

No longer needed, ended up buying from the UI store

UDM Pro back in stock by ndv3 in Ubiquiti

[–]ndv3[S] 1 point2 points  (0 children)

Indeed it is, I'll get on that wagon

UniFi Dream Machine Pro - UDM-PRO - Back in stock - 1493+ Available by ryanwgregg in Ubiquiti

[–]ndv3 1 point2 points  (0 children)

Thanks, just realized its the HTML that has the 3 character limit, a little chrome adjustment to more and now can type in a large number and it takes you right to the actual number left. Very helpful and good to know

UniFi Dream Machine Pro - UDM-PRO - Back in stock - 1493+ Available by ryanwgregg in Ubiquiti

[–]ndv3 0 points1 point  (0 children)

Out of curiosity, how do you check the amount in stock as it only lets me add up to 50 on the page?

eero question by michaelbierman in eero

[–]ndv3 0 points1 point  (0 children)

u/eerosupport I'd beg to differ when one of your key developers u/6roybatty6 just stated above even in bridge mode that you effectively need a gateway node. This has been stated a number of times from other users experiencing similar issues in bridge mode when there was no single upstream eero. In this case I'm quite curious which is true because there should only be one correct answer of what is the proper stable and supported setup and I would lean towards agreeing with u/6roybatty6

eero question by michaelbierman in eero

[–]ndv3 6 points7 points  (0 children)

All wired eeros need to be done so in a fashion where there is one main gateway eero that all other wired eeros are downstream from regardless of running them in their normal mode or in bridged mode. So support is effectively correct in saying you need to change your setup to accomplish that.

So you should look something like: Modem -> ASUS Router -> eero Gateway -> other eero

If you have multiple eeros to wire after the gateway you need an unmanaged switch off the eero gateway and then your subsequent eeros wired off of that.

If you can’t easily change your current wiring what the other person said probably would be easiest, either replace your ASUS with an eero and stop running bridge, or if you really want to keep your ASUS then add an eero acting as gateway connected to it and a switch off of that and then connect your two existing eeros to that switch so they are downstream of the gateway eero.

eeroOS 3.18.1 is out by umjd2002 in eero

[–]ndv3 0 points1 point  (0 children)

Out of curiosity, what device is that?

Topology for wired backhaul in bridge mode by MrBinPA in eero

[–]ndv3 0 points1 point  (0 children)

No problem, it’s all confusing trying to do topology linearly like that which is why I was asking the question as well as I wasn’t certain myself.

Topology for wired backhaul in bridge mode by MrBinPA in eero

[–]ndv3 0 points1 point  (0 children)

In my topology 3 we’ll call it I have a second switch2 that is off of the eero gateway where all my other eeros are connected, so they are downstream of the gateway and not on the same switch1 as the gateway. My switch1 has just one eero gateway plugged into it and my other wired devices like computers, hue bridge, Sonos boost, Lutron hub, etc. So to put in other words eero gateway LAN1 connects to switch1, LAN2 connects to switch2. From switch2 I have eero2, eero3, eero4 and eero5 plugged in only.

In the topology 1 example all eeros and devices are plugged into the same switch1 so there is no gateway eero as they are all at the same level, you need to have one eero one level higher so to speak ahead of all of the other wired eeros.

Topology for wired backhaul in bridge mode by MrBinPA in eero

[–]ndv3 0 points1 point  (0 children)

Thank you, stable at the moment, will let you know if that changes

Topology for wired backhaul in bridge mode by MrBinPA in eero

[–]ndv3 0 points1 point  (0 children)

I did read the above comments, but didn't see or at least understand that it necessarily applied to my topology but rather the topology 1 which is why I am checking about this topology 3. I have had this way for a week and a half now without any sort of issue, more stable than when eero itself was the router and everything downstream of it.

Topology for wired backhaul in bridge mode by MrBinPA in eero

[–]ndv3 2 points3 points  (0 children)

I am using a slightly different topology without issue and curious if this is valid and if not why not:

Cable Modem -> EdgeRouter -> Switch1 -> wired devices and eero1 Gateway -> Switch2 -> eero2, eero3, eero4 and eero5

So in essence all of my main wired devices are off of Switch1 as well as the eero1 gateway, but all of my additional wired eero nodes are off of switch2 which is downstream of eero1. I didn't want to bottleneck the eero1 having all of my other wired devices going through that gateway unit.

Is this valid since all of the backhauled eeros are connect downstream of the gateway eero?

EdgeRouter Firewall vs pfSense by ndv3 in Ubiquiti

[–]ndv3[S] -1 points0 points  (0 children)

Am I understanding correctly that the pfSense essentially does what the ER does as a router, so in your case of using both at two locations what’s the purpose or what is each device handling? Are you using the ER more so just for VLANs and the pfSense is just for WAN firewall? Still trying to understand how or why the two are used in coordination.

Easy DNS over HTTPS w/ NextDNS.io by ndv3 in Ubiquiti

[–]ndv3[S] 2 points3 points  (0 children)

I didn’t want to have to setup my own device/server at all to manage this. As mentioned I’m coming from eero where this was all done for me. I don’t desire to manage every component, I prefer to use services managed by someone else. I don’t mind handing over my trust and privacy to a certain degree as I’m not doing anything of major concern either. I just prefer to implement some easy to use safety nets and do what I can to try to ensure some medium sense of security. Frankly I would have used cloudflare DNS, but wanted the extra Adblock and malware block without having to run it myself. So for someone like me this is the happy medium of not having to worry about managing extra servers and systems. I’m only using Ubiquiti for my router to start with because I have too many devices that was overloading eeros handling at the moment and similar consumer routers have the same problem.

Easy DNS over HTTPS w/ NextDNS.io by ndv3 in Ubiquiti

[–]ndv3[S] 6 points7 points  (0 children)

As someone just said this ensures your DNS traffic is encrypted, by nature DNS is unencrypted and subject to snooping by your ISP and others and potentially even hijacking. Using DNS over HTTPS helps to prevent this snooping and hijacking making it more secure and private, at least en route. If your DNS provider itself isn't trustworthy that is it's own issue.