firmware icon indicating copy to clipboard operation
firmware copied to clipboard

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

Open everloop2 opened this issue 5 years ago • 9 comments

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

everloop2 avatar Mar 25 '20 17:03 everloop2

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

Probably relates to: https://github.com/freifunk-berlin/firmware/issues/292; https://github.com/freifunk-berlin/firmware-packages/pull/185; https://github.com/freifunk-berlin/firmware-packages/pull/190; https://github.com/freifunk-berlin/firmware/issues/465#issuecomment-309100088

SvenRoederer avatar Mar 25 '20 22:03 SvenRoederer

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

its CPE210 v2, one LAN Port

everloop2 avatar Mar 26 '20 10:03 everloop2

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?

SvenRoederer avatar May 09 '20 12:05 SvenRoederer

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)

everloop2 avatar May 09 '20 13:05 everloop2

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.

SvenRoederer avatar May 09 '20 14:05 SvenRoederer

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

-> FFuplink is started at boot

PR https://github.com/freifunk-berlin/firmware-packages/pull/190 would have fixed this.

pmelange avatar May 10 '20 08:05 pmelange

https://github.com/freifunk-berlin/firmware-packages/pull/185 https://github.com/freifunk-berlin/firmware-packages/pull/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

everloop2 avatar May 12 '20 10:05 everloop2

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).

SvenRoederer avatar May 12 '20 19:05 SvenRoederer

freifunk-berlin/firmware-packages#185 fails the test case described here https://github.com/freifunk-berlin/firmware-packages/pull/185#issuecomment-474150669 and is in my option not an option.

freifunk-berlin/firmware-packages#190 was commented on and the comment answered here https://github.com/freifunk-berlin/firmware-packages/pull/190#discussion_r361880433

pmelange avatar May 13 '20 11:05 pmelange