NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
keithamason
Jul 23, 2021Guide
Bridge Mode on AC1600 Model R6330
 I'm back to trying to configure the router as a bridge. See attached steps I took. After completing these steps, the R6300 didn't seem to function as a bridge. 
- Jul 24, 2021
I made a real "rookie" mistake during the configuraiton. I thought my home WiFi networked used WPA when in fact it was WPA-2. I had assumed the R6330 would give me an error when it didn't connected to the WiFi network and not show "Internet Staus: GOOD" on the main page. I've attached the steps used to get it configured properly for me that include screenshots.
 
antinode
Jul 23, 2021Guru
> I'm back to trying to configure the router as a bridge. [...]
For latecomers:
https://community.netgear.com/t5/x/x/m-p/2109030
> [...] After completing these steps, the R6300 didn't seem to function
> as a bridge.
   "didn't seem"?  A vague description of what does _not_ happen is less
useful than a clear description of what _does_ happen.  A vague
description of what does not _seem_ to happen is even less useful.
> Netgear config as wifi bridge.pdf
> 2. Connect to router over WiFi to default SSID
"Connect" from the Windows system?
   If my ultimate goal was to use an Ethernet connection between my
Windows system and the R6330, and to use the wireless stuff on the R6330
to communicate with some other router ("wireless bridge mode"), then I'd
start out using an Ethernet connection between my Windows system and the
R6330, and disable the wireless interface on the Windows system.
> I plugged LAN1 on the router to the computer and got the following IP
> Config.
   The main router's at "192.168.1.1"?  Your Windows system's Ethernet
interface seems to have gotten a valid IPv4 configuration from it (using
DHCP, I assume), which suggests that it's able to communicate with that
main router.
ping 192.168.1.1
> [...] the computer connected to the Netgear router can't get to the
> internet.
   "can't" is not a useful problem description.  It does not say what
you did.  It does not say what happened when you did it.  As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
   You seem to have the Ethernet interface on the Windows system active
at "192.168.1.3", and its wireless adapter active at "192.168.1.2".
Multiple active interfaces on the same subnet might cause some
confusion (for the computer as well as for me).  If you're trying to use
the R6330 as a wireless bridge, then why have the wireless interface on
the Windows system active?