Posted: Mon Dec 04, 2006 22:37 Post subject: have to reset by console when switchng AP/Client mode???
Hi!
I was testing the new version (12/3), and got kinda stuck. Here's what happened:
In wireless I had an card in AP mode, so i switched to client mode and puff.
Could not ping the router over the LAN.
So, ok, I figured a reset should be in order. Followed the steps outlined in
this post.
The first funny thing after the reboot was when I tried to login into the console, the default user/pass was not working. Rebooted again. Suddenly it works?
Ok, all was well I thought, but still I can't ping it (it didn't pick up the ip from my DHCP server, a another router).
Did a ping scan, nope, it doesn't show up.
Fired up my lappy and there it is: an AP with SSID dd-wrt.
I connected to it and, funnily enough found that the dd-wrt is bridging to my wired LAN.
Ok, tested it, got 23MBit/s transfer (kinda low, maybe it was going through my other router).
But I still can't login into the DD-wrt.
Did the reset thing all again, but got exactly the same results (even the wrong pass after the first reboot).
BTW, dd-wrt was picking up the DHCP from my other router before all this.
I tried make it use a static ip with: "ifconfig eth0 192.168.0.2" but no go.
So what now?
All i'm getting on the console is:
Code:
connect: Network is unreachable
connect: Network is unreachable
connect: Network is unreachable
gethostbyname: Network is unreachable
connect: Network is unreachable
connect: Network is unreachable
connect: Network is unreachable
gethostbyname: Network is unreachable
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Dec 05, 2006 0:14 Post subject:
if you change to client mode the first eth0 port gets a lan port too. this is why its getting unaccessible from your dhcp server. the ath0 interface which is the client, is now the wan port _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Dec 05, 2006 1:22 Post subject:
connect with your laptop or computer to the ethernet port. thats all. per default the unit will provide you a ip with dhcp which is 192.168.1.xxx from default. its like a standard lan port. since a second wan port makes no sense in client mode _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Dec 05, 2006 1:23 Post subject:
and from the default values internet connection is not set to dhcp but disabled. in this case the eth0 port is assigned again as lan port in ap mode too
this is the default setting to make it easier to configure wraps with just one ethernet port _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Ok, I think I got my head around it.
But all this switching around is kinda sneaky.
Is there somewhere I could read about it?
I'm used to working with MT routers (which we use in our wifi community) and this is baffling me.
After testing this DD-wrt based router should end up on my rooftop, and I'd really like not to have to climb there a few times a day. _________________ Is this my signature?
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Dec 05, 2006 14:17 Post subject:
no. but if you have 2 ethernet ports everything is fine. plug your cable into the second port. i had to introduce this for wrap boards with just 1 ethernet port since its almost impossible to configure them if you dont have a dhcp server running etc. so this way is better, and you have one lan port more in client mode _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s