- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
access point R6250
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
access point R6250
The netgear site is not to clear on how to use an R6250 as an access point on an already established network with a router.
I have done the following:
network is 192.168.0.x
main gateway is 192.168.0.1
I have configured the R6250 for address 0.199 and set the dns (since my router is not set up to do DNS) to the range of 150-175.
I have configured access point mode.
Enabled fixed ip settings
192.168.0.199
255.255.255.0
gateway 162.168.0.1
primary and secondary dns are set to 8.8.8.8 Like all the other computers on the network.
I can connect to the router main pages from a computer on the network.
I can connect to the router main pages from my phone.
I have updated the firmware to V1.0.4.38_10.1.30 from the old version, so I know that the 6250 can get to the internet.
I can connect via an IP address from my phone, but
It gives me a "this site can't be reached"
dns_probe_finished_bad_config when I attempt to browse from my phone.
I have tried this with the netword connected to both the LAN and WAN ports.
In wireless AP mode a lot of the stuff is grayed out.
I suspect it is user error here.
My network does not use DHCP explicitly for security. This access point will be going onto another network later, but I need to get it working on this one, so that I know it will work.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: access point R6250
> access point R6250
R6250 or R6250v2? Look for "Model" on the product label.
> The netgear site is not to[o] clear [...]
"The netgear site" is either very vague or very big or both. Which
part of what, exactly, have you been viewing?
For more/different documentation, visit http://netgear.com/support ,
put in your (actual) model number, and look for Documentation. Get the
User Manual (at least).
> I have configured the R6250 for address 0.199 [...]
Which "address"? LAN? A router (configured as a router) has one
address for its LAN interface, and one for its WAN/Internet interface.
> [...] and set the dns (since my router is not set up to do DNS) to the
> range of 150-175.
"DNS" or DHCP? A wireless access point seldom deals directly with
either.
You might create less ambiguity and cause less confusion if you
identified the place on the R6250 management web site, rather than what
you think it means. For example: ADVANCED > Setup > LAN Setup : Use
Router as DHCP Server, and so on. (Copy+paste seldom changes "DHCP" to
"DNS".)
Most likely, you'll want to enable a DHCP server on your
(unspecified) "a router".
> I have configured access point mode.
Advanced > Advanced Setup > Wireless AP?
I'd expect that to disable its DHCP server. Hence, most likely,
you'll want to enable a DHCP server on your (unspecified) "a router".
> gateway 162.168.0.1
"192.168.0.1"?
> primary and secondary dns are set to 8.8.8.8 Like all the other
> computers on the network.
I'd expect that to be harmless, but I doubt that anyone will care.
> I can connect to the router main pages from a computer on the network.
That's be a computer with static IP parameters? (Because I don't see
a DHCP server in your scheme.)
> I suspect it is user error here.
I agree.
> My network does not use DHCP explicitly for security. [...]
It's not clear to me how that means achieves that end. It _is_ clear
to me how not having a DHCP server can cause problems.
> [...] This access point will be going onto another network later, but
> I need to get it working on this one, so that I know it will work.
Then I'd suggest that you enable a DHCP server on your LAN. And a
Netgear router configured as a WAP won't do that job.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: access point R6250
@antinode wrote:> access point R6250
R6250 or R6250v2?
>>Which part of what, exactly, have you been viewing?
The part that tells you how to configure an access port.
https://kb.netgear.com/20927/How-do-I-change-my-NETGEAR-router-to-AP-mode-after-setting-it-up
"
- Scroll down to the AP Mode section and select Enable AP Mode.
The Get IP Address Dynamically and Get DNS Server Address Dynamically options are configured automatically by default. To manually assign an IP address to your router, contact your ISP for the IP information.
Note: We recommend that you assign a static IP address to your NETGEAR router (AP) so that your its IP address does not change. For more information, see How do I enter a static IP address on a NETGEAR router?."
This is not connecting to an isp. I am not configuring a router. I am trying to use an RN6250 AS an ACCESS POINT on an
existing network, that has a gateway located at 192.168.0..1
This does not address that type of configuration.
Which "address"? LAN? A router (configured as a router) has one
address for its LAN interface, and one for its WAN/Internet interface.
THE LAN ADDRESS.
I can do a scan of my network and see the device at 0.199, and log into it IF IT IS PLUGGED INTO *ONE* of the lan ports. With wifi enabled, my phones can connect to it, but they do not have internet access because DNS fails. IF I connect it to the WAN port, then do a netscan, I do not see it, which is the behavior I would expect. However in that case, I can still log into 192.168.0.199 from the cell phone that is connected to the RN6250.
"DNS" or DHCP? A wireless access point seldom deals directly with
either.
DHCP. When enabled on the R6250, in non access point mode, my android phones get an ip address. I enabled DHCP with a range of 150-175 so they won't conflict with other hard coded addresses.
Most likely, you'll want to enable a DHCP server on your
(unspecified) "a router".That is a Cybergear router, and I do not want to enable DHCP on it. I use hardwired IP addresses for a reason.
That router lives at 192.168.0.1
When I set up a windows box, I give it an fixed IP address and set it's gateway to 192.168.0.1 and the dns on the windows box
to 8.8.8.8 and 4.4.4.4 And I can get to the internet just fine.
I want the same ability for my wireless devices.
I have a fixed address of 0.199 for the RN6250.
I want to configure it to do the following:
1. Provide a way for a cell phone to connect to my network, and have the RN6250 give out addresses for the wireless connections, but not the lan connections.
Advanced > Advanced Setup > Wireless AP?
I'd expect that to disable its DHCP server. Hence, most likely,
you'll want to enable a DHCP server on your (unspecified) "a router"Actually, it seems to work:
> I can connect to the router main pages from a computer on the network.
That's be a computer with static IP parameters? (Because I don't see
a DHCP server in your scheme.)
Correct. 0.49 is a windows box with a hard coded address.
I can plug the RN6250 onto my network switch, and connect the wire to one of the 4 lan ports.
In that configuration, with the RN6250, I can browse to 192.168.0.199 from my 0.49 box.
I can connect a cell phone to the wifi at that point, and can browse to 192.168.0.199 from it. If I try browsing to
168.96.159.118 (i.e. mail.realtime.net) I get host unreachable.
Yet from my 0.49 box I can get there.
So what I need help with is configuring this RN6250 to do the following:
1. have a static IP on my network
2. allow a cell phone to connect to it, and have the RN6250 give it an IP address.
3. be able to browse the internet from the phone.
given:
I have a router at 192.168.0.1 that acts as my gateway for all other nodes on my network.
> My network does not use DHCP explicitly for security. [...]
It's not clear to me how that means achieves that end. It _is_ clear
to me how not having a DHCP server can cause problems.
I do not want someone being able to bring a computer into the facility, plug it in and have access automatically, as they would if DHCP were enabled. Right now, I am trying to make sure I can make this R6250 function as an access point.
I will be taking it to a place and connecting it to a network that DOES have a DHCP server on it, so I will have to test that configuration there.
> [...] This access point will be going onto another network later, but
> I need to get it working on this one, so that I know it will work.
Then I'd suggest that you enable a DHCP server on your LAN. And a
Netgear router configured as a WAP won't do that job.It actually does, but it does not resolve DNS requests.... see below:
hmmm..... lets see....
I go into the start page on the Rn6250 and it says internet is not connected. It shows 5 devices connected.
the main gateway at 0.1
to machines at 0.11, 0.49
2 wireless devices at 0.151 and 0.150
Advanced setup says router information ip address 192.168.0.199 DHCP on.
Wireles settings 2.4 ghz shows the SSID, Wireless AP set to on, and the 5 GHZ wireless settings show Wireless AP set to on.
The internet port is all nulls.
Under advanced setings Wireless settings has router PIN enabled.
Wireless AP does NOT have AP mode enabled, though the main status page does show it enabled for both of the WIFI interfaces.
So with that configuration, how do I tell the RN6250 to send packets out the gateway?
NOW: If I unplug the cable from the lan port on the RN6250 and plug it into the wan port, a netscan does show it, and the phone connected to it. And that is as it should be. I have access to 192.168.0.199 from the connected cell phone.
So if I use that configuration and enable WAP, with a fixed address, set to 192.168.0.199, netmask 255.255.255.0, gateway 192.168.0.1 and dns 8.8.8.8 aand 4.4.4.4 (both google). and hit apply, the router restarts properly, and when I do a netscan on my network it does show up, and the wire is still attached to the WAN port. But at that point, the cell phones connected to it just get a no internet signal. If I connect to the wifi at this point with another phone it takes a long time to get an IP address but it does, and it obtains an address of 0.151 which actually should have been 150, but it is in the valid range. And now that address shows up in the wireless devices. I have tried connecting a second phone and it fails to connect and get an IP address.
A netscan on the hard network shows 0.199 and 1.151
The phone that did connect and get an IP address, can connect to a web site via a direct IP address i.e. 192.96.159.118 , but not with an URL (mail.realtime.net). This indicates that the access point is forwarding packets to and from the gateway, but that DNS is not working for the phone. When the phone attempts a dns resolve, it comes back with DNS_PROBE_FINISHED_BAD_CONFIG.
So the WAP is working, but not supplying a DNS server to the phone most likely.
Unfortunately, the one phone that I NEED to connect with doesn't see, to be able to connect to the R6250...
From the hard network, I can log into the router, and it says internet status GOOD. Attached devices 4, and lists 0.1, 0.11,0.49 and the mac address and ip address of the wireless phone that did connect. unfortunately I can't attach the router config here.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: access point R6250
> R6250 or R6250v2? Look for "Model" on the product label.
Still wondering.
> For more/different documentation, visit http://netgear.com/support ,
> put in your (actual) model number, and look for Documentation. Get the
> User Manual (at least).
Did you? (Which Model?)
> https://kb.netgear.com/20927/
I'd suggest the User Manual. In fact, I _did_ suggest the User
Manual.
> [...] I am trying to use an RN6250 AS an ACCESS POINT on an
> existing network, that has a gateway located at 192.168.0..1 [...]
Fine. I got that. I suggested consulting a better set of
instructions than what you say you used. You don't seem to have done
that.
> [...] IF IT IS PLUGGED INTO *ONE* of the lan ports. [...]
Again, I'd suggest following the documented procedure.
> [...] IF I connect it to the WAN port, then do a netscan, I do not see
> it, which is the behavior I would expect. [...]
Again, I'd suggest following the documented procedure. The results
might be different.
> That is a Cybergear router, and I do not want to enable DHCP on it. I
> use hardwired IP addresses for a reason.
I did ask why. Still wondering.
> That router lives at 192.168.0.1
I got that, too.
If you use the the documented procedure, then the DHCP server in the
R6250[vX] will be disabled. If you insist on using the DHCP server in
the R6250[vX], then you'll need to use the old/ad-hoc WAP scheme. See,
for example:
https://community.netgear.com/t5/x/x/m-p/1463500
That's written for a Netgear C6300-as-WAP, but the steps are about the
same for any other router (any make/model) which lacks a one-step WAP
option. And leave the WAN/Internet Ethernet port on the R6250
unconnected.
You might see some odd (but minor?) problems that way, like, say, the
Internet LED might not look right, or the R6250 can't find a time
server, so its date+time might be wrong. Anything where the R6250 wants
to access the Internet (firmware updates, ...) could fail.
Those instructions include disabling the DHCP server on the
router-as-WAP. You can try _not_ doing that, but it's not immediately
obvious (to me) how the DHCP server in the router-as-WAP will get its
data (gateway, DNS servers, ...).
> [...] I do not want someone being able to bring a computer into the
> facility, plug it in and have access automatically, as they would if
> DHCP were enabled. [...]
Configure the DHCP server more carefully? I know nothing about that
router, but I'd look for a way to use reserved addresses for approved
devices, and shrink the pool to vanishingly small.
> Most likely, you'll want to enable a DHCP server on your
> (unspecified) "a router".
Still true. You can try to do this the hard way, and get into a
fight at every step, or you can take the easy way, and make it work.
> I will be taking it to a place and connecting it to a network that
> DOES have a DHCP server on it, [...]
Perhaps _I_'m stupid, but if the ultimate goal is to use the R6250 as
a WAP which is configured normally, in a normal (with-DHCP) environment,
then wouldn't a normally-configured (with-DHCP) test environment be more
realistic? Even if you do get it to work in your no-DHCP environment,
you'll need to reconfigure it _differently_ to make it work in the
target (with-DHCP) environment. Where's the sense in that?
And, it's only a test. Even if a working DHCP server _were_ a
secutity problem, which I dispute, how long would you need to leave it
enabled to run your (realistic) tests?
You seem to have decided to use a boat to cross a river, but it's
winter, and the river's frozen over. You might be able to find a way to
get that boat across, but just walking would be much easier. Especially
when you don't want the boat on the far bank.
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more