Default Gateway not transmitting to wireless clients

Our organization is using a Linksys BEFW11S4 router, and for the most part, everything is working correctly. However, ipconfig /all on the clients does not show a default gateway for the wireless machines. I can not find anywhere in the router web-page that will let me configure this.
What am I missing here?
Thanks,
Dennis

Hi
ipconfig /all is show the ip address and what is it?
Ok,verify option in router DHCP ->enable.
Authentication(WAP,WEP),SSID name, I dont know the settings of the router.
Just se the DHCP section,enable it and configure the subnet masks of the clients .
Thanks
Kind Regards
ing.George Gochev
DSL and Telecommunications Engineer

Similar Messages

Bridge does not work for wireless clients - connecting to existing network.

Hi - I really hope somebody can help out here, after hours of trial & error, I have finally given up
I need to connect my Airport Extreme Base Station to my existing network. I have a linksys router (192.168.15.1) connected to my modem and this linksys router acts as DHCP server too.
I suppose I have to use "bridge mode" for that to work. But should the linksys be connected to the AEBS using the AEBS's WAN or LAN port?
If I use "bridge mode", then wired computers to the AEBS works fine - getting an IP from the linksys etc. BUT, the wireless clients will have a self-assigned IP and not get through to the internet. It's like the AEBS will not allow wireless clients to "get through" unless AEBS itself is handing out IP addresses.
Page 36 of this manual ( http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf ) shows the setup I want. But in the picture, it says "Ethernet WAN port" but the text says: "The Apple wireless device (in this example, a Time Capsule) uses your Ethernet network to communicate with the Internet through the Ethernet LAN port ( <--> )." I don't know which one to use, WAN or LAN - they show WAN but say LAN?
When I set it up as "share an IP address", the AEBS status tells me "double nat" and to change from "shared IP" to "bridge mode". I do that, and everything seems fine - for the wired clients. Now the wireless clients cannot connect, Airport on the MacBook Pro just say "Connection failed" and the MacBook says "Invalid password" (translated from danish), even though I set the Airport Utlity to save the password in keyring, so it should be correct... If I disable wireless encryption, the wireless clients will connect but get a self-assigned IP, and therefor not work (cannot get online)...
It seems the only way I can get wireless to work, is if I set AEBS up as DHCP, but then it won't be on the "same network" as the linksys (192.168.15.1), but rather on 10.0.x.x as I select. If I select 192.168.x.x within AEBS, I'm also getting some error messages, conflict/subnet thing.
Anyway - I really hope somebody knows how to get wireless clients to get an IP address from existing ethernet when connected to the AEBS.
Thanks!!

I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

Cisco WAP4410N - not configurable as Wireless Client with WRT610N?

Hi!
On several workstations I use multiple network to
1 - access Internet and share Printers
2 - communicate within the local area
The second WLAN I need for several NDAS devices.
Due to their own LPX-Protocol these NDAS devices don't work properly with MAC address cloning. In combination with several access points or clients from other manufacturers Wireless N transmission does not work.
So in WLAN 2 I use the Cisco Linksys WRT 610N Router with 2.4 Ghz WLAN.
I intended to use the Cisco WAP4410N in Client Mode to connect a workstation with this router and set up NDAS connection.
Other workstations will directly connect to the router via Cisco Linksys WUSB-600N.
The connection from WUSB-600N to WRT610N works perfectly.
My problem is:
The WAP4410N does not connect to a wireless Network in Client Mode.
(It is not a problem of Channel configuration, Security or Signal strength - because if I connect my workstation via WUSB-600 this works instantly.)
If setup as an access Point it will start up sending competing to my router.
In Network Status it shows no received packages.
In Wireless Client/Repeater Mode there is no connection either.
My question is:
Is the WAP4410N not designed to be used as a Wireless Client?
An if it was - how is it to be set up as one?
Thanks
ando_user

