Celejar wrote: > On Fri, 16 Mar 2018 13:13:30 -0000 (UTC) > Dan Purgert <d...@djph.net> wrote: > >> Joe wrote: >> > [...] >> > I'd have thought that hardwired hubs are long gone, that all devices >> > with multiple Ethernet ports are switches and therefore software-based. >> > Indeed, many routers can be configured as VLANs. >> >> Hubs pretty much are. Not entirely sure where you're thinking switches >> are "software-based" though. Switching is typically done in ASICs these >> days ... >> >> > >> > I had a different problem recently, trying to work out which of a few >> > high-bandwidth 802.11ac routers could be configured in pairs as wireless >> > point-to-point links, which also uses the term 'bridging', and no, they >> > can't all do it. But documentation is usually very poor for the >> > lesser-used functions of most things. 'Bridging' is also used to mean >> > wireless repeating, which is a different thing again. >> >> Honestly, I'd never trust an "all-in-one" consumer router for that (even >> if it "supports" it on the box). Pair of purpose-built radios (e.g. >> Ubiquiti AirMAX) would probably do best for that situation. > > FWIW, I recently followed these directions: > > https://wiki.openwrt.org/doc/recipes/atheroswds > > to use an old Buffalo WZR-HP-G300NH to bring network connectivity to a > server in a location without ethernet cabling and lacking wireless > hardware. The Buffalo is configured as a wireless client connecting to > the main switch / router / AP (a TP-Link Archer [A]C2600), and the > Buffalo's wired switch is bridged to the rest of the network. The > TP-Link and Buffalo are both running OpenWRT [LEDE]. > > I'm not sure if I'm using the terminology correctly [...]
Yep, you've got the terms right. Does the buffalo also provide wifi access to other clients close to it? or is it JUST trying to pretend that it's a client device to the TP-Link? -- |_|O|_| Registered Linux user #585947 |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
