I've switched my primary router to 3200 on latest David's build.
So far so good, both WiFi works stable. Coverage a bit extended compared to previous one (Xiaomi mi3 router).
5G is better for sure, my work PC is always on AC, instead of fallback to 2.4G N.
I've got two issues, but both is LEDE-specific, not Wifi-related... first one, on status page I saw WAN interface as br-lan local IP. It's known "issue" - i've configured default GW as routed local IP in br-lan, so UCI web script showed that interface as WAN. Removed the GW and now showing right ipv4 WAN interface including DNSes.
THe second strange issue I've got is the dnsmasq won't startup after reboot.
I have to run in manually after reboot... I see no any logs of dnsmasq in /tmp/syslog

what I see is following:

root@LINKSYS:~# ps -ef| grep dns
root      2862     1  0 16:48 ?        00:00:00 /bin/sh /etc/rc.common /etc/init.d/dnsmasq reload
root      3070     1  0 16:48 ?        00:00:00 /bin/sh /usr/lib/ddns/dynamic_dns_updater.sh -v 0 -S afraid -- start
root      3744  3733  0 16:49 pts/0    00:00:00 grep dns
root@LINKSYS:~# ps -ef | grep dns
root      2862     1  0 16:48 ?        00:00:00 /bin/sh /etc/rc.common /etc/init.d/dnsmasq reload
root      3070     1  0 16:48 ?        00:00:00 /bin/sh /usr/lib/ddns/dynamic_dns_updater.sh -v 0 -S afraid -- start
root      4884  3733  0 16:51 pts/0    00:00:00 grep dns
root@LINKSYS:~#  /etc/init.d/dnsmasq reload
udhcpc: started, v1.26.2
udhcpc: sending discover
udhcpc: no lease, failing
root@LINKSYS:~# ps -ef | grep dns
root      2862     1  0 16:48 ?        00:00:00 /bin/sh /etc/rc.common /etc/init.d/dnsmasq reload
root      3070     1  0 16:48 ?        00:00:00 /bin/sh /usr/lib/ddns/dynamic_dns_updater.sh -v 0 -S afraid -- start
dnsmasq   5003     1  0 16:51 ?        00:00:00 /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg02411c -k -x /var/run/dnsmasq/dnsmasq.cfg02411c.pid
root      5037  3733  0 16:51 pts/0    00:00:00 grep dns

So as I can see, dnsmasq init script is started, but hunged on some step without any error log.
My wan interfaces (both ipv4 and ipv6) are DHCP.

I've googled but can't find any advice....

EDIT:
I've checked \etc\init.d\dnsmasq script and found udhcp called to check if there is no another dhcp server is running on that interface. "force" config is checked prior to that, so i've fixed my issue with dnsmasq startup after reboot by setting "force" in UCI web on lan interface.

(Last edited by AddRemover on 5 Sep 2017, 12:10)

Yep RCN in Boston also only assigns IPv4, yet offers FTTH as well. Also found out that their "HD" is 1080i instead of 1080p. I was floored. Is this 2004?

Most TSPs in Canada do the same thing.

Anyone know if there are any special settings that are recommended for gigabit WAN connections? I can't tell if it's an ISP change thing (went from Xfinity to RCN) or a speed tier change (250Mbps to 1Gbps), but I started getting these errors showing up on the system log:

kern.err kernel: [  207.082835] mvneta f1070000.ethernet eth1: bad rx status 0fad0000 (max frame length error), size=1536

and it seems to repeat every 10 mins or so. FWIW, my WAN MTU is set to the default 1500.

Thoughts?

(Last edited by anymouse617 on 5 Sep 2017, 19:36)

Thanks for answering. I already knew how to setup a guest network. It would be a good idea to include the guest network by default.

I sustain about 375 ish on average, initial 20 second burst is 440 down to 375 and holding. Late night can be higher however. Still running FQ_CODEL even with '0' on downstream and '32000' on up.

(Last edited by PolarisX on 6 Sep 2017, 00:14)

