NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6300 set to Bridge mode, which work fine, but now it set wireless to off.
Hello:
I set up my R6300 into a bridge mode, which works well on the LAN(solved my initial problem; which I wasn't able to Remote Desktop between to seperate subnets); however, when I logged into t...
> > R6300 [...]
>
> Plain/[v1] R6300 or R6300v2? Firmware version?
Still wondering.
> [...] 1. I have to connect between two buildings, [...]
If that set of gizmos acts like a long Ethernet cable (which is how
it sounds), then what you want at the second site may be a wireless
access point (instead of a full-function router or a router-as-bridge).
> [...] connected to the second router NetGear R6300.
When dealing with devices which have multiple Ethernet ports, it's
helpful to specify which port on each device is connected to which port
on the other device.
I'll assume that the radio gizmo at the main router is connected to a
LAN Ethernet port on that router, and the remote radio gizmo is
connected to the WAN/Internet Ethernet port on the second router.
> 2. It works very well, [...] two different subnets. [...]
That's what happens when you cascade two of these routers.
> [...] due to different subnets I could not remote desktop between PC1
> to PC2.
There's actually a way to make that work, but a better (simpler?) way
would be to configure the remote router as a wireless access point.
That should give you one big LAN with one subnet.
> 3. In order to solve the issue(which I did), I configured the NetGear
> R6300 in a Bridge Mode. [...]
I think that that was a fluke. "Bridge Mode" is intended to use the
remote router's wireless-network radio(s) to communicate directly with
the main router, as if it were a wireless client device, not a normal
router. As I understand it, you want to use the simulated-Ethernet
radio gizmos to connect the two routers, not their built-in
wireless-network radios.
> 5 I acomplished what I needed; however, the R6300 that is set to a
> Bridge Mode, show that the wireless is off [...]
Bridge Mode dedicates the remote router's wireless-network radio(s)
to communication with the main router, which may really be doing nothing
in this case, because the main router is too far away. A side effect of
Bridge Mode is (apparently) to disable the router's router functions,
much as would happen if you configured it as a WAP.
> So the qouestion is, when the NetGear R6300 is set to a "Bridge Mode
> (as described ablve)" can it support wireless? [...]
No. If you configure the remote R6300 as a WAP, then you should get
the desired effect. Again, the R6300-as-WAP gets stupid (no router
functions), but the wireless-network radio(s) will continue to operate
normally, supporting nearby client devices, rather than trying to link
back to the main router. (Your fancy radio gizmos will be linking the
two routers.)
If you have an R6300v2, then look in the User Manual for "Wireless
Access Point (AP)". As I read the User Manual for an R6300[v1], it
seems to lack the same one-step WAP-mode option, but there's a pretty
universal procedure which should be able to do the job:
https://community.netgear.com/t5/x/x/m-p/1463500
That's written for a Netgear C6300, but the steps are about the same for
any other router (any make/model) which lacks a one-step WAP option.
What could go wrong?
> R6300 [...]
Plain/[v1] R6300 or R6300v2? Firmware version?
> I set up my R6300 into a bridge mode, [...]
What does this "bridge" connect?
> [...] which works well on the LAN(solved my initial problem; which I
> wasn't able to Remote Desktop between to seperate subnets); [...]
A better explanation of what was connected to what how, and what's
now connected to what how, might make this less opaque.
> [...] I am quite confused why it is not broad casting the wifi signal.
"Bridge mode" on these routers normally means using the wireless
radio(s) to communicate wirelessly with a main router, rather than with
ordinary wireless client devices.
> Can I turn the wireless to on in a bridge mode?
Perhaps. Visit http://netgear.com/support , put in your model
number, and look for Documentation. Get the User Manual. Look for
"Wireless Repeating Function (WDS)". (I saw that in the User Manual for
the R6300[v1], not in that for the R6300v2.)
Thanks for looking at this issue. I'll try to be more specific:
1. I have to connect between two buildings, main building has the router (AMPLIFI) that is connected to a modem, and via "micro-antenas" radio the signal to a second building that connected to the second router NetGear R6300.
2. It works very well,meaning I have internet at both locations. But with this configuration first router 192.168.X.XXX and the other building was 192.168.Y.YYY; which are two diffrent subnets. I have a need to Remote Desktop from One PC at Building#1 (where the main router is AMLIFI) to a Server at Building#2 that is connected to the NetGear R6300-- due to different subnets I could not remote desktop between PC1 to PC2.
3. In order to solve the issue(which I did), I configured the NetGear R6300 in a Bridge Mode. (check the "Use Other Operation Mode", and Selected the "Bridge Mode" option.)
4. Set up the SSID and Password same as for the main router (AMPLIFI), and that solve the problem. Both the main router the AMPLIFI and the NetGear R6300 (that is in a bridge mode) are on the same subnet. I can remote desktop from PC1 at Building 1 and PC2 at Building 2.
5 I acomplished what I needed; however, the R6300 that is set to a Bridge Mode, show that the wireless is off (when I loged in to the settings for the NetGear R6300). Although the WiFi button on the router is clicked, and shows blue light. Also, I checked the settings for wireless and both the 2.4GHZ and 5GHZ wireless are enabled. None of my wirelss devices can connect to the NetGear R6300.
So the qouestion is, when the NetGear R6300 is set to a "Bridge Mode (as described ablve)" can it support wireless? (or at bridge mode the wireless is not available)
Thanks
> > R6300 [...]
>
> Plain/[v1] R6300 or R6300v2? Firmware version?
Still wondering.
> [...] 1. I have to connect between two buildings, [...]
If that set of gizmos acts like a long Ethernet cable (which is how
it sounds), then what you want at the second site may be a wireless
access point (instead of a full-function router or a router-as-bridge).
> [...] connected to the second router NetGear R6300.
When dealing with devices which have multiple Ethernet ports, it's
helpful to specify which port on each device is connected to which port
on the other device.
I'll assume that the radio gizmo at the main router is connected to a
LAN Ethernet port on that router, and the remote radio gizmo is
connected to the WAN/Internet Ethernet port on the second router.
> 2. It works very well, [...] two different subnets. [...]
That's what happens when you cascade two of these routers.
> [...] due to different subnets I could not remote desktop between PC1
> to PC2.
There's actually a way to make that work, but a better (simpler?) way
would be to configure the remote router as a wireless access point.
That should give you one big LAN with one subnet.
> 3. In order to solve the issue(which I did), I configured the NetGear
> R6300 in a Bridge Mode. [...]
I think that that was a fluke. "Bridge Mode" is intended to use the
remote router's wireless-network radio(s) to communicate directly with
the main router, as if it were a wireless client device, not a normal
router. As I understand it, you want to use the simulated-Ethernet
radio gizmos to connect the two routers, not their built-in
wireless-network radios.
> 5 I acomplished what I needed; however, the R6300 that is set to a
> Bridge Mode, show that the wireless is off [...]
Bridge Mode dedicates the remote router's wireless-network radio(s)
to communication with the main router, which may really be doing nothing
in this case, because the main router is too far away. A side effect of
Bridge Mode is (apparently) to disable the router's router functions,
much as would happen if you configured it as a WAP.
> So the qouestion is, when the NetGear R6300 is set to a "Bridge Mode
> (as described ablve)" can it support wireless? [...]
No. If you configure the remote R6300 as a WAP, then you should get
the desired effect. Again, the R6300-as-WAP gets stupid (no router
functions), but the wireless-network radio(s) will continue to operate
normally, supporting nearby client devices, rather than trying to link
back to the main router. (Your fancy radio gizmos will be linking the
two routers.)
If you have an R6300v2, then look in the User Manual for "Wireless
Access Point (AP)". As I read the User Manual for an R6300[v1], it
seems to lack the same one-step WAP-mode option, but there's a pretty
universal procedure which should be able to do the job:
https://community.netgear.com/t5/x/x/m-p/1463500
That's written for a Netgear C6300, but the steps are about the same for
any other router (any make/model) which lacks a one-step WAP option.
What could go wrong?Much appreciated your prompt reply:- )
So, you did answer my question in which NetGear R6300 at bridge mode does not support wireless :- (
I was looking at a WDS option, as your first reply suggested- unfortunatly, it seems that the AMPLIFI does not support it (at least I couldn't find it on the router setting itself nor any documentation from APMLIFI that show a WDS option).
I also looked at AP, but the problem is that the server does not have a wireless card (and DELL says that they'll void the warranty if I open the server for to install a wireless card). And my understanding is that AP will only support wireless. Is that right?
Worse come worse, I was thinking if I could connect a wireless extender to one of the NetGear6300 ports (like TP link), that way I could have a LAN connection to the server (as it currently set) and still have a wireless cover via a network extender of some sort. Unless, at Bridge mode that also not an option!