Re: [LEDE-DEV] [PATCH] Add ip_vs kernel netfilter modules to enable load balancing capabilities

2017-03-01 Thread Mauro Mozzarelli

@John,


I send this patch using git send-email. Please let me know if this one 
is OK.

Please note that patches sent previously are superseded by this version.

Mauro

On 28/02/17 15:54, ma...@ezplanet.org wrote:

From: Mauro Mozzarelli 

IPVS (IP Virtual Server) implements transport-layer load balancing inside the 
Linux kernel, so called Layer-4 switching. IPVS running on a host acts as a 
load balancer at the front of a cluster of real servers, it can direct requests 
for TCP/UDP based services to the real servers, and makes services of the real 
servers to appear as a virtual service on a single IP address.

This patch adds kmod-nf-ipvs kernel modules option to LEDE kernel netfilter

Signed-off-by: Mauro Mozzarelli 
---
  package/kernel/linux/modules/netfilter.mk | 89 +++
  1 file changed, 89 insertions(+)

diff --git a/package/kernel/linux/modules/netfilter.mk 
b/package/kernel/linux/modules/netfilter.mk
index 6162dbc..3e4d0ba 100644
--- a/package/kernel/linux/modules/netfilter.mk
+++ b/package/kernel/linux/modules/netfilter.mk
@@ -77,6 +77,17 @@ endef
  $(eval $(call KernelPackage,nf-conntrack))
  
  
+define KernelPackage/nf-conntrack-ftp

+  SUBMENU:=$(NF_MENU)
+  TITLE:=FTP connection tracking
+  KCONFIG:=CONFIG_NF_CONNTRACK_FTP
+  DEPENDS:=kmod-nf-conntrack
+  FILES:=$(LINUX_DIR)/net/netfilter/nf_conntrack_ftp.ko
+endef
+
+$(eval $(call KernelPackage,nf-conntrack-ftp))
+
+
  define KernelPackage/nf-conntrack6
SUBMENU:=$(NF_MENU)
TITLE:=Netfilter IPv6 connection tracking
@@ -271,6 +282,84 @@ define KernelPackage/ipt-ipset
  endef
  $(eval $(call KernelPackage,ipt-ipset))
  
+IPVS_MODULES:= \

+ipvs/ip_vs \
+ipvs/ip_vs_lc \
+ipvs/ip_vs_wlc \
+ipvs/ip_vs_rr \
+ipvs/ip_vs_wrr \
+ipvs/ip_vs_lblc \
+ipvs/ip_vs_lblcr \
+ipvs/ip_vs_dh \
+ipvs/ip_vs_sh \
+ipvs/ip_vs_fo \
+ipvs/ip_vs_ovf \
+ipvs/ip_vs_nq \
+ipvs/ip_vs_sed \
+xt_ipvs
+
+define KernelPackage/nf-ipvs
+  SUBMENU:=Netfilter Extensions
+  TITLE:=IP Virtual Server modules
+  DEPENDS:=@IPV6 +kmod-lib-crc32c +kmod-ipt-conntrack +kmod-nf-conntrack
+  KCONFIG:= \
+CONFIG_IP_VS \
+CONFIG_IP_VS_IPV6=y \
+CONFIG_IP_VS_DEBUG=n \
+CONFIG_IP_VS_PROTO_TCP=y \
+CONFIG_IP_VS_PROTO_UDP=y \
+CONFIG_IP_VS_PROTO_AH_ESP=y \
+CONFIG_IP_VS_PROTO_ESP=y \
+CONFIG_IP_VS_PROTO_AH=y \
+CONFIG_IP_VS_PROTO_SCTP=y \
+CONFIG_IP_VS_TAB_BITS=12 \
+CONFIG_IP_VS_RR \
+CONFIG_IP_VS_WRR \
+CONFIG_IP_VS_LC \
+CONFIG_IP_VS_WLC \
+CONFIG_IP_VS_FO \
+CONFIG_IP_VS_OVF \
+CONFIG_IP_VS_LBLC \
+CONFIG_IP_VS_LBLCR \
+CONFIG_IP_VS_DH \
+CONFIG_IP_VS_SH \
+CONFIG_IP_VS_SED \
+CONFIG_IP_VS_NQ \
+CONFIG_IP_VS_SH_TAB_BITS=8 \
+CONFIG_IP_VS_NFCT=y \
+CONFIG_NETFILTER_XT_MATCH_IPVS
+
+  FILES:=$(foreach mod,$(IPVS_MODULES),$(LINUX_DIR)/net/netfilter/$(mod).ko)
+  $(call AddDepends/ipt,+kmod-ipt-conntrack,+kmod-nf-conntrack)
+endef
+$(eval $(call KernelPackage,nf-ipvs))
+
+define KernelPackage/nf-ipvs/description
+ IPVS (IP Virtual Server) implements transport-layer load balancing inside the 
Linux kernel
+ so called Layer-4 switching.
+endef
+
+define KernelPackage/nf-ipvs-ftp
+  SUBMENU:=$(NF_MENU)
+  TITLE:=Virtual Server FTP protocol support
+  KCONFIG:=CONFIG_IP_VS_FTP
+  DEPENDS:=kmod-nf-ipvs +kmod-nf-nat +kmod-nf-conntrack-ftp
+  FILES:=$(LINUX_DIR)/net/netfilter/ipvs/ip_vs_ftp.ko
+endef
+
+$(eval $(call KernelPackage,nf-ipvs-ftp))
+
+
+define KernelPackage/nf-ipvs-sip
+  SUBMENU:=$(NF_MENU)
+  TITLE:=Virtual Server SIP protocol support
+  KCONFIG:=CONFIG_IP_VS_PE_SIP
+  DEPENDS:=kmod-nf-ipvs +kmod-nf-nathelper-extra
+  FILES:=$(LINUX_DIR)/net/netfilter/ipvs/ip_vs_pe_sip.ko
+endef
+
+$(eval $(call KernelPackage,nf-ipvs-sip))
+
  
  define KernelPackage/ipt-nat

TITLE:=Basic NAT targets



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Baptiste Jonglez
On Wed, Mar 01, 2017 at 08:23:13AM +0100, Stijn Segers wrote:
> OK... So I tried to disable offloading on the WAN interface (eth0.2 for the
> DIR-860L), but that throws the following error:
> 
> # ethtool -K tso off gso off gro off eth0
> Cannot get device feature names: No such device
> 
> Same for any other devices I try... Is there a way to disable offloading
> without ethtool?

I'm not sure the NIC of most embedded devices actually support
offloading...


signature.asc
Description: PGP signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] [PATCH] Opkg: add --no-configure option patch.

2017-03-01 Thread Jonas Gorski
Hi,

On 17 February 2017 at 19:10, daniel  wrote:
> Hi,
>
> I am writing an auto update shell script with special install handlers
> for some of my packages. The auto updater is a package itself and can
> also be updated.
>
> Without --no-configure, opkg would kill my auto updater while it is updating
> itself.

Please don't top post, it makes the discussion hard to follow.

Anyway this tidbit was all I was after, so LGTM.

Regards
Jonas

>
>
> On 02/17/2017 06:17 AM, Jonas Gorski wrote:
>> Hi,
>>
>> On 16 February 2017 at 02:14, Daniel Danzberger  wrote:
>>> Calling opkg  with --no-configure prevents opkg
>>> from running the configuration of the package (postinstall scripts ..etc)
>>>
>>> This way opkg will only install the package, without restarting the service 
>>> for example.
>>
>> What's the use case for this? When would I want to do that?
>>
>>> Signed-off-by: Daniel Danzberger 
>>
>>
>> Regards
>> Jonas
>>
>
> --
> Regards
>
> Daniel Danzberger
> embeDD GmbH, Breitenweg 10, CH-6370 Stans
>

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Stijn Segers

Hi Baptiste,

Thanks for your input. I found this thread [1] however which suggests 
offloading capabilities:


