this my sys log i delete my ip
Jan 1 12:00:11> AP Acquiring Lock
Jan 1 12:00:11> NTP Polling Timer for DHCP Started succesfully.
Jan 1 12:00:11> DSL Polling Timer Started succesfully.
Jan 1 12:00:12> Firewall NAT service started
Jan 1 12:00:12> AP REPORT LOCK ACQUIRED
Jan 1 12:00:12> wlan_handle_load_event - Acquired Lock
Jan 1 12:00:12> MAC address is : 00:50:f1:12:12:10
Jan 1 12:00:16> starting on port 80
Jan 1 12:00:16> (c)2000 Netfilter core team
Jan 1 12:00:16> netfilter PSD loaded - (c) astaro AG
Jan 1 12:00:16> Initializing the WAN Bridge.
Jan 1 12:00:16> Please set the MAC Address for the WAN Bridge.
Jan 1 12:00:16> Set the Environment variable 'wan_br_mac'.
Jan 1 12:00:16> xx.xx.xx.xx.xx.xx
Jan 1 12:00:16> Mounted root (squashfs filesystem) readonly.
Jan 1 12:00:16> Mounted devfs on /dev
Jan 1 12:00:16> 64k freed
Jan 1 12:00:16> Algorithmics/MIPS FPU Emulator v1.5
Jan 1 12:00:16> registered device TI Avalanche SAR
Jan 1 12:00:16> Ohio250(7200/7100A2) detected
Jan 1 12:00:16> DSP binary filesize = 356930 bytes
Jan 1 12:00:16> Setting mode to 0xffff
Jan 1 12:00:16> version:[6.00.01.00]
Jan 1 12:00:16> Disable_igmp_snooping_register!!!
Jan 1 12:00:16> Setting mode to 0xffff
Jan 1 12:00:16> Default Asymmetric MTU for nas0 1500
Jan 1 12:00:16> Registering protocol inspector: 0x94176bf8 for VCC:0x9400da00
Jan 1 12:00:16> Default Asymmetric MTU for br0 1500
Jan 1 12:00:16> Bridge Created: br0
Jan 1 12:00:16> Bridge Created: br1
Jan 1 12:00:17> 2
Jan 1 12:00:17> Default Asymmetric MTU for br1 1500
Jan 1 12:00:17> 2
Jan 1 12:00:17> WPA Authenticator Started
Jan 1 12:00:17> Bridge Interface Added: eth0
Jan 1 12:00:20> Default Asymmetric MTU for wlan0 1500
Jan 1 12:00:20> Default Asymmetric MTU for wdsup0 1500
Jan 1 12:00:20> Default Asymmetric MTU for wdsdw0 1500
Jan 1 12:00:20> Default Asymmetric MTU for wdsdw1 1500
Jan 1 12:00:20> Default Asymmetric MTU for wdsdw2 1500
Jan 1 12:00:20> Default Asymmetric MTU for wdsdw3 1500
Jan 1 12:00:20> ERROR: DIE ID Mismatch eeprom ID: 12345678 90abcdef TNETW ID: b0015d39 c7520a14
Jan 1 12:00:20> ERROR: Validate EEPROM Image failed
Jan 1 12:00:20> Error: Failed to get a valid EEPROM Image. AP is DOWN
Jan 1 12:00:20> NVS_TFTP_LOAD is enabled to download the correct EEPROM image during next boot. Set TFTP Server Address using IPA_SVR env variable
Jan 1 12:00:20> Setting bootloader env NVS_TFTP_LOAD to 1
Jan 1 12:00:20> AP Releasing Lock
Jan 1 12:00:20> MemAddr=0xa4000000, RegAddr=0xa4080000
Jan 1 12:00:20> starting cleanup:
Jan 1 12:00:20> cleanup finish succesfully, good-bye.
Jan 1 12:00:21> DSL Carrier is down
Jan 1 12:00:35> DSL in Sync
Jan 1 12:00:41> DSL Carrier is up
Jan 1 12:00:42> sar read trained mode (16)(ADSL_2plus_AnxM)
Jan 1 12:00:43> pingStat 2, oamHdr 230 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 200 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 280 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 240 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 260 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 600 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 230 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 800230 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 2B0 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 330 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 3B0 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 8002B0 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 800330 result 0
Jan 1 12:00:43> pingStat 2, oamHdr 8003B0 result 0
Jan 1 12:00:43> get 0xF at Addr 0xA30085B0
Jan 1 12:00:43> pppd 2.4.3 started by root, uid 0
Jan 1 12:00:43> Connect: ppp0 {--} nas0
Jan 1 12:00:46> peer from calling number 00:25:9E:D3:03:0F authorized
Jan 1 12:00:46> ppp0
Jan 1 12:00:46> WAN IP address
Jan 1 12:00:46> WAN gateway
Jan 1 12:00:46> primary DNS address
Jan 1 12:00:46> PPPoE Connect with IP Address
Jan 1 12:00:46> PPPoE Connection Successfully Established
Jan 1 12:00:46> PPPoE Connect with Gateway IP Address:

Run this script with the PCTool
When you reboot the router, your wireless should be working correctly (assuming that the MAC address is correct).

nothing no wirless everything was pased succesufly just the last line was failed
501 WLAN_EEPROM14 enverenment variable not set .
command unsetenv WLAN_EEPROM14 failed

I think the mac address is correct because I have copy from my router it is written down

Well, it should work. The last env that you posted had WLAN_EEPROM14 in it, and so there should be no error in unsetting it. It would seem to me that your env is fragmented, which is why you are getting these unnecessary errors.

Perhaps the best thing is to remove all the "unsetenv ..." lines from the script, and then run the script again.

think you the chief u are realy the chief and more than the chief ur the boss lol now my wirless is on

now do you have any idea about why my router don't connect with my server in dreambox reciever he take 15 minute to connect i dont know why i used anther router they connect after 1 minut but the my 2640t always take 15min to conncet

Chief is Chief

Thanks
Sorry, since I have no Dreambox, and know nothing about it, I have no idea. But if another router is connecting more quickly, then the problem is likely to be in the configuration of the Dreambox or the 2640T (perhaps they are not understanding each other very well). What you need to find out is the difference between the configuration of the router that connects very quickly, and the configuration of the 2640T. The answer to your question lies in understanding those differences.

You are so kind!

that's ok. for the configuration i have tried all option from the firwall to UPnP without success and I already do what you told me to make a comparison between the two routesr but there is no deference.
then i have one last question i has surefer the forum to see if the routertech firmware is compatible with my router or not nut i find there are somebudy who say it s working and another told no im confuse I wanted to change my firmware to see if the problem with dreambox may be repaired what do you suggested to me the chief can i change my firmware or not?


think for all the chief

I have a 2640T running a RouterTech 1350A wireless firmware. I have no problem with it. However, some people have problems with it. Officially, our firmware does not support the 2640T because it is a hit and miss affair whether it works or not. This is probably because there are sometimes differences in the hardware itself, but the model name is not changed. So, it is a big risk. Whether you want to take the risk or not is entirely up to you. But if it all goes bad, then don't blame us.

i can take the risk but i should be know four thinks before that
1-how did you flashed your 2640t in details pls ?
2-how can i know if i have the same hardware in my router as yours?
3-if it all goes bad can i get my router backup or not ?
4-i found this link when i m googling can you see it's correct method?
http://blog.tabinda.net/microhard/updat ... -firmware/

I'm very sorry to disturb you thechief with this all question

take care