CRIO failing to get a DHCP assigned address

I just went through heck with my IT deparment on this so thought I'd post it here.
I had four cRIO-9073s on a remote switch in one of our labs, that MAX (Measurement and Automation Explorer) was saying were using Link-local addresses. In fact, all were using the EXACT SAME address: 169.254.62.215. Very strange! I was able to talk to them using MAX some times, doing remote restarts, etc., but other times not. All were configured to grab a DHCP address or fall back to link-local.
As it turns out, the RIOs were attached to a Cisco switch that has a feature callled STP fully enabled on all ports. STP is designed to prevent accidental loops in the network from downing your network, and that feature blocks all initial transmissions from attached devices for 30 seconds before letting them through, while it "listens" and "learns" about your device, analyzing to make sure that letting it connect won't create a loop. Apparently this 30 second delay (forever in computer terms!) is too long for the cRIOs, so they take a link-local address, and since they can't even check the network for other link-local users because their transmissions aren't being forwarded, they all take the exact same address. I'm still amazed MAX can find them under these conditions!
The way to get it working is to turn on "PortFast" on the Cisco switches, which simply disables the steps in STP that cause the slowdown (blocking, listening, learning). Fortunately this can be done on a port-by-port basis, as it's recommended to NOT turn it on if ports are going to another switch (as that then opens the door for a loop).
Here's more info:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a00800b1500.shtml
Here's hoping you don't need this!

Hello Erik,
Thank you very much for the post. Great work figuring out the root cause of your communication issue!
Cameron F
Applications Engineer
National Instruments

Similar Messages

802.1x and DHCP assigned addresses

I've done a lot of reading on this but I am still confused. I'm not a Microsoft guru so I don't really know waht is going on with login scripts, or cached user/pass.
Scenario 1
==========
I have 802.1x implemented and Joe the contractor comes into the office and plugs in his laptop. He is a guest. I allow guests to have access to a guest VLAN. How can Joe automatically get an IP address, or does he have to do ipconfig /renew?
Scenario 2
==========
What is the behind the scenes process that takes place for my corporate users that login to a domain....how do they get DHCP assigned addresses?
Thanks

I assume from what you have written 'Joe' doesn't have an 802.1x supplicant on his PC? Therefore the switchport eapol frames are ignored by the PC and after a timeout the port is placed in the guest vlan. You need to make sure DHCP is enabled for the guest vlan - either add the appropriate entried to the protecting ACL or add a scope on the router? Depending on the timeouts you may have some delay issues here; I would test this before you roll it out.
For clients with 802.1x supplicants what happens is the PC effectively thinks it is disconnected from the network until the supplicant has authenticated. Once it has authenticated the PC thinks the network adapter is then connected and it will attempt to lease an IP address by broadcasting a DHCP request.
There are however a few 802.1x supplicants and I am not sure how they all integrate with the host O/S. I know the built-in Microsoft one operates as I have described.
HTH
Andy

EA4500 Won't get a DHCP WAN address from Cable Modem

