Dual SSID, V5.29.107.12, Wireless Bridge problem

Started by fonuser, Apr 24, 2010, 13:51:50

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

fonuser

Hi,

I have a wireless bridge powered by DD-WRT which successfully bridges to my old Linksys router but it does not seem to route properly to the 2-wire 2700, it says its connected but the 2-wire doesnt. I am trying to make it auth with the 'fusion' SSID but it doesnt seem to work either way.

Does anyone know where I might be going wrong?

Also how do I make it respond to pings over wireless AND how can I manage it over wifi?

Glenn

 :welc: :karma:

I can't help I'm afraid, but I'm sure if he can, Kinmel (Alan) will point you in the right direction
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

fonuser

thanks peeps but I'm only really here for these few problems lol but it does seem more stable than the linksys, just dont really wanna get rid of it as its been thru alot.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MisterW

Ok, for starters...
What IP have you got assigned to the DD_WRT box and what IP subnet is the 2700 using ?

MisterW

Right, after a spot of googling I found this nice concise setup guide
http://forums.speedguide.net/showthread.php?t=225481

Assuming your 2700 is on its default subnet ( see here http://home/xslt?PAGE=C06&THISPAGE=A02_POST&NEXTPAGE=C06 ) of 192.168.1.0, its address is 192.168.1.254 and the DHCP pool is 192.168.1.64-253.
Using the guide above then at step 4 use 192.168.1.2 as the local IP, 192.168.1.254 as the gateway and DNS.
The 2700 is often not very keen on showing ( in its devices list ) network clients with fixed IP addresses.
Sometimes pinging the device ( from the 2700 ) can make it appear. Go to the network test page on the 2700 ( http://home/xslt?PAGE=J19&THISPAGE=J19_STOP&NEXTPAGE=J19 ) and try pinging the DD_WRT box ( 192.168.1.2 if the setup above is used ).

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MisterW

Actually Rik I've just read fonuser's first post again...
QuoteI am trying to make it auth with the 'fusion' SSID but it doesnt seem to work either way.
It's probably not a good idea to use the fusion SSID. On the 2700 that's a completely separate network from the normal subnet of 192.168.1.0, and will only allow routing to/from the WAN. Turn off the fusion and try connecting to the normal SSID.

Ray

Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

fonuser

Quote from: MisterW on Apr 24, 2010, 16:52:38
Actually Rik I've just read fonuser's first post again...It's probably not a good idea to use the fusion SSID. On the 2700 that's a completely separate network from the normal subnet of 192.168.1.0, and will only allow routing to/from the WAN. Turn off the fusion and try connecting to the normal SSID.

The main reason I bought the 2700 was that it had Dual SSID so I could have my DS's connected and my computers connected but the DS's need WEP encryption which I refuse to use under normal use and thus needing to use the Fusion SSID as my primary as that cannot be changed unless you know of a method of changing the Fusion's Security. Also all my clients that connected to the Fusion got a 192.168.1.0 IP address so I can't see what is not allowing it.

Also the 2700 doesnt seem to respond to pings even though the firewall block is turned off, is there a way to making it repond?

MisterW

#12
You're right there's no way to change the encryption method on the Fusion SSID. Whenever I've used the fusion network its allocated me a 192.168.2.x address ( my 2700 is configured with a 192.168.5.0 subnet ) so I'm confused how yours allocates a 192.168.1.x . The whole idea of the fusion SSID is to keep any devices connected to it away from the main network.

A 2700 will respond to pings fine from the local network but I've never had a need to try from the WAN.

Edit: Try changing the default address of the 2700 from 192.168.1.x to something else like 192.168.3.x ( dont forget to change the DHCP range as well ) and see what happens. I must admit all the 2700's I look after ( mine, the office and 2 outworkers ) all have been changed from the defaults so maybe that makes a difference...

fonuser

thanks, I will look closer into this as it could just simply be routing issues with my dd-wrt.

fonuser

#14
just tried again and success my bridge works but kinda defeats the point as the routing isnt as it should be. the only thang I really need to be able to change is drop the fusions Protected to WEP.

So I can turn fusion protection off but not put it to wep and there's no Mac Address filtering on it, is fusion just a usless addon? this was the biggest reason for my getting this router.

MisterW

QuoteSo I can turn fusion protection off but not put it to wep and there's no Mac Address filtering on it, is fusion just a usless addon? this was the biggest reason for my getting this router.
AFAIK there is no way to change Fusion from WPA-PSK. Yes I'm afraid I don't think that the fusion facility is going to do what you wanted it for. It's not useless in general though, as I said earlier, in separates any fusion connected client from the main network. It can quite usefully be used in an office situation where you can use fusion to provide a wireless facility for visitors whilst keeping them away for your internal network.