Since I upgrade to the new release, port forwarding seems not working with me !! I re flash it again clean with no configurations and still I can't get any incoming.

I am testing the incoming through my Torrent tracker and not working at all it was working perfectly 2 releases ago ....

Before anyone asks, yes I did turn the firewall of on my Windows machine and testes the incoming

Any one can help?

(Last edited by alebreez on 6 Sep 2017, 21:34)

See if UPnP gets the port open for you.  Check the first 3 boxes, save and apply. Then start up the torrent program, and look for the port to show up in Active UPnP Redirects, and be sure to delete any other ports. Once the port is detected and is active, run the test and see if the result is different. When finished un-check the boxes/save and apply.

Also, the configuration hasn't changed at all since 2 builds ago?

*Edit* Is a VPN in use whilst torrenting?

*EDIT 2*  Is the firewall zone "WAN" set to Input "drop"?

(Last edited by davidc502 on 6 Sep 2017, 23:02)

So here is what I did, turned off windows firewall and then I removed the port from the Firewall of the router checked the UPnP and the port is active and the test result didn't change it says not accepting incoming.

- No configuration changed at all

- No VPN

- firewall zone "WAN" is as default after fresh flash and it is like in the picture bellow 

https://prnt.sc/gi0nr8

Edit1: not sure if this is relative, I noticed that the ISP has IPv6 now

Edit2: When I connect directly to the ISP router test went through with the Windows firwall is on

Thanks for the help

(Last edited by alebreez on 7 Sep 2017, 00:59)

At the very bottom of the image where it says WAN and column "Input" -- change to "reject" and try the test again.

@starcms

Began a new build with the CPU scaling patch and the Config-defaults.in change. Let me know if you think you will be on-line in around 2 hours (9:30pm CDT).

*EDIT*

Will get a hold of you tomorrow.

(Last edited by davidc502 on 7 Sep 2017, 03:27)

I tried everything nothing works

I need to mention here, that just came to my mind, ISP updated the firmware of their router couple of weeks ago not sure if this problem happens at the same time but if it does what do you think I need to change here ?

Can you log into the ISP router and verify port forwarding is configured?

I checked I am not sure if I need to do the port forwarding in there to my router, LEDE, then from lede to all machines that I have Torrent client installed .

so I tried something else I changed the ISP router to bridge mode tried to configure LEDE with no luck so I switched it back to router mode and voilà  everything seems to be working fine with no changes required.

My guess is ISP blocked that port for whatever reason although I tried changing the port all along several times but I am really not sure what seems to be the problem.

The good thing now is it works fine ..... The ugly, tho, is I need to understand what happened I am just curious

Thanks David for the help

(Last edited by alebreez on 7 Sep 2017, 16:57)

For a short period of time my ISP was blocking incoming on port 22, so I couldn't get to my router... sigh..  The next day I changed the listening port for SSH, on my router to port 21, and it worked no problem. Well, a couple weeks later, my ISP opened port 22 back up, so I switched back.... I only wish they would make up their minds.

The thing is I went back to test all ports that I had problem with and they worked so I am really confused LOL the only thing changed that I just noticed is the IP my public IP is changed as I couldn't check my servers from outside till I went back home and I noticed the IP changed

Could be 2 lvl of blocking like block that port on that IP !!!! Never seen this before but could be

Keep up the good work David

Sorry, long day at work yesterday and went to sleep early.  Should be up around that time tonight.

Any problems compiling?  Does it seem to work okay?

(Last edited by starcms on 7 Sep 2017, 21:15)

Well, both times I tried to compile, the machine rebooted about halfway through... Unknown reason why. Now that I'm back home, I'll try and babysit to see what might be happening.

@starcms,

Okay, it completed compiling... I guess it just needed reassurance from me sitting there

Let me know if you need the .img or any of the packages.

https://davidc502sis.dynamic-dns.net/temp/

So far so good on the new image. Also, let me know when you've grabbed it so it can be taken down.

*EDIT*
root@lede:~# which diff
/usr/bin/diff