I have an EA 4500 that I used to replace a bad WRT45 (or something like that). We have an ADT camera system that allows you to view the cameras locally and remotely. All I have to do is set a static internal address on the DVR and the public IP on the router in the application. I duplicated the setting in the old router and everything was running smoothly. However, the speed test result I was getting from the router and speedtest.net were not even close to what we were paying for (wireless and wired. But it was functional.
I called Comcast and they said we needed a Docsis 3 modem. So, I went to the Comcast office and they traded out my modem for a docsis 3. Hooked it up and everything was working again. Speeds were better but not really up to par. Hooked my laptop directly into the new modem and I was getting speeds off the charts. Frustrated, I called Comcast, they said the modem needed to be put in Bridge mode. Then the EA4500 wouldn't get a DHCP WAN adress. They took it out of bridge mode. Same result.
They sent a tech out (Mind you I've been a Network Engineer for almost 20 yrs) and he tells me they gave me the wrong modem (I wasn't there either, roommate let him in). He replaced the modem with a new all inclusive router/switch/wifi modem. He then proceeds to setup a whole new network, which of course , except the laptops that connected, my devices don't see ( printers, cameras, dvr, etc). Then, this baffles me... he did a factory reset on my EA4500. So now there are 2 seperate networks one with slow Internet and one without WAAN services.
After all this, my EA4500 still will not get a WAN address when plugged into the new modem. I would just use their new modem but to make any config changesto it, something as simple as changing the SSID name or the password, you have to call them. They won't give you access to the admin page.
Anyone have any ideas why my EA4500 won't get a WAN address? Oh, btw, I did do a MAC address clone on the EA4500 while connected to the modem and it DID get the address, but the speeds were dismal, not even 1mb up or down.

@stix180
There is a need to reset and reconfigure the EA4500 router to work with the new modem. There are certain configurations on the router that will make it work for a particular modem, and this might be causing the issue. Cable modem authenticates end users through username and password but there are cable modem/router as well in which the IP address are on the same range with the default IP address of the router. Please try to check the IP address of the computer wired directly to your modem, it should not be on the same IP address range with the EA4500 router since it will cause IP address conflict. You can change the default IP address of your router from 192.168.1.1 to 10.10.10.1. Please try to make sure that your router also has the latest firmware version installed. And it would help if you do port forwarding on the router for your camera and DVRs to resolve NAT issues.

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?

DHCP client fails to get an valid IP address from DHCP server. windows 8.1

I have a win 8.1 Pro 64 bit pc in my office .I'm trying to connect it to my wireless cisco router with either wireless or hardwired connection but I get an error in the event viewer with discription DHCP error 1007. and Ip address showing
169.254.93.17 but our dhcp range is 192.168.1.x
Log Name: Microsoft-Windows-Dhcp-
Source: Microsoft-Windows-Dhcp-Client
Date: 23/Jun/2014 12:03:21 PM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords: (1)
User: LOCAL SERVICE
Computer: sanddeplap.vts.com
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xF4B7E22D8721. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its
own from the network address (DHCP) server.
Event Xml:
<Event xmlns="http://schemas.">
<System>
<Provider Name="Microsoft-Windows-Dhcp-
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000001</
<TimeCreated SystemTime="2014-06-23T08:03:
<EventRecordID>363</
<Correlation />
<Execution ProcessID="988" ThreadID="7932" />
<Channel>Microsoft-Windows-
<Computer>sanddeplap.vts.com</
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">F4B7E22D8721<
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
I tried to track issue with microsoft network monitor I'm attaching the capture file also please help me to sort out this issue
capture report https://onedrive.live.com/redir?resid=AFE3D0245A92F6F8%21183

The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
address.
So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

WRT54G2 V1 Fails to get WAN DHCP address

Hi All,
I have a new WRT54G2 V1 that works fine, with the exception it will not pickup a DHCP address from the cable modem. I have gone through the standard steps assuring the modems, cables and computers work on other setups and have no issues there.
The wireless and hub portions of the G2 work as usual. I flashed the firmware to the latest FW_WRT54G2V1_1.0.04.005_US and there is no change in operation, also the G2 responds correctly to a full reset to factory settings.
On the router's reboot the WAN light comes on briefly (assume self-test), but remains off after the router is fully booted.
Have I forgotten something obvious, or is this an out-of-the-box failure ?
Cheers,

Once more step which you can try is, connect the Ethernet cable to the LAN Port 1 and the other end of that cable to the Internet Port of the Router and then check if the WAN light on your Router lids or not...
If it still doesn't lid, then i think it might be the problem with the Router itself, and you need to replace your Router.

How to set up both static and DHCP assigned addresses on an AirPort Extreme

I recently bought an AirPort Extreme to replace my failed Cisco/Linksys router.
I am having trouble figuring out how I can configure the Extreme to support the already static IP addresses on my network as well as assign IP addresses via DHCP to a few devices where static IPs are not supported, i.e., work laptop.
Additionally, when DHCP is turned on, are my only options the 10.0, 172.16, and 192.168? What if I am running something like 10.10 or 172.30?
I am far from green when setting up computer networks, but this AirPort Extreme is making me pull my hair out.
BTW, I have access to a number of computers running a number of OSes including Windows XP, 7, and 8, as well as Mac OS X Snow Leopard and Mountain Lion.
The Mountain Lion or Windows 7 machine would be the preferred ones to configure the Extreme. I already have the AirPort Utility software running on them.
Any help would be appreciated.

I have found the 'DHCP Reservations' option on the AirPort Extreme to be buggy. I seem to remember it causing IP conflicts for some reason. I think what I remember is that if the computer with the reservation was off, and the DHCP server then handed out that IP to another DHCP client, then there would be a conflict when the reserved IP computer was turned back on. Maybe it was an issue in ealier versions of the AE or OS X as the case may be, and maybe it's been corrected, but I've never bothered using it agian since the method I describe below has always worked without fail. Also, I'm guessing DHCP Reservations would work fine if one manually enters IPs outside of the DHCP range but in the AE 'DHCP Reservation Setup Assistant' the IP options provided are within the DHCP range which to me makes no sense and increases the potential for IP conflicts.
Here's what I do to setup a mixed environment of static and dynamic IPs on my network. It works like a charm and does not require the DHCP server (beyond the distribution of dynamic IPs to hosts using DHCP).
For machines on my network that are accepting services from the public network, I set them up with static IPs using the 'Manually' option (System Preferences/Network/Ethernet/Configure IPv4). The settings for 'Router' IP address and 'DNS Server' IP address should both be set with your gateway/router LAN IP). Use an IP address below or above the DHCP range of adresses (in AE/Internet/DHCP/DHCP Beginning & Ending Address).
i.e. if my subnet is 10.0.1.1 and my DHCP range is 10.0.1.100 to 10.0.1.150, you could set the static IPs on your local hosts as 10.0.1.x where x = any number from 2 - 99 or from 151 - 200 as an example.
All other machines and devices that do not require static routing are setup as DHCP clients and get a dynamic IP from the AE. To me it's a simpler setup though it might take a little extra time to setup initially.
John

