Serial to TTL cable did the trick, just changed eth0 from static to dhcp.
Don't know why the button is not working for failsafe with this version of OpenWRT
Topic: How to upgrade TPLINK TL-MR3020 firmware to technobit openwrt - page 5. (Read 57314 times)
September 17, 2014, 06:17:30 PM
September 07, 2014, 11:40:55 PM
What a joy to work with, with that Technobit/cgminer fw! After the recovery reset, is the ip not 192.168.0.254, like here, see the comments? http://tplinkmr3020.blogspot.nl/2012/09/failsafe-recovery-reset.html
What a joy dudeNext time use stock china firmware when yo mine.
So you will mine with 0 GH guaranteed but reset will work eventually
ps I am positive about the tb/cgminer, if you missed that.
My English sucks. Sorry
I am glad you like it.
Best
L
September 07, 2014, 02:52:33 PM
What a joy to work with, with that Technobit/cgminer fw! After the recovery reset, is the ip not 192.168.0.254, like here, see the comments? http://tplinkmr3020.blogspot.nl/2012/09/failsafe-recovery-reset.html
What a joy dudeNext time use stock china firmware when yo mine.
So you will mine with 0 GH guaranteed but reset will work eventually
ps I am positive about the tb/cgminer, if you missed that.
September 07, 2014, 12:45:55 PM
What a joy to work with, with that Technobit/cgminer fw! After the recovery reset, is the ip not 192.168.0.254, like here, see the comments? http://tplinkmr3020.blogspot.nl/2012/09/failsafe-recovery-reset.html
What a joy dudeNext time use stock china firmware when yo mine.
So you will mine with 0 GH guaranteed but reset will work eventually
For the record there is no such thing as factory reset in openwrt using buttons. Reset can be performed only via web.just read what fail safe openwrt mode is and how to use it
2good
1. I never use dhcp for mining
2. I have to dig serial cable like you and I will check this out
I have enough bricks already due to various reasons
so I will find a serial cable and max232 probably pull up res is needed also and will check that out. And I will recover all my bricks 
I hope marto staff will fix that in upcoming image
I vote dhcp to be removed. If a miner can not set ip mask gw and DNS this stuf is not for him at all
I am sure marto will take care of the above two issues.
September 07, 2014, 12:39:05 PM
What a joy to work with, with that Technobit/cgminer fw! After the recovery reset, is the ip not 192.168.0.254, like here, see the comments? http://tplinkmr3020.blogspot.nl/2012/09/failsafe-recovery-reset.html
September 07, 2014, 11:16:09 AM
All this was caused just by changing the static IP setting to DHCP in Technobit's OpenWRT. Beware of that!
I managed to accomplish the exact same result as gator, the problem is when you switch from static to DHCP you have to FIRST press the Switch Protocol button, then Save/Apply if not the device remains with static IP but not set any, i.e. null
So far I can not enter failsafe mode, maybe it's not included with this build or the buttons are ignored... don't know the reason. @loshia please share your opinion
P.S.
===
I have to find my serial cable to fix this piece of plastic
Did you manage to fix you tp-link gator
Ok
Sorry to say that gator but there is 0 activity on tplink LAN then
It is not asking for ip and also it is not broadcasting so
The only option left is to hack it and use console it is hardware hack
Yo can still try various buttons to reset it while sniffing it can revival itself eventually
Best
Sorry to say that gator but there is 0 activity on tplink LAN then
It is not asking for ip and also it is not broadcasting so
The only option left is to hack it and use console it is hardware hack
Yo can still try various buttons to reset it while sniffing it can revival itself eventually
Best
I am not so sure whether the switch position had impact to the system but i believe you should move it to 3G/4G.
Since the default IP is 192.168.0.99, maybe after reset the ip will be 192.168.0.99 not 192.168.1.1.
If you success then you can give command for full reset
Since the default IP is 192.168.0.99, maybe after reset the ip will be 192.168.0.99 not 192.168.1.1.
Quote
Failsafe Mode
- Set your computer's IP to 192.168.0.2, subnet 255.255.255.0
- Connect the TL-MR3020 to your computer via ethernet
- Power on the TL-MR3020
- When the WPS button starts to blink:
on BB (Breaking Barrier / trunk) move the sliding switch quickly from one side to the other.
- Do this until the WPS button starts blinking faster.
- The device is now in Failsafe-Mode
- You may access it by using telnet 192.168.0.99
- Set your computer's IP to 192.168.0.2, subnet 255.255.255.0
- Connect the TL-MR3020 to your computer via ethernet
- Power on the TL-MR3020
- When the WPS button starts to blink:
on BB (Breaking Barrier / trunk) move the sliding switch quickly from one side to the other.
- Do this until the WPS button starts blinking faster.
- The device is now in Failsafe-Mode
- You may access it by using telnet 192.168.0.99
If you success then you can give command for full reset
Code:
firstboot
I've tried all three switch positions.
I've tried 192.168.0.99 and 192.168.1.1 and DHCP but no luck, I just can't see it talking on the network or even directly connected.
I tried pressing the button after it flashes, and moving the switch after it flashes, but no luck, there is no high speed flash, and no reset.
All this was caused just by changing the static IP setting to DHCP in Technobit's OpenWRT. Beware of that!
The tp-link is awesome, simple to setup and so simple to make changes on the fly 
This is genius!
Thank you
Thank you
I am not so sure whether the switch position had impact to the system but i believe you should move it to 3G/4G.
Since the default IP is 192.168.0.99, maybe after reset the ip will be 192.168.0.99 not 192.168.1.1.
If you success then you can give command for full reset
Since the default IP is 192.168.0.99, maybe after reset the ip will be 192.168.0.99 not 192.168.1.1.
Quote
Failsafe Mode
- Set your computer's IP to 192.168.0.2, subnet 255.255.255.0
- Connect the TL-MR3020 to your computer via ethernet
- Power on the TL-MR3020
- When the WPS button starts to blink:
on BB (Breaking Barrier / trunk) move the sliding switch quickly from one side to the other.
- Do this until the WPS button starts blinking faster.
- The device is now in Failsafe-Mode
- You may access it by using telnet 192.168.0.99
- Set your computer's IP to 192.168.0.2, subnet 255.255.255.0
- Connect the TL-MR3020 to your computer via ethernet
- Power on the TL-MR3020
- When the WPS button starts to blink:
on BB (Breaking Barrier / trunk) move the sliding switch quickly from one side to the other.
- Do this until the WPS button starts blinking faster.
- The device is now in Failsafe-Mode
- You may access it by using telnet 192.168.0.99
If you success then you can give command for full reset
Code:
firstboot
I even put a router in between the laptop and the TP-Link just to make sure it's served a DHCP address, because setting DHCP Client is what caused this mess, nothing, laptop got a DHCP address, but the TP-Link Lights are on but no one is home. 
Connect tplink directly to your LAN card of PC
Fire wire shark
Stop all pings
Start capturing packets
Power tplink
Want 10 secs and post captured packets here
Fire wire shark
Stop all pings
Start capturing packets
Power tplink
Want 10 secs and post captured packets here
Code:
No. Time Source Destination Protocol Length Info
1 0.000000000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x5ff377b
Frame 1: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
No. Time Source Destination Protocol Length Info
2 0.452228000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 2: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
3 0.452317000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 3: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
4 2.438787000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x9c8bcfd5
Frame 4: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
No. Time Source Destination Protocol Length Info
5 2.452347000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 5: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
6 2.452401000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 6: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
7 2.952388000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 7: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
8 3.452432000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 8: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
9 3.959501000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 9: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info
10 4.452530000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 10: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
11 6.448461000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x3210f771
Frame 11: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
No. Time Source Destination Protocol Length Info
12 6.452567000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 12: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
13 6.452647000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 13: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
14 6.952622000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 14: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
15 6.959884000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 15: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info
16 7.452624000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 16: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
17 8.452699000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 17: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
18 9.465652000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
Frame 18: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
19 9.473102000 169.254.85.24 169.254.255.255 UDP 112 Source port: 27036 Destination port: 27036
Frame 19: 112 bytes on wire (896 bits), 112 bytes captured (896 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255)
User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036)
Data (70 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_.........
0010 a9 df d9 db 96 fa 01 10 01 29 00 00 00 08 06 10 .........)......
0020 06 18 e7 82 03 22 0a 41 43 45 52 2d 36 39 33 35 .....".Laptop
0030 47 30 03 38 09 4a 0b 09 c6 71 f8 05 01 00 10 01 G0.8.J...q......
0040 10 00 50 e4 82 03 ..P...
No. Time Source Destination Protocol Length Info
20 9.473210000 169.254.85.24 169.254.255.255 UDP 73 Source port: 27036 Destination port: 27036
Frame 20: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255)
User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036)
Data (31 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_.........
0010 a9 df d9 db 96 fa 01 10 00 02 00 00 00 08 35 ..............5
No. Time Source Destination Protocol Length Info
21 9.473936000 169.254.85.24 169.254.255.255 UDP 73 Source port: 27036 Destination port: 27036
Frame 21: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255)
User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036)
Data (31 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_.........
0010 a9 df d9 db 96 fa 01 10 00 02 00 00 00 08 36 ..............6
No. Time Source Destination Protocol Length Info
22 9.475913000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 22: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info
23 9.497883000 169.254.85.24 169.254.255.255 NBNS 92 Name query NB ISATAP<00>
Frame 23: 92 bytes on wire (736 bits), 92 bytes captured (736 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255)
User Datagram Protocol, Src Port: netbios-ns (137), Dst Port: netbios-ns (137)
NetBIOS Name Service
No. Time Source Destination Protocol Length Info
24 9.529278000 169.254.85.24 169.254.255.255 NBNS 110 Registration NB LaptopG<00>
Frame 24: 110 bytes on wire (880 bits), 110 bytes captured (880 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255)
User Datagram Protocol, Src Port: netbios-ns (137), Dst Port: netbios-ns (137)
NetBIOS Name Service
No. Time Source Destination Protocol Length Info
25 9.952803000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
Frame 25: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22)
Internet Group Management Protocol
No. Time Source Destination Protocol Length Info
26 9.959922000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 26: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0
Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info
27 10.229933000 169.254.85.24 169.254.255.255 NBNS 92 Name query NB Laptop<00>
Gator
You laptop did not picked address at all
There is no dhcp server to give address to your laptop
You do not have a gateway right besides openwrt Technobit build does not have dhcp server build in at all
Just use wire shark
According to windows rules there is no such thing as de configured state in order words when there is dhcp server to give you agrees windows picks one
Or,just set your laptop to 192.168.1.12/24
Ping 192.168.1.1 -t from dos
And try with reset button
When you do it you will see replies,from 1.1 tplinkk
You laptop did not picked address at all
There is no dhcp server to give address to your laptop
You do not have a gateway right besides openwrt Technobit build does not have dhcp server build in at all
Just use wire shark
According to windows rules there is no such thing as de configured state in order words when there is dhcp server to give you agrees windows picks one
Or,just set your laptop to 192.168.1.12/24
Ping 192.168.1.1 -t from dos
And try with reset button
When you do it you will see replies,from 1.1 tplinkk
I set the laptop to 192.168.1.10 255.255.255.0
Wireshark is recording the LAN
No other IP addresses show up in wireshark.
No response from pinging 192.168.1.1
When I try to do the reset thing when the light blinks on the TP-Link it doesn't blink faster afterwards.
also tried 192.168.0.10 255.255.255.0
No response from 192.168.0.99
which is where it original was after installing Technobits OpenWRT.
Fire wire shark
Stop all pings
Start capturing packets
Power tplink
Want 10 secs and post captured packets here
Gator
You laptop did not picked address at all
There is no dhcp server to give address to your laptop
You do not have a gateway right besides openwrt Technobit build does not have dhcp server build in at all
Just use wire shark
According to windows rules there is no such thing as de configured state in order words when there is dhcp server to give you agrees windows picks one
Or,just set your laptop to 192.168.1.12/24
Ping 192.168.1.1 -t from dos
And try with reset button
When you do it you will see replies,from 1.1 tplinkk
You laptop did not picked address at all
There is no dhcp server to give address to your laptop
You do not have a gateway right besides openwrt Technobit build does not have dhcp server build in at all
Just use wire shark
According to windows rules there is no such thing as de configured state in order words when there is dhcp server to give you agrees windows picks one
Or,just set your laptop to 192.168.1.12/24
Ping 192.168.1.1 -t from dos
And try with reset button
When you do it you will see replies,from 1.1 tplinkk
I set the laptop to 192.168.1.10 255.255.255.0
Wireshark is recording the LAN
No other IP addresses show up in wireshark.
No response from pinging 192.168.1.1
When I try to do the reset thing when the light blinks on the TP-Link it doesn't blink faster afterwards.
also tried 192.168.0.10 255.255.255.0
No response from 192.168.0.99
which is where it original was after installing Technobits OpenWRT.
Okay fired up wireshark
It seems to be broadcasting 169.254.85.24
so I set my laptop to DCHP client and it picked up the address
I definatly told the TP-Link/OpenWRT to use a DHCP client, not become a DHCP server!
I'm still none the wiser how to communicate with the thing 255.255.0.0 is a lot of possible addresses.
Does it matter what mode the switch is in? It's in the middle setting WISP.
GatorIt seems to be broadcasting 169.254.85.24
so I set my laptop to DCHP client and it picked up the address
Code:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::150c:a7b3:cc9e:5518%10
Autoconfiguration IPv4 Address. . : 169.254.85.24
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
I definatly told the TP-Link/OpenWRT to use a DHCP client, not become a DHCP server!
I'm still none the wiser how to communicate with the thing 255.255.0.0 is a lot of possible addresses.
Does it matter what mode the switch is in? It's in the middle setting WISP.
You laptop did not picked address at all
There is no dhcp server to give address to your laptop
You do not have a gateway right besides openwrt Technobit build does not have dhcp server build in at all
Just use wire shark
According to windows rules there is no such thing as de configured state in order words when there is dhcp server to give you agrees windows picks one
Or,just set your laptop to 192.168.1.12/24
Ping 192.168.1.1 -t from dos
And try with reset button
When you do it you will see replies,from 1.1 tplinkk
Okay fired up wireshark
It seems to be broadcasting 169.254.85.24
so I set my laptop to DCHP client and it picked up the address
I definatly told the TP-Link/OpenWRT to use a DHCP client, not become a DHCP server!
I'm still none the wiser how to communicate with the thing 255.255.0.0 is a lot of possible addresses.
Does it matter what mode the switch is in? It's in the middle setting WISP.
It seems to be broadcasting 169.254.85.24
so I set my laptop to DCHP client and it picked up the address
Code:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::150c:a7b3:cc9e:5518%10
Autoconfiguration IPv4 Address. . : 169.254.85.24
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
I definatly told the TP-Link/OpenWRT to use a DHCP client, not become a DHCP server!
I'm still none the wiser how to communicate with the thing 255.255.0.0 is a lot of possible addresses.
Does it matter what mode the switch is in? It's in the middle setting WISP.
HELP! Did something dumb.
Logged into TP-Link MR3020 via web page and set Network to from static to DHCP and now I cannot see it on any IP address.
DHCP server is enabled on the Internet router but it don't show up on the network.
I pressed the flashing reset button on boot-up but it didn't seem to reset OpenWRT to 192.168.1.1
Any ideas? Thanks.
Download ethereal wire sharkLogged into TP-Link MR3020 via web page and set Network to from static to DHCP and now I cannot see it on any IP address.
DHCP server is enabled on the Internet router but it don't show up on the network.
I pressed the flashing reset button on boot-up but it didn't seem to reset OpenWRT to 192.168.1.1
Any ideas? Thanks.
Install it
Plug tplink in your PC LAN directly
Fire sniffer wire shark
Power up tplink
And it will tell you what is going on
The flashing reset button is biggest one try it one more time
If you did it it will blink like traffic light
And make sure to adjust your LAN settings Also when you are trying to reach 192.168.1.1
There is open telnet on 192.168.1.1 nothing more no web
You have to login and type a bunch of commands
Please Read openwrt fail safe procedure first
Ps: I am glad to hear fro you gator even though the occasion is not so good. I thought you've quit mining
Jump to: