126

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hnyman wrote:

Backfire 10.03.SVN (r29594) / LuCI 0.10 Branch (0.10+svn8131)
http://koti.welho.com/hnyman1/Openwrt/backfire-r29594-2011-12-21-release-10.03.1/

Running smoothly here, thanks!

127 (edited by hnyman 2012-06-02 10:19:32)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hnyman wrote:

with the trunk build I have wondered about the stability of the new iwinfo based wireless-stats tab in luci-statistics. The recent builds have been occasionally crashing if that graph is enabled. But when the iwinfo section is disabled in luci-statistics, the last build r29571-2011-12-19 has been quite stable. The reason of the crashes is not quite clear yet, but I am keeping the graph off for the time being, just in case.

Looks like the iwinfo wireless stats has a memory leak. It steadily grabs more memory. See the chart where it is enabled for the last 2.5 hours...
https://dev.openwrt.org/ticket/10630#comment:6

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Hello,
I'm trying to make the QOS work. Currently, it isn't working, but I don't know wether something is wrong with my setup or with your build.
I've saw there is some requirement, as indicated on the wiki. By default, kmod-ifb is not included in your build, and I'm not sure as wether act_connmark is included or not.

I've manually added kmod-ifb with opkg. QOS seems to be still uneffective. Once again, that might be me misconfiguring it. I remember a lot of people having problems with QOS on OpenWRT
Before starting to fiddle around, I would be glad to know if anybody have a working QOS on their 3700 with this build ? Thanks !

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Basic QoS works for me out of package both with my Backfire build and with trunk build. As far as I know, there is no need to add any kernel modules, unless you want to do something more advanced.

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Has anyone determined the vulnerability of the WNDR3700/hnyman box to the recent WPS vulnerabilities? IIUC, attacks are now reported "in the wild".

http://lifehacker.com/5873407/how-to-crack-a-wi+fi-networks-wpa-password-with-reaver

Quote from the article:-
"...Unfortunately, as Gallagher points out at Ars, even with WPS
manually turned off through his router's settings, Reaver was still
able to crack his password.

In a phone conversation, Craig Heffner said that the inability to shut
this vulnerability down is widespread. He and others have found it to
occur with every Linksys and Cisco Valet wireless access point they've
tested. "On all of the Linksys routers, you cannot manually disable
WPS," he said. While the Web interface has a radio button that
allegedly turns off WPS configuration, "it's still on and still
vulnerable.

So that's kind of a bummer."

Quote from a linked article at
http://arstechnica.com/business/news/20 … -setup.ars

"The routers most vulnerable to these attacks—the ones without PIN
lockout features—include products from Cisco's Linksys division,
Belkin, Buffalo, Netgear, TP-Link, ZyXEL, and Technicolor.

None of the vendors has issued a statement on the vulnerability, or
replied to inquiries from Veihbock."

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hnyman wrote:

Basic QoS works for me out of package both with my Backfire build and with trunk build. As far as I know, there is no need to add any kernel modules, unless you want to do something more advanced.

Ok, thanks for the confirmation. I must now go dive in the qos documentation on OpenWRT, and understand why it's not effective for me...

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Do you possibly plan to provide sources for your builds?

133 (edited by hnyman 2012-01-22 08:03:32)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

mmhorda wrote:

Do you possibly plan to provide sources for your builds?

I already have released them as diffs.
E.g. for most recent trunk build, go http://koti.welho.com/hnyman1/Openwrt/trunk-r29722-2012-01-12/

Take the .config file that is there and use it for compilation (or modify it according to your tastes)
Then use unix 'patch' to patch main trunk source with http://koti.welho.com/hnyman1/Openwrt/t … 5-svn.diff
Then patch 'packages' feeds sources with http://koti.welho.com/hnyman1/Openwrt/t … kages.diff
(If you want to modify also LucI source, download LuCI sources and patch with Luci diff. There is mainly changes to statistics defaults, a comment about reset button and LuCI config option for WPS button functionality)

The main diff also includes my full build scripts.

EDIT: Well, the newest trunk build is now http://koti.welho.com/hnyman1/Openwrt/trunk-r29844-2012-01-22/

134 (edited by hnyman 2012-01-22 08:13:09)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

98i4rtg wrote:

Has anyone determined the vulnerability of the WNDR3700/hnyman box to the recent WPS vulnerabilities? IIUC, attacks are now reported "in the wild".

My build uses the normal hostapd component for wireless security functionalities. But only the "pushbutton" authentication method is active there, so the "PIN code" method should not work. And that vulnerability is just about the PIN code thing.

(I haven't checked how well hostapd would support PIN code authentication in Openwrt, and I haven't checked if they have already patched the vulnerability upstream at hostapd sources.)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

