Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kd2pm]

Rather than go out and get a dlink AP I would like to know if there are any plans to mod the code as it had been back in 1.03 to allow for bridging or AP mode.  I need an extremeN AP without the routing and since my DIR-655 is freed up (changed routers) I want to keep it and use it and not have to go out and spend more money on specific AP hardware. 

I guess I could turn off DHCP and tie a lan port on the DIR-655 to a lan port on the other router that has DHCP turned on and it will kinda sorta do.  But then I cant access the DIR-655 to make any changes. 

Perhaps setting the wan side to a different subnet and allowing the lan side to be on the same subnet as my new router, I could access it that way?

[EddieZ]

I did the 'Turn off DHCP an LAN port" trick and I can manage the router , no problem. The router is fully accessible on its own IP. Yes, some features do not serve any use as an AP, so them not working is fine. You use it as an AP because you already have a modem/router that takes care of firewalls ect.

So what's opposed to this solution?

And I do not understand this: "Perhaps setting the wan side to a different subnet and allowing the lan side to be on the same subnet as my new router".

[kd2pm]

I did the 'Turn off DHCP an LAN port" trick and I can manage the router , no problem. The router is fully accessible on its own IP. Yes, some features do not serve any use as an AP, so them not working is fine. You use it as an AP because you already have a modem/router that takes care of firewalls ect.

So what's opposed to this solution?

And I do not understand this: "Perhaps setting the wan side to a different subnet and allowing the lan side to be on the same subnet as my new router".

What I meant was that my new router is subnetted for 192.168.15.x.  I had to set up the WAN static IP to something other than 192.168.15.x so I made it 10.1.1.1 and then under the network settings I changed the IP for the internal side of the router to 192.168.15.200, rebooted and that allowed me to manage the router as well as be able to see the new router at 192.168.15.1.  Guess I can leave it that way.  I guess I could have set the LAN side of the new router to 192.168.1.2 and not had to change anything on the old DIR-655...ya live and learn...

[claykin]

What I meant was that my new router is subnetted for 192.168.15.x.  I had to set up the WAN static IP to something other than 192.168.15.x so I made it 10.1.1.1 and then under the network settings I changed the IP for the internal side of the router to 192.168.15.200, rebooted and that allowed me to manage the router as well as be able to see the new router at 192.168.15.1.  Guess I can leave it that way.  I guess I could have set the LAN side of the new router to 192.168.1.2 and not had to change anything on the old DIR-655...ya live and learn...

So you have the 655 WAN port connected to a LAN port on your main router?  Is that how you made your 655 into an AP?  if so, that's not advisable as now you are doing double NAT.  In a double NAT config, usually basic webbrowsing works OK, but most other things won't work properly.

[jason1722x]

So you have the 655 WAN port connected to a LAN port on your main router?  Is that how you made your 655 into an AP?  if so, that's not advisable as now you are doing double NAT.  In a double NAT config, usually basic webbrowsing works OK, but most other things won't work properly.

If he disable DHCP double nat shouldn't be an issue.