Yes, that's how I tried after the upgrade. My PC was the only thing connected (and the power )
The modem/router was only connected when I updated the firmware. So the clash could have been present. I have changed the IP before the update and that worked ok. Of course, the WiFi was useless then.
Search found 4 matches
- Sat Dec 28, 2013 6:12 pm
- Forum: Hardware / Installation Issues
- Topic: TP-Link WR1043NB - bricked?
- Replies: 8
- Views: 7007
- Thu Dec 26, 2013 1:38 pm
- Forum: Hardware / Installation Issues
- Topic: TP-Link WR1043NB - bricked?
- Replies: 8
- Views: 7007
Re: TP-Link WR1043NB - bricked?
Thanks again! There was no clash before the firmware update, and the other is a cisco, so I was sure on which I was installing on. The "Gargoyle defaults" section on the download page made me think that it changed the IP to 192.168.1.1 Unfortunately I don't have the tools to do the serial ...
- Thu Dec 26, 2013 7:15 am
- Forum: Hardware / Installation Issues
- Topic: TP-Link WR1043NB - bricked?
- Replies: 8
- Views: 7007
Re: TP-Link WR1043NB - bricked?
Hey, Thanks for your reply. Yes, I have tried the manual IP thing, but that didn't work. I have also tried the failsafe mode, but the sys led only blinks for a split second after giving it power, and no matter how many times I tried it didn't react to the QSS button at all. It doesn't even react to ...
- Mon Dec 23, 2013 6:24 pm
- Forum: Hardware / Installation Issues
- Topic: TP-Link WR1043NB - bricked?
- Replies: 8
- Views: 7007
TP-Link WR1043NB - bricked?
Hi, I need some help, please! I have installed gargoyle_1.5.3-ar71xx-tl-wr1043nd-v1-squashfs-factory.bin onto my new router, hoping that it'd solve the WiFi problem. (I have first tried the latest factory firmware, but that didn't help, so I tried gargoyle). It went through the installation fine, sa...