"The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
1-2 cpu ports and 1 further port that the internal HW offloading engine
connects to. The switch core used is a MT7530, which also exists as a
standalone chip. [...]"

Johh, is there a way to disable offloading on MT7530?

Thanks!

Stijn

[1] https://lkml.org/lkml/2016/2/26/527

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Sebastian Moeller
Hi Stijn,


> On Mar 1, 2017, at 10:46, Stijn Segers  
> wrote:
> 
> Hi Baptiste,
> 
> Thanks for your input. I found this thread [1] however which suggests 
> offloading capabilities:
> 
> "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
> 1-2 cpu ports and 1 further port that the internal HW offloading engine
> connects to. The switch core used is a MT7530, which also exists as a
> standalone chip. [...]"
> 
> Johh, is there a way to disable offloading on MT7530?

If you run “ethtool -k $IFACE” ethtool should show you which offloads the 
device supports and which can be toggled. Here is an example from a wndr3700v2 
(eth1 being the dedicated WAN interface not connected to a switch)

root@router:~# ethtool -k eth1
Features for eth1:
rx-checksumming: off [fixed]
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: off
tx-scatter-gather: off [fixed]
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
tx-tcp-segmentation: off [fixed]
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp6-segmentation: off [fixed]
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: off [requested on]
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: off [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
busy-poll: off [fixed]

Best Regards
Sebastian


> 
> Thanks!
> 
> Stijn
> 
> [1] https://lkml.org/lkml/2016/2/26/527
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Sebastian Moeller

> On Mar 1, 2017, at 10:59, Sebastian Moeller  wrote:
> 
> Hi Stijn,
> 
> 
>> On Mar 1, 2017, at 10:46, Stijn Segers  
>> wrote:
>> 
>> Hi Baptiste,
>> 
>> Thanks for your input. I found this thread [1] however which suggests 
>> offloading capabilities:
>> 
>> "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
>> 1-2 cpu ports and 1 further port that the internal HW offloading engine
>> connects to. The switch core used is a MT7530, which also exists as a
>> standalone chip. [...]"
>> 
>> Johh, is there a way to disable offloading on MT7530?
> 
> If you run “ethtool -k $IFACE” ethtool should show you which offloads the 
> device supports and which can be toggled. Here is an example from a 
> wndr3700v2 (eth1 being the dedicated WAN interface not connected to a switch)
> 
> root@router:~# ethtool -k eth1
> Features for eth1:
> rx-checksumming: off [fixed]
> tx-checksumming: off
>   tx-checksum-ipv4: off [fixed]
>   tx-checksum-ip-generic: off [fixed]
>   tx-checksum-ipv6: off [fixed]
>   tx-checksum-fcoe-crc: off [fixed]
>   tx-checksum-sctp: off [fixed]
> scatter-gather: off
>   tx-scatter-gather: off [fixed]
>   tx-scatter-gather-fraglist: off [fixed]
> tcp-segmentation-offload: off
>   tx-tcp-segmentation: off [fixed]
>   tx-tcp-ecn-segmentation: off [fixed]
>   tx-tcp6-segmentation: off [fixed]
> udp-fragmentation-offload: off [fixed]
> generic-segmentation-offload: off [requested on]
> generic-receive-offload: on
> large-receive-offload: off [fixed]
> rx-vlan-offload: off [fixed]
> tx-vlan-offload: off [fixed]
> ntuple-filters: off [fixed]
> receive-hashing: off [fixed]
> highdma: off [fixed]
> rx-vlan-filter: off [fixed]
> vlan-challenged: off [fixed]
> tx-lockless: off [fixed]
> netns-local: off [fixed]
> tx-gso-robust: off [fixed]
> tx-fcoe-segmentation: off [fixed]
> tx-gre-segmentation: off [fixed]
> tx-ipip-segmentation: off [fixed]
> tx-sit-segmentation: off [fixed]
> tx-udp_tnl-segmentation: off [fixed]
> fcoe-mtu: off [fixed]
> tx-nocache-copy: off
> loopback: off [fixed]
> rx-fcs: off [fixed]
> rx-all: off [fixed]
> tx-vlan-stag-hw-insert: off [fixed]
> rx-vlan-stag-hw-parse: off [fixed]
> rx-vlan-stag-filter: off [fixed]
> l2-fwd-offload: off [fixed]
> busy-poll: off [fixed]
> 


What I forgot to mention, if ethtool -k does not show anything ethtool -K 
should also fail...

> Best Regards
>   Sebastian
> 
> 
>> 
>> Thanks!
>> 
>> Stijn
>> 
>> [1] https://lkml.org/lkml/2016/2/26/527
>> 
>> ___
>> Lede-dev mailing list
>> Lede-dev@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread John Crispin
Hi Antony,
Hi Alban,

I have been working on the ath79 OF target the last days. I created a
new target within LEDE that uses pure devicetree support with the hope
of obsoleting all our mach files and simplifying the code. The
tl-wr-1043nd-v1 now boots fine and I just started adding OF support to
the ethernet driver. Next on my list are

* adding a pinctrl driver
* adding a usb phy driver

What other tasks do you know of and does any prior work exist for the 2
previously mentioned tasks that i could use ?

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] USB3.0 regression / trying to isolate / testers needed

2017-03-01 Thread Rafał Miłecki

On 03/01/2017 08:18 AM, Thomas Reifferscheid wrote:

When you have a device running Lede that comes with at least one USB3.0
port then please insert a USB 3.0 drive/thumb drive and power it on. If
you happen to get similar dmesg messages from your cmdline within the
first 30 seconds after poweron then please report to FS#177 with a full
dmesg.


