this is wrong syntax for psk/2

hello xssa

your reply was correct it was the wrong syntax i have changed the following

/etc/config/wireless
config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'channel' '5'
        option 'disabled' '0'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'wan'
        option 'mode' 'sta'
        option 'key' '*********'
        option 'txpower' '19'
        option 'ssid' '**********'
        option 'encryption' 'psk'

/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 'dns' '192.168.1.100'
        option 'gateway' '192.168.1.100'
        option 'ipaddr' '192.168.1.55'

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

root@TPLink-mpcs_v2:~# wifi
udhcpc (v1.11.2) started
Sending discover...
root@TPLink-mpcs_v2:~# Sending discover...
Sending select for 192.168.0.3...
Lease of 192.168.0.3 obtained, lease time 86400
udhcpc: ifconfig ath0 192.168.0.3 netmask 255.255.255.0 broadcast +
udhcpc: setting default routers: 192.168.0.1
udhcpc: setting dns servers: **************

root@TPLink-mpcs_v2:/etc/config# ping google.com -c3
PING google.com (74.125.235.16): 56 data bytes
64 bytes from 74.125.235.16: seq=0 ttl=49 time=220.193 ms
64 bytes from 74.125.235.16: seq=1 ttl=49 time=195.459 ms
64 bytes from 74.125.235.16: seq=2 ttl=49 time=192.477 ms

root@TPLink-mpcs_v2:/etc/config# uci -P/var/state get network.wan.ipaddr
192.168.0.3 (assigned by ap router)

root@TPLink-mpcs_v2:/etc/config# brctl show
bridge name     bridge id               STP enabled     interfaces
br-lan          8000.940c6df6d82b       yes             eth0

now i can ping to the internet and the ap from the openwrt telnet console but not from the the windows computer which has only access to the openwrt telnet console with static entry from /etc/network

my other question is how to enable dhcp on this router as i cannot acquire an ip from this router i can only assign static ip ,gateway in windows tcp/ip controls to connect to the router telnet console .....

there is no dhcp in /etc/config to edit or set or

how to connect to the router to get to internet...... all this time i have been assigning static ip in windows xp to connect to the router but with static ip i  cannot get internet on the browser or ping to anything other than the openwrt console

ps from the openwrt console i can ping to the the internet and to the ap router but not from windows machine

thanks in advance

(Last edited by drekthar on 20 Aug 2011, 19:39)

Your setup needs any routing and NAT features to be build into the kernel but will make it bigger more then 128kB so there will be no space for jffs2 overlay, and I think there will be a significant limit in RAM to handle NAT tables. DHCPd is need to be included as busybox feature as it does not in current image. If you need one i can build it, hope it will not increase rootfs size. Some research has to be done on what your wishes can be included and will not make this device unstable.
Your wish list?

xssa

You are very kind........ but to the extent of my knowledge i have understood that in a client mode setup. the client router requires dhcp to issue leases to the clients connected to it by lan... hence making the clients  on a different subnet...... while in a client bridge setup all the clients behind the client router and the ap router are under one subnet (ie the subnet of the ap router) and all the ip addrsses are assigned by the ap router ie (no dhcp is required in the client router)

So from what i have understood the client mode will not work unless there is a dhcp server running on the wr340g so it can assign ip to the clients that are connected to it
.................................so do u think DHCPd will fit into an other image without any problems with size

and as asked earlier my wish is to use this router in client mode ......... and even i think that with only 8mb ram in these routers stability in the router will be a problem with dhcpd anyway best way to know is to test.....

ps: you say in the previous post u have successfully used this router as client how did you do this ?
thanks in advance

(Last edited by drekthar on 8 Aug 2011, 16:56)