DHCP assign address range to AD computer groups - possible?

Not by OU, no. DHCP doesn't interrogate AD.

Hello
Does anyone know if it's possible to get the Windows DHCP server to assign an address range to a group of computers in Active Directory? Is it possible?
This topic first appeared in the Spiceworks Community

Since 10.7.4 update keep getting wifi self assigned address message. I can get on with iMac but can't share the wifi with my iPad.

Anyone have any fixes?

This is confusing as you say in the first post you have Lion installed and want to upgrade to Mavericks, and in your second post say Mavericks is installed. If you have Mavericks installed, what are you trying to upgrade?
As to your request in the first post, there is no DVD or USB version of Mavericks available. Mavericks is only available by Internet download.

AEX fails to get DHCP address, but works on DLink

Sorry for the long post -- I'm hoping the details will help you diagnose the problem faster in the long run.
My DLink router gets a DHCP IP address from the (Comcast) cable modem, but when I switch to the AirPort Extreme (5th gen, refurbished), it doesn't. It shows an autoconfiguration IP address of the 169.254 variety, suggesting that DHCP isn't working for the AEX. (Just fyi, my girlfriend's macbook can connect to the AEX and get 10.0.1.x IP addresses; I can ping the AEX over wifi.)
Airport Utiltiy shows a red number 2 with a single error indicating Internet failure to get IP address or something. The suggested solution is power-cycling the modem; failing that, contact the ISP. Contacting Comcast was amusing but useless...they gave me instructions for setting up AEX with a DSL modem -- twice -- without understanding my objection!
The AEX is configured for DHCP (not Static or PPPoE), and uses all stock settings (I did both a soft reset and used the Airport Utility to restore default settings...not sure if those two are the same).
I've tried power-cycling the router and cable modem numerous times, including leaving them off for 15+ minutes and leaving the AEX connected for 6+ hours. I tried using the DLink to release the DHCP reservation and then quickly switching the cable over to the AEX.
I read somewhere that resetting the "CMTS (cable modem termination system)" might help. I mentioned it to the Comcast tech support, but they didn't respond.
At this point, I'm not sure what else to try. It could be the refurbished unit is broken, but 95% of the time these sorts of things are configuration issues. (I know a fair amount about networking, but I'm new to Apple products so I could be doing something stupid.) I may try connecting the AEX to the LAN side of the DLink to see if it can get a DHCP address from that...but I'm clearly grasping at straws.
<whimpers>...Help?