Hi!
On several workstations I use multiple network to
1 - access Internet and share Printers
2 - communicate within the local area
The second WLAN I need for several NDAS devices.
Due to their own LPX-Protocol these NDAS devices don't work properly with MAC address cloning. In combination with several access points or clients from other manufacturers Wireless N transmission does not work.
So in WLAN 2 I use the Cisco Linksys WRT 610N Router with 2.4 Ghz WLAN.
I intended to use the Cisco WAP4410N in Client Mode to connect a workstation with this router and set up NDAS connection.
Other workstations will directly connect to the router via Cisco Linksys WUSB-600N.
The connection from WUSB-600N to WRT610N works perfectly.
My problem is:
The WAP4410N does not connect to a wireless Network in Client Mode.
(It is not a problem of Channel configuration, Security or Signal strength - because if I connect my workstation via WUSB-600 this works instantly.)
If setup as an access Point it will start up sending competing to my router.
In Network Status it shows no received packages.
In Wireless Client/Repeater Mode there is no connection either.
My question is:
Is the WAP4410N not designed to be used as a Wireless Client?
An if it was - how is it to be set up as one?
Thanks
ando_user

Wireless Acess Point not transmitting to wireless devices

I had to move my WAP to another location about 200ft from the Gateway (NVG589). After the move the STB/TV connected properly and works fine. This WAP is connected by an in-ground CAT5 cable directly to the Gateway. I also connected another wireless STB directly to the gateway with CAT5, and the Wireless STB/TV connected to it also works correctly.
However, now my wireless devices (iPad, iPod, etc) do not connect to the WAP. As long as I'm relatively close to the gateway, my network is available and the wireless devices work fine. However, they do not even show the network when near the WAP.
I had planned on placing a second router (in WAP mode) near the gateway to strengthen the signal in the house' but wanted to make sure this worked first. (It didn't) Any suggestions would be appreciated...

Install your second router to where you placed the WAP for wifi signal in that area. Relocate the WAP close to your wireless set top boxes. If your set top boxes are close to an ethernet connection, you could disconnect the WAP altogether since it won't be needed.

Dhcp: default gateway not added if ip and gateway in different subnets

Hi! Help needed with Arch's DHCP client. (dhcpcd)
Assume that ISP leased ip 78.37.180.62/24 and gateway 78.37.0.1
On my home router when you plug cable, routing table is like this:
Destination Gateway Genmask Flags Metric Ref Use Iface
78.37.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
78.37.180.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
0.0.0.0 78.37.0.1 0.0.0.0 UG 202 0 0 eth0
But on Arch it's much tinyer:
78.37.180.0 * 255.255.255.0 U 202 0 0 eth0
And no internet for me.
I've read that before adding a gateway you need to add a route to that gateway or you get an error: SIOCADDRT: No such process.
I believe this very error is what Arch's dhcp cliet gets when it tries to add the gateway.
Funny thing is if you manually add the route to the gateway, the gateway is auto-added in 5-10 sec.
# route add 78.37.0.1/32 dev eth0
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
78.37.0.1 * 255.255.255.255 UH 0 0 0 eth0
78.37.180.0 * 255.255.255.0 U 202 0 0 eth0
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
78.37.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
78.37.180.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
0.0.0.0 78.37.0.1 0.0.0.0 UG 202 0 0 eth0
Where to dig? Are the routes added by some script that can be modified?
Last edited by leniviy (2009-05-23 20:22:52)

also, until correct route is added, someone keeps logging to daemon.log:
May 23 21:27:22 IL dhcpcd: eth0: add_route: No such process
May 23 22:33:05 IL dhcpcd: eth0: send_raw_packet: Network is down
May 23 22:34:54 IL dhcpcd: eth0: add_route: No such process
May 23 22:35:09 IL dhcpcd: eth0: add_route: No such process
May 23 22:35:24 IL dhcpcd: eth0: add_route: No such process
May 23 22:35:39 IL dhcpcd: eth0: add_route: No such process
May 23 22:35:54 IL dhcpcd: eth0: add_route: No such process
May 23 22:36:09 IL dhcpcd: eth0: add_route: No such process
May 23 22:36:24 IL dhcpcd: eth0: add_route: No such process

