RV320: DHCP Option 82 + DHCP relay at Ethernet switch
We purchased a RV320 router and want to use the DHCP Option 82 IP Assignment in combination with a ZyXEL GS1910-24 Smart Managed Switch.
The switch is able to insert Option 82 Circuit-IDs into DHCP requests, if they are relayed to a specific DHCP server. So there must be configured exactly one IP address of the DHCP server in the switch configuration (eg 192.168.1.1). The problem is, that the RV320 creates different IP subnets for different Circuit-IDs. So the RV320-router has multiple IPs, one unique IP per subnet (192.168.1.1, 192.168.2.1, 192.168.3.1, ...).
How can I use the Option 82 IP assignment with this configuration?
Is a routing/firewall rule at the RV320 a solution (to forward DHCP requests from subnet specific IP - eg 192.168.3.1 - to exactly one IP, eg 192.168.1.1)?
mpyhala,
seems not to work as the RV320 is restricted to 6 custom VLANs (+ 1 Management VLAN with ID 1).
Maybe I should describe the whole scenario, which should be implemented:
The configuration is like for a small hotel: each room should be logically seperated from each other (no inter-room traffic for security) and each rooms bandwidth should be managed.
Bandwidth management at the RV320 relies on IP addresses. So I need to achieve somehow, that a room (= port number on switch) is always assigned a specific IP address.
14 rooms should be covered in that way.
The problem is currently the link IP<->Switch Port. I thought DHCP option 82 is the way to go, but VLANs (one VLAN for each room) may be also a solution. Unfortunately none of the two ways work.
What can be a solution? Was the RV320 the wrong decision (not enough flexibility)?
Thanks.
Similar Messages
-
DHCP Option Tags are not being applied...
Hi,
About to loose my mind... basically we are working towards a small WYSE Thin Client deployment in our environment. The WYSE clients require to receive certain DHCP Option Tags to find the WCM server of which they receive their configuration from. Same
applies to the WDM Server as well. The problem is no matter what we do, our test client is not receiving the custom option tags we've defined in our DHCP server.
DHCP Servers:
vlan41
10.40.1.206
10.40.1.207
Test Client:
vlan46 - ip helpers defined on the switch
Set to receive the same ip address from the DHCP server through the reservation route.
Option Tags:
186 - WDM Server - 10.40.1.184
195 - WCM Server - 10.40.1.185
196 - WCM Path - /
I've installed Wire Shark on the test client to monitor the DHCP activity. The above custom options tags are not being pushed on to the client.
The Router, DNS Server and Domain Tags are being pushed. So it's working but also not working????!!!
Anybody with some insight to this problem?Hi hpaul_p
In all fairness I'm about to give up... the vendor is not coming up with a solution and constantly blaming Microsoft. To further test and confirm this wasn't a network issue, I've setup a secondary test environment using a 4 port switch, a client and
a DHCP server. Same results!!! I'm really running out of time, so my work around is this: I've setup a SRV records pointing to the WCM server... in your case this would be SRV record for the WDM server. I've disabled the auto
discovery functionality of the WDM Agent, for some reason it seems to be clashing with the WCM agent. Since you will be using WDM only, don't disable auto discovery, tick the DNS SRV record from the Discovery Settings under the client agent.
I'm going to add the clients to the WDM server manually through their ip addresses so don't need auto discovery. From what I gather from the manuals the WCM searches for the repository or conifg servers in this order: 1. SRV 2.DNS (A record)
3.DHCP (Options), I bet it's the same with WDM. Though SRV and DNS methods has their limitations, if you will be using the default paths and credentials it shouldn't be a problem. This is all I have have. Steven Song I've forwarded you the
DHCP database, if you find any problems with it please let me know. -
If DHCP option 82 is supported, how can I add it to my server?
Thanks, I upgraded software to newest 1.3.0.59, then rebooted. After configuring ( only option 82 - no relay agent ) there is still no 82 option in dhcp discover packets.
Wireshark with captured dhcp discover broadcast packet. Dhcp part:
As You can see - there is no 82 option.
All interfaces are trusted (dhcp snooping).
Should I configure anything else to make it work ?
regards, -
3000 series and Multiple DHCP scopes (DHCP-relay)
I need to send different DHCP options to users; however, I need to put certain groups in different subnets. Is it possible to setup the concentrator to relay for addresses from different scopes?
- Configuration
- System
- IP Routing
- DHCP Relay
a. Enable 'Enabled' checkbox
b. Select Forward to
c. Address == 192.168.10.8 255.255.255.0
- Address Management
- Assignment
a. Enable 'Use DHCP'
- User Management
- Groups
- Select 'groupA'
- Modify Group
- Click General tab
- Enter 'DHCP Network Scope' x.x.x.x
- Select 'groupA'
- Remove Address Pool
Now I get the following error:
118 02/08/2005 13:29:00.720 SEV=3 DHCPDBG/39 RPT=34
DHCP discover timeout: no response from polled servers (xid 3821297335)
I can ping the server, and it is serving up this scope to other devices (just not from the concentrator) -
Dear all,
I've got an issue trying to perform dhcp relay in a following topology:
The goal is for dhcp server to offer an ip address, according to option 82.
It seems like dhcp server can recognize the value in a link selection option, but still uses giaddr to see from which address pool to offer.
DHCP Server
ip dhcp excluded-address 192.168.20.1 192.168.20.2
ip dhcp pool VPN1
vrf test-vrf-R2
network 192.168.20.0 255.255.255.0
class VPNCG1
address range 192.168.20.2 192.168.20.254
ip dhcp pool VPN2
vrf test-vrf-R3
network 192.160.30.0 255.255.255.0
ip dhcp class VPNC1
ip dhcp class VPNCG1
relay agent information
relay-information hex 970c00746573742d7672662d52329604c0a814009804c0a81401
relay-information hex 1a970c00746573742d7672662d52329604c0a814009804c0a81401
relay-information hex 521a970c00746573742d7672662d52329604c0a814009804c0a81401
no ip domain lookup
ip cef
no ipv6 cef
multilink bundle-name authenticated
redundancy
ip tcp synwait-time 5
interface Ethernet0/0
ip dhcp relay information trusted
ip address 10.100.0.1 255.255.255.0
R2
vrf definition test-vrf-R2
address-family ipv4
exit-address-family
ip dhcp relay information option vpn
no ip domain lookup
ip cef
no ipv6 cef
multilink bundle-name authenticated
interface Ethernet0/0
ip address 10.100.1.2 255.255.255.0
interface Ethernet0/1
no ip address
shutdown
interface Ethernet0/2
no ip address
shutdown
interface Ethernet0/3
no ip address
shutdown
interface Ethernet1/0
vrf forwarding test-vrf-R2
ip address 192.168.20.1 255.255.255.0
ip helper-address global 10.100.0.1
DHCP Server debug output
*Mar 6 13:33:13.724: DHCPD: client's VPN is test-vrf-R2.
*Mar 6 13:33:13.724: DHCPD: No option 125
*Mar 6 13:33:13.724: DHCPD: Giaddr from server-id-override suboption 192.168.20.1
*Mar 6 13:33:13.724: DHCPD: Sending notification of DISCOVER:
*Mar 6 13:33:13.724: DHCPD: htype 1 chaddr aabb.cc00.0500
*Mar 6 13:33:13.724: DHCPD: remote id 020a00000a64000100000000
*Mar 6 13:33:13.724: DHCPD: circuit id 00000000
*Mar 6 13:33:13.724: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d61.6162.622e.6363.3030.2e30.3530.302d.4574.302f.30 through relay 10.100.1.2.
*Mar 6 13:33:13.724: DHCPD: Seeing if there is an internally specified pool class:
DHCPSrv#
*Mar 6 13:33:13.724: DHCPD: htype 1 chaddr aabb.cc00.0500
*Mar 6 13:33:13.724: DHCPD: remote id 020a00000a64000100000000
*Mar 6 13:33:13.724: DHCPD: circuit id 00000000
*Mar 6 13:33:13.724: DHCPD: there is no address pool for 10.100.1.2.
DHCPSrv#
*Mar 6 13:33:15.639: DHCPD: client's VPN is test-vrf-R3.
*Mar 6 13:33:15.639: DHCPD: No option 125
*Mar 6 13:33:15.639: DHCPD: Giaddr from server-id-override suboption 192.168.30.1
*Mar 6 13:33:15.639: DHCPD: Sending notification of DISCOVER:
*Mar 6 13:33:15.639: DHCPD: htype 1 chaddr aabb.cc00.0600
*Mar 6 13:33:15.639: DHCPD: remote id 020a00000a64000100000000
*Mar 6 13:33:15.639: DHCPD: circuit id 00000000
*Mar 6 13:33:15.639: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d61.6162.622e.6363.3030.2e30.3630.302d.4574.302f.30 through relay 10.100.2.2.
*Mar 6 13:33:15.639: DHCPD: Seeing if there is an internally specified pool class:
DHCPSrv#
*Mar 6 13:33:15.639: DHCPD: htype 1 chaddr aabb.cc00.0600
*Mar 6 13:33:15.639: DHCPD: remote id 020a00000a64000100000000
*Mar 6 13:33:15.639: DHCPD: circuit id 00000000
*Mar 6 13:33:15.639: DHCPD: there is no address pool for 10.100.2.2.
DHCPSrv#Hello,
can you provide an updated link?
This one is dead:
Govind [MSFT] - Bereitgestellt am Montag, 13. August 2007 05:53:48
http://blogs.technet.com/teamdhcp/archive/2005/09/21/411344.aspx
Or is there another article that describes how to configure a Windows DHCP Server 2003
with option 82?
Thx! -
Adding DHCP options into bootpd.plist
Hello All,
I'm having issues inserting DHCP options 66 and 67 into the /etc/bootpd.plist file. I'm a bit baffled by this task and it's not rocket science so I really don't understand why this is not working the way it should.
Goal:
I'm setting up a dual platform imaging server for the company I work for using DeployStudio. I have the mac side imaging 100% perfectly with no issues. Now, the PC side is a different story. I can get the PC machines to PXE boot just fine, DHCP IP address received, then continues to load the imaging applications console and then hangs with a tftp error.
We are running Mountain Lion 10.8.4 and using OS X Server 2.2.1
the options I added are 66 and 67.
Option 66:
10.10.10.2 is the IP address I want to use.
Option 67:
pxelinux.0
I've added my bootpd.plist file below and bolded the data I entered into the file. I don't even know if I entered the data into the right place or it needs to go somewhere else. I really don't know if i'm inserting the correct data I need into options 66 and 67. I've sat there and read the man page for bootpd and it provided very little to no information on the topic.
Thanks in advance!!
================================================================================ =======
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NetBoot</key>
<dict/>
<key>Subnets</key>
<array>
<dict>
<key>allocate</key>
<true/>
<key>dhcp_domain_name</key>
<string>no-dns-available.example.com</string>
<key>dhcp_domain_name_server</key>
<array>
<string>0.0.0.0</string>
</array>
<key>dhcp_option_66</key>
<data>
CgoKAg==
</data>
<key>dhcp_option_67</key>
<data>
cHhlbGludXguMA==
</data>
<key>lease_max</key>
<integer>3600</integer>
<key>name</key>
<string>10.10.10 USB Ethernet</string>
<key>net_address</key>
<string>10.10.10.0</string>
<key>net_mask</key>
<string>255.255.255.0</string>
<key>net_range</key>
<array>
<string>10.10.10.2</string>
<string>10.10.10.253</string>
</array>
<key>selected_port_name</key>
<string>en1</string>
<key>uuid</key>
<string>EE34E237-9C59-42A9-BB26-9B54CEE66447</string>
<key>dhcp_option_66</key>
<data>
CgoKAg==
</data>
<key>dhcp_option_67</key>
<data>
cHhlbGludXguMA==
</data>
</dict>
</array>
<key>allow</key>
<array/>
<key>bootp_enabled</key>
<false/>
<key>deny</key>
<array/>
<key>detect_other_dhcp_server</key>
<false/>
<key>dhcp_enabled</key>
<array>
<string>en1</string>
</array>
<key>old_netboot_enabled</key>
<false/>
<key>relay_enabled</key>
<false/>
<key>relay_ip_list</key>
<array/>
<key>timeServiceStarted</key>
<string>2013-07-31 22:32:12 +0000</string>
</dict>
</plist>Hey John,
Been reading many of your posts and they all seem quite helpful, but I'm also stuck trying to configure options 66 & 67.
I'm running Server 3.1.2 on Mavericks, your utility to generate the options seems to work, but I'm not sure where to place them in the file, tried a few different locations without success. Here is my current bootpd.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NetBoot</key>
<dict>
<key>startTime</key>
<string>2014-06-30 18:29:49 +0000</string>
</dict>
<key>Subnets</key>
<array>
<dict>
<key>allocate</key>
<true/>
<key>dhcp_domain_name</key>
<string>domain.ad</string>
<key>dhcp_domain_name_server</key>
<array>
<string>172.16.10.10</string>
<string>172.16.10.7</string>
<string>8.8.8.8</string>
</array>
<key>dhcp_option_66</key>
<data>
rBAKEw==
</data>
<key>dhcp_option_67</key>
<data>
cHhlbGludXguMAA=
</data>
<key>dhcp_domain_search</key>
<array>
<string>domain.ad</string>
</array>
<key>dhcp_router</key>
<string>172.16.8.1</string>
<key>lease_max</key>
<integer>3600</integer>
<key>name</key>
<string>172.16.8/22 Ethernet</string>
<key>net_address</key>
<string>172.16.8.0</string>
<key>net_mask</key>
<string>255.255.252.0</string>
<key>net_range</key>
<array>
<string>172.16.8.10</string>
<string>172.16.11.253</string>
</array>
<key>selected_port_name</key>
<string>bond0</string>
<key>uuid</key>
<string>0F3374EB-FDDA-4DCD-A8F8-E5CDFC661A99</string>
</dict>
</array>
<key>allow</key>
<array/>
<key>bootp_enabled</key>
<false/>
<key>deny</key>
<array/>
<key>detect_other_dhcp_server</key>
<false/>
<key>dhcp_enabled</key>
<array>
<string>bond0</string>
</array>
<key>netboot_enabled</key>
<array>
<string>bond0</string>
</array>
<key>old_netboot_enabled</key>
<false/>
<key>relay_enabled</key>
<false/>
<key>relay_ip_list</key>
<array/>
<key>timeServiceStarted</key>
<string>2014-07-02 15:16:23 +0000</string>
</dict>
</plist>
I have a Fog server handling my Windows imaging on 172.16.10.19, using pxelinux.0 (all tested through a TFTP client), but when I boot a Dell into PXE, it finds an IP address but the output for the TFTP server looks like this:
TFTP.
Then it just exits, before it should show the IP address of the TFTP server.
I do have the option of using DHCP on a Windows Server VM, but I'd rather have my Mac Mini do it. -
SF302-08 - CLI configuration of dhcp option 66
Hi,
i'm trying to use cli to configure dhcp option 66 but i'm getting this error below.
thanks
switch702df6(config-dhcp)#ip dhcp pool network Voice
switch702df6(config-dhcp)#option 66 ascii-string "http://provisioning.domain.tld/$MA.xml"
% Wrong number of parameters or invalid range, size or characters enteredHi Luis, I do not believe option 66 is supported.
1, 3, 4, 6, 12, 15, 44, 46, 50, 51, 53, 54 55, 56, 58, 59, and 61.
If you remove the name of your file, you will notice the switch declares it is an unsupported option
switchb28f36(config-dhcp)#option 66 ascii test
Not supported option.
-Tom
Please mark answered for helpful posts -
Guest LAN and DHCP Options not passing through
Managed to get the Guest LAN up and running for wired clients and all's working well. Users are sat behind a proxy and if I force the use of a appropriate wpad file I can get the WLC auth to happen and then push off to the proxy.
I'm trying to use option 252 in DHCP to present the WPAD url. Only issue that happens is that while the DHCP server on the egress interface is handing out addresses to clients on the ingress interface correctly, the WLC doesn't appear to be handing through the option 252 I have set in DHCP. I've used network monitor to see what the dhcp request process is dishing out in terms of options, and all look good if I'm not behind the WLC.
Anyone know if theres a limitation on the WLC that prevents DHCP options being passed through to the guest LAN?
TIAWhen configured as a DHCP server, some of the firewalls do not support DHCP requests from a relay agent. The WLC is a relay agent for the client. The firewall configured as a DHCP server ignores these requests. Clients must be directly connected to the firewall and cannot send requests through another relay agent or router. The firewall can work as a simple DHCP server for internal hosts that are directly connected to it. This allows the firewall to maintain its table based on the MAC addresses that are directly connected and that it can see. This is why an attempt to assign addresses from a DHCP relay are not available and the packets are discarded. PIX Firewall has this limitation.
For more information please refer to the link-http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008070ba8f.shtml -
I'm wondering if anybody knows some way to configure the AEBS to distribute DHCP options - specifically, the TFTP server option 150. I've got a piece of development hardware that I have to flash over TFTP.
It's actually a home-theater receiver that I've been developing the firmware for. I had been simply running it in my lab on a separate network served by DHCP Turbo in Windows, but now I've moved it to my living room, so I can actually use the thing. It's stable in the lab, so I want to get some real-world use on it. I don't have a separate network drop out there - just the AEBS network.
I have a clunkier way to flash it, but I prefer using the netboot built into the receiver's CPU, which requires DHCP, and Option 150. There's no NV storage for the server address on board, without adding dedicated hardware.
The real problem here is that I actually want the thing on the AEBS network, since I've added a lot of internet connectivity to the box The separate network would just be for flashing, and so I have to keep switching networks between flashing and debugging. This will be even more of a pain, now that I've moved the receiver out of the lab.
I was hoping somebody knew about some super-secret backdoor configuration for the AEBS DHCP server. Not at all optimistic about this, but hope springs eternal.
My fallback is to set up a separate wireless network out to the living room, and keep running out to manually switch networks. Yuck.
-RickNovell's dhcp console only goes to Option 133...
If you have C-1, you might be able to add option 150 manually to the DHCP object. I've done something like that before for another option which never seemed to work well once you added it through the DHCP console...
--El
Originally Posted by netwo
Hi,
Is thers a way to add option 150 for dhcp for an array of tftp servers?Im using oes2 sp3.
thanks, -
I have a Catalyst 3750 switch at a remote location that hands out DHCP addresses to clients.
I need to enable options 66 & 67 for remote-boot capabilities, but I am not sure on the syntax to use.
on a windows DHCP server, the setting for 67 is
067 Bootfile Name standard Boot\x86\wdsnbp.com
how would I put that into the DHCP options on the switch?ip dhcp pool DATA_LAN
network 10.250.1.0 255.255.255.0
default-router 10.250.1.1
option 66 ip 10.250.1.2
option 67 ascii smsboot\x64\wdsnbp.com
dns-server 10.111.18.241 10.111.18.242
domain-name corp.shire.com
ip dhcp excluded-address 10.250.1.1 10.250.1.10 -
Multiple domains via DHCP (option 15)
It seems Mac OS X (I use 10.4.10 but I suspect it affects many versions) is incompatible with receiving multiple domain names in a single string over DHCP Option 15.
If DHCP returns Option 15 with "exampledomain.com eng.exampledomain.com", then any lookup (using dig, ping, Microsoft Entourage, etc.) of a non-fully qualified domain name will fail.
You can see this in the /etc/resolv.conf file, which contains:
domain exampledomain.com eng.exampledomain.com
nameserver 10.X.X.1
nameserver 10.X.X.2
I know that putting multiple domains within the same "domain" option in DHCP is a proprietary hack but some networks still use this. Has anybody run into this and have they found a good resolution to make Mac OS X work with multiple domains?While a single mailbox can be configured to receive on multiple addresses (called "proxy addresses" or "aliases"), the mailbox is configured with only one primary SMTP address (outbound address). So if your requirement is to send
as the received address, you would not be able to do that with a single mailbox through normal means.
Some people have developed a workaround to the above limitation by configuring Outlook to use multiple POP3 accounts for a single mailbox. See this link for additional details:
http://blogs.technet.com/b/hot/archive/2012/04/26/how-to-add-an-alias-to-an-office-365-account-and-how-to-set-up-outlook-to-send-email-messages-as-this-alias.aspx
I would also be sure to look at the client requirements for Exchange Online. The supported version of Outlook is going to be Outlook 2010 SP2. Older versions may work but would not be supported. Outlook 2003 would at best possibly
connect via POP3.
Joseph Palarchio http://www.itworkedinthelab.com -
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. -
Implement DHCP Option 60 in SPA100 series
Hello,
Is there any plan to implement DHCP Option 60(vendor class id) in SPA100 series devices in future FWs? CISCO SPA5xx series already has this option implemented.
Regards,
Josep.I'm not sure what exact device you mean saying "SPA100 series devices" but in SPA112 and SPA122 it is implemented already. I'm using it for long time. See catched packet:
0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
Hostname Option 12, length 6: "SPA112"
Vendor-Class Option 60, length 12: "CISCO SPA112"
Don't forget to mark thread as answered if it answers your question ... -
As default, SPA122 and SPA112 have DHCP Options 66, 160, 159 and 150 turned on.
Our pre-provisioning process includes adding our default profile rule to our provisioning server for the device to pull its configuration files once the device has been added to an account.
However, it seems like some customers have had problems with the device downloading the definite configuration file and manually turning off option Option 66 in the provisioning tab in the device solves this issue.
Is there any option we could add to our pre-provisioning file so that it removes 66 from the "DHCP Option to Use" field in the provisioning tab?
Please advise...Thanks Dan,
I didn't know the dhcp server could serve different options to different classes of clients, I'll have to look that up!
Moises
so if your provisioning file has this line below (this is from a spa5xx config I had in my temp folder, so use the line from your provisioning file, or use the SPC tool to create a new default config for that device type)
<DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">66,160,159,150,60,43,125</DHCP_Option_To_Use>
change it to
<DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">160,159,150,60,43,125</DHCP_Option_To_Use>
Hope it helps,
Provisioning guide is here
Cisco IP Telephony Devices Provisioning Guide - Cisco Support Community
Dan -
Dnsmasq sends out its own ip as dns-server dhcp option
Hi,
i have a gateway / dns server on 192.168.1.1
I have a dhcp server on 192.168.1.2 (dnsmasq)
I configured dnsmasq to look into /etc/resolv.conf (well, that's actually default behavior) and use that to specify dns server when replying to client dhcp requests.
However, it sends out its own ip instead, which is *not cool*.
# cat /etc/resolv.conf
nameserver 192.168.1.1
#nameserver 127.0.0.1
#nameserver 212.71.0.33
# edpnet
nameserver 212.71.0.33
# grep -v ^# /etc/dnsmasq.conf | grep -v '^$'
domain-needed
bogus-priv
dhcp-range=192.168.1.5,192.168.1.255,12h
dhcp-host=q700
dhcp-host=dieter-ws
dhcp-host=dieter-dellD620-arch
dhcp-host=gibran
dhcp-host=hilde-compaq-arch
dhcp-host=hilde-vbox-win
dhcp-host=BRN_0441B3
dhcp-option=option:router,192.168.1.1
log-dhcp
# cat /etc/hosts
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
192.168.1.2 dieter-p4sci-arch server
192.168.1.3 q700
192.168.1.5 dieter-ws
192.168.1.6 dieter-dellD620-arch
192.168.1.7 dieter-delle5410-arch gibran
192.168.1.8 hilde-compaq-arch
192.168.1.9 hilde-vbox-win
192.168.1.10 BRN_0441B3 hl5250
178.79.146.162 dieter-linode1
# End of file
here's what I see in /var/log/daemon.log, when I start dnsmasq and do a dhcp request.
Note the discrepancy between what it says as "using nameserver" and what it actually tells clients.
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: started, version 2.55 cachesize 150
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq-dhcp[2168]: DHCP, IP range 192.168.1.5 -- 192.168.1.255, lease time 12h
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: reading /etc/resolv.conf
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 212.71.0.33#53
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 192.168.1.1#53
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: read /etc/hosts - 10 addresses
Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 DHCPRELEASE(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPDISCOVER(eth0) 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPOFFER(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 02
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.1
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPREQUEST(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPACK(eth0) 192.168.1.5 80:ee:73:09:fa:94 dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 05
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 9 option: 12:hostname dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.11 yes, the dhcp server who's scope is full will not do a dhcp
'offer'
2 dhcp that answers fastest with a 'offer' will win. A delay is configurable (but changes nothing
about the root scenario were the fastest will win)
Note that if the scopes overlap on the servers, they might not lease out all the addresses in the scope.
I would enlarge the scope as you will want to fence against unavailability of one of the servers (or a network connection for that matter). you currently have more addresses leased out than any set of two of your servers can offer.
MCP/MCSA/MCTS/MCITP
Maybe you are looking for
-
i am trying to install oracle 11g xe on ubuntu aws instance when i execute sudo /etc/init.d/oracle-xe configure command iam getting this error: sudo: /etc/init.d/oracle-xe : command not found.
-
My wife and i ahev two user set up our pc. we both have itunes with different content. I would really like to combine them..is this possible
-
Integration Repository: change XSD type in data types
Hi, we created data types for our interface where we used the XSD type float and integer. We built on that Message types and Message interfaces and used them as abstract types in a BPM scenario. During our test phase we encountered errors with these
-
Exchange server send email issue
I can receive but not sent emails to my 1 and 1 exchange server. Some time ago my exchange email started playing up on my I phone, i don't use it often so i ignored it. Shortly after followed problems with my iPad and my mac. I talked to my service p
-
Problems downloading IOS 5 to Ipad
Is it normal to take hours to download IOS 5 to my Ipad? It seems to freeze or slow down midway through download, so I cancel. I have yet to succeed downloading IOS 5. Could it possibly be my personal computer (which is old) or the downloading proc