Update: The AEX does get a DHCP address when connected to the LAN side of the DLink gateway. (But the AEX doesn't get one when connected directly to the cable modem. Yet the DLink gets a DHCP address when connected to the cable modem.) So...??!?!!!

DHCP Assigned IPs

My old D-Link router had a table where I could tell the DHCP server to assign specific IPs based on the MAC address of the device. I can't find a place in the WRT54G to do this. Do I have to go to each device and assign a fixed IP at the device? I like to keep the DHCP server active for setting up new devices and visitors. By using DHCP in my devices I don't have to reconfigure when I travel. With the old D-Link this worked find. It appears this could be a problem with the WRT54G. Am I missing something? Thanks, Bob

You are correct. The WRT54G does not support the "DHCP reservation" feature. However, several of the newer Linksys wireless n routers support this feature.
With the WRT54G, you can manually assign your computers a fixed LAN IP address. You can also have a fixed address on some computers, while others take their address from the WRT54G's DHCP server. Generally, unless you have a specific need for a fixed LAN IP address (for example, some online games require this for port forwarding to work properly), you should use a DHCP assigned address.
Linksys has some specific rules about assigning fixed LAN IP addresses. They are different from the D-Link.
Rules for using fixed LAN IP addresses on Linksys routers:
With Linksys routers, a fixed (static) LAN IP addresses must be assigned in the device that is using the address. So you need to enter the fixed address in the computer or printer, not in the router.
When using a Linksys router, any fixed LAN IP address must be outside the DHCP server range (typically 192.168.1.100 thru 192.168.1.149), and it cannot end in 0, 1, or 255.
Therefore any fixed LAN IP address would normally need to be in the range of
192.168.1.2 thru 192.168.1.99 or
192.168.1.150 thru 192.168.1.254
assuming you are still using the default DHCP server range.
Also, in the computer, when you set up a static LAN IP address, you would need to set the "Subnet mask" to 255.255.255.0 and the "Default Gateway" to 192.168.1.1 and "DNS server" to 192.168.1.1
It is also important that no two devices on your network be set to the same static LAN IP address.

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]

Setting up new imac on network using dhcp nut not getting a valid ip address. Same happens when I try to connect via wi-fi. IP address being assigned is 10.45.190.195

Have new Imac that I'm setting up. Company is using DHCP to manage IP addresses. Mac is plugged into netgear hub along with a PC. Mac is getting an invalid IP address of 10.45.190.195. PC is working fine. I've powered the hub on and off. I've renewed th DHCP lease on the Mac many times but IP address always comes back as 10.45.190.195. I've plugged the network cable directly in the network port bypassing the hub. Same result.
Having the same issue when trying to connect via Wi-Fi,
Anyone experiencing this issue?

I see what you are saying. When I lived in the dorms, I was set up in bridge mode because we had that type of modem. My question now is do I distribute a range of static IP's or share a public? Either of these settings give me errors where the starting and ending DHCP addresses conflict. I use 10.0.1.1 and 10.0.1.100 and this error no longer seems to persist, but then I am not able to connect to the internet and the amber light keeps flashing- along with my computer showing that I am still connected to the TM.
Thank you for your support so far.

Guest VLAN unable to get DHCP IP address from Anchor Controller

