RSV4000 DHCP Gateway address problem

I have an RSV4000 which I'm using as a gateway. I changed the default 192.168.1.0/24 network to 10.255.255.0/24 and configured the DHCP address pool to use 64 host addresses starting at 10.255.255.64
Every so often users on VLAN 1 get a gateway IP address of 192.168.1.1 even though they received a DHCP address of 10.255.255.64, 65, 66, etc.
I ran a packet capture and the RSV4000 is actually giving out the wrong gateway address.
I have to power cycle the RSV4000 and it works until some random point in time, then starts giving out the wrong gateway address again.
Is Cisco going to fix this?
I'm running version 1.3.2.0 and I do not have the V4 model so I can't run v2.0.0.3

Hey mdoldan,
Were you the one that upgraded the firmware of 1.3.2.0 on the router or did you receive it like that.
This is a very odd case, where it is giving out ip address on the default lan even though you changed it.
Have you tried reflashing the firmware, factory resetting the router and reloading the configurations back to it.
I would try that and see if the problem persist.

Similar Messages

DHCP beginning address problem.

Hi guys,
I cannot understand how to configure my TC. I put exactly the same network settings as they were in the Airport Express to share the Internet connection. Everything works fine except the internet itself. The problem as I see it is that dhcp beginning address cannot be set far away from the static IP. In my case, the static IP is 213.170.70.** and I only can change these ** last figures in the dhcp range.
But this conflicts with my provider and I have no internet while the TC itself works fine. If I set "share the only address" it doesn't help either.
Anybody can help?
Many thanks in advance.

None really. These are the three IP Address ranges available for Private Networks. The Internet Engineering Task Force (IETF) has directed the Internet Assigned Numbers Authority (IANA) to reserve these IPv4 address ranges for private networks. This has been published in RFC 1918.
More info: Wikipedia: Private network

HH3 Gateway Address Problem

Hi,
I have just had Infinity installed and have an issue with the BT homehub3.
The hub has an IP 192.168.1.254 however when it assigns an IP address to either my desktop or laptop using DHCP it assigns the gateway address as 192.168.1.1 and consequently I can’t get an internet connection. If I set the IP and gateway manually it works fine.
Any ideas as to why it isn’t setting the correct gateway?

Does it work if you set the IP address manually e.g
IP Address          192.168.1.50
Subnet Mask       255.255.255.0
Default Gateway 192.168.1.254
DNS                   192.168.1.254
There is no advantage in using DHCP, unless your computer is used on other networks. Static addressing is quicker and more reliable.
If you need to use DHCP, then make sure the subnet mask is set to 255.255.255.0
There are a couple of DHCP pools within the home hub, one is reserved for the BT Openzone/FON VLAN connection.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Time Capsule, DHCP not providing correct gateway address

I have gone back and forth between my AP Extreme and Time Capsule and have determined that Time Capsule is not providing the proper gateway address to my wireless clients. Instead of providing the correct gw address it provides the address I assigned the base station. This is contrary to my Airport Extreme which provides the proper gw address to my wireless clients. Sounds like a bug in the DHCP base station software. Any thoughts?

I have a very similar problem. I originally had cable broadband and a Airport Extreme (AE) upgraded to 7.3.1 all worked fine. The AE was being used as a DHCP server to distribute the dynamic IP address provided by the ISP. I then replaced the AE for a Time Capsule (TC) and installed a new 802.11n Airport Express. I upgraded the TC and AExpress to 7.3.1. The TC was setup identically to the now replaced (disconnected and switched off) AE.
Unfortunately the TC failed to work as a DHCP server. It did not recognize the ISP provided dynamic IP address and replaced it with an 'Invalid' IP address which of course meant no internet access. I then replaced the TC with the original AE (identically set up) and all worked fine, including the AExpress.
While I wait for Apple to fix the TC firmware I am running the AE as the DHCP Server and the TC as a wireless bridge to the AExpress. Time Machine is recognizing Time Capsule and backups from two macs are working fine.