nerbrume wrote:
hnyman wrote:

Basic QoS works for me out of package both with my Backfire build and with trunk build. As far as I know, there is no need to add any kernel modules, unless you want to do something more advanced.

Ok, thanks for the confirmation. I must now go dive in the qos documentation on OpenWRT, and understand why it's not effective for me...

You have to check the default speed limits for QoS and then turn it on. (I have turned it off by default, as having it on without your personalized speed limits for your connection, it would be futile to have it enabled.)

136

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

My question may sound dumb, but anyway, here it is. I'm new to the WNDR3700v2 and have flashed hnyman's WNDR3700v2-trunk-r29844-2012-01-22-0802-squashfs-sysupgrade.bin, at the default settings. There are only IPv4 addresses in my LAN. I would like connect to the internet thru a cable modem, but I never get a (IPv4) address from my ISP UnityMedia. The WAN interface is set to DHCP, so it should be a no-brainer, shouldn't it...

137

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Many cable modems require a reset to accept a new mac/device.

138

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Did several resets, tried different cables (Cat5e, Cat6, Cat6Crossover). The best I can get is a WAN LED blinking at a rate of about 3 seconds. My WRT54G/DD-WRT works fine on the same cable I use now, and so did my TP-Link 1043ND/OpenWRT before I bricked it.

My network:

package 'dhcp'

config 'dnsmasq'
        option 'domainneeded' '1'
        option 'boguspriv' '1'
        option 'filterwin2k' '0'
        option 'localise_queries' '1'
        option 'rebind_protection' '1'
        option 'rebind_localhost' '1'
        option 'local' '/lan/'
        option 'domain' 'lan'
        option 'expandhosts' '1'
        option 'nonegcache' '0'
        option 'authoritative' '1'
        option 'readethers' '1'
        option 'leasefile' '/tmp/dhcp.leases'
        option 'resolvfile' '/tmp/resolv.conf.auto'

config 'dhcp' 'lan'
        option 'interface' 'lan'
        option 'start' '100'
        option 'limit' '150'
        option 'leasetime' '12h'

config 'dhcp' 'wan'
        option 'interface' 'wan'
        option 'ignore' '1'


package 'network'

config 'interface' 'loopback'
        option 'ifname' 'lo'
        option 'proto' 'static'
        option 'ipaddr' '127.0.0.1'
        option 'netmask' '255.0.0.0'

config 'interface' 'lan'
        option 'ifname' 'eth0.1'
        option 'type' 'bridge'
        option 'proto' 'static'
        option 'ipaddr' '192.168.1.1'
        option 'netmask' '255.255.255.0'

config 'interface' 'wan'
        option 'ifname' 'eth1'
        option 'proto' 'dhcp'

config 'switch'
        option 'name' 'rtl8366s'
        option 'reset' '1'
        option 'enable_vlan' '1'
        option 'blinkrate' '2'

config 'switch_vlan'
        option 'device' 'rtl8366s'
        option 'vlan' '1'
        option 'ports' '0 1 2 3 5t'

config 'switch_port'
        option 'device' 'rtl8366s'
        option 'port' '1'
        option 'led' '6'

config 'switch_port'
        option 'device' 'rtl8366s'
        option 'port' '2'
        option 'led' '9'

config 'switch_port'
        option 'device' 'rtl8366s'
        option 'port' '5'
        option 'led' '2'

139

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

You might try using the "Override MAC address" option on the WAN interface to match that of your working WRT54G. If that succeeds, then you could either leave it that way, or call your ISP and complain about having to register your router.

140

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

It turned out to be a weird, cable-related problem. My Cisco EPC3212 cablemodem, the WNDR3700 and a Netgear GS108 GBit-Switch are located in two different corners of the room. My previous setup looked like C-----W-N, where one dash stands for one meter of Ethernet cable. I changed that to C-W-----N, and now it works. Using the same cables!

From what I've read in the forum, there are reports about both GBit and Crossover cable issues with the WNDR3700. I still don't know how to make sense of the above.

141 (edited by hnyman 2012-01-28 13:11:28)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hnyman wrote:

Looks like the iwinfo wireless stats has a memory leak. It steadily grabs more memory.

Jow has fixed that memory leak in iwinfo component, so the trunk wireless stats should again be stable.

I have updated both Backfire and Trunk builds to r29933. One addition in January has been the HTTPS support for LuCI.