Hello everybody,
In our test set up, we have two WLC 5508 Controllers connected via Checkpoint UTM-1 firewall Inside and DMZ Interfaces. Both the WLC controllers are connected to the firewall via Cisco 3750 switch. On the Local (Inside) Controller, guest SSID is enabled and attached to the wireless management Interface. On the remote anchor controller, guest SSID is enabled and attached to the Management Interface as well. The following configs are replicated on both the Controllers.
SSID Name - guest
Interface - Management ( VLAN 10 on Local and VLAN 20 on remote) -
Mobility Group: Same configs at both ends
SSID Anchor : Anchor SSID on local and local SSID on Anchor.
AP: CAPWAP 3502 Management Subnet
SSID Security etc all defaults and matching on both ends
Checkpoint Firewall Rules: Allowed 16666-7, IP 97 etc on the firewall
Checkpoint Inside/DMZ to Outside(Internet) is NAT enabled.
EoIP Tunnel Status: Up, UP - Both ends
Mping - OK
eping - OK
WLC Sofware Version on Local - 7.0.98.0
WLC Sofware Version on Local - 7.0.116.0
DHCP Scope: Definitions on Anchor Controller and Guest Anchor SSID points to the Anchor management IP as the Primary DHCP server.
Management IP Subnet on Local: 10.x.x.x
Management IP Subnet on Anchor: 172.x.x.x
The problem definition as follows:
When guest SSID associates to the local AP, the guest SSID never gets a DHCP address assigned from the Anchor Controller and the following debugs are obtained.
1. WLAN ID 1 (for Guest SSID Number) delete message appears in the Controller message logs, but the SSID does not DHCP from the local Management Subnet and i can see DHCP request via the tunnel to the Anchor WLC as follows:
DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54774 (1237665652), secs: 42, flags: 0
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to EoIP tunnel
2. Similar debugs on the Anchor controller yields the following results;
Cisco Controller) >*DHCP Socket Task: Feb 25 04:30:25.488: 64:b9:e8:33:2d:13 DHCP options end, len 72, actual 64
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec05)
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54778 (1237665656), secs: 52, flags: 0
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to DS
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec05)
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54778 (1237665656), secs: 61, flags: 0
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to DS
*apfOrphanSocketTask: Feb 25 04:37:49.931: 34:51:c9:59:b1:c7 Invalid MSCB state: ipAddr=169.254.254.148, regType=2, Dhcp required!
Is there any thing missing in the wireless configs and or the firewall rules as i could not see DHCP request back from the Anchor Controller. Also, after DHCP is obtained, the web authentication request will be redirected to an Amigopod device for authentication. In this case is the redirect URL congiguration to be performed only on the Anchor Controller or is this to be replicated on both the Local and Anchor Controllers.
Thanks and Regards.

The DHCP issue is resolved if external DHCP server is configured on a 3750 switch connected to the WLC and the default gateway for DHCP points to the Firewall, which is in the data path between the Inside and Anchor Controllers. DHCP is essentially bridged (no Proxy setting now) from the EoIP tunnel to the Distribution system network. We will test this solution on pilot production and then consider upgrading to 7.0.116.0, as there are about six offices running 7.0.98.0, which will need to be upgraded.
For L3 security, configuration is set up on both the controllers for external captive portal redirection.I will try this only on the Anchor and revert.
Thanks again very much for all your help.

WRT54GS: without Windows, force a given MAC address to always get the same IP address via DHCP?

I have just now set up my WRT54GS to manage my home wireless network, and it works great. I just have one question that I haven't been able to find an answer for (forgive me if I have overlooked an obvious source of information).
I have set up the WRT54GS to be a DHCP server, and it assigns addresses in an ad hoc manner to all the devices that connect to it. In general, this is what I want, but in one case, I want a certain host to always get the same IP address, for example, 192.168.1.10.
You should know that I have no Windows machines on my network. Everything is either running Linux, MacOSX, or Symbian (on a Nokia N95 handheld). Therefore, I can't set up a static IP for my device using the software supplied on the CD that comes with my router, as that software only runs under Windows.
Using a different manufacturer's router, I am able to accomplish this by telling the DHCP software on that router to always assign 192.168.1.10 to the host who connects with a certain MAC address. I can then use this mechanism to force my specific host to always get this desired IP address. However, I haven't been able to find any way to do that with the WRT54GS without the software on the Windows-based CD. Is it possible at all? If I can indeed do this without that Windows software, could someone point me to some docs which explain how to accomplish this?
... or is there perhaps a different way to cause this to happen, perhaps by means of some sort of DHCP client ID?
Thank you very much in advance for any pointers you can give me.
Message Edited by HippoMan on 10-16-2007 05:27 PM
Take a hippopotamus to lunch today.

