Hi,

I tried to install gpsd-clients on my old ATTITUDE ADJUSTMENT (Bleeding Edge, r31672) with LUCI.
The installation was succesfull.
LUCI said:
Installing gpsd-clients (3.7-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Multiple packages (librt and librt) providing same name marked HOLD or PREFER. Using latest.
Installing libncurses (5.7-5) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Installing terminfo (5.7-5) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Configuring terminfo.
Configuring libncurses.
Configuring gpsd-clients.

but then I tried to start a program from this package

root@OpenWrt:~# gpspipe -h
gpspipe: can't load library 'libcap.so.2'

thats in /usr/lib

root@OpenWrt:/usr/lib# ls
crda                 libip4tc.so          libpanel.so
iptables             libip4tc.so.0        libpanel.so.5
libcurses.so         libip4tc.so.0.0.0    libpanel.so.5.7
libform.so           libiwinfo.so         libusb-1.0.so
libform.so.5         liblua.so.5.1.4      libusb-1.0.so.0
libform.so.5.7       libmenu.so           libusb-1.0.so.0.0.0
libgps.so.20         libmenu.so.5         libxtables.so
libgps.so.20.0       libmenu.so.5.7       libxtables.so.5
libgps.so.20.0.0     libncurses.so        libxtables.so.5.0.0
libgpsd.so.20        libncurses.so.5      lua
libgpsd.so.20.0      libncurses.so.5.7    opkg
libgpsd.so.20.0.0    libnl-tiny.so        pppd

Any suggestions ??

So attitude adjustment is not the same as bleeding edge. I have no idea which build is which in terms of revision numbers.
But that is your problem: any older firmware will fail to install trunk packages (they are at least weekly, if not daily builds.
You could try flashing AArc1 and use packages from that "stable" build.

I have two boxes, the newer one is flashed with rc1 and added support for gpds with LUCI.
The old box is flashed with a self build firmware
Both boxes are now working, but the box with the rc1 lacks 3g support and has only 9% free.

But I got the old box with my self build firmware working with gpspipe

This is the info my older box gives after looging in with putty.

BusyBox v1.19.4 (2012-04-24 21:04:04 CEST) built-in shell (ash)
.....
ATTITUDE ADJUSTMENT (Bleeding Edge, r31672)

this is what I did:

I copied the libcap.so,  libcap.so.2, libcap.so.2.22  from the newer box with the rc1  to an usb-storage,
and then from the usb-storage to the /usr/lib  on the old box and made them executable.

This what I got.
root@OpenWrt:/usr/lib# ls -al
drwxr-xr-x    1 root     root             0 Mar 28 14:46 .
drwxr-xr-x    1 root     root             0 Mar 27 11:15 ..
...
-rwxr-xr-x    1 root     root         10696 Mar 28 14:46 libcap.so
-rwxr-xr-x    1 root     root         10696 Mar 28 14:46 libcap.so.2
-rwxr-xr-x    1 root     root         10696 Mar 28 14:46 libcap.so.2.22

Is a dirty hack but it is succesfull.

why I'm  doing this?

there is more space on the old box with all needed features installed

root@OpenWrt:/usr/lib# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                     640       424       216  66% /
/dev/root                 2560      2560         0 100% /rom
tmpfs                    14756       128     14628   1% /tmp
tmpfs                      512         0       512   0% /dev
/dev/mtdblock3             640       424       216  66% /overlay
overlayfs:/overlay         640       424       216  66% /
/dev/sda1              2753976    122704   2493240   5% /mnt/sd1

so gpspipe can now log to /dev/sda1 which has lots of space.

thanks for the other infos you provided

P.S.

we discussed the wrong flash layout of my new self build firmware in post 364 in this thread

root@OpenWrt:/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   14656        44     14612   0% /
/dev/root                 3072      3072         0 100% /rom
tmpfs                    14656        60     14596   0% /tmp
tmpfs                      512         0       512   0% /dev
root                     14656        44     14612   0% /tmp/root

is there any tool in openwrt to check the flash-layout of a firmware.bin before it is flashed to a device?

Hi,

i have a problem with my MR3020. I installed the "openwrt-ar71xx-generic-tl-mr3020-v1-squashfs-factory" thru the interface.
Telnet into the router after rebooting it, and that works.

I then " sysupgrade -v /tmp/openwrt-ar71xx-generic-tl-mr3020-v1-squashfs-sysupgrade.bin"

and this works to, i enter my wifi info in the  "/etc/config/wireless" and  " /etc/init.d/network restart"

But i than get the error:   command failed device or resource busy (-16) successfully initialized wpa_supplicant

Sometimes i get internet for a couple of second, but then its gone.

Anyone have any idea ?

Hope someone can help me

Regards Nextria

what revision?? trunk or AA?

anyway i cannot understand why did you sysupgrade?

Hey,

Thanks for the replay, i am trying to create a minipwner, and am following this guide:

http://www.hangelot.eu/?p=282&lang=en

It's the trunk version.

Hope you can help me out with this.

Regards,

Nextria

Okay so ive been trying all weekend. and flashed the stock firmware back.

From there i updated to the AA firmware thru the interface.

I log in to the LuCI interface. and this works.

So i want to connect with the MR3020 to my home router for wifi.

But if i set up the network as client, it connects, but it looks like the wlan0 keeps scanning.

If it on channel 6 it connects to my wifi at home but keeps on scanning and losses the connection

Anyone else got this problem ??

everything else works, but i can't seem to get internet

Regards Nextria

what kind of configuration are you trying to achieve?

there are some choices to do...

http://wiki.openwrt.org/doc/howto/clientmode

Hi,

I'm not really sure. I've got the Mr3020 connected through Ethernet cable to my laptop.

And want to use it as a "receiver". So I set it up as a client and input my home SSID and password.

But if I look at the status page on the bottem, I can see on what channel it is.

But it keeps changing. And only when it is on channel 11 I see that it is connected. But only for a second or so....

Regards nextria

when I flashed my main router netgear wndr 3700 with latest openwrt fw my wifi connection from MR3020 was broken and always tried to connect.

and when I flashed mr3020 with new fw from trunk - it connected succesful.
so it seems there is some connection between new fw on netgear and fw on mr3020..

I wonder what's hapened with package libftdi ? It disappear from packages for a long time.
Also I can't it compile. I always get the error:
configure: error: *** libusb-config not found. You need a working libusb installation.
but there is no such package "libusb-config" or any mentions of it in menuconfig and feeds

Hi

I still havent got my router going.
Openwrt works I can log into the web interface.

But what I read and what ever I try I can seem to get internet on it.

Not even I directly input it into the router or modem.

Ive been trying for almost a week now...

Can anyone help me with this, or have a link to a easy setup page

Tnx

Have you tried the same with a non-trunk image (e.g. Imagebuilder)? What was the result?

Post your /etc/config/network, /etc/config/wireless, /etc/config/firewall.

hi guys i purchased this modem today it's TP-LINK TL-MR3020 v1.8

which firmware should i install because i see only v1.0 to v1.7 is supported..

or i would be fine with the latest Attitude Adjustment RC1 snapshot ?

i don't want to take any risk please suggest..

thank you :]

Hi,

No i never used a non-trunk image.
But since last night i'm a little bit further.

I have the MR3020 connected to my router, and given it a ip adress of 192.168.1.177.
So i can log into Luci over the network.

I created a AP called TP-Link, if i connect to this network with my laptop i have internet and everything works.

But when i use putty (or the Luci interface) and use the command opkg update
i still get a error that theres no internet (wget: bad address 'downloads.openwrt.org'

or if i ping google.com i get the same thing.

Here are my config files:

/etc/config/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'
        option type 'bridge'
        option proto 'static'
        option netmask '255.255.255.0'
        option ipaddr '192.168.1.177'
        option gateway '192.168.1.1'
        option dsn '192.168.1.1'
  

/etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option macaddr 'f8:1a:67:4d:6b:db'
        option hwmode '11ng'
        option htmode 'HT20'
        list ht_capab 'SHORT-GI-20'
        list ht_capab 'SHORT-GI-40'
        list ht_capab 'RX-STBC1'
        list ht_capab 'DSSS_CCK-40'
        option txpower '27'
        option country 'US'

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'TP-LINK'
        option encryption 'psk2'
        option key '*******'

/etc/config/firewall

config defaults
    option syn_flood '1'
    option input 'ACCEPT'
    option output 'ACCEPT'
    option forward 'ACCEPT'

config zone
    option name 'lan'
    option input 'ACCEPT'
    option output 'ACCEPT'
    option forward 'ACCEPT'
    option network 'wan lan'
    option masq '1'
    option mtu_fix '1'

config zone
    option name 'wan'
    option output 'ACCEPT'
    option masq '1'
    option mtu_fix '1'
    option input 'ACCEPT'
    option forward 'ACCEPT'
    option network ' '

config rule
    option name 'Allow-DHCP-Renew'
    option src 'wan'
    option proto 'udp'
    option dest_port '68'
    option target 'ACCEPT'
    option family 'ipv4'

config rule
    option name 'Allow-Ping'
    option src 'wan'
    option proto 'icmp'
    option icmp_type 'echo-request'
    option family 'ipv4'
    option target 'ACCEPT'

config rule
    option name 'Allow-DHCPv6'
    option src 'wan'
    option proto 'udp'
    option src_ip 'fe80::/10'
    option src_port '547'
    option dest_ip 'fe80::/10'
    option dest_port '546'
    option family 'ipv6'
    option target 'ACCEPT'

config rule
    option name 'Allow-ICMPv6-Input'
    option src 'wan'
    option proto 'icmp'
    list icmp_type 'echo-request'
    list icmp_type 'echo-reply'
    list icmp_type 'destination-unreachable'
    list icmp_type 'packet-too-big'
    list icmp_type 'time-exceeded'
    list icmp_type 'bad-header'
    list icmp_type 'unknown-header-type'
    list icmp_type 'router-solicitation'
    list icmp_type 'neighbour-solicitation'
    list icmp_type 'router-advertisement'
    list icmp_type 'neighbour-advertisement'
    option limit '1000/sec'
    option family 'ipv6'
    option target 'ACCEPT'

config rule
    option name 'Allow-ICMPv6-Forward'
    option src 'wan'
    option dest '*'
    option proto 'icmp'
    list icmp_type 'echo-request'
    list icmp_type 'echo-reply'
    list icmp_type 'destination-unreachable'
    list icmp_type 'packet-too-big'
    list icmp_type 'time-exceeded'
    list icmp_type 'bad-header'
    list icmp_type 'unknown-header-type'
    option limit '1000/sec'
    option family 'ipv6'
    option target 'ACCEPT'

config include
    option path '/etc/firewall.user'

config forwarding
    option dest 'lan'
    option src 'wan'

config forwarding
    option dest 'wan'
    option src 'lan'

hope someone knows what the problem is, would be great if i could get this working !

Nextria

you edited the firewall config.. no need to do it!
also "option dsn" is not a valid option in lan network config..

still no libftdi even in 201 build..
where can I get it ?
I'm really need this package for connecting my arduino to mr3020

(Last edited by d00m178 on 9 Apr 2013, 13:31)

test with mr3020 with huawei e169 dongle, the e169 doesn't support mr3020

Hi everyone, I'm new to this forum and OpenWRT in general.  A few days ago, I started to learn about OpenWRT on my WRT54GL.  I got sort of far with it and was able to load packages, only to find that the Broadcom chipset doesn't seem to support monitor mode.

So now I've joined the TL-MR3020 camp.  I got my first one today, and seem to have "bricked" it already.  Rather than download the Attitude Adjustment binary recommended for this model, I compiled the latest revision checked in to SVN.  Whoops, that might have been a bad idea.  Now I can't telnet or ssh to the device.

I've been going through this thread page by page, and I'm now at the point where I've got the PCB out.  I have headers and a TTL-232R-3V3 cable handy from another project, so tomorrow I'll solder everything together and use the serial console instead.  By the way, I have a v1.8, but the PCB doesn't look any different than what's in the wiki.  The PCB still says 1.1 silkscreened.  Maybe it's just a bootloader change...

I'm sure I'll be posting again shortly, but not until after I've read the previous 16 pages and try to get this thing going on my own.    You are all doing great work here!

EDIT -- well, I am happy to say that I did not brick my router with the code I had compiled.  For some reason, I couldn't get to it from the desktop I was using for my WRT54GL, but it worked from my laptop.  Anyhow, I still soldered in the serial console pins and captured the data upon bootup for future reference.  I'd attach it here now but can't attach files to my post.

(Last edited by AutonoBot on 11 Apr 2013, 14:40)

I'm trying to setup my MR3020 as a bridged AP to my existing wireless router to extend the signal in my house.  So I have:

internet == DSL Modem == E3000 router AP == MR3020 AP, all hard-wired.

I want wireless clients on the MR3020 to dhcp from the E3000 as I have access restrictions setup there.  I've followed the Bridged AP guide (http://wiki.openwrt.org/doc/recipes/bridgedap) and although clients seem to get a dhcp allocated address, they are unable to access the internet, or even the E3000.  In addition, clients of the E3000 (wired or wireless) are unable to access the MR3020, I can only see it from the E3000, or a a client of the MR3020.

I'm using AArc1, does anyone know if this configuration is supported with this software\hardware combination?

gbloice
check first wired connection between mr3020 and your router (E3000) - open ssh console on both and ping each other.
If all is ok - you should get sucessful ping.
then take a look at http://wiki.openwrt.org/doc/recipes/relayclient

@d00m178

Yep, I can ping both ways from the mr3020 and the e3000, devices connected to either of these can't see beyond them though.  The link you've posted is for a wireless bridge, I want a wired one as per the link I posted.

@gbloice
There is no difference if you have a wired or wireless connection to the router  from mr3020
there is problem that described if you see my link:
http://wiki.openwrt.org/doc/howto/clien … ode.issues

lan and wlan interfaces can't be included in the same subnetwork.

(Last edited by d00m178 on 15 Apr 2013, 09:23)

Issue with MR 3020:

Using the latest OpenWrt Barrier Breaker r36349 firmware.

1. Consider the wireless router is connected to another router via ethernet connection (using DHCP):

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

config globals 'globals'
    option ula_prefix 'fd98:71f9:aa2f::/48'


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

config interface 'wifi'
        option proto 'static'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'

config defaults
    option syn_flood    1
    option input        ACCEPT
    option output        ACCEPT
    option forward        REJECT

config zone
    option name        lan
    option network        'lan'
    option input        ACCEPT
    option output        ACCEPT
    option forward        REJECT

config zone
    option name        wan
    option network        'wan'
    option input        REJECT
    option output        ACCEPT
    option forward        REJECT
    option masq        1
    option mtu_fix        1

config forwarding
    option src        lan
    option dest        wan

config rule
    option name        Allow-DHCP-Renew
    option src        wan
    option proto        udp
    option dest_port    68
    option target        ACCEPT
    option family        ipv4

config rule
    option name        Allow-Ping
    option src        wan
    option proto        icmp
    option icmp_type    echo-request
    option family        ipv4
    option target        ACCEPT

config rule
    option name        Allow-DHCPv6
    option src        wan
    option proto        udp
    option src_ip        fe80::/10
    option src_port        547
    option dest_ip        fe80::/10
    option limit        1000/sec
    option family        ipv6
    option target        ACCEPT

config rule
    option name        Allow-ICMPv6-Forward
    option src        wan
    option dest        *
    option proto        icmp
    list icmp_type        echo-request
    list icmp_type        echo-reply
    list icmp_type        destination-unreachable
    list icmp_type        packet-too-big
    list icmp_type        time-exceeded
    list icmp_type        bad-header
    list icmp_type        unknown-header-type
    option limit        1000/sec
    option family        ipv6
    option target        ACCEPT

config rule
    option name        Enforce-ULA-Border-Src
    option src        *
    option dest        wan
    option proto        all
    option src_ip        fc00::/7
    option family        ipv6
    option target        REJECT

config rule
    option name        Enforce-ULA-Border-Dest
    option src        *
    option dest        wan
    option proto        all
    option dest_ip        fc00::/7
    option family        ipv6
    option target        REJECT

config include
    option path /etc/firewall.user

config zone
        option name             wifi
        option input            ACCEPT
        option output           ACCEPT
        option forward          REJECT

config forwarding
        option src              wifi
        option dest             wan

2. Even though there is internet access available on the "other" router, nslookup works, I am unable to access the internet from MR3020.
3. Interestingly if I use other protocol for e.g 3g/EVDO, the connection works fine. Something in dhcp is not working out.

Any clues? Thanks

Another issue with using USB as ext root

1. I am using MR3020 in conjunction with a USB 2.0 hub along with a USB disk (ITEM A) and a CDMA USB device (ITEM B).
2. The problem is the item A's device path and the item B (cdrom)'s device path varies in between boot. So my following configuration

/etc/config/fstab

config global automount
    option from_fstab 1
    option anon_mount 1
    
config global autoswap
    option from_fstab 1
    option anon_swap 0
    
config mount
    option device   /dev/sda2
    option fstype    ext4
    option options    rw,sync
    option enabled    1
    option enabled_fsck 0
    option is_rootfs 1

config swap
    option device   /dev/sda1
    option enabled    1

doesn't work always.

Look at following logread

root@OpenWrt:~# logread | grep sda
Jan  1 00:00:33 OpenWrt kern.notice kernel: [   10.800000] sd 0:0:0:1: [sda] Attached SCSI removable disk
root@OpenWrt:~# logread | grep sdb
Jan  1 00:00:33 OpenWrt kern.notice kernel: [   11.250000] sd 1:0:0:0: [sdb] 7913472 512-byte logical blocks: (4.05 GB/3.77 GiB)
Jan  1 00:00:33 OpenWrt kern.notice kernel: [   11.250000] sd 1:0:0:0: [sdb] Write Protect is off
Jan  1 00:00:33 OpenWrt kern.debug kernel: [   11.260000] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.260000] sd 1:0:0:0: [sdb] No Caching mode page present
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.270000] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.280000] sd 1:0:0:0: [sdb] No Caching mode page present
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.280000] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 00:00:33 OpenWrt kern.info kernel: [   11.290000]  sdb: sdb1 sdb2 sdb3
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.300000] sd 1:0:0:0: [sdb] No Caching mode page present
Jan  1 00:00:33 OpenWrt kern.err kernel: [   11.300000] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 00:00:33 OpenWrt kern.notice kernel: [   11.310000] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Jan  1 00:00:41 OpenWrt user.notice fstab: mount: mounting /dev/sdb1 on /mnt/sdb1 failed: Invalid argument
Jan  1 00:00:42 OpenWrt kern.err kernel: [   42.210000] EXT4-fs (sdb2): couldn't mount as ext3 due to feature incompatibilities
Jan  1 00:00:42 OpenWrt kern.err kernel: [   42.230000] EXT4-fs (sdb2): couldn't mount as ext2 due to feature incompatibilities
Jan  1 00:00:42 OpenWrt kern.info kernel: [   42.360000] EXT4-fs (sdb2): recovery complete
Jan  1 00:00:42 OpenWrt kern.info kernel: [   42.360000] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 00:00:43 OpenWrt kern.err kernel: [   43.460000] EXT4-fs (sdb3): couldn't mount as ext3 due to feature incompatibilities
Jan  1 00:00:43 OpenWrt kern.err kernel: [   43.470000] EXT4-fs (sdb3): couldn't mount as ext2 due to feature incompatibilities
Jan  1 00:00:43 OpenWrt kern.info kernel: [   43.480000] EXT4-fs (sdb3): recovery complete
Jan  1 00:00:43 OpenWrt kern.info kernel: [   43.490000] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
root@OpenWrt:~# 

3. I have tried using mount-utils with no success. It seems no matter what the busybox's mount is always used instead that from mount-utils. I tried this to enforce using LABEL or UUID but with no success.
4. I had deleted links to busybox in /sbin for mount/umount with that from mount-utils. It just didn't work, infact it didn't boot. So I had to do a failsafe recovery.
5. Is there a way to enforce the order of usb device? So that the usb disk always get /dev/sda and the CDMA device always get /dev/sdb? Is there any other way? The problem is it becomes difficult for someone else to troubleshoot this behaviour.

Thanks.
~LT