Trunk seems to have some trouble with mounting mtdblocks(?):
Jan 24 18:44:09 OpenWrt user.notice fstab: mount: mounting /dev/mtdblock0 on /mnt/mtdblock0 failed: Invalid argument
The system log contains those references to /mnt/mtdblock0, 1, 2, 3, 5, 6, (but not 4). However, I have not seen any actual negative effects. I wrote a ticket about it: https://dev.openwrt.org/ticket/10850
Build 29890 had already the error messages, while  29844 did not have. So, some change between them is causing this. (This has also been reported by Ferob in Arokh's thread, so this is not just in my builds.)

142

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Would you take any feature requests? I could really use NFS client access, i.e. lockd.ko, sunrpc.ko (kmod-fs-nfs-common) and nfs.ko (kmod-fs-nfs)...

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hvkls wrote:

Would you take any feature requests? I could really use NFS client access, i.e. lockd.ko, sunrpc.ko (kmod-fs-nfs-common) and nfs.ko (kmod-fs-nfs)...

I haven't really thought about it. I have no need for that functionality, and I have tried to keep the router pretty basic.

hnyman wrote:

Trunk seems to have some trouble with mounting mtdblocks(?):
Jan 24 18:44:09 OpenWrt user.notice fstab: mount: mounting /dev/mtdblock0 on /mnt/mtdblock0 failed: Invalid argument
The system log contains those references to /mnt/mtdblock0, 1, 2, 3, 5, 6, (but not 4). However, I have not seen any actual negative effects. I wrote a ticket about it: https://dev.openwrt.org/ticket/10850

I think I have narrowed the regression range down: r29860 does not produce the error, but the version built with r29862 does produce that error.

Of the two changesets r29861 and r29862, r29862 sounds like a more probable suspect for the reason of those error messages. If I understand the change correctly, it makes some of the hotplug triggers to re-run.  https://dev.openwrt.org/changeset/29862

144

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

hnyman wrote:

I haven't really thought about it. I have no need for that functionality, and I have tried to keep the router pretty basic.

In my opinion that's the best thing about the build, that it is a router and only a router. It improves performance, security and maintainability. When additional funtionality is needed, the standard packages are easily loaded in any case.

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

The default kernel for ar71xx builds was bumped up from Linux 2.6 to 3.2 with svn changeset 30403. So, that may cause some "unexpected features" in the near future, before things stabilize.

Apparently the "mtdblock bug" is mostly cosmetics. See https://dev.openwrt.org/ticket/10850

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

The default compiler was bumped up to gcc4.6, and that seems to break several modules. Some of them have already been fixed, but collectd, the base of LuCI statistics, seems to be still broken (due to too tight compiler warning checks). After a small makefile patch I managed to get the compilation to work (https://dev.openwrt.org/ticket/10962 ) , so trunk r30523 is the first version with the new 3.2 kernel and built with the new compiler. The build seems quite ok, so far.

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Related to collectd, after Jow had patched it to relax the warning checks, I noticed that those two surplus variables about which gcc4.6 complained, have been removed in August 2011 from the collectd source code.

"Many build fixes that turned up with GCC 4.6."  http://git.verplant.org/?p=collectd.git;a=commit;h=61a1fa91ba73e4fe3a34949f77c5f017056f2b7a

The fixes would be included the current collectd 4.10.5, but because Openwrt is still using the old 4.10.2, gcc ran into that problem already fixed in upstream.

I have patched my trunk build 30585 with collectd 4.10.5 and submitted a patch to update it in the general source code. Hopefully it gets officially implemented at some point. https://lists.openwrt.org/pipermail/openwrt-devel/2012-February/014017.html

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

I have tentatively switched from rng-tools to haveged as the entropy source in r30685.
The package is not yet in the packages feed repository, but Olipro has submitted the definition to the Openwrt-devel mailing list, so hopefully it ends up in the repository: https://lists.openwrt.org/pipermail/openwrt-devel/2012-February/014127.html

149

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

Sorry to bug you again-- I tried to force the installation of the nfs-common/nfs (client) trunk kernel modules, but the post-installation insmod operation never completed. I didn't dare to reboot without having reverted the installation. Is there any way to use precompiled kmod-nfs(-common) modules with your build? The FTDI module, for example, just works.

150 (edited by hnyman 2012-03-26 21:25:23)

Re: IPv6 oriented Openwrt build for WNDR3700/WNDR3800

It depends.
Kernel modules calculate nowadays a checksum for the kernel options used in compilation, so getting additional kernel modules to install is hard.

I have otherwise pure vanilla defaults, but I have enabled timestamps from kernel log. That may be enough to prevent from using pre-compiled snapshot modules.

EDIT: additionally, the ar71xx snapshots seem to be from 14 March 2012, when there still was the 3.2.9 kernel. It has been updated to 3.2.12 after that and my newest build already uses that.

I wonder, why the snapshots have not been run in almost two weeks.