Hey David, know any particular changes in this release?
Topic: davidc502 1900ac 3200acm builds
The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
One particular one is the switch configuration fix for the 3200acm. Over 3 weeks there's a ton of stuff. Most of it not for the 1900/3200 series specifically, but improvements in software none-the-less. The other change worth mentioning is the kernel bump from 4.4.48 to 4.4.50.
@davidc502 I finally got around to restoring my ACv1 to factory Linksys firmware with my usb/ttl. Tested cybrnook's build then yours again and had reboots on both. I also tested latest LEDE (with 4.9.12) and that's still broken for me too.
Thanks for that method of booting to alt @nitroshift . Very handy
I'm on my last known working build now (r3498 image I had luckily kept). I'm about to try your 4.4.50.
Thanks for sticking on the older branch for now!
Edit: Looking good so far
22:00:56 up 2:57, load average: 0.09, 0.06, 0.00
(Last edited by listerwrt on 27 Feb 2017, 12:01)
@davidc502
I see you've included your config.seed for the build at [davidc502sis[dot]dynamic-dns[dot]net[dot]mvebu/ Rango[dot]lede_Rango.]
I'd like to compile my own firmware. How can I make sure I'm using the correct version of the lede-project to match your config.seed?
When I cat /include/kernel-version.mk the latest git clone of lede-project, I see the following. Will this work with the config-seed you provided at [davidc502sis[dot]dynamic-dns[dot]net[dot]mvebu/ Rango[dot]lede_Rango.] Thank you.
LINUX_VERSION-3.18 = .43
LINUX_VERSION-4.4 = .50
LINUX_VERSION-4.9 = .13
LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
LINUX_KERNEL_HASH-4.4.50 = e4944ca5bb0bdf63a7e97dc7fbdd38bcc820d8b3b57c4a3a7b3bf9c8a48216b7
LINUX_KERNEL_HASH-4.9.13 = 36464aec4fb32ed192252645819abb55ceb21eef17b3f7210b4a673e7486a268
(Last edited by TREX on 27 Feb 2017, 15:12)
@david
Installed r3582 on my wrt1900acs v1. Have same issue I had when cybrnook did his first builds after the switch change. I assign a custom MAC to the IPv4 WAN interface. When I do this I no longer get a public IP address from my ISP and do not have any Internet connectivity. My configuration is ATT UVerse Gateway (modem/router) to Internet. I configure in the Gateway DMZ a MAC address. When things work I then get the same IPv4 address as the Gateway assigned to the router WAN interface. As long as I do not make the MAC change I get an IP address from the Gateway and have Internet. Of course also double NAT. Had this same issue with cybrnook's first build with the switch change. His later builds do not have this issue.
Here is the network config file - yes I know about publishing the MAC address
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option ifname 'eth1.2'
option proto 'dhcp'
option hostname 'LEDE'
option macaddr 'E4:F4:C6:08:18:7B'
config interface 'wan6'
option ifname 'eth1.2'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 5t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
For now I am running ispyisail Gargoyle 2-10-2017
Runs well.
(Last edited by bill1228 on 27 Feb 2017, 23:14)
@bill1228
at&t sucks! I have a co-worker on at&t, and he has to put his router in the DMZ as well. He did buy a ubiquiti router that has 3 interfaces (WAN and 2 LAN). It has the ability to split the specific traffic to allow the att router to authenticate, and the rest of the traffic goes to his router. I don't think he has it set up like this yet, but it's something he wants to work on.
Thanks for the info.
@david
Never had any issues with this setup until the switch change for, I guess, wrt3200. ATT for me has been rock solid. Much better then what my daughter gets from Comcast. They have to reset their modem at least once a week. Have had service calls, etc without any fix. My good old UVerse just keeps purring along. My ATT gateway has been up for over a year now. May not be the fastest service, 23Mbps, but for my streaming and downloading just works and is dependable.
Not sure what cybrnook did with his builds, but I do not have any issues with his since the first one with the new switch config. Maybe he just grabbed a source that was fixed. I know when I run his the WAN is eth1.2 same as yours.
Let me know if there is something you would like me to try. I usually can get a window of time between teen girl and wife when I can take things down without too much screaming. Teen wants to stream stuff and wife wants her email fix.
(Last edited by bill1228 on 28 Feb 2017, 02:15)
Thanks Bill... Will take you up on it with 4.9.x
After updating to the new build 2/26/2017 (no nvram reset) on my 1900ACS shelby I wasn't able to mount my USB drive (has SWAP and ext4 partition) anymore, also after generating a new config and rebooting. Went back to 2/4/2017 (again no nvram reset) and hard drive is working again as expected. Anyone else have this issue?
After updating to the new build 2/26/2017 (no nvram reset) on my 1900ACS shelby I wasn't able to mount my USB drive (has SWAP and ext4 partition) anymore, also after generating a new config and rebooting. Went back to 2/4/2017 (again no nvram reset) and hard drive is working again as expected. Anyone else have this issue?
I had that problem but I changed from USB1/eSATA port to USB2 port and everything worked magically. Not sure if it was a problem with a specific rev. or not but nothing would mount on the USB1 port. It kept resetting and filling my syslog.
Hey David,
One package that would be really useful is the kmod-ledtrig-netfilter, which allows the LEDs to be triggered by certain packets (i.e. SSH). I noticed it's not currently included, nor does it appear to be a listed package on the LEDE site, however it is referenced as a trigger option in the LEDE documentation.
Here's the LEDE page where it's referenced:
lede-project.org/docs/user-guide/led_co … net_filter
Here's the listing of LEDE packages, where it's missing:
lede-project.org/packages/start
Any idea why it's excluded or if it could be included?
Brit
@anymouse617
I'm not sure what would be involved in tailoring it for the 1200ac/1900/3200 series. Seems like it would need to have configuration files once installed so it could control led's from different manufacturers.
Check out the rango DTS seems to be properly installed in the power management port usb/esata, must be gpio1 = 16, mpp = 48.
Check please.
(Last edited by ValCher on 1 Mar 2017, 23:50)
Hey David,
One package that would be really useful is the kmod-ledtrig-netfilter, which allows the LEDs to be triggered by certain packets (i.e. SSH). I noticed it's not currently included, nor does it appear to be a listed package on the LEDE site, however it is referenced as a trigger option in the LEDE documentation.
Here's the LEDE page where it's referenced:
lede-project.org/docs/user-guide/led_co … net_filterHere's the listing of LEDE packages, where it's missing:
lede-project.org/packages/startAny idea why it's excluded or if it could be included?
Brit
When I got home from work I started looking over the available packages, and was wondering if you've posed the question on the lede board?
After updating to the new build 2/26/2017 (no nvram reset) on my 1900ACS shelby I wasn't able to mount my USB drive (has SWAP and ext4 partition) anymore, also after generating a new config and rebooting. Went back to 2/4/2017 (again no nvram reset) and hard drive is working again as expected. Anyone else have this issue?
So far, tried both USB ports and so far am not having an issue with mounting the USB. Were you able to get it solved or did you revert?
This is my current mount.
/dev/sda /mnt/usb 14.91 GB / 14.91 GB 0% (40.00 KB)
Regarding mamba reboots on 4.9, you may want to follow this thread:
When I got home from work I started looking over the available packages, and was wondering if you've posed the question on the lede board?
I did shortly after posting the question, and I received a reply referencing this:
https://git.lede-project.org/?p=source. … f81daf0611
So it seems it was considered a duplicate package. I do have the kmod-ipt-led package installed but do not have an option for any netfilter/ipt-based LED triggering in the Luci UI. I wonder what's up with that.
davidc502 wrote:When I got home from work I started looking over the available packages, and was wondering if you've posed the question on the lede board?
I did shortly after posting the question, and I received a reply referencing this:
https://git.lede-project.org/?p=source. … f81daf0611So it seems it was considered a duplicate package. I do have the kmod-ipt-led package installed but do not have an option for any netfilter/ipt-based LED triggering in the Luci UI. I wonder what's up with that.
You may want to go back and say "not so fast!" lol It appears there are parts still missing, meaning it's not an exact duplicate.
Regarding mamba reboots on 4.9, you may want to follow this thread:
Thanks for the heads up --- Will do
@davidc502, @anymouse617: That was my link regarding the led on the netfilter commit. Things are now to be found:
make menuconfig->Kernel modules->Netfilter Extensions->kmod-ipt-led
or just / (search) that module in the interface. I do not use the facility myself so no idea what may be required in addition off of that page (I assume).
(Last edited by Villeneuve on 2 Mar 2017, 18:33)
p4p4 wrote:After updating to the new build 2/26/2017 (no nvram reset) on my 1900ACS shelby I wasn't able to mount my USB drive (has SWAP and ext4 partition) anymore, also after generating a new config and rebooting. Went back to 2/4/2017 (again no nvram reset) and hard drive is working again as expected. Anyone else have this issue?
So far, tried both USB ports and so far am not having an issue with mounting the USB. Were you able to get it solved or did you revert?
This is my current mount.
/dev/sda /mnt/usb 14.91 GB / 14.91 GB 0% (40.00 KB)
I reverted to 2/4/2017 and USB ist working fine again. I have the drive plugged into USB 2. Haven't tried the newer build with nvram reset and configuring everything new, will try that when I have time and report back. Until then I'll stick with the 2/4/2017 build.
davidc502 wrote:p4p4 wrote:After updating to the new build 2/26/2017 (no nvram reset) on my 1900ACS shelby I wasn't able to mount my USB drive (has SWAP and ext4 partition) anymore, also after generating a new config and rebooting. Went back to 2/4/2017 (again no nvram reset) and hard drive is working again as expected. Anyone else have this issue?
So far, tried both USB ports and so far am not having an issue with mounting the USB. Were you able to get it solved or did you revert?
This is my current mount.
/dev/sda /mnt/usb 14.91 GB / 14.91 GB 0% (40.00 KB)
I reverted to 2/4/2017 and USB ist working fine again. I have the drive plugged into USB 2. Haven't tried the newer build with nvram reset and configuring everything new, will try that when I have time and report back. Until then I'll stick with the 2/4/2017 build.
Update: after updating to 2/26/2017 and resetting to defaults and configuring from scratch USB is working fine with the most recent build.
@david
WRT3200ACM question. I do not see talk of poor performance and dropouts on 5GHz wireless using your builds on theWRT3200ACM. I see lots of complaints of stability issues on the DD-WRT forums. Reason for asking is I was thinking of picking one up if the price was right.
I know there is a new driver coming soon from Marvell that should address issues.
--bill
(Last edited by bill1228 on 7 Mar 2017, 16:57)
@david
WRT3200ACM question. I do not see talk of poor performance and dropouts on 5GHz wireless using your builds on theWRT3200ACM. I see lots of complaints of stability issues on the DD-WRT forums. Reason for asking is I was thinking of picking one up if the price was right.I know there is a new driver coming soon from Marvell that should address issues.
--bill
For right now wireless does not work well on the 3200acm. 2.4Ghz is shaky and 5Ghz frankly isn't stable at all. But as we all know it is being worked on by Linksys.
I would go ahead and buy one because it does make a great router, and paired with a Wifi AP works even better. So, when the new wifi driver comes out you will be ready to go.
@david
Thanks for the info. Figure when the wrt3200x comes out the price of the wrt3200acm should drop.