Flexconnect AP(Local Switching) Wireless clients are not able communicate eachother

Hi,
Scenario : We are deployed the WLC in Corparate Office and Access Points are placed in Branch Office with FlexConnect Local Switching mode.
In this case, I am not able to Ping the Wireless clients eachother . Peer to Peer Block Option also Disabled.
Some time Wireless clients Ping eachother & some times not. Both Wireless clients are associated with Same AP & Same WLAN SSID.
Please help me urgent ..
Devices :
1)WLC 2500 series , Software 7.2
2)Cisco 1400 series APs
3)CISCO ACS server for AAA authentication
Regards,
Shanmugam Nachimuthu

Hi Shanmugam,
Please apply following steps to configure P2P setting for WLAN:
Step 1 Choose WLANs to open the WLANs page.
Step 2 Click the ID number of the WLAN for which you want to configure peer-to-peer blocking.
Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
Step 4 Choose one of the following options from the P2P Blocking drop-down list:
• Disabled — Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.
NOTE: Traffic is never bridged across VLANs in the controller.
• Drop—Causes the controller to discard the packets.
• Forward - Upstream — causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.
NOTE: To enable peer-to-peer blocking on a WLAN configured for FlexConnect local switching, select Drop from the P2P Blocking drop-down list and select the FlexConnect Local Switching check box.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Thanks,
Prashant Gondaliya

Loss of default gateway - to auto-shutdown radio

Hi,
I need a solution where, if an access point looses its connection to its default gateway, that it automatically shuts the radio down. And when the default gateway is again available, the radio is automatically turned on again. By connection, I do not just mean that the AP FastEthernet port link status changes.
Some kind of functionality like the 'track rtr reachability' that probes the default gateway, and takes action if the default gateway cannot be reached.
How to, if at all possible...
Problem is that wireless equipment will connect to the access point if the radio is up but the access point does not have access to its default gateway (for some error reason other than the local Ethernet link, but also that...)
Thanks
Johnny

Hi,
unfortunately that does not solve this problem:
Router (def. gw for WAP)
Switch 1
Switch 2
Wireless Access Point (WAP)
If switch 1 is down or if the link from switch 1 to the router is down, then the WAP radio will still be up. I need for it to handle a loss to its default gateway, not just its local ethernet wire.
Tx
Johnny

What does the number after my wireless client name mean

I have an airport express and have set up my network properly. Just recently I have noticed that there is a number (sometimes in parentheses, sometimes not) after the wireless client name when I look at my network with my airport utility. What does this number stand for and why does it keep changing?

This is a known bug in Yosemite.
On your Yosemite Macs.......
Open System Preferences (gear icon on the dock)
Open Sharing
Edit the name of the Mac to what you want
Things may be OK for a day or two, but the (2), (3), (4), etc will come back to visit until we get a fix from Apple
I don't have an AppleTV here to check, but you can probably change the name in the settings for the AppleTV.

WLC cannot get IP of the Wireless Clients and client not able to ping to the gateway

