Hi,
I just have a couple of general question regarding best practice for
maintaining a functional router that requires (performs best with) trunk
builds. I have a routerstation pro, and compiled/installed a custom
image so the 8316 switch would function. (and a side question on that
at the end)
I have been using openwrt for quite some years, but never had the need
to use trunk before. Everything is operating quite nicely, but since
there are no public opkg repos that include trunk builds of the
packages, do most people do what I did and just house the repo locally?
I am mostly only interested in compat-wireless, platform and
eb/ip/xtables updates, Since ath9k and mac80211 are quite the movers
and shakers on linux-wireless I like to be able to pick and choose what
compat-wireless builds I merge in, but definitely do not want the
possibility of the kmods from the public opkg repo creeping in and
biting me one day.
Is it possible to have multiple repos in my opkg.conf, or should I just
plan on building every package I use? I am just really looking for some
"I do it like this" testimony to make a decision on best practice for
openwrt. I have not used a build system that is quite layed out like
this before where the kernel and userspace are interwoven like this.
As for the 8316 switch, I have not nailed it down yet, but there is a
package that gets installed at some point that changes the gui switch
config page from saying eth1 is the switch name to cfg56xxx as the
switch name. I have not nailed down the exact package yet, and using
the cfgxxxxx name with swconfig does not work. No matter what is
displayed in the gui, eth1 is always the value that swconfig responds
to. Just an oddity I have seen pop up through several different builds..?
Thanks!
-Greg
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-users
