Luci has been updated today. Supposedly Luci is now in sync with the current config options.
http://luci.subsignal.org/trac/changeset/10181

r40780 includes the new Luci version. I haven't really tested the changes, but based on the Luci changes, some changes are needed for /etc/config/wireless to make n mode work ok. (htmode option changes from HT40+ to HT40, if set with luci)

(Last edited by hnyman on 19 May 2014, 21:30)

Thanks as always Hnyman!

@hnyman

Have you been having any wireless issues with the latest r40780 revision? All my devices connect for a few seconds and then immediately disconnect. I had initially tried with my own custom compile, and then did a full factory reset through TFTP of that same firmware but still, no luck.

I then tried your revision on dropbox and same issue :-/ Both factory and sysupgrade versions have trouble with clients staying connected. Just for kicks I tried out your revision r40772 and the wireless worked fine. I just tried compiling the latest  revision that was pushed out 40801 and it looks like there's a bunch of 802.11 patches.

Anyways, I might also push by build to match yours, seeing as how something clearly broke with the mac80211 drivers. I actually can't even compile all the way with 40801, it does seem to get stuck on the new 80211 update.

make[3]: Entering directory `/home/user/code/openwrt/trunk/package/kernel/mac80211'
make[3]: *** [/home/user/code/openwrt/trunk/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2014-05-19/.configured_ynnnnnnnnnnnnnnnnnnnnnnnnnnnnyynnynnnnnnnnnnnnnnnnnnnnnnnnyynnnnnnn] Error 1
make[2]: *** [package/kernel/mac80211/compile] Error 2
make[1]: *** [/home/user/code/openwrt/trunk/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.package_compile] Error 2
make: *** [world] Error 2

Try "make clean" first before rebuilding.

I have not yet had time to test 40780 for a longer period. There have been a few recent patches, some of which may have broken something. There are also new bugs that sound similar:
https://dev.openwrt.org/ticket/16553
https://dev.openwrt.org/ticket/16545

EDIT: possibly fixed by 40802

(Last edited by hnyman on 20 May 2014, 12:19)

- r41148 trunk: first build with the new packages/oldpackages split

The Openwrt source code repository is seeing large changes regarding the packages, which have split into new "packages" and semi-abandoned "oldpackages". Also Luci has been partially split and reorganised.

r41148 trunk build is the first build with the new packages/oldpackages split. Packages repo was also changed to use git, while I still prefer svn. So there are some changes in the build scripts.

Although everything seems to work for me, it is quite possible that there some adjustments need to be made in the next few days. (And I have not yet tested creating a new build environment with the new structure.)

hnyman after an update to r41148 (without keeping settings) Luci stops working with the follow message when I try to login to the router:

/usr/lib/lua/luci/dispatcher.lua:211: /etc/config/luci seems to be corrupt, unable to find section 'main'
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:211: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

I had to revert back to r41051

That will probably be fixed in the next build with http://luci.subsignal.org/trac/changeset/10286

EDIT: Looks like it is fixed in the r41172 build.

(Last edited by hnyman on 12 Jun 2014, 21:26)

- r41191 trunk: revert to default git feeds (from svn feeds)

I have changed my trunk build to use the git feeds that are now default. The main Openwrt sources are still fetched with svn.

I made some cleanup to the build scripts at the same time to ease the adoption of git. The newOpenwrtBuildroot.sh script is now even simpler and requires no editing.

EDIT:
The next build will have also a git-compatible version of the versionT.sh "time machine" script. Going back to history with git can be tricky, as by default the "shallow" git repository created by Openwrt only contains log history starting from the creation of the local git repo for each feed. We can deepen the history by "git pull --depth=500". After that we can use "git rev-list" to find the correct revision by date and give that as an argument for "git checkout":
git checkout `git rev-list -n 1 --before="$1" master`

#!/bin/bash
#
# versionT  -  Update source code to revision T and then build
#              T argument: date as yyyy-mm-dd or "yyyy-mm-dd hh:mm"
#              first "git pull --depth=500" to deepen git history (shallow)
#              use "git checkout master" for each feed to get back to HEAD

echo "...update SVN source..."
svn up -r {"$1"}
echo "...update feeds..."
(cd feeds/luci ; git checkout `git rev-list -n 1 --before="$1" master`)
(cd feeds/packages ; git checkout `git rev-list -n 1 --before="$1" master`)
(cd feeds/oldpackages ; git checkout `git rev-list -n 1 --before="$1" master`)

(Last edited by hnyman on 15 Jun 2014, 20:03)

Hey hnyman, can you exaplain how to assign static dhcpv6 addresses in odhcpd ? I can't for the life of me figure it out..

I haven't tested it, but the best documentation is probably at https://github.com/sbyx/odhcpd You apparently need a "host" section in the config file:

Sections of type host (static leases)
Option        Type    Default            Description
ip        string                IP-Address to lease
mac        string                MAC-address
duid        string                DUID in base16
hostid        string                IPv6 host identifier
name        string                Hostname

Yeah, i got that much, since it maps to options that dnsmasq was using, i just don't get the format in which hostid is supposed to be written - is it just the suffix (that didn't work), does it need a subnet value at the end, is DUID needed. That kind of thing.

I could just wait for the docs on the wiki, but we don't know when BB will be stabilized, and apple clients don't play nice with dhcpv6 since they don't send a hostname with the request, so they have a nice "?" in luci and can't be found by DNS inside the lan - i want to fix that.

(Last edited by movi on 16 Jun 2014, 11:37)

The authors original advice was here: https://forum.openwrt.org/viewtopic.php?pid=202184#p202184

That was for "6relayd", the predecessor of odhcpd, but I guess the advice is still mainly valid (except that section is now host instead of lease, thanks to https://github.com/sbyx/odhcpd/commit/3ebfad09209efc88d21bc4ede6d88516dc584ea3, and "id" is probably "hostid").

Thanks, that KINDA got it to work.

Except the osx hosts ignore the IP assigned to them and get their own somehow (?), and the linux boxes (networkmanager+dhclient6) ignore the hostname that i set.
Also, even though the leasetime is set to 24h, odhcpd sets it to 1h. I think i need to create a new thread for this.

Just updated to WNDR3700-trunk-r41261-2014-06-18-1922-squashfs-sysupgrade.bin. Everything is good so far!

Question about UPNP. What is a good method to test that it is indeed working? My PC is Windows 7.

I noticed in Luci if I go to Services > UPNP. That "Start UPnP and NAT-PMP service" is not selected. Should I enable it?

Also, how can I change the "Connection-specific DNS Suffix" that is shown in IP config for the network settings? I would like change the default label of "lan" to something else.

Thanks!

Hey guys, anyone using sixxs here? Been playing with IPv6 at home. I'm using the latest aiccu with netifd integration, and it works great. Only one strange thing I noticed, even though I have a delegated /48 subnet it seems odhcpd is telling my LAN devices it's a /64?

Here's my configuration:

# uci show network.lan
network.lan=interface
network.lan.ifname=eth0.1
network.lan.type=bridge
network.lan.proto=static
network.lan.netmask=255.255.255.0
network.lan.ipaddr=10.1.1.1
network.lan.ip6assign=48
network.lan.ip6addr=2001:16f5:eeb4::1/48
network.lan.ip6prefix=2001:16f5:eeb4::/48

# uci show network.wan6
network.wan6=interface
network.wan6.proto=aiccu
network.wan6.username=myuser
network.wan6.password=mypass
network.wan6.tunnel_id=myid
network.wan6.protocol=tic
network.wan6.server=tic.sixxs.net
network.wan6.defaultroute=1
network.wan6.nat=0
network.wan6.heartbeat=1
network.wan6.verbose=0
network.wan6.ip6prefix=2001:16f5:eeb4::/48
network.wan6.ip6addr=2001:16f5:ee00:135::2/64

Doing an "ifstatus lan" shows the assignment being /48 as well but here's how it gets assigned on my Linux box:

# ip addr show dev eno1 | grep inet6
inet6 2001:16f5:eeb4:0:eea8:6bff:fefc:8a67/64 scope global mngtmpaddr dynamic

Works fine though, default gateway is set and routing works like it should. Just wondering if this is correct behaviour.

I use a static SixXS 6in4 tunnel. Haven't used aiccu for some time.

If I remember correctly the discussions with odhcpd designer (CyrusFF / sbyx), the servers hands down /64 prefixes, so that you could have simultaneously several /64 prefixes inside the /48 and prefix delegation would work.

(and addresses could be get both via dhcpv6 and RA, and dhcpv6 does not transmit prefix size, or something like that. https://forum.openwrt.org/viewtopic.php?pid=237068#p237068)

Good to hear that aiccu works ok again. I noticed the new netifd integration last week.

EDIT:
******  Next build from me: in late July  ******

(Last edited by hnyman on 27 Jun 2014, 15:43)

Dear hnyman,
tried to use your new scripts for compiling new customized releases.
Compilation worked only first time, the second got errors.
After investigation I realized that updateNmake.sh has no longer make dirclean command possibility
Amended updateNmake.sh and after that further compilations were ok.
Is there any reason why you removed the make dirclean in new scripts?
Do you have any explanation about compilation failure without above command?
Thanks and regards

Sergio

make dirclean was only there for convenience. I removed it to make the script cleaner. Make clean or dirclean before the build is a good practice but not always necessary. Quite much depends what has changed after the last make. Kernel or toolchain changes usually make a clean necessary.

@hnyman

Sounds logical, thanks for clearing that up

@hnyman
Thanks as usual for your answers.
Now some more... (I bag your pardon)
I own netgear WNDR3700v2 and have no problem in building trunk releases with your scripts.
I also own a tp-link MR3240v2 and as far as I know it is opewrt compatible with same building target of WNDR3700 i.e. AR71xx.
Unfortunately the MR3240 router has only 4 MB flash. Questions:
- will it be possible to build a releas for MR3240 only adding the right target in .config file?
- do you think it will be possible to cut some of the packets of your build (and which of them) in order to get a light version reduced to 4MB?

I mainly use it in my second house with a 3G usb key.
I already installed a firmware based on openwrt called Rooter (Funnelweb) which is working good but with no ipv6 6in4
Best regards

Sergio

in principle you can change the build target in make menuconfig. Or change it in.config manually. And the build itself should go OK. But some scripts expect the built binaries to contain wndr3x00, so some cleanup and I do building steps after the main build may fail.

To get below 4 MB you will need to remove nonessential packages. E.g. remove Ftp server etc.

Hi hnyman,

Does your build include vpn?

Thanks

yardern

Looks like I'm not the only one having this issue:

https://dev.openwrt.org/ticket/16781

I'm happily running your version:
OpenWrt Attitude Adjustment 12.09-r40877

Things are great but I'm stuck trying to add an old Linksys WRT54GS v2.1 with Tomato Shibby 1.28 as a simple Wifi Repeater.

I've setup WDS in the Tomato firmware with the MAC from my NetGear.   My issue is trying to get the OpenWRT setup correctly.  I found the "Acess Point (WDS)" in the wLan(0) interface configuration but wasn't given anywhere to enter the MAC address of the other wifi router.

Has anyone done a WDS setup with this firmware (using the Luci web interface)?

Thanks!

PS - I have always used WPA2 Personal + AES can this remain or needs to be changed to WPA Personal + ??? 

If I change encryption type do you need to reconfigure everything that uses your wifi?

(Last edited by Beaker1024 on 15 Jul 2014, 16:42)

I have. Instructions and my config can be found on earlier pages of this thread...

But wds is rather manufacturer-specific, so I doubt if you can do mixed Openwrt & something else wds.