Set a DHCP gateway for WRT300N

Dear Friends Hello I have to networks with IP ranges 192.169.1.x & 192.168.1.x I want to connect this two networks,the problem is that the ip address of gateway is 192.168.1.1 and the IP address of router(WRT300N) is 192.168.1.2 I don't have windows server,and i can't set static IP for all of users How can I set a gateway in DHCP settings ?

You can't do this with your WRT. It is a broadband router with limited configuration options. One limitation is that the DHCP server in the WRT always uses its own IP address as gateway IP address. You cannot freely configure the DHCP server. It is supposed to be a broadband router, i.e. it is supposed to host the internet connection and thus be the default gateway.
Technically, you only want to route a subnet differently and not the whole internet. Thus the default route/gateway is the wrong place to modify.
The proper solution would be to add a static route for the other subnet on all client computers. Then the computers will correctly route the traffic. The proper solution would also be to run your own DHCP servers to do the IP assignment there and not assign any gateway address at all.
If you don't want to do that you can only add a static route on the routers to reroute the traffic for the other subnet.
First of all, please renumber the IP subnet 192.169.1.* to a private IP address, e.g. 192.168.2.*. 192.169.1.* is a public IP address and should not be used for private addresses.
Now say, you have the computers with the modem link sitting on 192.168.1.1/255.255.255.0 and 192.168.2.1/255.255.255.0.
The routers with DHCP server enabled sit on 192.168.1.2/255.255.255.0 and 192.168.2.2/255.255.255.0.
Now add a static route on the router 192.168.1.2 on the advanced routing page:
route destination LAN IP 192.168.2.0, subnet mask 255.255.255.0 to gateway 192.168.1.1 on the LAN interface.
likewise on 192.168.2.2 add:
route destination LAN IP 192.168.1.0, subnet mask 255.255.255.0 to gateway 192.168.2.1 on LAN interface.
With those two routes in place you should be able to use the Diagnostics tools on the Administration tab of the router to ping or traceroute IP addresses in the other subnet.
These routes should also redirect the traffic from the computers to the other subnet. You should make sure that the firewalls on all computers are not configured to block ICMP (in particular ICMP redirects). The router will tell the computers the correct gateway address for the traffic, i.e. the computer will only send the first packet to the router and then learns that the correct destination is the computer with the modem link and forwards everything directly there. Many firewalls are overzealous and unnecessarily block ICMP breaking many IP mechanism for troubleshooting and optimization. Therefore: make sure your firewalls are turned off or correctly configured. Otherwise you unnecessarily route all your traffic to the other subnet through the router as well.
Again: i would rather recommend to set up your own DHCP server and set static routes on the computers or push the routes through DHCP.

WTR54GS Fails to obtain a DHCP IP Address from Upstream

Greetings!
I had effectively given-up on Linksys Router WTR54GS, as it was advertised that it could be plugged into a pre-existing network (friends home network, a hotel room ethernet jack, etc), but sadly the WTR54GS itself is incapable of obtaining a DHCP IP Address from an upstream DHCP server (like the hotel, etc).
I have tried repeatedly to work with Linksys Support but everyone wants to blame the upstream router, suggesting that I change it's configuration to "Bridged-mode". Yeah, right. Like I'm going to walk down to the hotel lobby main desk and tell them that they need to place THEIR network in bridged mode just so my WTR54GS will work. I was willing to believe that the first router (version 2.0) that I was sent was defective, and let Tech Support talk me into returning it to my vendor and seeking a replacement.
I receieved the replacement (this time version 1.0) and had EXACTLY the same problem. I returned that one as well (marked defective) after talking with Ellen in Linksys 2nd Level Technical Support. She promised this would be referred to the Linksys Engineering group for further study. This was 4+ months ago.
I would like to buy another one, but am hesitant to buy because I just do not trust Linksys Technical Support anymore. Can someone please confirm that Linksys Engineering is aware of this problem, acknowledges its existence, and has resolved (or is at least working on resolving) this problem?
-Elrendhel
Forum Administrator, Product Reviewer, & Moderator at MobilitySite,
Forum Admin, Lead Tech Support Mgr & Moderator at GPS Tuner,
Moderator at Microsoft's Windows Mobile Owners Circle forums.