No problem here

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.13 (za...@linux-samsung.lan) (gcc version 
5.4.0 (LEDE GCC 5.4.0 r3346+1-9eacb9d7fc) ) #0 SMP Wed Mar 1 06:10:48 2017
[0.00] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt:Machine model: SmartRG SR400ac
(...)
[5.799735] usbcore: registered new interface driver usbfs
[5.805365] usbcore: registered new interface driver hub
[5.810765] usbcore: registered new device driver usb
[5.819220] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[5.826554] ehci-platform: EHCI generic platform driver
[5.833589] ehci-platform 18021000.ehci: EHCI Host Controller
[5.839348] ehci-platform 18021000.ehci: new USB bus registered, assigned 
bus number 1
[5.847569] ehci-platform 18021000.ehci: irq 36, io mem 0x18021000
[5.848316] bcm_ns_usb3 18105000.usb3-phy: Registered Broadcom Northstar USB 
3.0 PHY driver
[5.849959] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[5.851094] ohci-platform: OHCI generic platform driver
[5.851318] ohci-platform 18022000.ohci: Generic Platform OHCI controller
[5.851353] ohci-platform 18022000.ohci: new USB bus registered, assigned 
bus number 2
[5.851504] ohci-platform 18022000.ohci: irq 36, io mem 0x18022000
[5.923213] ehci-platform 18021000.ehci: USB 2.0 started, EHCI 1.00
[5.925076] hub 2-0:1.0: USB hub found
[5.925176] hub 2-0:1.0: 2 ports detected
[5.930636] xhci-hcd 18023000.xhci: xHCI Host Controller
[5.930676] xhci-hcd 18023000.xhci: new USB bus registered, assigned bus 
number 3
[5.931039] xhci-hcd 18023000.xhci: hcc params 0x02501164 hci version 0x100 
quirks 0x02010010
[5.931096] xhci-hcd 18023000.xhci: irq 37, io mem 0x18023000
[5.932301] hub 3-0:1.0: USB hub found
[5.932409] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
[5.932612] xhci-hcd 18023000.xhci: xHCI Host Controller
[5.932633] xhci-hcd 18023000.xhci: new USB bus registered, assigned bus 
number 4
[5.950320] usb usb4: We don't know the algorithms for LPM for this host, 
disabling LPM.
[5.951037] hub 4-0:1.0: USB hub found
[5.951134] hub 4-0:1.0: 1 port detected
[5.953543] kmodloader: done loading kernel modules from 
/etc/modules-boot.d/*
[5.970438] init: - preinit -
[6.014412] hub 1-0:1.0: USB hub found
[6.018233] hub 1-0:1.0: 2 ports detected
[6.740299] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
(...)
root@LEDE:/# uptime
 06:14:24 up 3 min,  load average: 0.08, 0.06, 0.02

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread Alban
On Wed, 1 Mar 2017 12:26:40 +0100
John Crispin  wrote:

> Hi Antony,
> Hi Alban,
> 
> I have been working on the ath79 OF target the last days. I created a
> new target within LEDE that uses pure devicetree support with the hope
> of obsoleting all our mach files and simplifying the code. The
> tl-wr-1043nd-v1 now boots fine and I just started adding OF support to
> the ethernet driver. Next on my list are

Having the ethernet working would be nice. Do you just target LEDE or
are you trying to get it in a state that would be acceptable for
mainline?

> * adding a pinctrl driver
> * adding a usb phy driver

The USB phy driver is already done:

http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1332371.html

That hasn't been merged for 4.11, we have to hope it make it in 4.12.

> What other tasks do you know of and does any prior work exist for the 2
> previously mentioned tasks that i could use ?

Check my github tree: https://github.com/AlbanBedel/linux/commits/ath79

There is some basic support for the TL-WR-1043ND V2 (irqchip driver for
the QCA955X EXT interrupt controller + DT) and for the ath9k.

That is not yet in my github tree, but I'm currently working on adding
nvmem support to load the eeprom data for the ath9k. With this and a few
other details the ath9k should be fully usable with DT. I hope to be
able to submit this soon enough that it could potentially be merged in
4.12.

Otherwise we would need a few more irqchip drivers, and probably some
clk driver for the clocks used by the ethernet block. Finally there is
the PCI, but I don't really know what to do with this as I don't have
any hardware using it. Is there any hardware, beside the ref boards,
known to use it?

Alban


pgpFP8NUSwXtj.pgp
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread John Crispin
Hi Alban,

thanks for the reply


> Having the ethernet working would be nice. Do you just target LEDE or
> are you trying to get it in a state that would be acceptable for
> mainline?

first of i want to make it work inside LEDE but i do want to reduce our
technical debt this year so its a realistic option to send it upstream.
once it works with a hack i will draft a proper OF binding and fwd it to
get review comments before implementing it.




>> * adding a pinctrl driver
>> * adding a usb phy driver
> 
> The USB phy driver is already done:
> 
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1332371.html
> 
> That hasn't been merged for 4.11, we have to hope it make it in 4.12.
> 

awesome, i just merged it to my test tree. i'll start working on the
pinctrl tomorrow in that case.

>> What other tasks do you know of and does any prior work exist for the 2
>> previously mentioned tasks that i could use ?
> 
> Check my github tree: https://github.com/AlbanBedel/linux/commits/ath79
> 
> There is some basic support for the TL-WR-1043ND V2 (irqchip driver for
> the QCA955X EXT interrupt controller + DT) and for the ath9k.
>

great !

> That is not yet in my github tree, but I'm currently working on adding
> nvmem support to load the eeprom data for the ath9k. With this and a few
> other details the ath9k should be fully usable with DT. I hope to be
> able to submit this soon enough that it could potentially be merged in
> 4.12.
> 

please CC me on the mails so i am up to date and can adopt the patches
as early as possible

> Otherwise we would need a few more irqchip drivers, and probably some
> clk driver for the clocks used by the ethernet block. Finally there is
> the PCI, but I don't really know what to do with this as I don't have
> any hardware using it. Is there any hardware, beside the ref boards,
> known to use it?

there are boards using PCI/e. i will have a closer look at PCI and see
if it is also a DW variant.

could you give a more detailed list of what clk and irq drivers are
missing ? i could help write the code, i am just scared to duplicate
some of your work.

apart from that, Thanks for sending this all upstream, i will be sending
a few minor patches that i created the last days in the coming days.

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] ImageBuilder ar71xx BIN_DIR issue

2017-03-01 Thread Nemesis
Hi everybody,

today we started testing lede-17.01 for OpenWISP.org and we noticed a
strange issue with the image-generator.

We supply a command like:

make image PROFILE="Default" BIN_DIR="$BIN_DIR"

but the image building fails because something goes to look for binaries
in ./bin/targets/ar71xx/generic instead of
"$BIN_DIR/targets/ar71xx/generic".

If we create manually the dir with:

mkdir ./bin/targets/ar71xx/generic

The image building procedure completes successfully.

Is this desired behaviour or not?

Regards
Federico

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] [RFC] Need help to support CPU frequency setting on Mikrotik RB devices

2017-03-01 Thread Cezary Jackiewicz
Dnia 2017-02-27, o godz. 12:28:48
Thibaut  napisał(a):

> Hi,

Hi

> I’m currently working with Alex Samorukov on bringing cpu frequency setting 
> to rbcfg for Mikrotik Routerboards devices, and in doing so, we would need a 
> bit of input from people owning that hardware and running LEDE on it:

RB411U

> 1. output of `cat /proc/cpuinfo`

root@LEDE:/# cat /proc/cpuinfo
system type  : Atheros AR7130 rev 2
machine  : MikroTik RouterBOARD 411U
processor: 0
cpu model: MIPS 24Kc V7.4
BogoMIPS : 199.06
wait instruction : yes
microsecond timers   : yes
tlb_entries  : 16
extra interrupt vector   : yes
hardware watchpoint  : yes, count: 4, address/irw mask: [0x0ffc, 
0x0ffc, 0x0ffb, 0x0ffb]
isa  : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16
shadow register sets : 1
kscratch registers   : 0
package  : 0
core : 0
VCED exceptions  : not available
VCEI exceptions  : not available

> 2. output of `dmesg | grep board=`

[0.00] Kernel command line: parts=1 boot_part_size=4194304 gpio=1983 
HZ=15000 mem=32M kmac=4C:5E:0C:31:B3:F5 board=411U ver=3.22 hw_opt= 
boot=1 mlc=8 console=ttyS0,115200 rootfstype=squashfs noinitrd

> 3. if possible, whether or not RouterBOOT offers a “cpu frequency” setting 
> (typically under key ‘f’) at boot time

Select CPU frequency:
   1 - 100MHz
   2 - 150MHz
   3 - 200MHz
* 4 - 300MHz

> 4. if possible, for various cpu frequency settings (ideally for all of them), 
> the output of `dmesg | grep Clocks; hexdump -C /dev/mtdblockN` where 
> mtdblockN is the soft_config partition. Please provide this output at least 
> once, even if there’s no frequency setting.

root@LEDE:/# dmesg | grep Clocks
[0.00] Clocks: CPU:300.000MHz, DDR:300.000MHz, AHB:150.000MHz, 
Ref:40.000MHz

root@LEDE:/# cat /proc/mtd | grep soft_config
mtd3: 1000 1000 "soft_config"
root@LEDE:/#
hexdump -C /dev/mtd3
  ff ff ff ff ff ff ff ff  ff ff 7d c7 00 00 00 00  |..}.|
0010  5b 3a 16 18 4b d4 5b 92  73 1e 24 4f bb 43 71 f1  |[:..K.[.s.$O.Cq.|
0020  64 55 a5 04 8b 57 7f 1b  f5 77 e1 47 2b fc 3a f1  |dU...W...w.G+.:.|
0030  3e 30 6e 04 fd 6e 8c 51  d7 1a 57 26 a6 e8 1c 53  |>0n..n.Q..W&...S|
0040  ee e2 42 9d 19 9a 9f 6f  4b 2a de e6 50 b4 71 0c  |..BoK*..P.q.|
0050  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  ||
*
1000


> 5. Finally, which frequency setting is the factory default one


300MHz

And RB912:

system type : Atheros AR9342 rev 3
machine : Mikrotik RouterBOARD 912UAG-2HPnD
processor   : 0
cpu model   : MIPS 74Kc V4.12
BogoMIPS: 299.82
wait instruction: yes
microsecond timers  : yes
tlb_entries : 32
extra interrupt vector  : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 
0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented: mips16 dsp dsp2
shadow register sets: 1
kscratch registers  : 0
package : 0
core: 0
VCED exceptions : not available
VCEI exceptions : not available

dmesg | grep board=
[0.00] Kernel command line:  no-uart parts=1 boot_part_size=4194304 
gpio=130607 HZ=3 mem=64M kmac=4C:5E:0C:E6:15:3D board=711Gr100 
Board=711Gr100 ver=3.33 hw_opt=00200205 boot=1 mlc=10 console=ttyS0,115200 
rootfstype=yaffs noinitrd

dmesg | grep Clocks
[0.00] Clocks: CPU:600.000MHz, DDR:350.000MHz, AHB:350.000MHz, 
Ref:25.000MHz

Clocks:
400
500
550
600
650
700
750

(Via webfig)

root@WiFi-Spot:/etc/wifispot/req# hexdump -C /dev/mtd3
  74 66 6f 53 d5 3c 09 86  00 04 00 0c 00 00 00 18  |tfoS.<..|
0010  00 04 00 11 00 00 00 00  00 04 00 0a 00 00 00 02  ||
0020  00 04 00 01 00 00 00 00  00 04 00 02 00 00 00 02  ||
0030  00 04 00 03 00 00 00 01  00 04 00 04 00 00 00 00  ||
0040  00 04 00 05 00 00 00 00  00 04 00 07 00 00 00 00  ||
0050  00 04 00 09 00 00 00 00  00 04 00 0f 00 00 00 00  ||
0060  00 04 00 15 00 00 00 00  00 04 00 17 00 00 00 00  ||
0070  00 04 00 0d 00 00 00 00  00 04 00 06 33 2e 33 33  |3.33|
0080  00 08 00 0b 00 00 00 00  00 01 64 10 00 04 00 1d  |..d.|
0090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
1000


Default is 600MHz

-- 
Pozdrawiam,
 Cezary Jackiewicz

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread Alban
On Wed, 1 Mar 2017 16:44:30 +0100
John Crispin  wrote:

> could you give a more detailed list of what clk and irq drivers are
> missing ? i could help write the code, i am just scared to duplicate
> some of your work.

For IRQ all that is left in arch/mips/ath79/irq.c should be moved to
clean drivers in drivers/irqchip with OF support added. Keeping the old
non-OF platform running is the annoying part.

For the clocks AFAIR the ethernet driver do some direct access in the
clock registers. This should obviously be replaced with a clean
abstraction to get it in mainline. Otherwise like for the IRQ the code
in arch/mips/ath79/clock.c should be moved to drivers/clk.

Alban


pgpQdEbhB297b.pgp
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread John Crispin


On 01/03/2017 18:03, Alban wrote:
> On Wed, 1 Mar 2017 16:44:30 +0100
> John Crispin  wrote:
> 
>> could you give a more detailed list of what clk and irq drivers are
>> missing ? i could help write the code, i am just scared to duplicate
>> some of your work.
> 
> For IRQ all that is left in arch/mips/ath79/irq.c should be moved to
> clean drivers in drivers/irqchip with OF support added. Keeping the old
> non-OF platform running is the annoying part.
> 
> For the clocks AFAIR the ethernet driver do some direct access in the
> clock registers. This should obviously be replaced with a clean
> abstraction to get it in mainline. Otherwise like for the IRQ the code
> in arch/mips/ath79/clock.c should be moved to drivers/clk.
> 
> Alban
> 

ok, i'll stumble acrss those clk regs in the ag71xx driver tomorrow when
i remove pdata support.

i just stumbled across
Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt and it
looks like we can reuse the generic code and just describe the pinmux
inside the devicetree. test image is building just now.

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] [PATCH] brcm63xx: Add Comtrend AR-5315u support

2017-03-01 Thread Daniel Gonzalez Cabanelas
Add support for the Comtrend AR-5315u router

This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, 
with an onboard BCM43217 wifi, 4 ethernet ports and 1 
USB host port

Signed-off-by: Daniel Gonzalez Cabanelas 
diff --git a/target/linux/brcm63xx/base-files/etc/board.d/01_leds 
b/target/linux/brcm63xx/base-files/etc/board.d/01_leds
index 61f685e..959b1ca 100755
--- a/target/linux/brcm63xx/base-files/etc/board.d/01_leds
+++ b/target/linux/brcm63xx/base-files/etc/board.d/01_leds
@@ -16,6 +16,9 @@ a4001n1)
 a4001n)
ucidef_set_led_usbdev "usb" "USB" "A4001N:green:usb" "1-1"
;;
+ar-5315u)
+   ucidef_set_led_usbdev "usb" "USB" "AR-5315u:green:usb" "1-1"
+   ;;
 av4202n)
ucidef_set_led_netdev "wlan0" "WLAN" "AV4202N:blue:wifi" "wlan0"
;;
diff --git a/target/linux/brcm63xx/base-files/etc/board.d/02_network 
b/target/linux/brcm63xx/base-files/etc/board.d/02_network
index f703dfd..2b6dfe8 100755
--- a/target/linux/brcm63xx/base-files/etc/board.d/02_network
+++ b/target/linux/brcm63xx/base-files/etc/board.d/02_network
@@ -98,6 +98,7 @@ vr-3026e)
"0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "8t@eth0"
;;
 
+ar-5315u |\
 vh4032n)
ucidef_add_switch "switch0" \
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "8t@eth0"
diff --git a/target/linux/brcm63xx/base-files/etc/diag.sh 
b/target/linux/brcm63xx/base-files/etc/diag.sh
index df1d616..8c74efa 100644
--- a/target/linux/brcm63xx/base-files/etc/diag.sh
+++ b/target/linux/brcm63xx/base-files/etc/diag.sh
@@ -12,6 +12,9 @@ set_state() {
a4001n)
status_led="A4001N:green:power"
;;
+   ar-5315u)
+   status_led="AR-5315u:green:power"
+   ;;
ar-5381u)
status_led="AR-5381u:green:power"
;;
diff --git a/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc 
b/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
index 650db9d..d05926b 100644
--- a/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
+++ b/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
@@ -13,6 +13,7 @@ do_fixcrc() {
 case "$(brcm63xx_board_name)" in
a4001n |\
a4001n1 |\
+   ar-5315u |\
ar-5381u |\
ar-5387un |\
bcm96328avng |\
diff --git a/target/linux/brcm63xx/base-files/lib/brcm63xx.sh 
b/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
index 4fe33eb..5e75042 100755
--- a/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
+++ b/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
@@ -84,6 +84,9 @@ brcm63xx_dt_detect() {
"BT Voyager V2500V")
board_name="v2500v_bb"
;;
+   "Comtrend AR-5315u")
+   board_name="ar-5315u"
+   ;;
"Comtrend AR-5381u")
board_name="ar-5381u"
;;
diff --git a/target/linux/brcm63xx/dts/ar-5315u.dts 
b/target/linux/brcm63xx/dts/ar-5315u.dts
new file mode 100644
index 000..2ff067a
--- /dev/null
+++ b/target/linux/brcm63xx/dts/ar-5315u.dts
@@ -0,0 +1,67 @@
+/dts-v1/;
+
+#include "bcm6318.dtsi"
+
+#include 
+
+/ {
+   model = "Comtrend AR-5315u";
+   compatible = "comtrend,ar-5315u", "brcm,bcm6318";
+
+   chosen {
+   bootargs = "root=/dev/mtdblock2 rootfstype=squashfs,jffs2 
noinitrd console=ttyS0,115200";
+   };
+
+   gpio-keys-polled {
+   compatible = "gpio-keys-polled";
+   #address-cells = <1>;
+   #size-cells = <0>;
+   poll-interval = <20>;
+   debounce-interval = <60>;
+
+   wps {
+   label = "wps";
+   gpios = <&gpio0 3 1>;
+   linux,code = ;
+   };
+   reset {
+   label = "reset";
+   gpios = <&gpio1 1 1>;
+   linux,code = ;
+   };
+   };
+
+   gpio-leds {
+   compatible = "gpio-leds";
+
+   wps_green {
+   label = "AR-5315u:green:wps";
+   gpios = <&gpio0 0 1>;
+   };
+   power_green {
+   label = "AR-5315u:green:power";
+   gpios = <&gpio0 1 1>;
+   default-state = "on";
+   };
+   usb_green {
+   label = "AR-5315u:green:usb";
+   gpios = <&gpio0 2 1>;
+   };
+   inet_green {
+   label = "AR-5315u:green:inet";
+   gpios = <&gpio0 8 1>;
+   };
+   inet_red {
+   label = "AR-5315u:red:inet";
+   gpios = <&gpio0 9 1>;
+   };
+   dsl_green {
+   label = "AR-5315u:green:dsl";
+   gpios = <&gpio0 10 1>;
+   };
+   power_red {
+  

Re: [LEDE-DEV] [PATCH] brcm63xx: Add Comtrend AR-5315u support

2017-03-01 Thread Florian Fainelli
On 03/01/2017 10:37 AM, Daniel Gonzalez Cabanelas wrote:
> Add support for the Comtrend AR-5315u router
> 
> This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, 
> with an onboard BCM43217 wifi, 4 ethernet ports and 1 
> USB host port
> 
> Signed-off-by: Daniel Gonzalez Cabanelas 

There is something wrong with your patches submitted, in that they don't
conform to this:

subject: something

Commit message

Signed-off-by: myself
---


Essentially, we are missing the --- between your Signed-off-by tag and
the git diff, how are you producing these patches? Can you make sure you
use git format-patch + git send-email and do a git commit -s  when
creating local changesets?

> diff --git a/target/linux/brcm63xx/base-files/etc/board.d/01_leds 
> b/target/linux/brcm63xx/base-files/etc/board.d/01_leds
> index 61f685e..959b1ca 100755
> --- a/target/linux/brcm63xx/base-files/etc/board.d/01_leds
> +++ b/target/linux/brcm63xx/base-files/etc/board.d/01_leds
> @@ -16,6 +16,9 @@ a4001n1)
>  a4001n)
>   ucidef_set_led_usbdev "usb" "USB" "A4001N:green:usb" "1-1"
>   ;;
> +ar-5315u)
> + ucidef_set_led_usbdev "usb" "USB" "AR-5315u:green:usb" "1-1"
> + ;;
>  av4202n)
>   ucidef_set_led_netdev "wlan0" "WLAN" "AV4202N:blue:wifi" "wlan0"
>   ;;
> diff --git a/target/linux/brcm63xx/base-files/etc/board.d/02_network 
> b/target/linux/brcm63xx/base-files/etc/board.d/02_network
> index f703dfd..2b6dfe8 100755
> --- a/target/linux/brcm63xx/base-files/etc/board.d/02_network
> +++ b/target/linux/brcm63xx/base-files/etc/board.d/02_network
> @@ -98,6 +98,7 @@ vr-3026e)
>   "0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "8t@eth0"
>   ;;
>  
> +ar-5315u |\
>  vh4032n)
>   ucidef_add_switch "switch0" \
>   "0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "8t@eth0"
> diff --git a/target/linux/brcm63xx/base-files/etc/diag.sh 
> b/target/linux/brcm63xx/base-files/etc/diag.sh
> index df1d616..8c74efa 100644
> --- a/target/linux/brcm63xx/base-files/etc/diag.sh
> +++ b/target/linux/brcm63xx/base-files/etc/diag.sh
> @@ -12,6 +12,9 @@ set_state() {
>   a4001n)
>   status_led="A4001N:green:power"
>   ;;
> + ar-5315u)
> + status_led="AR-5315u:green:power"
> + ;;
>   ar-5381u)
>   status_led="AR-5381u:green:power"
>   ;;
> diff --git a/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc 
> b/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
> index 650db9d..d05926b 100644
> --- a/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
> +++ b/target/linux/brcm63xx/base-files/etc/uci-defaults/09_fix_crc
> @@ -13,6 +13,7 @@ do_fixcrc() {
>  case "$(brcm63xx_board_name)" in
>   a4001n |\
>   a4001n1 |\
> + ar-5315u |\
>   ar-5381u |\
>   ar-5387un |\
>   bcm96328avng |\
> diff --git a/target/linux/brcm63xx/base-files/lib/brcm63xx.sh 
> b/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
> index 4fe33eb..5e75042 100755
> --- a/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
> +++ b/target/linux/brcm63xx/base-files/lib/brcm63xx.sh
> @@ -84,6 +84,9 @@ brcm63xx_dt_detect() {
>   "BT Voyager V2500V")
>   board_name="v2500v_bb"
>   ;;
> + "Comtrend AR-5315u")
> + board_name="ar-5315u"
> + ;;
>   "Comtrend AR-5381u")
>   board_name="ar-5381u"
>   ;;
> diff --git a/target/linux/brcm63xx/dts/ar-5315u.dts 
> b/target/linux/brcm63xx/dts/ar-5315u.dts
> new file mode 100644
> index 000..2ff067a
> --- /dev/null
> +++ b/target/linux/brcm63xx/dts/ar-5315u.dts
> @@ -0,0 +1,67 @@
> +/dts-v1/;
> +
> +#include "bcm6318.dtsi"
> +
> +#include 
> +
> +/ {
> + model = "Comtrend AR-5315u";
> + compatible = "comtrend,ar-5315u", "brcm,bcm6318";
> +
> + chosen {
> + bootargs = "root=/dev/mtdblock2 rootfstype=squashfs,jffs2 
> noinitrd console=ttyS0,115200";
> + };
> +
> + gpio-keys-polled {
> + compatible = "gpio-keys-polled";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + poll-interval = <20>;
> + debounce-interval = <60>;
> +
> + wps {
> + label = "wps";
> + gpios = <&gpio0 3 1>;
> + linux,code = ;
> + };
> + reset {
> + label = "reset";
> + gpios = <&gpio1 1 1>;
> + linux,code = ;
> + };
> + };
> +
> + gpio-leds {
> + compatible = "gpio-leds";
> +
> + wps_green {
> + label = "AR-5315u:green:wps";
> + gpios = <&gpio0 0 1>;
> + };
> + power_green {
> + label = "AR-5315u:green:power";
> + gpios = <&gpio0 1 1>;
> + default-state = "on";
> + };
> + usb_green {
> + labe

[LEDE-DEV] Drumming up more interest in LEDE

2017-03-01 Thread tapper
Hi Is LEDE ready to try and get more people from the wider community 
involved?


A thought I had is to do a code optimization week.
I know that LEDE is optimized to fit on small flash chips, but It mite 
be a good way of getting other coders to look in the code to see if they 
can save a bite here and there, or try and make something run a little 
faster.
Or if that is know good what about a bug bash week? MS has bug bashes 
and they seem to get a lot of people talking about windows 10. I am not 
a coder and don't understand all the ins and outs of what I am talking 
about, but I like LEDE. If just one new dev or doc righter was to be 
added to the team it is a net win for all.


If something like this was to be tryed you could post about it on the 
forLinux forums and on Slashdot, Hacker News and /r/linux r/openwrt.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] [PATCH] brcm63xx: Add Comtrend AR-5315u support

2017-03-01 Thread Daniel
2017-03-01 19:46 GMT+01:00 Florian Fainelli :
> On 03/01/2017 10:37 AM, Daniel Gonzalez Cabanelas wrote:
>> Add support for the Comtrend AR-5315u router
>>
>> This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash,
>> with an onboard BCM43217 wifi, 4 ethernet ports and 1
>> USB host port
>>
>> Signed-off-by: Daniel Gonzalez Cabanelas 
>
> There is something wrong with your patches submitted, in that they don't
> conform to this:
>
> subject: something
>
> Commit message
>
> Signed-off-by: myself
> ---
> 
>
> Essentially, we are missing the --- between your Signed-off-by tag and
> the git diff, how are you producing these patches?

Hi Florian. For the patches I use this procedure

git add file1 file2
git diff --cached > mypatch.patch

Then I copy the patch into my email client (KMail) and send it as a
regular mail to the mailing list

> Can you make sure you
> use git format-patch + git send-email and do a git commit -s  when
> creating local changesets?

I guess this generates the patch with the required header?
git add file1 file2
git commit -s
git format-patch -1 HEAD

only the stuff between --- and signed-off is missing, or is there
anything else wrong?.  Just to be sure because I also want to continue
using KMail for sending patches.

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] [PATCH] brcm63xx: Add Comtrend AR-5315u support

2017-03-01 Thread Florian Fainelli
On 03/01/2017 11:44 AM, Daniel wrote:
> 2017-03-01 19:46 GMT+01:00 Florian Fainelli :
>> On 03/01/2017 10:37 AM, Daniel Gonzalez Cabanelas wrote:
>>> Add support for the Comtrend AR-5315u router
>>>
>>> This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash,
>>> with an onboard BCM43217 wifi, 4 ethernet ports and 1
>>> USB host port
>>>
>>> Signed-off-by: Daniel Gonzalez Cabanelas 
>>
>> There is something wrong with your patches submitted, in that they don't
>> conform to this:
>>
>> subject: something
>>
>> Commit message
>>
>> Signed-off-by: myself
>> ---
>> 
>>
>> Essentially, we are missing the --- between your Signed-off-by tag and
>> the git diff, how are you producing these patches?
> 
> Hi Florian. For the patches I use this procedure
> 
> git add file1 file2
> git diff --cached > mypatch.patch

Woah that seems complicated, you are essentially not tracking your files
with git here, so rebasing, branching and so on is not going to work
quite well. Highly recommend you commit and rebase changes when you need to.

> 
> Then I copy the patch into my email client (KMail) and send it as a
> regular mail to the mailing list
> 
>> Can you make sure you
>> use git format-patch + git send-email and do a git commit -s  when
>> creating local changesets?
> 
> I guess this generates the patch with the required header?
> git add file1 file2
> git commit -s
> git format-patch -1 HEAD
> 
> only the stuff between --- and signed-off is missing, or is there
> anything else wrong?.

That's the only thing.

>  Just to be sure because I also want to continue
> using KMail for sending patches.

Why use KMail when git-send-email is a known good SMTP client? It won't
mangle your patches unlike what Kmail could do...
-- 
Florian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Stijn Segers
Op wo, 1 mrt 2017 om 10:59 , schreef Sebastian Moeller 
:

Hi Stijn,


 On Mar 1, 2017, at 10:46, Stijn Segers 
 wrote:


 Hi Baptiste,

 Thanks for your input. I found this thread [1] however which 
suggests offloading capabilities:


 "The GSW is found in all of the 1000mbit SoCs. it has 5 external 
ports,
 1-2 cpu ports and 1 further port that the internal HW offloading 
engine
 connects to. The switch core used is a MT7530, which also exists as 
a

 standalone chip. [...]"

 Johh, is there a way to disable offloading on MT7530?


If you run “ethtool -k $IFACE” ethtool should show you which 
offloads the device supports and which can be toggled. Here is an 
example from a wndr3700v2 (eth1 being the dedicated WAN interface not 
connected to a switch)


root@router:~# ethtool -k eth1
Features for eth1:
rx-checksumming: off [fixed]
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: off
tx-scatter-gather: off [fixed]
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
tx-tcp-segmentation: off [fixed]
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp6-segmentation: off [fixed]
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: off [requested on]
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: off [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
busy-poll: off [fixed]

Best Regards
Sebastian




 Thanks!

 Stijn

 [1] https://lkml.org/lkml/2016/2/26/527

 ___
 Lede-dev mailing list
 Lede-dev@lists.infradead.org
 http://lists.infradead.org/mailman/listinfo/lede-dev


Hi Sebastian,

That does indeed return a long list, but it looks like the things that 
Dave Taht suggested I disable are already disabled?


ethtool -K tso off gso off gro off

Of those, only gso shows as tx-gso-robust [off]: fixed...

# ethtool -k eth0
Features for eth0:
rx-checksumming: on
tx-checksumming: on
tx-checksum-ipv4: on
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: on
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp6-segmentation: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: off [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
busy-poll: off [fixed]


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] ath79 - pending tasks

2017-03-01 Thread Martin Blumenstingl via Lede-dev
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Alan,

first I'd like to say thank you for your work on upstream ath79 support!

On Wed, Mar 1, 2017 at 2:32 PM, Alban  wrote:
> There is some basic support for the TL-WR-1043ND V2 (irqchip driver for
> the QCA955X EXT interrupt controller + DT) and for the ath9k.
>
> That is not yet in my github tree, but I'm currently working on adding
> nvmem support to load the eeprom data for the ath9k. With this and a few
> other details the ath9k should be fully usable with DT. I hope to be
> able to submit this soon enough that it could potentially be merged in
> 4.12.
I've also seen your RFC patch on the linux-wireless list. you may want
to split things to make it easier to review though (that's my personal
opinion):
1. add the 25MHz clock handling to the existing ath9k_of_init function
2. add OF support to ath9k/ahb.c
3. add devdata support (maybe to eeprom.c instead of ahb.c since there
are many boards with ath9k PCI without EEPROM - there devdata support
could be interesting as well)

with just 1. and 2. you should be able to get the ath9k AHB devices
running if you add the "qca,no-eeprom" property and then provide the
EEPROM data using a firmware hotplug script (see [0] and [1])


Regards,
Martin


[0] 
http://lxr.free-electrons.com/source/drivers/net/wireless/ath/ath9k/init.c#L574
[1] 
https://github.com/torvalds/linux/blob/fc383ffdb91a393086daf56c3d48a545e1cbd6e4/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt

--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Sebastian Moeller
Hi Stijn,


> On Mar 1, 2017, at 21:28, Stijn Segers  
> wrote:
> 
> Op wo, 1 mrt 2017 om 10:59 , schreef Sebastian Moeller :
>> Hi Stijn,
>>> On Mar 1, 2017, at 10:46, Stijn Segers  
>>> wrote:
>>> Hi Baptiste,
>>> Thanks for your input. I found this thread [1] however which suggests 
>>> offloading capabilities:
>>> "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
>>> 1-2 cpu ports and 1 further port that the internal HW offloading engine
>>> connects to. The switch core used is a MT7530, which also exists as a
>>> standalone chip. [...]"
>>> Johh, is there a way to disable offloading on MT7530?
>> If you run “ethtool -k $IFACE” ethtool should show you which offloads the 
>> device supports and which can be toggled. Here is an example from a 
>> wndr3700v2 (eth1 being the dedicated WAN interface not connected to a switch)
>> root@router:~# ethtool -k eth1
>> Features for eth1:
>> rx-checksumming: off [fixed]
>> tx-checksumming: off
>>  tx-checksum-ipv4: off [fixed]
>>  tx-checksum-ip-generic: off [fixed]
>>  tx-checksum-ipv6: off [fixed]
>>  tx-checksum-fcoe-crc: off [fixed]
>>  tx-checksum-sctp: off [fixed]
>> scatter-gather: off
>>  tx-scatter-gather: off [fixed]
>>  tx-scatter-gather-fraglist: off [fixed]
>> tcp-segmentation-offload: off
>>  tx-tcp-segmentation: off [fixed]
>>  tx-tcp-ecn-segmentation: off [fixed]
>>  tx-tcp6-segmentation: off [fixed]
>> udp-fragmentation-offload: off [fixed]
>> generic-segmentation-offload: off [requested on]
>> generic-receive-offload: on
>> large-receive-offload: off [fixed]
>> rx-vlan-offload: off [fixed]
>> tx-vlan-offload: off [fixed]
>> ntuple-filters: off [fixed]
>> receive-hashing: off [fixed]
>> highdma: off [fixed]
>> rx-vlan-filter: off [fixed]
>> vlan-challenged: off [fixed]
>> tx-lockless: off [fixed]
>> netns-local: off [fixed]
>> tx-gso-robust: off [fixed]
>> tx-fcoe-segmentation: off [fixed]
>> tx-gre-segmentation: off [fixed]
>> tx-ipip-segmentation: off [fixed]
>> tx-sit-segmentation: off [fixed]
>> tx-udp_tnl-segmentation: off [fixed]
>> fcoe-mtu: off [fixed]
>> tx-nocache-copy: off
>> loopback: off [fixed]
>> rx-fcs: off [fixed]
>> rx-all: off [fixed]
>> tx-vlan-stag-hw-insert: off [fixed]
>> rx-vlan-stag-hw-parse: off [fixed]
>> rx-vlan-stag-filter: off [fixed]
>> l2-fwd-offload: off [fixed]
>> busy-poll: off [fixed]
>> Best Regards
>>  Sebastian
>>> Thanks!
>>> Stijn
>>> [1] https://lkml.org/lkml/2016/2/26/527
>>> ___
>>> Lede-dev mailing list
>>> Lede-dev@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/lede-dev
> 
> Hi Sebastian,
> 
> That does indeed return a long list, but it looks like the things that Dave 
> Taht suggested I disable are already disabled?
> 
> ethtool -K tso off gso off gro off
> 
> Of those, only gso shows as tx-gso-robust [off]: fixed...
> 
> # ethtool -k eth0
> Features for eth0:
> rx-checksumming: on
> tx-checksumming: on
> tx-checksum-ipv4: on
> tx-checksum-ip-generic: off [fixed]
> tx-checksum-ipv6: on
> tx-checksum-fcoe-crc: off [fixed]
> tx-checksum-sctp: off [fixed]
> scatter-gather: on
> tx-scatter-gather: on
> tx-scatter-gather-fraglist: off [fixed]
> tcp-segmentation-offload: on
> tx-tcp-segmentation: on
> tx-tcp-ecn-segmentation: off [fixed]
> tx-tcp6-segmentation: on
> udp-fragmentation-offload: off [fixed]
> generic-segmentation-offload: on

This is GSO

> generic-receive-offload: on

And this GRO

so both seem to be still on, I do seem to remember that Linux will keep giant 
packets intact once assembled, so for testing you might want to disable GRO for 
all interfaces, to make sure no large meta-packet ever reaches cake… I also 
recall being flummoxed by the fact that the output of ethtool -k is not 
identical with what to give to ethtool -K...

Best Regards

> large-receive-offload: off [fixed]
> rx-vlan-offload: off [fixed]
> tx-vlan-offload: on
> ntuple-filters: off [fixed]
> receive-hashing: off [fixed]
> highdma: off [fixed]
> rx-vlan-filter: off [fixed]
> vlan-challenged: off [fixed]
> tx-lockless: off [fixed]
> netns-local: off [fixed]
> tx-gso-robust: off [fixed]
> tx-fcoe-segmentation: off [fixed]
> tx-gre-segmentation: off [fixed]
> tx-ipip-segmentation: off [fixed]
> tx-sit-segmentation: off [fixed]
> tx-udp_tnl-segmentation: off [fixed]
> fcoe-mtu: off [fixed]
> tx-nocache-copy: off
> loopback: off [fixed]
> rx-fcs: off [fixed]
> rx-all: off [fixed]
> tx-vlan-stag-hw-insert: off [fixed]
> rx-vlan-stag-hw-parse: off [fixed]
> rx-vlan-stag-filter: off [fixed]
> l2-fwd-offload: off [fixed]
> busy-poll: off [fixed]
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Weedy
On 28 February 2017 at 05:40, Martin Tippmann  wrote:
> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>  wrote:
>> Okay, so I tracked it down to cake being the culprit. When I disable the
>> Cake SQM instance, no more of those traces, and no more sudden reboots.
>>
>> If I can help debug this, let me know - I enabled a Cake SQM instance on an
>> APU2 and so far that seems to run fine.
>
> cake: Maybe it's related - I'm seeing high cpu usage with cake on
> TP-Link 841N routers even with none, moderate traffic after a while. I
> don't see hanging tasks in the logs but the system feels sluggish even
> it's idle.


I have a WR842ND v2, I'm also seeing high CPU suddenly with only
default fq-codel on 4.4.50.
Are you able to git bisect? This particular device is installed in a
remote location so I can't deal with it for a while.

 >pppoe-wan│ 494.90KiB351 pps │  12.13KiB192 pps

Mem: 19620K used, 8308K free, 4K shrd, 864K buff, 1472K cached
CPU:   1% usr  93% sys   0% nic   0% idle   0% io   0% irq   4% sirq
Load average: 6.89 4.88 2.96 5/58 9906
  PID  PPID USER STAT   VSZ %VSZ %CPU COMMAND
 1555 1 root R 1948   7%  16% /usr/sbin/hostapd -s -P /var/run/wifi
   97 2 root SW   0   0%  12% [kworker/0:1]
  440 1 root S 1180   4%   7% /sbin/ubusd
 9165  8584 root R 1196   4%   5% top -d3
  840 1 root S 1396   5%   5% /usr/sbin/odhcpd
 9886  9883 root R 1224   4%   4% /bin/sh /etc/netCheck.sh
3 2 root SW   0   0%   4% [ksoftirqd/0]
  104 2 root SW   0   0%   2% [kswapd0]

On the other hand, here is my WDR4300

 >pppoe-wan│ 420.29KiB   1.69K pps│  78.09KiB
 1.10K pps

Mem: 21212K used, 6716K free, 12K shrd, 792K buff, 1584K cached
CPU:   6% usr  88% sys   0% nic   0% idle   0% io   0% irq   5% sirq
Load average: 3.38 2.13 1.16 1/56 9259
  PID  PPID USER STAT   VSZ %VSZ %CPU COMMAND
   97 2 root RW   0   0%  18% [kworker/0:1]
 1555 1 root S 1948   7%  12% /usr/sbin/hostapd -s -P /var/run/wifi
 2714  2713 root R 2484   9%   4% /usr/sbin/bmon -p ppp*
 9240  9239 root S 1184   4%   4% /bin/ping -W 3 -c 6 -q -I pppoe-wan g
  840 1 root S 1396   5%   4% /usr/sbin/odhcpd
3 2 root SW   0   0%   4% [ksoftirqd/0]
 9241  9239 root S 1204   4%   3% awk /packets received  {print $4}
 9165  8584 root R 1188   4%   3% top -d3
 2389 1 dnsmasq  S 1412   5%   2% /usr/sbin/dnsmasq -C /var/etc/dnsmasq

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Weedy
On 1 March 2017 at 17:40, Weedy  wrote:
> On 28 February 2017 at 05:40, Martin Tippmann  wrote:
>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>>  wrote:
>>> Okay, so I tracked it down to cake being the culprit. When I disable the
>>> Cake SQM instance, no more of those traces, and no more sudden reboots.
>>>
>>> If I can help debug this, let me know - I enabled a Cake SQM instance on an
>>> APU2 and so far that seems to run fine.
>>
>> cake: Maybe it's related - I'm seeing high cpu usage with cake on
>> TP-Link 841N routers even with none, moderate traffic after a while. I
>> don't see hanging tasks in the logs but the system feels sluggish even
>> it's idle.
>
>
> I have a WR842ND v2, I'm also seeing high CPU suddenly with only
> default fq-codel on 4.4.50.
> Are you able to git bisect? This particular device is installed in a
> remote location so I can't deal with it for a while.
>
>  >pppoe-wan│ 494.90KiB351 pps │  12.13KiB192 
> pps
>
> Mem: 19620K used, 8308K free, 4K shrd, 864K buff, 1472K cached
> CPU:   1% usr  93% sys   0% nic   0% idle   0% io   0% irq   4% sirq
> Load average: 6.89 4.88 2.96 5/58 9906
>   PID  PPID USER STAT   VSZ %VSZ %CPU COMMAND
>  1555 1 root R 1948   7%  16% /usr/sbin/hostapd -s -P 
> /var/run/wifi
>97 2 root SW   0   0%  12% [kworker/0:1]
>   440 1 root S 1180   4%   7% /sbin/ubusd
>  9165  8584 root R 1196   4%   5% top -d3
>   840 1 root S 1396   5%   5% /usr/sbin/odhcpd
>  9886  9883 root R 1224   4%   4% /bin/sh /etc/netCheck.sh
> 3 2 root SW   0   0%   4% [ksoftirqd/0]
>   104 2 root SW   0   0%   2% [kswapd0]
>
> On the other hand, here is my WDR4300
>
>  >pppoe-wan│ 420.29KiB   1.69K pps│  78.09KiB
>  1.10K pps
>
> Mem: 21212K used, 6716K free, 12K shrd, 792K buff, 1584K cached
> CPU:   6% usr  88% sys   0% nic   0% idle   0% io   0% irq   5% sirq
> Load average: 3.38 2.13 1.16 1/56 9259
>   PID  PPID USER STAT   VSZ %VSZ %CPU COMMAND
>97 2 root RW   0   0%  18% [kworker/0:1]
>  1555 1 root S 1948   7%  12% /usr/sbin/hostapd -s -P 
> /var/run/wifi
>  2714  2713 root R 2484   9%   4% /usr/sbin/bmon -p ppp*
>  9240  9239 root S 1184   4%   4% /bin/ping -W 3 -c 6 -q -I pppoe-wan 
> g
>   840 1 root S 1396   5%   4% /usr/sbin/odhcpd
> 3 2 root SW   0   0%   4% [ksoftirqd/0]
>  9241  9239 root S 1204   4%   3% awk /packets received  {print $4}
>  9165  8584 root R 1188   4%   3% top -d3
>  2389 1 dnsmasq  S 1412   5%   2% /usr/sbin/dnsmasq -C 
> /var/etc/dnsmasq

Crap wrong paste, both of those top excerpts are from my WR842ND at
about 550pps.
But choking on sys usage.

HERE is my WDR4300, moving over 2000pps with basically no sys usage.

Mem: 42960K used, 17456K free, 216K shrd, 3084K buff, 9716K cached
CPU:   5% usr   1% sys   0% nic  79% idle   0% io   0% irq  14% sirq
Load average: 0.14 0.13 0.13 1/59 7749
  PID  PPID USER STAT   VSZ %VSZ %CPU COMMAND
 2365 1 nobody   R 5260   9%   4% /usr/sbin/darkstat --verbose -i br-la
 2297  2295 root S 2408   4%   3% /usr/sbin/bmon -p ppp*
3 2 root RW   0   0%   1% [ksoftirqd/0]
 2548  2536 root R 1188   2%   1% top -d3
 2229   995 root S 1132   2%   0% /usr/sbin/dropbear -F -P /var/run/dro
20388 2 root SW   0   0%   0% [kworker/0:0]

 >pppoe-wan│ 420.29KiB   1.69K pps│  78.09KiB
 1.10K pps

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Martin Tippmann
On Wed, Mar 1, 2017 at 11:40 PM, Weedy  wrote:
> On 28 February 2017 at 05:40, Martin Tippmann  wrote:
>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>>  wrote:
>>> Okay, so I tracked it down to cake being the culprit. When I disable the
>>> Cake SQM instance, no more of those traces, and no more sudden reboots.
>>>
>>> If I can help debug this, let me know - I enabled a Cake SQM instance on an
>>> APU2 and so far that seems to run fine.
>>
>> cake: Maybe it's related - I'm seeing high cpu usage with cake on
>> TP-Link 841N routers even with none, moderate traffic after a while. I
>> don't see hanging tasks in the logs but the system feels sluggish even
>> it's idle.
>
>
> I have a WR842ND v2, I'm also seeing high CPU suddenly with only
> default fq-codel on 4.4.50.

with fq_codel everything is fine for me (on WR841Nv7/8/11), even cake
is fine on a MAC1200R. We have a few a few WR842N in our community
mesh network but these are also remote and in use at the moment.

Just to be sure: Is the build newer than January 27? We've seen high
sys without these fixes:
https://git.lede-project.org/?p=source.git;a=commit;h=82d580e8b5c43f4dd228f2bb5927ca3e47752a34
https://git.lede-project.org/?p=source.git;a=commit;h=b94177e10fc72f9309eae7459c3570e5c080e960

> Are you able to git bisect? This particular device is installed in a
> remote location so I can't deal with it for a while.

Never done that but I guess it's possible. At the moment I'm not even
sure how to reliable reproduce the cake issue. Filling /tmp might
trigger it. I've discovered after routers got slow after uploading the
a new sysupgrade image to /tmp.

I wanted to play with trace-cmd (ftrace) after discovering that you
can use trace-cmd to record what's going on in the kernel remotly
using the -N option
(http://man7.org/linux/man-pages/man1/trace-cmd-record.1.html) but
this is pretty much all new to me.

The idea was to get a grasp where that high sys is coming from. Had no
time to play with this and I'm not sure if trace-cmd record is even
the right tool for this or works on my 32mb ram/4mb flash device.
http://www.brendangregg.com/linuxperf.html has a lot of stuff that
looks useful.

I don't have much time until the weekend, if I manage to get the
traces running I'll post them in the bugticket.

regards
Martin

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51

2017-03-01 Thread Martin Tippmann
On Thu, Mar 2, 2017 at 2:32 AM, Martin Tippmann  wrote:
> On Wed, Mar 1, 2017 at 11:40 PM, Weedy  wrote:
>> On 28 February 2017 at 05:40, Martin Tippmann  wrote:
>>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>>>  wrote:
 Okay, so I tracked it down to cake being the culprit. When I disable the
 Cake SQM instance, no more of those traces, and no more sudden reboots.

 If I can help debug this, let me know - I enabled a Cake SQM instance on an
 APU2 and so far that seems to run fine.
>>>
>>> cake: Maybe it's related - I'm seeing high cpu usage with cake on
>>> TP-Link 841N routers even with none, moderate traffic after a while. I
>>> don't see hanging tasks in the logs but the system feels sluggish even
>>> it's idle.
>>
>>
>> I have a WR842ND v2, I'm also seeing high CPU suddenly with only
>> default fq-codel on 4.4.50.

Totally missed the 4.4.50 part, sorry - so it's not the ath9k fixes, I
have no idea.

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] LEDE - Telnet Client

2017-03-01 Thread Carlo
Hi,
I was using OpenWrt as remote "swiss army knife" with the embedded telnet
client. I'm usual to get access via SSH to the remote OpenWRT box and from
there use the telnet client for router/switch configuration, for mail/http
session simulation/troubleshooting  etc .
Now I'm starting using LEDE, but it seems that the telnet client has been
removed from busybox.

If I search the package list i see only this programs:

mac-telnet-client
mac-telnet-discover
mac-telnet-ping
mac-telnet-server
openocd
perl-net-telnet
ruby-net-telnet
ser2net

I don't want to recompile the sources to re-include telnet client, since I
prefer to keep the OS as standard as possible, to use it an all the
supported hardware.
I was wondering if the dev-team can consider to re-introduce the telnet
client in the OS or consider to make available a stand-alone pkg telnet
clien.

Regards
Carlo

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev