TP-Link CPE210/220: berlin-development-572abd8: not sharing internet connection

[everloop2]

What is the problem?

-> ffuplink is enabled and shows connected

and

Thu Mar 12 16:56:08 2020 daemon.err collectd[2522]: ping_sendto: Permission denied
Thu Mar 12 16:56:08 2020 daemon.err collectd[2522]: ping plugin: ping_send failed: Permission denied

What is the expected behaviour?

-> ffuplink should be disabled? at boot

-> ping should be disabled in mesh mode?

Firmware Version:
freifunk-berlin-development-572abd8

Workarounds:

disable ff_uplink -> login to box -> network -> interfaces -> ff_uplink -> edit -> disable at boot

disable ping -> login to box -> statistics -> setup -> network plugins -> ping -> disable

Comments

while testing got frequent reboots not disabling ff_uplink / ping -> not shure if its related

[SvenRoederer]

Is this a dual or single-LAN-port board?
The PoE-port will be freifunk-LAN by default.

Probably relates to: #292; freifunk-berlin/firmware-packages#185; freifunk-berlin/firmware-packages#190; #465 (comment)

[everloop2]

https://openwrt.org/toh/tp-link/cpe210

its CPE210 v2, one LAN Port

[SvenRoederer]

So this LAN-port is Freifunk-DHCP - net by default and an uplink should only be found via mesh.
Did you change the meaning of the LAN-port to be WAN?

[everloop2]

So this LAN-port is Freifunk-DHCP - net by default
yes, works like expected

uplink should only be found via mesh
yes, FreifunkWizard -> choosed: not sharing internet connection

Did you change the meaning of the LAN-port to be WAN?
no, tested mesh only mode -> if WAN is needed it has to be set up after FFwizard via wifi due one LAN port

its a major in master branch -> FreifunkWizard -> choosed: not sharing internet connection:

-> FFuplink is started at boot
-> pingcheck tries to ping

edit: WAN is not there if "not sharing internet connection" (like expected)

[SvenRoederer]

edit: WAN is not there if "not sharing internet connection" (like expected)

Upstream-OpenWrt at least defines a LAN-network (which we use as Freifunk-DHCP later) and if there are enough physical ports they will also define a WAN-network. So for single-port devices there is currently no WAN at all.
That's a thing that can be solved with some work on out configtools-package.

[pmelange]

its a major in master branch -> FreifunkWizard -> choosed: not sharing internet connection:

-> FFuplink is started at boot

PR freifunk-berlin/firmware-packages#190 would have fixed this.

[everloop2]

freifunk-berlin/firmware-packages#185
freifunk-berlin/firmware-packages#190

what about using both solutions? -> "sharing internet" disabled by default

"sharing internet" only activated by ffwizard choice

and/or installing uplink package

• if uninstalling uplink package "sharing internet" should be disabled again

[SvenRoederer]

As far as I remember, each PR has its own drawback. We should decide, which one is causing less problems (now and also for the code maintenance at all).

[pmelange]

freifunk-berlin/firmware-packages#185 fails the test case described here freifunk-berlin/firmware-packages#185 (comment) and is in my option not an option.

freifunk-berlin/firmware-packages#190 was commented on and the comment answered here freifunk-berlin/firmware-packages#190 (comment)