So you have connected WTR through the correct (blue) port to the internet connection?
You have configured the WTR for wired internet connection type?
You have configured the WTR for DHCP?
What does the WTR say on the Status page?
Have you tested the WTR inside your home network?

Clients not receiving DHCP IP address from HREAP centrally Switched Guest SSID

Hi All,
I am facing a problem in a newly deployed branch site where the Clients are not receiving DHCP IP address from a centrally switched Guest SSID. I see the client status is associated but the policy manager state is in DHCP_REQD.
The dhcp pool is configured on the controller itself. The local guest clients are able to get DHCP and all works fine, the issue is only with the clients in the remote site. The Hreap APs are in connected mode. Could you please suggest what could be the problem. Below is the out of the debug client.
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Adding mobile on LWAPP AP 3c:ce:73:6d:37:00(1)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Reassociation received from mobile on AP 3c:ce:73:6d:37:00
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'Guest-ACL' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific IPv6 override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying IPv6 Interface Policy for station 10:40:f3:91:7e:24 - vlan 81, interface id 13, interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 STA - rates (8): 140 18 152 36 176 72 96 108 0 0 0 0 0 0 0 0
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Initializing policy
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 3c:ce:73:6d:37:00 vapId 17 apVapId 1
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 apfMsAssoStateInc
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfPemAddUser2 (apf_policy.c:222) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Idle to Associated
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 49) in 28800 seconds
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sending Assoc Response to station on BSSID 3c:ce:73:6d:37:00 (status 0) ApVapId 1 Slot 1
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfProcessAssocReq (apf_80211.c:4672) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Associated
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4183, Adding TMP rule
*apfReceiveTask: May 24 11:35:53.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
type = Airespace AP - Learn IP address
on AP 3c:ce:73:6d:37:00, slot 1, interface = 13, QOS = 3
ACL Id = 255, Jumbo F
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006 IPv6 Vlan = 81, IPv6 intf id = 13
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sent an XID frame
*apfMsConnTask_3: May 24 13:26:49.401: 10:40:f3:91:7e:24 Updating AID for REAP AP Client 3c:ce:73:6d:37:00 - AID ===> 1
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 12) in 10 seconds
*osapiBsnTimer: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:4897) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Disassociated
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 45) in 10 seconds
*osapiBsnTimer: May 24 13:29:09.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Sent Deauthenticate to mobile on BSSID 3c:ce:73:6d:37:00 slot 1(caller apf_ms.c:4981)
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsAssoStateDec
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:5018) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Disassociated to Idle
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [3c:ce:73:6d:37:00]
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Deleting mobile on AP 3c:ce:73:6d:37:00(1)
*pemReceiveTask: May 24 13:29:09.317: 10:40:f3:91:7e:24 0.0.0.0 Removed NPU entry.

#does the client at the remote site roams between AP that connects to different WLC?
#type 9 is not good.
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
#Does your dhcp server getting hits.
#Also, get debug dhcp message & packet.
#Dhcp server is not responding.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.

IP Address Problem