Hi. I have bricked TP-LINK 340G V2.3. I make SPIPGM programmer and unsolder flash 2MB 25L16050M2C . How program flash by SPI with 900KB bin? Adding at end file FF FF FF... not working :-( I need full 2MB bin file to program in SPIPGM. THX.
http://imageshack.us/photo/my-images/71 … inside.jpg

(Last edited by tplink10 on 11 Aug 2011, 14:07)

to
xssa

all the documentation in openwrt wiki states the a client bridge cannot work on an atheros platform ....because of the atheros drivers but you say client bridge is possible with this image could you explain how ? did you use arp-nat scripts  or some other workaround ?

thanks in advance
help is appreciated

WA-500g
with kamikaze 8.9.2 have no bootable image found, try default location 0xBFC10000 .. on backfire ap boot ok but have problem with rootfs ..

to our guru ;> Xssa
any chance for config backfire .. that U build for wa500g ..
Thank you in advance ..
update :. Backfire (10.03.1-RC6, r27980)  boot ok..

root@OpenWrt:/# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 1.0M   1004.0K     20.0K  98% /

20k hmm, ;>

(Last edited by lowac on 14 Aug 2011, 16:31)

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

If you'll google "openwrt client-bridge" you'll find https://forum.openwrt.org/viewtopic.php?pid=98452 and etc.

(Last edited by xssa on 15 Aug 2011, 21:34)

The Openwrt config is not only an issue to build such tiny images. There are also many changes in kernel config, toolchain, some makefiles and base-files. So it is fork. Can anyone prepare hosting?

to xssa

at both these links ,https://forum.openwrt.org/viewtopic.php?pid=98452 and  http://wiki.openwrt.org/doc/howto/clientmode
they point out that a client bridge is not possible in an atheros platform but rather only in a broadcom platform because of the drivers

quote
First of all: client bridge mode on Kamikaze works only with the brcm-2.4 variant and the proprietary broadcom driver.

So the only possible options are

1)Routed client mode (which i have tested and it work properly)
2)client mode (which requires a dhcp server on the router to assign ip addresses ie dnsmasq)
3)wds (which i cannot use or try as my ap router does not have this feature )

PS I can take up the duty to host all the files..... i have been wondering why all the images i create don't even boot all the leds start flashing like crazy i don't have a  serial console at the moment so i can't post log but i don't think it will be helpful as the router doesn't attempt to boot at all.. as soon as the power is plugged in all the leds starts flashing very fast....... i am using kamikaze 8.09 and backfire rc5 sources both with no working images

i have one more question in the images u built the rootfs has an extention of .rom (rootsq.rom) while all the images i create have the extension of .squashfs how did you make a .rom file ?

xsaa is it possible for u to make a new image with a dhcp server (dnsmasq) all my efforts where with futile results

thanks in advance

(Last edited by drekthar on 29 Aug 2011, 16:21)

What about change flash on 4mb ? what about redboot in this case .. exp. EN25Q40 ..? series is supported ..? :>
What about gpioctl foud .. gpioct 2 -> led2 , gpioctl  7 -> led 4 .. Need two more ;>  6 reset ..

(Last edited by lowac on 19 Aug 2011, 14:21)

I was wondering on implementing a sd/mmc mod the TP-LINK WR340G router.....

I figured that if we managed to create a striped down kernel and rootfs and maybe drop wifi support and include all the driver required for a sd/mmc card to work..... then eveything can be installed later on via opkg or binary packages to the attached memory card later on

here are my findings of the gpio pins from the tool gpioctl

gpio pins

1              ,2            ,3         ,4             ,5                    ,7
.                .             .           .               .                      .
.                .             .           .               .                      .
.                .             .           .               .                      .
cannot     wlan                                 cannot               Sys 
control      led           ?          ?           control              light
              (Led 8                                                   (which constantly
             on Pcb)                                                    flashes always.
                                                                          so gpioctl reads
                                                                            high and low
                                                                            consequently)
                                                                                (Led 2
                                                                               on Pcb)
                         
i haven't found the exact location of the pins on the pcb board. Probing the pcb board with a voltmeter is in order here....

will report back when more info is available
to be continued.........

(Last edited by drekthar on 2 Sep 2011, 09:24)

WIKI HAS BEEN UPDATED

http://wiki.openwrt.org/toh/tp-link/wr340gd?s[]=wr340g

i want to buy an wr340g and flash it with openwrt.
i see an tp-link site there are v1 to v5.
which of this one is supported? has marvell switch, not atheros.?
how can i know what HW version to buy?

