RVS4000 DHCP server on all but VLAN 1 broken in v1.3.2.0

I'm trying so subdivide my home network into VLANs to split Jumbo Frame capable devices from the rest.
Using the preinstalled 1.3.0.5 version I could configure this correctly. After upgrading to v1.3.2.0 the DHCP server on any VLAN (except 1) no longer responds to DHCP requests.
I have tried going back to factory defaults and rebuilding the config step by step but this did not help.
Has anyone else come across this issue?
Setup:
Port 1 (VLAN 1) - laptop 100Mbps
Port 2 (VLAN 1) - Down
Port 3 (VLAN 2) - NAS 1Gbps
Port 4 (VLAN 2) - PC 1Gbps
VLAN1 is configured as 192.168.1.0/24, VLAN2 is configured as 192.168.2.0/24.
(Originally I tried 192.168.1.0/25 and 192.168.1.128/25).

Well - my update for the day...
Fully charged last night and unplugged. Woke up to about 24 minutes usage which is ok. PUSH and used a little before retiring for the night. This morning, I left 3G and PUSH on as well as GPS. I don't live in a 3G area so until I got into the "city", I didn't have 3G. So my short trip through town did use 3G and tested for a short time(at a red light). At work I don't have 3G in my office so all day was EDGE. I do listen to the iPod both ways to work and some at work. Anyways, before leaving work I had about 4 hours usage and about 60 percent battery left. A little lower than I am used to but liveable. On the way home I made a few stops, hammering on the 3G with a passion. Before I got home, I was below the 20 percent warning...All for about 40 minutes of usage between GPS, iPod, and 3Ging.
Bottom line - the 3G experience was very power hungry. More than I can remember with my other 3G devices that I have owned.
I think Apple has some tuning to do and they probably know it now. I have no regrets as I wanted the GPS more than the 3G. Doesn't suck power? I am sure it does to some degree but I don't intend to use for constantly on door to door(even it doesn't do this). I would power via my car anyways if I did.
Basically, many have said to turn off the 3G when not being used. I agree . I wish there was a fast way to turn on and off as it is numerous clicks deep. When you know you need some "umph" to your connection, turn it on and get after it.
I am sure there will many posts similar to this one as expected.
Hope this helps.
--Mickey

Similar Messages

  • Help. How to configure ASA5515 as 'one armed router' for access to DHCP server on a different VLAN

    Hi,
    My setup
         router > ASA5515(ver8.6) > 4 SGE2010p switches
     I want to put the guest WiFi users on a separate network. I have layer 2 switches and want to configure the ASA5515 as a 'router on a stick' setup for the guest vlan to have access to the DHCP server on the native vlan.
    I have
    1. created a sub-interface for the inside interface and enabled intra-interface traffic.
    2. A static route on the ASA point the guest network to the switch.
      What else do I need to configure on the ASA for inter-vlan routing?
    ASA related config:
    interface GigabitEthernet0/1
     nameif inside
     security-level 100
     ip address 10.15.xx.1 255.255.252.0 standby 10.15.xx.2
    interface GigabitEthernet0/1.2
     vlan 100
     no nameif
     no security-level
     ip address 10.100.xx.1 255.255.255.0
    C    10.15.xx.0 255.255.252.0 is directly connected, inside
    S    10.100.xx.0 255.255.255.0 [1/0] via 10.100.xx.2, inside

    Thanks for the quick response Reza.
     Actually that command is already there. Didn't include it in my post.
    So I am guessing my ASA config is correct.
    I am having trouble setting up the trunk ports on the layer2 SGE2010P switch for trunk port.
    I am used to command line layer3 switches (CLI is wasy) but not familiar with these switches GUI. I am going through the config guide right now.
    Could you help me with that too?
    Not to bother you with a completely different issue though.
    Thanks again!

  • DHCP Setup across multiple VLANs on RV325 - DHCP Server only working on VLAN 1

    I have multiple VLAN subnets defined on my RV325 - when I try and utilize a DHCP Server on each VLAN, it only seems to be issuing IP Addresses to clients on VLAN ID 1.  When I first set this up months ago, I thought I had tested it providing IP Addresses via the other subnets.  Now that I am trying to do so, it isn't working "as expected".  Example - I am using VLAN 25 as the GuestWireless subnet utilizing a separate 802.11n WAP that is set to Bridge connections to the IP Address of the VLAN interface.  Devices are able to connect to the WAP, but end up with a self-assigned IP Address 169.x.x.x address.  There has to be an easy fix to this, but I seem to be "stuck" figuring out what it is…pointers/redirects appreciated.  Thanks!

    Thanks - I've already reviewed that information before I posted.  I've been working with DHCP since the mid-90's, so I'm comfortable with the settings/configuration I need to leverage to make this work via other means using various Network-based OSes.
    I'm wondering if there are other options in configuring this device that can impact the ability to dynamically serve IP addresses on a VLAN/subnet-by-VLAN/subnet basis.
    As I did more testing, I discovered when I reserved an IP Address via the IP & MAC Binding option within the DHCP Settings, those devices would receive their static reservations and work as expected, so the problem seems to be leveraging the DHCP Pool for devices connecting to VLANs other that VLAN 1.
    Any ideas as to why the DHCP Pool's are "non-functioning" for the other VLANs is greatly appreciated...
    Each VLAN is setup with a separate DHCP Server configuration as shown below:
    VLAN ID = 1 (Default, Inter VLAN Routing = Enabled, LAN1-6 = Untagged, LAN7=Tagged, LAN8=Excluded, LAN9-14 Untagged)
    Device IP Address = 172.16.xxx.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 172.16.xxx.100
    Range End = 172.16.xxx.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    Correctly serving IP Addresses via DHCP (both static and dynamic) to Wired devices & Wireless devices connecting through WAP (set to Bridge)
    VLAN ID = 25 (GuestWireless, Inter VLAN Routing = Disabled, LAN1-LAN7 = Excluded, LAN8 = Untagged, LAN9-14 = Excluded)
    Device IP Address = 172.16.yyy.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 172.16.yyy.100
    Range End = 172.16.yyy.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    NOT serving dynamic IP Addresses via DHCP to Wired devices & Wireless devices connecting through WAP (set to Bridge)
    Static DHCP Reservations setup via IP & MAC Binding settings DO WORK in terms of providing the assigned static IP Address to the client.  Inbound/Outbound traffic to Internet works for devices with Static DHCP Reservations.
    VLAN ID = 100 (Voice, Inter VLAN Routing = Disabled, LAN1-6 Excluded, LAN7 = Untagged, LAN8-14 = Excluded)
    Device IP Address = 192.168.zzz.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 192.168.zzz.100
    Range End = 192.168.zzz.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    NOT serving dynamic IP Addresses via DHCP to Wired devices & Wireless devices connecting through WAP set to Bridge
    Static DHCP Reservations setup via IP & MAC Binding settings DO WORK in terms of providing the assigned static IP Address to the client.  Inbound/Outbound traffic to Internet works for devices with Static DHCP Reservations.

  • WLC 5508, vlan select, reserved address in external DHCP server

    Hi guys,
    I have a deploy with a WLC 5508 version 7.0.116.0, APs mode local and vlan select feature enable. The issue is that the reserved IP address in external DHCP server not work. The DHCP contains a reserved IP address associates with mac address, but the assignement of IP is not match with de policies in DHCP. All others services operate normally.
    This reserved assignment operate previusly to modificate the WLAN to vlan select feature. Help me to improve this situation.
    Thanks.-
    Best regards

    Hello Abhishek, thanks for you quick answer....
    the link was a document used for the deploy, but not especifict nothing about the reserved IP address for particular host. In other words, the reserved IP address (through MAC address) in external DHCP server not work when "vlan select" its enable.

  • Cascading RV180 as DHCP server but pointing to another default gateway router

    Hi,
    My network topology is as follows:
    Internet <-> Residential Gateway (RG) from ISP (OEM: Pace) [192.168.1.254/255.255.255.0] <-> RV180 [192.168.1.253/255.255.255.0] <-> SG500 switch [192.168.1.250/255.255.255.0] <-> rest of network.
    I know this is a cascading LAN-to-LAN arrangement. The cable from the RG to the RV180 is from a LAN port on the RG to a LAN (not WAN) port on the RV180.
    I eventually want to segment my network into a few VLANs from the RV180 down. I am aware most people would recommend DHCP on the "primary" router, but the RG is non-VLAN aware, so I figure I need to handle the DHCP off the RV180. At the same time, I have also opted not to do a LAN-to-WAN cascade because I want to retain the ability to configure the RG from the rest of the network and not have to cart a computer over to the RG to do it.
    On the RG, I've disabled DHCP, and placed 192.168.1.253 in the DMZ.
    On the RV180, I've enabled DHCP and put it in Router mode.
    The issue is that I do not have any Internet connectivity. If I allow the computers in the network to receive IP addresses over DHCP, the default gateway that is communicated is 192.168.1.253, which is the RV180. If I configure static IPv4 information on my computers to point to 192.168.1.254, I am able to connect outside, as you would expect.
    How can I get the RV180 to pass out DHCP IP addresses, but point to 192.168.1.254 as the default gateway? I thought the solution might be to create a default route (or something). I went to the static routes tab but it wouldn't let me enter 0.0.0.0 as a destination IP to route through 192.168.1.254.
    Further down the line, is it possible for both the RG and the RV180 to connect directly to the SG500, along with the other nodes in my network? That way the RV180 only serves to maintain the VLANs and pass out IP addresses via DHCP, instead of having it be the choke through which everything goes through on the way out?
    Sorry if there is a really obvious solution to this. It's really been floundering about in the dark so would appreciate any advice

    Hi Jason, I have considered your post here for quite some time. I came to one conclusion based off your text. The entire purpose of the RV180 is a DHCP server for multiple subnet / vlan.
    Here's the thing, you have a SG500 switch. Based off reading your text, this will do everything the RV180 can except the DHCP service. The limitation you are going to run in to is still going to be your gateway unit, the RG.
    In the end, even with such a configuration using the RV!80 or the SG500 (layer 3), the RG will have to be configured with static routes since the RG has no concept of those other LAN segments.
    Here is a post I wrote about a SG300 connecting to a RV0XX router (which doesn't understand the VLANs)
    https://supportforums.cisco.com/message/3739083#3739083
    Using the concept of this topic, you may be able to add aditional static routes on the RV180 sending each subnet to the common IP interface of the RG.
    It would be very interesting to see if we could make that work.
    -Tom
    Please rate helpful posts

  • SF300-24 DHCP Server not responding (worked once but not again)

    Tried to get the new firmware DHCP Server option working but after turning it off and back on it doesn't seem to give any addresses anymore.
    Anyone else having troubles or success actually using the SF300 v1.4 DHCP Server?
    I even tried factory default reset but no luck.
    When I did have it working everything was good but the older Cisco Meraki would not get an IP address so I had to revert to an older DHCP server.  When I tried again today by turning the older server off and the SF300 back on, none of the Windows machines that previously would work would get an address.
    Am running:
    System Summary
    System Information
    System Operational Mode:
    L2 Mode
    System Description:
    SF300-24 24-Port 10/100 Managed Switch
    System Location:
    Edit
    System Contact:
    Edit
    Host Name:
    switche2653d
    Edit
    System Object ID:
    1.3.6.1.4.1.9.6.1.82.24.1
    System Uptime:
    0 day(s), 0 hr(s), 37 min(s) and 28 sec(s)
    Current Time:
    17:33:23;2014-Aug-06
    Base MAC Address:
    00:25:84:e2:xx:xx
    Jumbo Frames:
    Disabled
    Software Information
    Firmware Version (Active Image):
    1.4.0.88
    Firmware MD5 Checksum (Active Image):
    66ab3618cb29023da5ce7c2177e6c3d4
    Firmware Version (Non-active):
    1.3.7.18
    Firmware MD5 Checksum (Non-active):
    1f59c2af2f50786e1a8a3146de42c867
    Boot Version:
    1.3.5.06
    Boot MD5 Checksum:
    da44c9c583e5a8a274f911c4d16f501e
    Locale:
    en-US
    Language Version:
    1.4.0.88
    Language MD5 Checksum:
    N/A
    TCP/UDP Services Status
    Edit
    HTTP Service:
    Enabled
    HTTPS Service:
    Enabled
    SNMP Service:
    Disabled
    Telnet Service:
    Disabled
    SSH Service:
    Disabled
    Serial Number:
    DNI15xxxxx
    PID VID:
    SRW224G4-K9 V01

    Tried to get the new firmware DHCP Server option working but after turning it off and back on it doesn't seem to give any addresses anymore.
    Anyone else having troubles or success actually using the SF300 v1.4 DHCP Server?
    I even tried factory default reset but no luck.
    When I did have it working everything was good but the older Cisco Meraki would not get an IP address so I had to revert to an older DHCP server.  When I tried again today by turning the older server off and the SF300 back on, none of the Windows machines that previously would work would get an address.
    Am running:
    System Summary
    System Information
    System Operational Mode:
    L2 Mode
    System Description:
    SF300-24 24-Port 10/100 Managed Switch
    System Location:
    Edit
    System Contact:
    Edit
    Host Name:
    switche2653d
    Edit
    System Object ID:
    1.3.6.1.4.1.9.6.1.82.24.1
    System Uptime:
    0 day(s), 0 hr(s), 37 min(s) and 28 sec(s)
    Current Time:
    17:33:23;2014-Aug-06
    Base MAC Address:
    00:25:84:e2:xx:xx
    Jumbo Frames:
    Disabled
    Software Information
    Firmware Version (Active Image):
    1.4.0.88
    Firmware MD5 Checksum (Active Image):
    66ab3618cb29023da5ce7c2177e6c3d4
    Firmware Version (Non-active):
    1.3.7.18
    Firmware MD5 Checksum (Non-active):
    1f59c2af2f50786e1a8a3146de42c867
    Boot Version:
    1.3.5.06
    Boot MD5 Checksum:
    da44c9c583e5a8a274f911c4d16f501e
    Locale:
    en-US
    Language Version:
    1.4.0.88
    Language MD5 Checksum:
    N/A
    TCP/UDP Services Status
    Edit
    HTTP Service:
    Enabled
    HTTPS Service:
    Enabled
    SNMP Service:
    Disabled
    Telnet Service:
    Disabled
    SSH Service:
    Disabled
    Serial Number:
    DNI15xxxxx
    PID VID:
    SRW224G4-K9 V01

  • DHCP Server configuration

    Dear team,
    Here is my DHCP configuration in Juniper route, but now i need to configure DHCP in windows 2008 r2 Server, kindly guide me witch is best way to go head.

    Kumar 
             You no need to configure anything for clients when they are in same vlan or subnet of the DHCP Server. All you need to do for the other vlan clients that can be done by configuring ip helper in defualt gateway..consider
    this as example..
       DHCP Server 192.168.10.1 (vlan 10)       ---------------------------- clients get ip because they are also vlan 10 192.168.10.5,,,,192.168.10.10 etc
    other vlans, ex (vlan 20)     your client ipconfig will be     192.168.20.1/24
    default gateway will be 192.168.20.254    this will be in a switch     Go to that interface in switch configure this          ip helper address 192.168.10.1              
                 it should work if my understanding is correct..        
    Thanks        

  • SF300-48P gets error message trying to enable DHCP server in unit

    We have a SF300-48P that has been used as a dumb switch.  The network is currently a peer-to-peer with all 30 devices (mixed desktop computers and some printers) having a fixed IP assigned or selected in them.  While trying to add a NAS device the device reported it needed a DHCP connection.  So, checking, I found that the latest firmware for the SF300 has a DHCP server inside it.  (At least that's what I get out of the "features" commnets.)  I downloaded the firmware from Cisco and upgraded the firmware to ver. 1.3.0.62.  I changed the password as required and then went to the "IP configuration".  I tried to check the box for "enable DHCP server" but got an error message something like  "must unplug all DHCP devices".  So I unplugged everthing from the switch except one computer with the IP fixed as 192.168.1.149 and tried to enable the DHCP server again.  But, I got the same error.
    Does the SF300 have a DHCP server internally with the ver 1.3.0.62 firmware?  (or, did I misread the meaning?)
    If the SF300 can be used as a DHCP server how do I go about enabling it?
       ( I am a complete n00b when it comes to networking so I will require some step-by-step guidance.)

    Hi Terry, the switch must be operating in layer 3 mode. Additionally, any vlan interface created must have a static IP address. The error you received is most likely because the default vlan or any other vlan does not have a static IP (assuming you're in layer 3 already)
    -Tom
    Please mark answered for helpful posts

  • Windows DHCP Server and Linux DHCP Relay Agent

    We are trying to organize a VLAN (say VLAN 1) for guests who must be assigned IP addresses from a DHCP server in a different VLAN (VLAN 2). This DHCP server is configured with two scopes - 172.16.0.0/24 (for VLAN 2) and 172.16.4.0/24 (for the Guests
    VLAN 1). The DHCP server successfully distributes addresses to clients in its VLAN (it has the IP address 172.16.0.2). For the clients in the other VLAN a DHCP Relay Agent has been setup on the router. It is DHCRELAY running on Linux (CentOS) which has
    been configured to accept the DHCPDISCOVER broadcasts coming on the VLAN1 interface of the router and forward these to the DHCP server. The IP address of the VLAN1 interface of the router is 172.16.4.254 and on the VLAN2 interface - 172.16.0.254
    The problem is that the DHCP server won't respond with a DHCPOFFER message to the relay agent. I have traced the frames on the router and on the DHCP server. They arrive on the DHCP server with the correct GIADDR of the relay agent. According to all documentation,
    if a scope has been configured on the DHCP server and it receives a unicast message with the GIADDR set by a relay agent that matches one of the configured scopes, the DHCP server must send a unicast DHCPOFFER to the relay agent. But it doesn't.
    Here is what Wireshark reports (ignore the Destination port unreachable messages, the DHCP service was stopped at the time Wireshark was running)
    When the service is running, there are just DHCPDISCOVERs - no OFFER. You can see that the server has the two scopes configured:
    The relay agent seems to work normally - it forwards the DHCPDISCOVERs to the server continuously (tried many times with ipconfig /renew on the client).
    I read many posts about this problem. Some users had other services running on the DHCP server that used the DHCP port, but I don't have such an issue (you see that when the service is stopped, an ICMP port unreachable is sent which is correct). Others however
    did not find a solution. Am I missing something? Is there something specific when using the DHCRELAY agent from DHCPD? Can I turn on some verbose logging to track this down? Thanks in advance.

    WIth DHCP, there is really nothing to configure. If the Relay Agent/IP Helper is pointing to it, and the VLAN subnet exactly matches the scope subnet, then it should just work.
    What I've seen in the VLAN config is either a static route back to the subnet the DHCP server itself is sitting on is not configured or incorrectly configured, or there are ports blocked (need UDP, too, since that's what DHCP uses to pass the OFFER), and
    other necessary ports are opened, then it should just work.
    Sometimes NIC teaming on the DHCP server will cause it. Not sure. Microsoft doesn't support teaming prior to Windwos 2012, but it doesn't mean that it doesn't work. Don't get me wrong, teaming works nicely, but they just don't support it because they never
    certified the drivers, that's all.
    The issues I've seen with DHCP relays and VLANs in the forums are usually based on misconfigs in the VLAN or ports blocked. Sometimes we'll refer to call Microsoft Support for specific, hands-on assistance. And searching the threads, from what
    I've found that if they did call support, they've never posted back what the problem was based on or the resolution. I can post a couple of them for you to read through, but there were never any response with the actual resolution.
    If you like, you also have the option to contact Microsoft Support. Here's a list of phone numbers if you choose this option:
    http://support.microsoft.com/contactus/
    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
    This post is provided AS-IS with no warranties or guarantees and confers no rights.

  • SF/SG 300 DHCP server

    Hi,
    is it possible for SF/SG300 switches to be used as DHCP server for non-management VLAN-s.
    The switch has VLAN1 as management VLAN - has IP address assigned.
    The switch has additional VLAN - VLAN200 and I'd like SG300 to act as DHCP server for clients on this VLAN.
    Is this possible at all?

    Hi Jernej, the switch must operate in layer 3 mode. You can enable dhcp server per vlan.
    To qualify to make a DHCP pool for a layer 3 vlan, none of the vlan interface can have an IP address issued via DHCP, so you vlan 1 and 200 must have a static ip address assigned.  The vlan 1 does not require dhcp server configured for vlan 200 to have one.
    Here is a sample configuration
    config t
    vlan database
    vlan 200
    exit
    interface vlan 1
    ip address 192.168.100.137 255.255.255.0
    no ip address dhcp
    exit
    interface vlan 200
    ip address 192.168.99.1 255.255.255.0
    exit
    ip dhcp server
    ip dhcp pool network test
    address low 192.168.99.1 high 192.168.99.254 255.255.255.0
    default-router 192.168.99.1
    dns-server 8.8.8.8
    -Tom
    Please mark answered for helpful posts

  • Redundancy DHCP Server (Backup Server)

    Hi,
    How to configure redundancy DHCP server as all my clients reservice  with MAC address .I need same ip address for the clinet.
    How to configure it.

    Greetings!
    You did not mention which operating system you are talking about. There is no built in feature in order to support fail over and redundancy for DHCP in Windows Server 2008 R2. So you have to use two DHCP server and reserve your desire IP address with appropriate
    MAC address on both DHCP servers.
    If you have Windows Server 2012 installed, you can use built in DHCP fail over feature:
    Scoping out the NEW DHCP Failover in Windows Server
    2012
    Regards.
    Mahdi Tehrani   |  
      |  
    www.mahditehrani.ir
    Please click on Propose As Answer or to mark this post as
    and helpful for other people.
    This posting is provided AS-IS with no warranties, and confers no rights.
    How to query members of 'Local Administrators' group in all computers?

  • New VLan can't talk to DHCP server

    We have just created a new vlan (172.18.1.0/24 vlan 3) on our network and we are trying to use an exsisting DHCP server (192.168.0.1 vlan 8) But the clients on the 172.18.1.0 network can't connect to this DHCP server on vlan 8. My questions are.
    1. Do we need to specify vlan 3 on the switchport that the DHCP server is plugged into?
    2. Is there something @ L3 we need to enable to pass these DHCP server messages too across these vlans?
    Has any used DHCP servers on different subnets?
    Any info would be great.

    You need to configure an IP helper on the appropriate VLAN interface(s). Routers, by default, will not forward broadcast packets. Since DHCP client messages use the destination IP address of 255.255.255.255 (all Nets Broadcast), DHCP clients will not be able to send requests to a DHCP server on a different subnet unless the DHCP/BootP Relay Agent is configured on the router. The DHCP/BootP Relay Agent will forward DHCP requests on behalf of a DHCP client to the DHCP server. The DHCP/BootP Relay Agent will append its own IP address to the source IP address of the DHCP frames going to the DHCP server. This allows the DHCP server to respond via unicast to the DHCP/BootP Relay Agent. The DHCP/BootP Relay Agent will also populate the Gateway IP address field with the IP address of the interface on which the DHCP message is received from the client. The DHCP server uses the Gateway ip address field to determine the subnet from which the DHCPDISCOVER, DHCPREQUEST, or DHCPINFORM message originates.
    See more at the following document, with configuration steps and examples:
    http://www.cisco.com/warp/public/473/100.html#configdhcpbootpciscoios

  • Cisco 1702i WAP: how to get an interface in a non-native bridge group/ VLAN to be recognized by the internal DHCP server

    Does anyone know how the internal DHCP server in these access points connects to virtual interfaces and bridges in the unit?
    Is there some sort of default connection that connects the DHCP server to the native bridge group or VLAN?
    In a test case, with an SSID in the native VLAN and bridge group, the 1702i serves an IP address to a wireless client no problem. But with a second SSID in a non native VLAN and bridge group, no IP gets served. My only guess is that since the bvi1 defaults to the native bridge group and VLAN, sub-interfaces also in this group are assumed to be in the same subnet as bvi1, or in this case:
    interface bvi1
      ip address 192.168.1.205 255.255.255.0
      no ip route-cache
      exit
    It would be the ..1. subnet.
    Since the dhcp pool is set as:
    ip dhcp pool GeneralWiFi
      network 192.168.1.0 255.255.255.0
      lease 1
      default-router 192.168.1.1
      dns-server 8.8.8.8
      exit
    There may be an assumption that anything bvi1 can talk to is in the ..1. subnet, so the above pool gets activated on a request coming through bvi1.
    Is the DHCP server just hanging out waiting for a request from an "area" that is assumed to be on the same subnet as the given pool?
    Do I need to somehow show the device what subnet the 2nd SSID/ subinterfaces are in so the internal DHCP server can decide it needs to go to work, or is there some sort of bridging between the DHCP server and the interfaces that needs to be done? I am trying to use the same DHCP pool for the second subnet at this point, since I assume I will need another router to service an additional subnet and DHCP pool.

    Keep in mind that DHCP is a broadcast packet to start. So the AP can only listen in the subnet that it has an IP address for.
    Now, for any other subnet you can use the AP for DHCP but you have to have an IP helper address on your L3 pointing back to the AP.
    That being said, I wouldn't use the DHCP server on the AP as it is limited. You'd be better off using a Microsoft server or some other device that is designed for DHCP.
    HTH,
    Steve

  • Phones not getting IP address via DHCP server on same VLAN

    Hello....we have a new series of Cisco SF-200s and one new Cisco SF-300.  All switches are operating in layer 2 mode currently.  Let's say for all intents and purposes, all ports are in VLAN1....pretty much default setup.  There is a fiber backbone between uplink ports...and it is working correctly it appears.
    There is a DHCP server allocating addresses 192.168.0.60 thru 192.168.0.79.  Subnet mask is 255.255.255.0.
    PCs and laptops successfully receive an IP address and can access things.....such as surfing the internet.  Tested that from multiple switches....all seems to work just fine.
    However, it seems that some newly purchased phones (Digium models) simply will not acquire an IP address like the PCs and laptops do.
    Pretty broad question....but just wondering.
    Thanks!

    Hi  Greg,
    Might be interesting to goto the following sections of the GUI disable the discovery protocols;
    1. Administration>Discovery -LLDP >properties
    2. Administration>Discovery -CDP >Management interface
    3  Smartports >Properties > Admministrative Auto Smartports  is disabled.
    the switches are real smart and may pre-empt what you are trying to achieve.
    regards dave

  • 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

Maybe you are looking for