Forget about the CD. There is nothing on the CD which you don't configure better through the router web interface at http://192.168.1.1/ You don't need the CD. Never. I have never used the CD to configure any of my routers. The program on the CD is just a software which helps you with the initial configuration of the router. It is just a software which pretty much contacts the web interface in the background and sends some settings changes there. You can do everything yourself directly. Then you know what you change.
You have to configure the static IP address on the computer and on the computer only, e.g. on your Mac use Static IP instead of DHCP in the network preferences. Enter the IP address you want to use for the computer, the subnet mask, gateway address and DNS server(s). That's it. The router is not involved in any of this.
You just have to make sure that you use an IP address inside the LAN of the router. By default, Linksys routers use the IP address 192.168.1.1 on the LAN side for the the router. The subnet mask is 255.255.255.0. The IP address together with the subnet mask says that all IP addresses 192.168.1.0-255 are considered part of the LAN. Everything else is outside and needs to be routed to the router and from there into the internet. (If you want to know how the subnet mask works exactly read the wikipedia article on it or search for "subnet calculator" or similar in the internet)
Thus, if you connect a computer to your LAN and set a static IP address on the computer it should be inside this IP address subnet/range in order to have internet and LAN access on the computer. It does not matter which address you use as long as it is inside the IP subnet. The DHCP server on the router automatically assign a correct IP address inside the IP subnet and also automatically assigns the correct gateway address (its own address = the address to which everything should be sent which does not belong into the LAN, i.e. the internet traffic) and the DNS server. With static IP you have to assign those values yourself.
But again, there is no Windows computer or CD involved to do that nor is there any configuration on the router required to set the static IP address on the Mac. The IP address you set must simply match your LAN IP which is basically defined through the settings on the router as you want to have internet and thus need access to the router and its address 192.168.1.1.
Some routers allow you define fixed IP addresses for specific devices in the DHCP server of the router. With that function you can set a fixed IP address on the router. The computer can remain on DHCP. It will always get the IP address you have configured in the list on the router through the DHCP server. However, your Linksys router does not have this option. If any device inside your LAN is supposed to receive the same IP address at any time you have to configure that on the device only.
If you have not changed the default LAN IP address, subnet mask and DHCP server settings on the router, the router has 192.168.1.1, subnet mask 255.255.255.0 and the DHCP server uses 192.168.1.100-149 for dynamic assignments. To avoid potential address conflicts you should not use any static IP addresses inside the DHCP server address pool. This leaves you with IP addresses 192.168.1.2-99 and 150-254 as static IP addresses inside your LAN. You can pick any address you like as long as any device with a static IP address has a unique IP address inside your LAN.
Assign the subnet mask 255.255.255.0 on the computer and set the default gateway to 192.168.1.1. The DNS servers are a little bit more complicated. Generally it is better and faster if you use the DNS servers of your ISP. You can, however, also use the IP address of the router 192.168.1.1 as DNS server. The router will then operate as DNS proxy, i.e. it contacts the DNS servers of your ISP for any request from your computer.
If you want to use the DNS servers of your ISP, click on the Status tab in the router web interface. It shows you the current settings of the router on the internet port. It should show you multiple entries for DNS servers. Choose those DNS server IP addresses in the computer.
If you don't want to go through the hassle with the direct access to the DNS servers of your ISP, simple use 192.168.1.1 as only DNS server on the computer.
There are all settings you have to make on your Mac or other computers to assign a static IP address. As long as the IP address is inside 192.168.1.* it belongs to the LAN and has internet access through the router (as long as the default gateway address is 192.168.1.1 of course).
Firmware is loaded either through the web interface of the router, usually somewhere on the Administration tab or with tftp. Both ways work fine on any Mac or Linux box.

CRIO failing to get a DHCP assigned address

Similar Messages

Maybe you are looking for