(Last edited by maurer on 17 Sep 2011, 10:05)

hello maurer

the version you see on the tplink site are software versions rather than actual harware revisions
there are mainly two harware revisions that i am aware of
1 v2.24 (the v2.24 has the marvell switch which is fully supported by the vxkiller image
2 v3.1 (v3.1 is not supported by the vxkiller  image as it has the Atheros ar8236 switch chip which is not supported by the Vxkiller image LAN/WAN ports will not work...

you can see the actual revision no on the black sticker found on the back side of the unit......

ps: read the wiki on this router it has more information

http://wiki.openwrt.org/toh/tp-link/wr340gd?s

(Last edited by drekthar on 17 Sep 2011, 13:48)

Where i can get wr542_linux.bin ?
Thanks !

email member xssa he can help he made all the vxkiller in this forum

Hello.
Who knows how to set up work wr340g in sta mode with wpa2 security. Thank you in advance.

i have tried this and have successfully cliented to an ap with wpa-psk encryption

what kernel and rootfs did u flash in your router.......did u build your own image ?....if yes.....did u include dnsmasq(dhcpserver )  in you build ?

more information is required on the linux you'r running

To drekthar.
Happy for You. I hope that You and Your experience will help me.
1)Made Everything for Your article in the Wiki. Images uploaded on the links in the article http://wiki.openwrt.org/toh/tp-link/wr340gd?s[]=wr340g.
2)Apparently no wpa_supplicant(although I can its just not found) , there is only wpa_passphrase(not very strong in supplicante).
3)Ideally, I want to connect wr340 as a client Bridge with wpa2(as I understood it is necessary to collect the image with the patch from the gargoyle). The second option if I understand correctly xssa the native firmware from the tl-WA500g with VxWorks.
4)Meanwhile, run as Routed Client with wpa2 security.
To install wpa_supplicant in the image of the wiki is not enough space on the jffs2.
From here I think it is necessary to dig in the assembly of my own image. Unfortunately a large experience in the matter of assembling your system does not have(such as the kernel, i can leave the old or rebuild it.). If you can tell me the key moments of the path that I need to pass or share your correct images, if any.
5)I want not only to implement the plan, and i want  improve the knowledge on Linux, especially in embedded systems.
Big thank you.

glad to see people interested in openwrt
sorry for the late reply was busy with school......
okay here goes...
quote
".To install wpa_supplicant in the image of the wiki is not enough space on the jffs2"

okay the rootfs and kernel you flashed to your router does not have opkg package system nor does it have wpa-supplicant preinstalled but there is another way to put wpa supplicant in the current build in the form of a binary

instructions are
download the wpa supplicant binary from this link http://sharecash.org/download.php?file=2341970
after this put this binary on any available
ftp/http server, then download it to the /tmp directory on the your
openwrt, add executable rights to it, and move it to the /usr/sbin

(in windows  i used radienftp it is quite easy to setup)
commands are

#cd /tmp
#wget ftp://user:pass@server_ip/wpa_supplicant
#chmod +x wpa_supplicant (make it executable)
#mv wpa_supplicant /usr/sbin

THIS METHOD WAS CREATED BY XSSA THIS IS HIS BINARY THE ONE HE BUILT.......FULL CREDIT GOES TO HIM I AM MERELY HELPING

after this just configure cd /etc/config/wireless with the ssid of the router u wan to connect followed by the password

here is the syntax for wpa-psk 1
pinging to the router
config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'wan'
        option 'mode' 'sta'
        option 'key' '*********'
        option 'txpower' '19'
        option 'ssid' '**********'
        option 'encryption' 'psk'

after this do
ifup wan
wifi

you should be connected now to the ap router test by pinging to the ap router or the internet

quote
"3)Ideally, I want to connect wr340 as a client Bridge with wpa2(as I understood it is necessary to collect the image with the patch from the gargoyle). "
Yes the patch is arp-nat from gargoyle it uses arp-nat to create a bridge. and ddwrt firmwares use this trick for client bridge in their atheros supported routers here is a link for more information
http://projectgus.com/wireless-client-b … h-openwrt/