I have a PowerMac G4 Quicksilver 2002 running OSX 10.3.9, with Verizon DSL service. I suddenly have a very strange problem with my IP Address and some erratic behavior. When the internet connection works, my network settings are:
Location: Verizon DSL
Show: Built-in Ethernet
for TCP/IP
Configure IPv4: Using DHCP
IP Address: 71.xxx.xxx.xx (a series of automatically assigned numbers)
Subnet: 255.xxx.xxx.x (a series of automatically assigned numbers)
Router: 71.xxx.xxx.x (a series of automatically assigned numbers)
Recently, without changing any of the settings, I get an IP Address something like 169.xxx.xxx.xx. This IP Address does not work. The tech people at Verizon Online said that the line from my DSL modem to their server was fine, but that the automatically assigned IP Address should be the 71.xxx.xxx.xx number.
There is no pattern to this error. Originally the connection would work in the morning and begin the error IP Address about 4:00 pm. Today when I booted, the connection was out and the 169.xxx showed in the network window. I used the internal Apple modem and a secondary dial-up account and could connect to the internet. After I disconnected the dial-up, the Ethernet connection worked, showing the correct IP Address of the 71.xxx numbers.
Does anyone have any ideas what's going on here. Thanks.
Quicksilver G4 Mac OS X (10.3.9)
Quicksilver G4 Mac OS X (10.3.9)

I seem to have this (or a very similar) problem repeatedly after updates. I use a wireless connection to the internet when at work, which mostly is trouble free. However following the last two itunes/quicktime updates and now also following the latest security update (Security Update 2006-005 (10.3.9)) which deals with the airport protocol, I have had this problem.
Where the airport managed to connect and obtain a valid IP address before, with exactly the same settings the computer uses a 'self-assigned' IP address following the update. As you observe the self assigned IP address does not enable you to connect.
However following the itunes/quicktime updates the problem resolved itself after a few days ( a few hours the second time) and did not reoccur. I have only just encountered the problem following the security update and hope it also resolves itself soon.
Any advice on how to avoid this altogether would be appreciated.
15" powerbook G4 Mac OS X (10.3.9)

Releasing unused DHCP IP addresses in OSX Server 10.4

