-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xDSL: WAN not configurable via LuCI due missing packages #838
Comments
other options would be:
The 2nd option mentioned by @everloop2 seems also very "bloaty", as it will require to add a lot of excludes the the common packagelists. I assume the listed packages are included by upstream per default, but should not interfere with normal operation (beside of additional RAM-usage). The 1st option (changing the defauit from PPP-uplink to DHCP-uplink) seems the most practical. As this is very likely the most common usecase and the wizard don't support other uplink-types (#601). P.S: A prototype to use board specific packages, in addition to the generic packagelists, can be discussed in #765 |
@everloop2 can you post the relevant section of the uci-config? |
disadvantage i've seen so far: disabling WAN at boot does stop xDSL connection loop and together with freifunk-berlin/firmware-packages#213 syslog is not spammed by dnsmasq bothering about br-wan and ffuplink_wan
gluon: lantiq-xrx200: remove modem packages from image #2087: freifunk-gluon/gluon#2087 ~1MB less images, no xDSL connection loop, no software to run on blobbed xDSL hardware (only some paranoia / "less is more") all related packages to exclude can be put bottom in /firmware/packagelists/xxx.txt - if they dont exist for specific targets they will be ignored - "doesnt hurt". |
think this is good place:
|
If packages: ppp-mod-pppoe ppp luci-proto-ppp are removed/missing interface WAN cant be edited via LuCI (missing protocol) seen this on some xDSL boxes not using stock OpenWRT Solution see: freifunk-berlin/firmware#838 (comment)
… integrated This is based on Issue freifunk-berlin#838 to make the WAN-port configurable in LuCI.
… integrated This is based on Issue #838 to make the WAN-port configurable in LuCI.
… integrated This is based on Issue #838 to make the WAN-port configurable in LuCI.
PR #863 should fix the issue by adding the required packages for the relevant boxes only. |
… integrated This is based on Issue #838 to make the WAN-port configurable in LuCI.
… integrated This is based on Issue #838 to make the WAN-port configurable in LuCI.
Allows to define packages to be added / remove from the packagelist on a per router basis. This gives a way to do something similar to OpenWrt devicepackages, to adapt to router specific requirements. The initial usecase is handling of ath10k-wave1 chips (#696), but also turned out be handy for xDSL (#838) and others.
Firmware Version:
master: Freifunk Berlin Development 91b6ae0 -> think all others too
What is the problem?
boxes got a DSL port (FritzBox 7360x, 3370..) -> WAN not configurable via LuCI due missing packages:
What is the expected behaviour?
WAN should be configurable via LuCI - expecially to switch: DSL_WAN to LAN_WAN
(OpenWRT stable/snapshot needed packages are not missing)
Workaround/Solutions:
direct use of DSL_uplink is not done in most cases and setting it up not k.i.s.s. .
or set it via Freifunk wizard.
/firmware/packagelists/..
The text was updated successfully, but these errors were encountered: