On Tue, Nov 22, 2016 at 06:50:35AM -0800, David Lang wrote: > On Tue, 22 Nov 2016, Marc Haber wrote: > >thanks for sharing your knowledge. I appreciate that. > > > >On Fri, Nov 18, 2016 at 08:29:02PM +0100, Mirko Parthey wrote: > >>On Sun, Nov 13, 2016 at 05:23:06PM +0100, Marc Haber wrote: > >>> - 802.1q support on the Ethernet > >> > >>The switch chips in consumer access points come with some limitations, > >>you should check if they can meet your requrements: > >>- They only support a small number of vlans, a typical limit is 15. > > > >Does that mean that the VLAN IDs are also limited to the 0..15 range > >or can I have 15 VLANs with arbitrary IDs? > > As I noted earlier, most current switches don't have this limit. But older > switches (and many current switches in their default startup mode) have a > limit. On some of them it's 0..15, on others it's 0..31, etc. This was > common even on commercial switches 5-10 years ago, but the advance of > technology means that in most cases it's a matter of flipping a toggle in > the config to support all 4K VLANS.
Commercial Switches (for example the HP 25**, 28** devices) had a limit on number of VLANs (I think it was 32 out of the box, I increased that first thing after unpacking), but never a limit on the range of VLAN IDs. You could have VLANs 1, 250, 100, 3847, but not more than 32 of them in the default settings. > >>> When I tried to build my own OpenWRT for the last time, I failed > >>> miserably. Therefore, I would like to be able to use a pre-built > >>> OpenWRT image on the device. I believe this might influence the device > >>> selection since the image is probably going to be fairly large, > >>> influencing the need of flash size. > >> > >>It is rarely necessary to build from source yourself. > >>You can use the Image Builder, which will download your choice of pre-built > >>binary packages (*.ipk) and combine them into a flashable image. > >>https://wiki.openwrt.org/doc/howto/obtain.firmware.generate > >>This will give most of the same benefits, such as optimal use of the > >>flash memory space through filesystem-level compression. > > > >That sounds good. > > That said, there are significant advantages of being able to build your own. > What did you run into trouble with? (or contact me off-list and I'll help > you try again) I don't remember, it was too long ago. I think that I didn't even get past the "get a working compiler" stage after unpacking the OpenWRT build chroot. I think I even set up a CentOS VM to make sure that my Debian host didn't interfere with the OpenWRT build process. > >>The config interfaces may not be as polished as in commercial offerings, > >>but they do the job. For me, the advantages of OpenWrt/LEDE more than > >>make up for some rough edges in the UI. > >> > >>For an evaluation of the config frontends, you could also try out > >>OpenWrt/LEDE on x86 hardware, even on a virtual machine. > > > >I would be willing to buy a cheaper accesspoint in the 50-euro-range > >to try things out. Any recommendations? > > Take a look at the WNDR3800, it's getting old, but that means it's cheap on > e-bay :-) It's cheap if you Ebay it in the US. In Europe, it most likely was never on the market, Ebay Germany does only have a single offer with a price of well over 80 Euros. > It doesn't do -ac, but for most of what you are trying to figure out, > that isn't going to matter. Get the basic configuration and > capabilities (and build process) figured out, then switch to a more > expensive router that will do the speed you want and very little will > change. That's what I intended to do, yes. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