In OSX Server 10.4.11 is there any way to release unused DHCP client addresses in the Server Admin app? We have 73 clients showing (and only 30 on the network) because various computers have been added to the network and removed/reinstalled at various times, and that means we're running out of available addresses in our little chunk of the subnet.
We've previously set a longish lease time on DHCP addresses because we've had problems in the past with sleeping Macs being woken up and having clashing IPs with other Macs that have had that IP reassigned to them, but it means that we do have a long list of unused DHCP clients.
Does Server 10.5/10.6 allow the release of DHCP addresses from the admin app (oh, for a right-click delete!), or is that just not possible in the DHCP protocol (NB I'm trying to release unused IP addresses, not asking live clients to rescind their IP address).

It's not legal within the DHCP protocol - as far as the server is concerned, that IP address has been handed to the client and should be reserved for that client until the lease expires. The server has no way of knowing whether the client is still using the address.
You may be able to break the rules, though - the server stores the DHCP leases in /var/db/dhcpd_leases, so you should be able to stop the DHCP server, edit the file to remove the unnecessary leases, then start the server back up. No guarantees, tho'.

DHCP provided address time limits

Hi there,
I have been searching for any way to limit DHCP supplied addresses in regards to time usage. I am looking to restrict certain addresses, specified via MAC, to only be able to access my network during specific times of the day.
For example, I would like for address 192.168.0.28 to only be able to access the network (and the internet of course) between the hours of 9 a.m. to 5 p.m.
If this cannot be done by OSX 10.5 Server, is there any affordable software or hardware solution out there that anyone knows of which can perform this function?

I removed the Belkin router and set up the Airport Time Capsule as the DHCP server. No problems since.

Get IPv6 gateway address on Windows XP

Hi guys,
Windows XP supports IPv6, but if I want to get the IPv6 gateway address linked to an adapter I've a big problem:
GetAdaptersInfo can get the gateway address but works only with IPv4
GetAdaptersAddresses works with IPv6 and can get the gateway address, but the related parameter FirstGatewayAddress of its structure ip_adapter_addresses was added only on Windows Vista and later
Win32_NetworkAdapterConfiguration WMI class can retrieve IPV6 gateway address but it is available only from Vista
What can I do?

No simple way, basically, on XP+ use GetAdaptersAddresses, it adds ipv6.
XP has been end of support by MS, so maybe upgrading OS is a better way to promote things forward.
Best Regards,
Please remember to mark the replies as answers if they help

Gateway Address ???

I have an iMac which is connected via an AirPort router. I have no problems getting online. However, I am trying to connect a blu-ray player to the network and it asks for the Gateway Address. I can't find it anywhere. Can anyone help?

danbee46 wrote:
I have an iMac which is connected via an AirPort router. I have no problems getting online. However, I am trying to connect a blu-ray player to the network and it asks for the Gateway Address.
I believe it's the LAN address of your AirPort router, such as 10.0.1.1.

PXE Boot a Hyper V Guest - Not receiving a DHCP IP Address

Hello Everyone,
I am trying to PXE boot a Hyper V guest, but am not getting a DHCP IP Address. Eventually the DHCP query times out and loads into the guest OS I have manually installed. See the PXE Boot Screen below. When in the installed guest OS, I do receive
a DHCP IP address as shown below. I am utilizing the Legacy Network Driver. I don't think it is related to VLAN identifier, but tried with/without and still no go. Any ideas what could be preventing this? Please let me know.
PXE Boot Screen:
CLIENT MAC ADDR: 00 15 5D F2 99 0C GUID: B366BBA1-D503-4D64-A77E-77474F3A2193
DHCP.........-
PXE-E51: No DHCP or proxyDHCP offers were received.
DHCP IPCONFIG in Guest OS:
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : mywork.com
   IPv4 Address. . . . . . . . . . . : 10.242.242.251
   Subnet Mask . . . . . . . . . . . : 255.255.255.128
   Default Gateway . . . . . . . . . : 10.242.242.129
Thanks,
Ron

Hi Ron,
A solution is provided in this thread. You may need to have a look on the steps below:
• PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
DHCP services are not available on the network to which the PXE-enabled NIC is connected.
A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
DHCP is available on the network, but PXE is not.
The network cable is not attached to the PXE-enabled NIC on the target server.
See: http://social.technet.microsoft.com/Forums/en-US/d06413a4-af2b-4736-a510-c0a68eb880cf/cannot-get-certain-machines-to-pxe-boot
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

RV042 DHCP Gateway Settings

I have a core routing switch along with my RV042. I am using the RV042 for DHCP, BUT I would like to issue a different default gateway than the router itself. I'd rather give the address of the core switch as the default gateway to my DHCP clients as I have to route to various other VLAN's. Instead now I have to do static routes in the RV042 to get back to those when it would be cleaner if I can just get the RV042 to issue a different Default Gateway to DHCP clients. Is this possible?

I don't think you are understanding the request. I want the RV042 to remain the external gatway router. The core swotch is configured to use it as the last hop to the internet for all VLAN's. My simple issue is when using DHCP on the RV042 it gives clients It's own address 192.168.100.1 as the gateway. I want to CHANGE that entry to simply give clients 192168.100.10 as the gateway which is the core switch interface. I don't have a physical DHCP server on the network and I am trying to avoid routing through the RV042 when I have a high speed core routing switch. I just want the RV042 to stay as the last hop gateway and simple change the DHCP gateway entry it's handing out to clients. This really is a simple request and I feel can be done with the telnet console given the right login credentials and the commands to make the change in the DHCP server settings.
This has nothing to do with physical port connectivity, it's a question about the DHCP server configuration in the device, and both WAN ports are already in use for dual WAN connectivity.

When they ask for the gateway address on the Tv what number is that or what number should I be looking for?

When they ask for the gateway numbers on the TV, what number is that or what should I be looking for? I am trying to connect my wifi network on my Samsung smart TV.

The "Gateway" address would be the Private (LAN-side) IP address of your Internet router. If you are using an AirPort base station for that router, the default gateway IP address would be: 10.0.1.1

RSV4000 DHCP Gateway address problem

Similar Messages

Maybe you are looking for