Dear Cisco Expertise,
I have configured WLC embedded in Cisco C3650 switch and also 1 unit AP3702I. AP now able to join to the controller. My client able to connect to the AP and get the IP address (10.127.117.1) from the DHCP server but unable to ping to the gateway (10.127.117.254 - interface gateway). Both switch and AP able to ping to the interface gateway. I also trying to ping to the client from the switch and also from the AP to the client but not able to ping.
I've check via switch can see the client's IP address and MAC address (using ARP)
#sh arp vlan 77
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.127.117.1 0 843a.4b90.17e0 ARPA Vlan77
Internet 10.127.117.254 - 3c08.f6b7.2173 ARPA Vlan77
Need your expertise on this matter. Thank you.
Configuration as below:
Switch
ip dhcp pool LWAPP_VLAN
network 10.127.117.0 255.255.255.0
default-router 10.127.117.254
dns-server 10.127.113.10
domain-name xxx.com
vlan 77
name LWAP_VLAN
interface Vlan10
ip address 10.127.112.254 255.255.255.128
interface Vlan77
ip address 10.127.117.254 255.255.255.0
ip helper-address 10.127.117.254
interface GigabitEthernet3/0/5
description Connect to AP Test
switchport access vlan 10
switchport mode access
no logging event link-status
wireless mobility controller
wireless management interface Vlan10
wireless security web-auth retries 5
wireless mgmt-via-wireless
wlan APAC-WLAN 2 Wifi-Test
client vlan LWAP_VLAN
ip dhcp opt82
ip dhcp opt82 ascii
ip dhcp opt82 format add-ssid
ip dhcp required
ip dhcp server 10.127.117.254
no security wpa akm dot1x
security wpa akm psk set-key ascii 0 B*MY2014
security wpa wpa2 ciphers tkip
session-timeout 300
no shutdown
ap group APGroup-Test
description "For Testing Purposes"
wlan APAC-WLAN
vlan LWAP_VLAN
AP
interface Dot11Radio0
antenna gain 0
stbc
mbssid
power client local
packet retries 64 drop-packet
station-role root
interface Dot11Radio1
antenna gain 0
stbc
mbssid
power client local
packet retries 64 drop-packet
station-role root
interface GigabitEthernet0
duplex auto
speed auto
interface GigabitEthernet0.1
encapsulation dot1Q 1 native
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface BVI1
mtu 1792
ip address 10.127.112.202 255.255.255.128
interface Virtual-WLAN0
ip default-gateway 10.127.112.254
ip forward-protocol nd
ip dns server

Pls try the below SSID configuration. WPA2 to be configured with AES & not TKIP.
wlan APAC-WLAN 2 Wifi-Test
client vlan LWAP_VLAN
security wpa
no security wpa akm dot1x
security wpa wpa2 ciphers aes
security wpa akm psk set-key ascii 0 B*MY2014
ip dhcp required
no shutdown
This post should give you some help as well
http://mrncciew.com/2013/12/04/wlan-config-in-3850-part-1/
HTH
Rasika
**** Pls rate all useful responses ****

Wireless clients not trusting well-known Certificate Authorities by default??

