The_Ogre
Honorary Master
A couple of days ago I bought a TP-link tl-wr840n as I wanted to load dd-wrt on it - this is after I verified it supports dd-wrt.
Turns out TP-Link made a royal fsckup of note! They released two routers with exactly the same model number, but one with a Broadcom and the other with an Atheros chipset.
Anyway, so I ended up using it as an extender (via WDS) to my ADSL router.
I'm thinking of using it as a VPN server to connect to my home network by loading some other custom firmware (tomato, gargoyle, etc).
My problem: even after defaulting the router and using a static IP on my PC, I can't get to the admin screen. I'm trying via cable. I can ping it on its default IP and it responds.
Whats baffling me is that if I do a scan its SSID is still the same as my home network, which leads me to believe the WDS binding still exists somehow. TO verify this I set a random SSID on an old router I had then reset it to factory default settings.
The SSID doesn't get defaulted!
Any ideas?
Turns out TP-Link made a royal fsckup of note! They released two routers with exactly the same model number, but one with a Broadcom and the other with an Atheros chipset.
Anyway, so I ended up using it as an extender (via WDS) to my ADSL router.
I'm thinking of using it as a VPN server to connect to my home network by loading some other custom firmware (tomato, gargoyle, etc).
My problem: even after defaulting the router and using a static IP on my PC, I can't get to the admin screen. I'm trying via cable. I can ping it on its default IP and it responds.
Whats baffling me is that if I do a scan its SSID is still the same as my home network, which leads me to believe the WDS binding still exists somehow. TO verify this I set a random SSID on an old router I had then reset it to factory default settings.
The SSID doesn't get defaulted!
Any ideas?
