2,776

Re: Fully featured OpenWrt build for the WNDR3700

@masta

Polish is welcome, but I don't see why dns queries to localhost should be done through IPv6. You'll have to clarify why it's a good idea smile Added ::1 to hosts.

@ferob

Ok thx, fixed in latest build.

Also switched back to 3.3 kernel, someone posted a fix.

2,777

Re: Fully featured OpenWrt build for the WNDR3700

arokh wrote:

@masta

Polish is welcome, but I don't see why dns queries to localhost should be done through IPv6. You'll have to clarify why it's a good idea smile Added ::1 to hosts.

@ferob

Ok thx, fixed in latest build.

Also switched back to 3.3 kernel, someone posted a fix.

Hey Arkoh about polishing:
You can also change these for alternate version in /etc/config/transmission

    option peer_limit_global 40
    option peer_limit_per_torrent 10

since wndr3700 cannot handle more than that and it will reboot router when the MEM and CPU will reach the top.

2,778

Re: Fully featured OpenWrt build for the WNDR3700

ferob wrote:

@arokh

There was some changes (r21211) to minidlna.

I've noticed those changes also yesterday. But does that mean that we will be able to configure minidlna from Luci or what was the uci support added for in general?

2,779

Re: Fully featured OpenWrt build for the WNDR3700

It's just UCI support, which would be a prerequisite for adding Luci support. I'll modify the transmission defaults, thx mmhorda.

2,780 (edited by written_direcon 2012-04-07 11:45:06)

Re: Fully featured OpenWrt build for the WNDR3700

UCI support was added in general to minidlna.

EDIT: Okay. There is also a LuCI frontend: http://luci.subsignal.org/trac/changeset/8516 & http://luci.subsignal.org/trac/changeset/8517 added at the subsignal server.

2,781 (edited by mmhorda 2012-04-07 13:04:42)

Re: Fully featured OpenWrt build for the WNDR3700

written_direcon wrote:

UCI support was added in general to minidlna.

EDIT: Okay. There is also a LuCI frontend: http://luci.subsignal.org/trac/changeset/8516 & http://luci.subsignal.org/trac/changeset/8517 added at the subsignal server.

Perfect!
Arkoh do you think you could add it to your next build please? smile

2,782

Re: Fully featured OpenWrt build for the WNDR3700

New build with libnl and luci-app-minidlna coming right up smile

2,783

Re: Fully featured OpenWrt build for the WNDR3700

First I just would like to say big thank you to you arokh for putting out these awesome builds.

Now on to my little issue, lol.

Basically I've been getting

our AdvValidLifetime on br-lan for [ipv6 prefix] doesn't agree with [ipv6 address given to modem by default config?]

along with

our AdvPreferredLifetime on br-lan for [ipv6 prefix] doesn't agree with [ipv6 address given to modem by default config?]

Not sure why this warning is spamming the system log. I've searched and most things I seem to find state that this is usually caused by two instances of radvd or radvd and some other ipv6 daemon advertising -- but only one instance of radvd is running and it's a freshly installed build from April 5th. If anyone could point me in the right direction of getting this to stop flooding the system log that'd be much appreciated.

And thanks again arokh.

2,784

Re: Fully featured OpenWrt build for the WNDR3700

Probably that you need to enable it, UCI default is off smile

2,785 (edited by mmhorda 2012-04-07 20:14:32)

Re: Fully featured OpenWrt build for the WNDR3700

ferob wrote:

@arokh

The wifi is working with the latest build, but there is something wrong with minidlna.


EDIT: No, I tried that after the upgrade.

And there is no default config for it.
I tried to create one manually, but the problem is still the same and it would not start up.

These two lines are missing from your makefile:

$(INSTALL_DIR) $(1)/etc/config
$(INSTALL_BIN) ./files/minidlna.config $(1)/etc/config/minidlna

I am afraid you don't need to create /etc/conf/minidlna
I took a look at /etc/init.d/minidlna and it seems that config is creatied as arokh says in /tmp/minidlna when you enable it in Luci and all the rest of the settings are being stored there.

I will test the build tonight in a few hours smile

Thanks arokh!

PS: @ferob  could you please confirm if it is working or not when you start it in Luci?

2,786 (edited by mmhorda 2012-04-07 22:06:58)

Re: Fully featured OpenWrt build for the WNDR3700

arkoh. ferob is right
I have installed minidlna and luci-minidlna on top of your previous build. I am testing right now the correct settings.
So far i got till here. It appears in luci but i didnt test to start yet as i am a bit busy.  WIll let you know when i finish with tests.

vi /etc/config/minidlna

config minidlna
    option enabled '0'
    option port '8200'
    option interface 'br-lan'
    option friendly_name 'OpenWrt DLNA Server'
    option db_dir '/mnt/sda1/.minidlna'
    option inotify '1'
    option album_art_names 'Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg'
    option notify_interval '900'
    option root_container '.'
    option media_dir '/mnt/sda1'

2,787

Re: Fully featured OpenWrt build for the WNDR3700

Ops, fixed in next smile

2,788

Re: Fully featured OpenWrt build for the WNDR3700

arokh wrote:

Ops, fixed in next smile

Just wanted to quickly chip in my appreciation for how fast you're responding and fixing stuff cropping up in your builds. smile

2,789 (edited by mmhorda 2012-04-07 23:55:34)

Re: Fully featured OpenWrt build for the WNDR3700

arokh wrote:

Ops, fixed in next smile

Arokh. Something  is still wrong with this libnl
wifi seems working good but when i type wifi from command line i can see this:

root@OpenWrt /root# wifi
Failed to read classid file: Object not found
Failed to read classid file: Object not found
root@OpenWrt /root#

It was not happening before.

edit:

SOLUTION:
root@OpenWrt /root# mkdir /etc/libnl
root@OpenWrt /root# touch /etc/libnl/classid
root@OpenWrt /root# wifi
root@OpenWrt /root#

2,790

Re: Fully featured OpenWrt build for the WNDR3700

surtin wrote:

[...]

Basically I've been getting

our AdvValidLifetime on br-lan for [ipv6 prefix] doesn't agree with [ipv6 address given to modem by default config?]

along with

our AdvPreferredLifetime on br-lan for [ipv6 prefix] doesn't agree with [ipv6 address given to modem by default config?]

Not sure why this warning is spamming the system log.

[...]

@Surtin

You might want to take a look at your /etc/config/radvd  settings.

Double check any RA lifetime in luci or in that config file.

I suggest unsettling any values that might have been configured to see if the log msg disappears.

Question: are you accepting RA's from the WAN side of your router, or even from a tunnel interface?

What is your V6 topology? Native, dual stack, tunnel, upstream  DHCPv6  or RA?


I'm just wondering if your RADVD is deviating from what an upstream RA solicitation has provided?

Home                               Work                          Parents
Netgear wndr3800            Netgear wndr3800      Netgear wndr3700v2
Netgear JGS524 Switch       Lacie 1TB USB              64GB USB thumb
DroboFS 10TB NAS

2,791

Re: Fully featured OpenWrt build for the WNDR3700

mmhorda wrote:

SOLUTION:
root@OpenWrt /root# mkdir /etc/libnl
root@OpenWrt /root# touch /etc/libnl/classid
root@OpenWrt /root# wifi
root@OpenWrt /root#

Thx, will include those dirs as well.

2,792

Re: Fully featured OpenWrt build for the WNDR3700

It would be more worthwhile to fix libnl-tiny instead of evading the problem with full libnl (which is 10x the size).

Re: Fully featured OpenWrt build for the WNDR3700

For a short time fix it's easier to use the full version of libnl. Once libnl-tiny is fixed we can still switch to it :-)

2,794

Re: Fully featured OpenWrt build for the WNDR3700

For a short time fix it would be easier to not even use Linux 3.3 - a new, not yet default kernel usually just brings regressions and bloat - otherwise it'd be in use already. Wifi drivers are independant and not affected by the kernel.

2,795

Re: Fully featured OpenWrt build for the WNDR3700

jow wrote:

For a short time fix it would be easier to not even use Linux 3.3 - a new, not yet default kernel usually just brings regressions and bloat - otherwise it'd be in use already. Wifi drivers are independant and not affected by the kernel.

I don't really know what is better but I can say that latest build with linux 3.3.1 works great.

2,796

Re: Fully featured OpenWrt build for the WNDR3700

So I just built trunk ar71xx with Kernel 3.3 and libnl-tiny and I don't see any wifi issue related to hostapd, so I have no clue what the fuzz is about after all.

2,797

Re: Fully featured OpenWrt build for the WNDR3700

jow wrote:

So I just built trunk ar71xx with Kernel 3.3 and libnl-tiny and I don't see any wifi issue related to hostapd, so I have no clue what the fuzz is about after all.

the latest build is also build with libnl-tiny but normal libnl i can find there too.

libnl        3.2.7-1
libnl-tiny    0.1-3

2,798

Re: Fully featured OpenWrt build for the WNDR3700

@jow

That's very strange, there is definitely a problem with libnl-tiny and 3.3.x smile


On a different note, changed my build script a little bit to make it easier doing different builds in the future. New builds will have an opkg.conf that pulls packages from the specific build version's packages directory.

Added a 'fat' build, which is basically the alternate build with rsync, tcpdump, lsof and minidlna. Need to come up with good configuration sets and a cleaner way to maintain configs.

Going on vacation again, back in three weeks smile

2,799

Re: Fully featured OpenWrt build for the WNDR3700

If there is a problem I'd be grateful about a proper bug report. So far I've only seen vague indications and hand-waving about "something being wrong" with hostapd, libnl-tiny and Linux 3.3. I gave it a quick try here and was able to start and associate to the wifi nromally so I have no idea what to look for. Also note that a critical libnl-tiny issue was fixed with https://dev.openwrt.org/changeset/31155 .

2,800

Re: Fully featured OpenWrt build for the WNDR3700

Did you see the posts to the mailing list about the issue?

https://lists.openwrt.org/pipermail/openwrt-devel/2012-April/014772.html