Re: [LEDE-DEV] hnet-full & LEDE: bug report

2016-07-19 Thread Dave Taht
Ironically, we took a stab at getting homenet stuff up yesterday in an IETF breakout session, but got stopped at step 0 due to all the hardware we had on us not getting built for. I filed a bug on the buildbot at: https://bugs.lede-project.org/index.php?do=details&task_id=56 On Tue, Jul 19, 2016

[LEDE-DEV] hnet-full & LEDE: bug report

2016-07-19 Thread Rich Brown
I have always wanted to try out homenet. In light of the recommendation expressed in http://lists.infradead.org/pipermail/lede-dev/2016-July/001772.html, it looks as if LEDE would be a good platform for further experimentation. I followed Tore Anderson's excellent instructions at: https://blo

[LEDE-DEV] May be out of commission

2016-07-19 Thread Daniel Dickinson
Hi all, Things have gotten a little crazy around here and I've not been able spend time on LEDE, and there's indications that I may soon be permanently unable to assist (not by my choice). Maybe I'm just having issues, if I am things should be back on track soon and I'll be back because I'm going

[LEDE-DEV] Netgear WNAP210 support

2016-07-19 Thread Miha Verlič
Hello, a few monts ago I've sent similar mail to OpenWrt hackers mailing list, but got no reply. Not sure whether the cause is no interest in porting or OpenWrt/LEDE split I'm resending it here. I've come accross few Netgear WNAP210 access points, which is listed on OpenWrt Wanted Hardware page.

[LEDE-DEV] Update - Re: Getting started with LEDE?

2016-07-19 Thread Rich Brown
Update: I had good success getting LEDE installed on two routers (Netgear WNDR3800 and mqmaker WiTi Router). Based on that experience, I created a "Getting Started with LEDE" page that could become the home page of the Documentation section. I submitted a PR for review and (hopefully) incorpora

Re: [LEDE-DEV] Ethernet link up/down mt7688 board not detected by hotplug

2016-07-19 Thread Baptiste Clenet
Additional information: Board is down and ethernet unplugged. Board is switched on, I wait for end of boot then I plug ethernet cable, here; hotplug is call ACTION=ifup Then I unplug, no hotplug call, then I plug, no hotplug call. I don't understand why it is called only if I boot without ethernet

[LEDE-DEV] [PATCH] base-files: use procd init for urandom_seed

2016-07-19 Thread Etienne CHAMPETIER
Previous implementation was blocking the init and breaking halt/reboot/sysupgrade (reported by Daniel Golle) Signed-off-by: Etienne CHAMPETIER --- package/base-files/files/etc/init.d/urandom_seed | 29 package/base-files/files/sbin/urandom_seed | 19 +++

Re: [LEDE-DEV] [PATCH v5] base-files: seed /dev/urandom

2016-07-19 Thread Etienne Champetier
2016-07-19 2:44 GMT+02:00 Daniel Golle : > Hi Etienne, > Hi Arjen, > Hi John, > Hi Jo, Hi Daniel > > while wondering which process is blocking my rootfs from being > unmounted for sysupgrade I discovered that getrandom story going > on and while waiting for blocking I/O read from /dev/urandom, it

Re: [LEDE-DEV] wrong switch configuration

2016-07-19 Thread e9hack
Hi, it's my fault. The image contains 02_network and 02_network.orig in /etc/board.d. I did add TP-Link WR802N to the build tree. For pull, sometimes I've to revert my changes and apply the patches afterwards again. This did generate some *.orig and *.rej files. The build script copies the whol

[LEDE-DEV] Ethernet link up/down mt7688 board not detected by hotplug

2016-07-19 Thread Baptiste Clenet
Hi, I added two scripts in hotplug /etc/htoplug.d/net and /iface to check when the interface eth0 is up or down or even link up/down. Each time I plug the cable, Kernel driver says: [ 1376.48] rt305x-esw 1011.esw: link changed 0x01 and unplug: [ 1373.49] rt305x-esw 1011.esw: link c

Re: [LEDE-DEV] Routing two interfaces on same subnet

2016-07-19 Thread Baptiste Clenet
I think, most simple would be to detect a link up/down with Hotplug and then run ifup/down on ethernet so route is automatically removed. I tried to add my hotplug script: root@:/# cat /etc/hotplug.d/iface/40-eth # enable access from client network #[ "$INTERFACE" = lan ] || exit 0 #[ "$ACTION" =