(Last edited by davidc502 on 8 Sep 2017, 00:43)

Got it.

if it worked, u should be able to just issue a diff command anywhere.  Just type diff in SSH and see what happens, or I'll let u know soon enough.  Like diff --help

Edit: Crap, I thought it was working, but then I saw you had the diffutils package installed.  When I removed it, it stopped working. 

You edited source/package/utils/busybox/Config-defaults.in and under BUSYBOX_DEFAULT_DIFF, BUSYBOX_DEFAULT_FEATURE_DIFF_DIR, and BUSYBOX_DEFAULT_FEATURE_DIFF_LONG_OPTIONS you changed it from "default n" to "default y"?  You sure that the edited version was compiled and it didn't pull it off github (like the issue u were having when u were first trying to modify the file inside of mwlwifi to change the version number/date)?

I'll check out the throttling now, that is honestly more important, because if we can't get the diff option to work in busybox, you can just leave the diffutils package included as it was in that build.  The point of doing these changes was to enable the diff command in busybox so that diffutils wouldn't be needed.

Edit2: Double crap on a stick.  Doesn't look like the throttling patch worked either, because all the commands on the page I had linked to don't work:

cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

all return can't open (find) file, just as it is  (was) when the patch wasn't implemented. 

Did you build a version for yourself on your 3200ACM?  Any luck running diff --help with diffutils removed or any luck with any of those cat commands?  Maybe the .bin for my 1200AC didn't get the change to the busybox file or the kernel patch but the one for your 3200 did?  It's definitely running a new version, r4795 with kernel 4.9.47 and had diffutils included.

What were the problems you were having when you were building it?  Related to either the change to the busybox file or the kernel patch for throttling?

@hnyman, any advice you can give to @david on implementing your kernel patch to enable cpu throttling?

@david, I'm sure both things are something simple you overlooked, because quite a few people reported in @hynman's thread getting the throttling working (no one had issues).  It's just as if both changes didn't make/compile into the build.

(Last edited by starcms on 8 Sep 2017, 03:26)

Looks like that patch will require a bit of rework post commit, as things got moved.

Edit: My bad, thought I spotted a patch under target/linux/generic/.

(Last edited by Villeneuve on 8 Sep 2017, 04:15)

Guess I'm tired or I'm overlooking something obvious.

How does https://github.com/lede-project/source/ … 6e304c201f (the github version of the commit you linked, easier tor read I think) affect https://github.com/hnyman/source/commit … e0ce41c1ac

The patches are still located in https://github.com/lede-project/source/ … atches-4.9

Hi,

Apologies for a question of basic nature.

I have a 3200acm that has stock firmware on partition 2 and dd-wrt on partition 1. It is currently running off dd-wrt on partition 1. I wanted to try Davidc’s firmware. So, I booted to partition 2, stock firmware. Used the file “lede-mvebu-linksys-wrt3200acm-squashfs-factory-2017-08-20.img” and used stock firmware to update/ overwrite partition 1.

But, after the update, when the router booted to partition 1, the radios did not come up. The power LED was glowing solid. But the internet LED was blinking, white. I power cycled the router but same result.

Can someone suggest what went wrong? Will OpenWRT not write onto a partition being used by dd-wrt? Should I first put stock firmware on both partitions and then try? Should I not change the name of the firmware file? I added the release date to the name.

If this has already been answered, can someone point me to the solution.

Thank you for your time.

Two things:

1. Reboot your modem after your router boots into LEDE. You need to do this as your modem needs to rebind with your router (I am probably not using correct terminology here)

2. LEDE has wireless disabled by default as it would be insecure to have an open wireless connection. Instead, hook up a computer via ethernet and go to 192.168.1.1. You will log in with no password, and then you can set a password. From there, go to the wireless config setup (I believe it is under Network -> Wireless) and you can enable your wireless bands, along with configure channels, security etc.)

Thank you. Did 1, but forgot about 2. Had read about it somewhere but skipped my mind. Going to give it another shot over the weekend.