quote
"The second option if I understand correctly xssa the native firmware from the tl-WA500g with VxWorks."
Yes this is correct although the bridge can be created only with wep encryption.....  besides vxworks suck's

quote
"4)Meanwhile, run as Routed Client with wpa2 security. "
Again i have tried this and it run's flawlessly. although i was not happy with routed client mode and wanted to use client mode which requires a dhcp server in the image which issues lease to all the clients connected to the router rather than static routes for each clients......
although i have not been able to make an image with dnsmasq included...... as size was very high as i am not an experienced linux user or programmer i have sent xssa a mail regarding a new kernel and rootfs with dhcp server so that client mode can be implemented 

quote
"5)From here I think it is necessary to dig in the assembly of my own image. Unfortunately a large experience in the matter of assembling your system does not have(such as the kernel, i can leave the old or rebuild it.). If you can tell me the key moments of the path that I need to pass or share your correct images, if any.5)I want not only to implement the plan, and i want  improve the knowledge on Linux, especially in embedded systems.
Big thank you"

Okay her's is what you have to know. Making openwrt firmware is a very easy business using buildroot for 4mb flash router as they have enough space for linux to run and offer more functionality.... but in the case of 2mb flash routers openwrt devs has made no attempt to make minimal firmware to support 2mb flash router like the tp-link wr340g the openwrt devs answer to this by saying that 2mb flash router's are useless and that none of the openwrt devs have 2mb flash router's..... so a lot of people have to endup making their own minimal striped down firmware by removing MANY unwanted features to get a linux running on the router.....

okay now to get a openwrt running on a 2mb flash router remove everything and keep only

essential packages for openwrt to boot

base-files-atheros_14.3-r18801_mips
busybox_1.11.2-2.2_mips (remove unwanted busybox applets to save space)
hotplug2_0.9+r102-2_mips
libgcc_4.1.2-14.3_mips
libuci_0.7.3-1_mips
uci_0.7.3-1_mips
uclibc_0.9.29-14.3_mips
udevtrigger_106-1.1_mips

as for wifi the madwifi driver is very big and i have no idea how xssa manged to include a minimal image with wifi........ i had no luck in making an image with wifi to reach the size xssa has achieved in his image....... i still use the kernel and rootfs which he built......

busybox can be stripped  by removing
archival tools
ipv6 support
and anything else unwanted

next the kernel should  be made smaller with make kernel_menuconfig (By removing support for hardware that isn't present on the router ie usb support etc) and many more thing......

remeber xssa kernel and rootfs with wifi is 640/704kb respectively which is amazing how he made everything fit (especially wifi) at only 1.344 mb

keep updating of you success with this router in the forum

(Last edited by drekthar on 29 Sep 2011, 18:11)

A very large, just a huge thank you for the information.
"I understand everything ", thanks for the link to wpa_supplicant. I'll try, unfortunately after the weekend, tomorrow I am going on a business trip.
Once again thank you.

hello after storm my wlan port propably dont work, can I use vlan feature to set wlan port lan 1-4 ? If yes please tell me how

thx for anserw

aww sorry yes it's WAN port (that blue)

config from WRT54GL (kamikaze 7.09):
WAN port as LAN port nr 1.

#### VLAN configuration
config switch eth0
        option vlan0    '0 1 2 5*'
        option vlan1    '3 5'

#### Loopback configuration
config interface loopback
        option ifname   "lo"
        option proto    static
        option ipaddr   127.0.0.1
        option netmask  255.0.0.0

#### WAN configuration               
config interface        wan       
        option ifname   "eth0.1"
        option proto    dhcp 

#### LAN configuration
config interface lan
        option type     bridge
        option ifname   "eth0.0"
        option proto    static
        option ipaddr   192.168.0.1
        option netmask  255.255.255.0
        option dns      192.168.1.1

what change for TP Link ? I dont know how edit this '0 1 2 5*' :(

(Last edited by l0l on 24 Sep 2011, 10:34)