I'm using PEAP-MSCHAPv2 for wireless authentication. The radius server is a Windows 2008 server running NPS. The clients consist of a bunch of laptops (mostly running Windows). Not all of these laptops are members of Active Directory. So, pushing any type of policy out to all clients isn't feasible (ie. using a private PKI and using AD to push the server cert and wireless config to all domain members). So we decided to use a public PKI and obtained a certificate for our radius server through a well known CA. So far, so good.
When clients to go connect, they still get a nasty warning saying:
--START--
The credentials provided by the server could not be validated. We recommend that you terminate the connection and contact your administrator with the information provided in the details. You may still connect but doing so exposes you to security risk by a possible rogue server.
Details
Radius Server: $radius
Root CA: $ca
The server "$radius" presented a valid certificate issued by "$ca", but "$ca" is not configured as a valid trust anchor for this profile. Further, the server "$radius" is not configured as a valid NPS server to connect to for this profile.
--STOP--
(I replaced the actual radius server name with $radius and the CA with $ca).
Doing a little digging, it appears this is just the expected behavior of the Windows wireless client??? What's the point of getting a signed cert by a well-known CA if the client is still going to get a nasty warning like this?
Web browsers certainly don't behave like this. The only difference between a web browser and the wireless client is with a browser, you're always going after a URL (ie, you can match what the browser wants to connect to versus what the CN on the server's cert comes back with) whereas on the wireless client, you generally won't know the radius server you're going to authenticate against. But, in either scenario, the server's cert is signed by a well known CA.
I found a nice post that mentions this, but no solution:
http://social.technet.microsoft.com/Forums/en/winserverNIS/thread/26886f09-e424-48da-9ecc-cf7efd9dccc0
Well, I suppose a solution is to manually configure the client to trust certs issued by the CA and/or configure my radius server in the connection profile. But that requires configuring each client. And there's no way we can use AD to push a policy/cert to all clients.
So my questions are:
-is this really the expected behavior?
-so browsers generally trust the default CAs whose certs are stored on the OS by default but the wireless adapters don't?

This is a limitation of the Windows wireless client.
http://support.microsoft.com/kb/2518158
Somewhere was an artical the described that Microsoft wirless client does not trust public root CAs by default. Using a 3rd party utility like Intel Pro Set trusts all the 3rd party root CAs by default so you dont get this message.
Please respond to Microsoft and voice your problem maybe they will fix their wireless client to trust public root CAs.
Justin.

The Default Gateway Is Not Available / Problem

Hello, I recently purchased this HP Pavileon laptop, and I've been encountering this problem very often (every 2-10 minutes). This problem is getting extremely frustrating as absolutely nobody has been able to provide a fix for this issue.
When the laptop is on battery mode (this does not happen when plugged in); I commonly get disconnected from my wi-fi connection and to fix it, I must run the troubleshooter. This temporarily fixes the issue by resetting the wi-fi adapter.
What I have tried and has not worked:
* Turn off to save power option in the driver settings (in Device Manager) untickets
* Updated drivers
* New power plan
* Tried different drivers
* Complete system restore
The wireless adapter is Realtek RTL 8188EE. Upon running the troubleshooter, this is all the information from the detailed information section:
Windows Network Diagnostics
Publisher details
Issues foundThe default gateway is not available
The default gateway is not availableThe default gateway is a device that connects a local network or computer to the Internet. A broadband modem or router is usually the default gateway.
Fixed
Reset the "WiFi" adapter
Completed
Investigate router or broadband modem issues
Not run
Issues found
Detection details
6The default gateway is not availableFixed
The default gateway is a device that connects a local network or computer to the Internet. A broadband modem or router is usually the default gateway.
Reset the "WiFi" adapterCompleted
This can sometimes resolve an intermittent problem.
Network Diagnostics LogFile Name: 2D0FE1F0-C2C2-43B5-A857-2D2B3C4B8A51.Repair.1.etl Investigate router or broadband modem issuesNot run
If you're connected to a hotspot or domain network, contact the network administrator. Otherwise: 1. Unplug or turn off the device. 2. Once all the lights on the device are off, wait at least 10 seconds. 3. Turn the device on or plug it back in to the power outlet. To restart a router or modem that has a built-in battery, press and quickly release the Reset button.
Detection details
Diagnostics Information (Network Adapter)
Details about network adapter diagnosis:
Network adapter WiFi driver information:
Description . . . . . . . . . . : Realtek RTL8188EE 802.11b/g/n Wi-Fi Adapter
Manufacturer . . . . . . . . . : Realtek Semiconductor Corp.
Provider . . . . . . . . . . . : Realtek Semiconductor Corp.
Version . . . . . . . . . . . : 2012.2.827.2013
Inf File Name . . . . . . . . . : C:\WINDOWS\INF\oem8.inf
Inf File Date . . . . . . . . . : 12 September 2013 10:17:00
Section Name . . . . . . . . . : HP8188ee.ndi
Hardware ID . . . . . . . . . . : pci\ven_10ec&dev_8179&subsys_197d103c
Instance Status Flags . . . . . : 0x180200a
Device Manager Status Code . . : 0
IfType . . . . . . . . . . . . : 71
Physical Media Type . . . . . . : 9
Diagnostics Information (Wireless Connectivity)
Details about wireless connectivity diagnosis:
Information for connection being diagnosed
Interface GUID: 7c04789b-0b43-472c-abd6-a84cb31e9053
Interface name: Realtek RTL8188EE 802.11b/g/n Wi-Fi Adapter
Interface type: Native WiFi
Connection incident diagnosed
Auto Configuration ID: 1
Connection ID: 1
Connection status summary
Connection started at: 2014-07-24 04:19:49-759
Profile match: Success
Pre-Association: Success
Association: Success
Security and Authentication: Success
List of visible access point(s): 0 item(s) total, 0 item(s) displayed
Connection History
Information for Auto Configuration ID 1
List of visible networks: 1 item(s) total, 1 item(s) displayed
BSS Type PHY Security Signal(RSSI) Compatible SSID
Infra <unknown> Yes 100 Yes Matt
List of preferred networks: 1 item(s)
Profile: Matt
SSID: Matt
SSID length: 4
Connection mode: Infra
Security: Yes
Set by group policy: No
Connect even if network is not broadcasting: No
Connectable: Yes
Information for Connection ID 1
Connection started at: 2014-07-24 04:19:49-759
Auto Configuration ID: 1
Profile: Matt
SSID: Matt
SSID length: 4
Connection mode: Infra
Security: Yes
Pre-Association and Association
Connectivity settings provided by hardware manufacturer (IHV): No
Security settings provided by hardware manufacturer (IHV): No
Profile matches network requirements: Success
Pre-association status: Success
Association status: Success
Last AP: 98-fc-11-88-61-b8
Security and Authentication
Configured security type: WPA2-PSK
Configured encryption type: CCMP(AES)
802.1X protocol: No
Key exchange initiated: Yes
Unicast key received: Yes
Multicast key received: Yes
Number of security packets received: 0
Number of security packets sent: 0
Security attempt status: Success
Connectivity
Packet statistics
Ndis Rx: 34302
Ndis Tx: 32619
Unicast decrypt success: 0
Multicast decrypt success: 0
Unicast decrypt failure: 0
Multicast decrypt failure: 0
Rx success: 0
Rx failure: 0
Tx success: 0
Tx failure: 0
Tx retry: 0
Tx multiple retry: 0
Tx max lifetime exceeded: 0
Tx ACK failure: 0
Roaming history: 0 item(s)
Diagnostics Information (Wireless Connectivity)
Details about wireless connectivity diagnosis:
For complete information about this session see the wireless connectivity information event.
Helper Class: Auto Configuration
Initialise status: Success
Information for connection being diagnosed
Interface GUID: 7c04789b-0b43-472c-abd6-a84cb31e9053
Interface name: Realtek RTL8188EE 802.11b/g/n Wi-Fi Adapter
Interface type: Native WiFi
Result of diagnosis: There may be problem
Diagnostics Information (Wireless Network Adapter)
Details about wireless network adapter diagnosis:
For complete information about this session see the wireless connectivity information event.
Helper Class: Native WiFi MSM
Initialise status: Success
Information for connection being diagnosed
Interface GUID: 7c04789b-0b43-472c-abd6-a84cb31e9053
Interface name: Realtek RTL8188EE 802.11b/g/n Wi-Fi Adapter
Interface type: Native WiFi
Profile: Matt
SSID: Matt
SSID length: 4
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: There may be problem
Network Diagnostics LogFile Name: 2D0FE1F0-C2C2-43B5-A857-2D2B3C4B8A51.Diagnose.0.etl
Other Networking Configuration and LogsFile Name: NetworkConfiguration.cab Collection information Computer Name: LAPTOP Windows Version:6.3Architecture:x64Time:24 July 2014 04:34:47
Windows Network Diagnostics Detects problems with network connectivity. Package Version:1.0Publisher:Microsoft Windows

Run the HP Support Asssitant's Tune up application. There should be a new BIOS available. sp66866
Have you installed the latest Windows 8.1 updates?
Do not install optional video graphics updates.
I was runnning into a similar problem with my HP product loan Envy Spectre 13 TouchSmart Ultrabook until I did the updates. I had upgraded my wireless router to a model with 802.11AC specification.
Invoke the Device Manager and ensure that the box next to Allow this computer to turn off this device to save power is unchecked.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

How get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?

Hi,
I have a RVS4000 router with DHCP enabled and in router mode.
The LAN is 192.168.2.x. The RVS4000 static IP address is 192.168.2.8
The router is not the RVS4000 and is at 192.168.2.1
The RVS4000 dhcp is assigning it's clients a default gateway of 192.168.2.8 instead of what I want 192.168.2.1.
How can I get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?
Thanks

Hi Gail, you cannot do this. The router, as the DHCP server will only assign a default gateway of what IP interface the DHCP server runs on. If you have the default IP, the gateway is 192.168.1.1. If you create a second vlan, by default it would be 192.168.2.1.
There are not configuration options for the built-in DHCP server. If you'd like to expand this functionality, you would need an external dhcp server.
-Tom
Please mark answered for helpful posts

Incorrect Default Gateway for Clients using a Concentrator

Hey all,
Hopfully an easy one - I'm trying to configure a VPN Concentrator for use with the old VPN Client for an IPSec CVPN.
The clients connect fine, but they are getting the incorrect default gateway during the address assignment.
My address pool is 192.168.0.128/25. The client correctly picks up the first address in the range, 192.168.0.129, but the default gateway for the VPN adapter is assigned as the next address in the range, 192.168.0.130.
I need the gateway address to be 192.168.0.254 (the SVI of the L3 switch connected to the Concentrator), but I can't for the life of me fine a configuration option anywhere in the pool assignment. I've set the tunnel default gateway to this 192.168.0.254, but this makes no difference.
Any ideas where I can find this config option?
Thanks!

Andrew
In the chart that you posted about the routing setup it refers to a DMZ network and DMZ gateway. Can you clarify what these are since I do not see them in the drawing that is in that post?
I agree with Herbert that it is cleaner to have the address pool on the concentrator use addresses that do not overlap with the concentrator subnet connecting to the layer 3 switch. And as long as the layer 3 switch has a route to that address pool, and the next hop in the route is the address of the concentrator interface then the separate pool addressing should work just fine.
I have re-read this thread and want to make sure that after some changes that you have made that the problem symptoms are still the same. You told us earlier that: "Now the client can ping the interfaces on its local LAN (concentrator interface 192.168.0.253, and the L3 switch, 192.168.0.253), but it cannot reach the rest of our internal LAN behind the layer 3 switch." Is this still an accurate statement of the problem?
As Herbert said earlier this could either be caused by the concentrator not have a correct route for the inside or it could be because the inside does not have a correct route to the client. In re-reading your description of the routing set up it looks like the concentrator has a default route configured but not the tunnel default route. May I suggest that you try configuring a tunnel default route (in addition to the normal default route) and see whether that makes any difference?
If that does not help the problem then I would suggest that you verify that the devices on the inside do have their default gateway set correctly and that the layer 3 switch does have a route for the VPN address pool with the concentrator interface address as the next hop.
HTH
Rick
[edit] I just focused on the question that you asked about the concentrator possibly needing a route for the address pool. The concentrator does not need any route statements for the address pool - it knows its own address pool, pretty much like having a connected interface subnet. The layer 3 switch is what needs a route for the address pool.

Some clients get Default Gateway assigned from WRT300N while others don't

Two existing desktops, one wired other wireless and existing laptop wireless connects to internet fine.
Trying to add work laptops, they aquire wireless signal, gets DHCP IP address assigned but doesn't connect. Looked at the ipconfig output and shows no default gateway - router IP is set to 192.168.1.1 - with everything default, I did a reset on it.
The existing machines all have default gateway assigned. Only difference I see is work machines are XP pro. Never had problems with work laptops connecting anywhere else.
Any ideas on how to setup so work laptops can connect?
Solved!
Go to Solution.

namralk wrote:
Ethernet adapter VMware Network Adapter VMnet8:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
        Physical Address. . . . . . . . . : 00-50-56-C0-00-08
        Dhcp Enabled. . . . . . . . . . . : No
         IP Address. . . . . . . . . . . . : 192.168.1.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
         Default Gateway . . . . . . . . . :
You have configured vmware on your computer to use 192.168.1.1 on the VMnet8 adapter. This means the computer uses 192.168.1.1 itself on that adapter and obviously won't set 192.168.1.1 as default gateway on your wireless adapter because 192.168.1.1 is the computer itself.
Fix your network configuration in vmware. After that a "ipconfig /renew *" or a reboot should obtain a new working lease including the default gateway. Make sure vmware does not use the 192.168.1.0/255.255.255.0 subnet for it's network adapters.

E1200 Wireless Client List will not display and causes web UI to temporarily stop responding

I picked up an E1200 and set it up successfully. I am using wireless MAC filtering, and decided to pull up the list of connected wireless clients (Wireless >> Wireless MAC Filter >> push "Wireless Client List" button).
When I do so, it immediately throws this back:
Immediately after this the Web UI of the E1200 becomes inaccessible. It still routes traffic, and the router remains pingable, but it will not allow access to the Web UI for several minutes. The error that appears upon attempt to access the Web UI during this time window is similar to the above, but reads "Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection."
I have tried this in Google Chrome, Firefox 4, and MSIE on two separate computers. Each browser displays the error a bit differently (MSIE, for example, just says it can't display the page and gives no further detail) but the net results are always the same. I have tried resetting the device to factory defaults in addition to re-downloading the firmware from the Cisco/Linksys website and installing it. No improvement.
I have also noted that the Log (Administration >> Log; and yes, I have it enabled) doesn't appear to be picking up anything at all. In fact, the Security log, which supposedly (according to the Help) "displays the login information for the Router’s browser-based utility," is also blank.
Is this a bug, or should I head back to the retailer and swap this device?

Ok - I nailed this down, I think, and it looks like a firmware bug.
Short version is that a factory reset cleared the issue, but during stepwise reconfiguration the problem came back. Through a bunch of iteration I figured out that if I have the E1200's DHCP server disabled *and* have wireless clients connected to it, the problem I described appears.
Turn the DHCP server back on and the problem goes away. Turn it off and the problem comes back. Turn it back on and it goes away. You get the idea.
If I had to pose a theory here, it's that the initial display of the Wireless Client List, which uses "IP Address" as the default sort, somehow implodes if the E1200 isn't actually assigning those IP addresses to the clients.
When this happens it appears to crash the Web UI wholesale. Just for grins, while the Web UI was unresponsive, I pinged the router it as before - still pingable - then ran nmap against it - no open ports found on the router. When the Web UI is functional, though, nmap detects port 80 quite easily. I have not timed how long it takes for the Web UI to come back up, but it is longer than 5 minutes, and I presume some sort of watchdog process has to detect that it has gone kaput and start it up again.
Final test was to restore my saved configuration from before the factory reset (note that the saved config was done under the same firmware version, and in this config, the DHCP server is disabled). Boom, problem. Wait for the Web UI to come back, turn on the DHCP server. Problem goes away. Turn the DHCP server off. Boom, problem comes back.
So, there you go.
Would be interesting if someone could verify this via a test against another E1200. It may be worth noting that in my baseline test I was also using Manual wireless setup (vs. Wi-Fi Protected Setup), and WPA2. Didn't make any other setting changes from the factory defaults. I did not actually have to turn the Wireless MAC Filter on to do the test. All one needs to do is click Enable on the Wireless MAC Filter tab, and then do *not* click Save Settings - just clicking Enable will light up the Wireless Client List button, which you can then push to get the list. That is how I handled testing to ensure that neither specific entries, nor the Prevent/Permit setting, nor having the filter enabled in saved configuration were involved in the problem.
Separately, no explanation for the lack of entries in the security log, but that pretty much looks like a firmware bug to me as well.

Default Gateway not transmitting to wireless clients

Similar Messages

Maybe you are looking for