1 |
On Tue, Nov 26, 2019 at 8:10 PM Dale <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> I went to Newegg. Hey, I buy stuff there sometimes. Anyway, I've |
4 |
> looked at several routers and none of them mention IPv6 that I can |
5 |
> find. I even skimmed the reviews and can't find a mention of it. Is |
6 |
> there some secret way to know when IPv6 is supported? Is it called |
7 |
> something else maybe? |
8 |
> |
9 |
|
10 |
IMO there are three reasonable approaches you can take towards getting |
11 |
a router you won't curse yourself for buying a year from now: |
12 |
|
13 |
1. DIY. PC or other general-purpose computing hardware with multiple |
14 |
NICs. There are SBCs that work well for this. You can run pfsense or |
15 |
some other router-oriented distro/software/wrappers. Or you can just |
16 |
roll your own with netfilter and such. Max flexibility, but also max |
17 |
fuss. Unless you use a SBC you'll also be paying a price in |
18 |
electricity. Don't underestimate how much you pay for any x86-based |
19 |
system that runs 24x7 - especially anything old you have lying around. |
20 |
|
21 |
2. OpenWRT/DD-WRT/etc. Again it is a bit fussy but generally way |
22 |
less so than going pure DIY unless you're running pfsense or some |
23 |
other appliance-oriented distro. If you go this route then definitely |
24 |
check for recommendations on hardware that is known to work WELL. |
25 |
Some stuff technically works but can be very prone to having to play |
26 |
around with JTAG and such if you make the slightest mistake. You'll |
27 |
probably spend an extra $20 on hardware you won't regret buying - do |
28 |
it. |
29 |
|
30 |
3. Something commercial that isn't terrible. There are various |
31 |
options, but everybody always points to Ubiquiti and I'm mostly happy |
32 |
with them. If you want something that is more gui-based I'd go with |
33 |
their Unifi line. I'd avoid Amplifi as it is more consumer-oriented |
34 |
and you'll end up being frustrated with it. EdgeOS is getting closer |
35 |
to something like OpenWRT - it runs linux and you can get a shell and |
36 |
mess around with the CLI. However, while the EdgeOS routing options |
37 |
are great they aren't so good with WiFi and EdgeOS and Unifi don't |
38 |
interoperate all that well (not impossible, but they don't really talk |
39 |
to each other so you have to maintain two configs). I also really |
40 |
dislike that the EdgeOS management software is only supplied as a |
41 |
docker image, which is a pain if you're not using docker (one of these |
42 |
days I'll have to get it working with my bridge interface as it always |
43 |
tries to create its own and ends up having no physical network |
44 |
access). The Unifi controller software is packaged for a couple of |
45 |
distros which makes it much more flexible to deploy (and you can use |
46 |
it on docker if you wish). |
47 |
|
48 |
Personally I'm running EdgeOS on my router and Unifi on everything |
49 |
else. If I could go back I might have gone with Unifi on the gateway |
50 |
but it does bug me that it is so much more expensive and does the same |
51 |
thing. If I had it then end-to-end VLAN/etc would be much more |
52 |
practical, though I'd need a pile of managed switches to make it work |
53 |
well. |
54 |
|
55 |
I've run all three options at various points. Unless your needs are |
56 |
special I think there is value in just going with #3. It just runs |
57 |
itself for the most part, and if you want multiple access points or |
58 |
anything like that the network basically runs itself. I just plug in |
59 |
new hardware and then on the controller software it shows up, and one |
60 |
click provisions it which configures it to fit in with all my global |
61 |
settings. |
62 |
|
63 |
-- |
64 |
Rich |