Unable to get IP address DHCP-NAT

I bought this modem few days ago, the new airport extreme with the latest firmware 7.7.3 I think.(upgraded after it does not work). This router only works when I set it up in a bride mode connecting to anther router. It is not able to get an IP or dns if I connect it directly to the service provider fibre modem. I tried all methods online...reset it to factory, reset, power up sequence waited 15 mins for modem and then router...etc...etc...etc. It just could not get a connection to the internet when I connect it directly to the ISP modem. Sent it to the service center and they said everthing is fine and working there on their side. Got no clue why it is like this. I suspect it might not be compatible with my ISP modem but I am not really sure. It should be a very straight forward setup like any routers I have used over the years. Any ideas? I already use mavericks x 10.9.3 and even tried to do it with a windows 7 laptop...No resolution. Called up apple and asked for a refund and they refused it.

I configured it as a bridge bit it is getting 169.xx.xx.xx ip address.
That would indicate to me that the Extreme cannot find the DHCP service provided by your ISP that is passed-through your ZTE modem. This may also indicate that the Extreme and the ZTE may not be compatible with each other.
Just to be sure, please check out the following AirPort User Tip for power recycling your network hardware.

Similar Messages

Unable to get BP address in to PO Bill to abd ship to

Hi All,
I have exported data of BP and the address using DTW.
When i am raising PO. i am unable to get the address in ship to & bill to fields on Logistics tab.
am i missing any thing.
Thanks
Mahi.

Hi Mahendra,
In the logistics tab if you select bill to and **** to drop down, you will get the addresses defined in the master.
and they will get pulled in PO screen.
some times it happens that they do not get pulled into the transaction screens.
Are you experiencing this in every transaction screen ?
Try setting default address.
thanks
Malhaar

Unable to get IP address from DHCP since upgrading

Hi all,
I upgraded my machine to Mountain Lion last night. Ever since then I have been unable to get any IP information using DHCP. Each time I hit Renew Lease within the Network control panel I just get back a self assigned IP address. If I look in the system logs I see the following generated each time my machine tries to look for the DHCP server:
Jul 26 01:32:27 Lightning.local configd[22]: bootp_session: bind port 68 failed, No route to host
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_open_socket: S_get_bootp_socket() failed, No route to host
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_bind_socket_to_if(en1, 6): session socket isn't open
Jul 26 01:32:27 Lightning.local configd[22]: bootp_session_transmit: neither bpf nor socket send available
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_bind_socket_to_if(en1, 0): session socket isn't open
Jul 26 01:32:28 Lightning.local configd[22]: bootp_session_delayed_close(): socket is already closed
I've tried rebooting, clearing the PRAM, deleting Prefs, etc, but nothing seems to have worked.
Anyone any ideas what is going on or what else to try? It used to work perfectly before I upgraded.
Thanks

I am also having this problem since I upgraded to Mountain Lion. I did an upgrade from Lion, not a clean install. I had done a clean install of Lion though. In my case, the network connection is working most of the time, but it is droping one a day. Deactivating the Ethernet and the Wi-Fi adapters and reactivating them does not help.
Here is my what I am getting in the console when I have lost internet connection and I try to renew the DHCP lease:
2012-08-30 6:13:59.158 PM configd[17]: bootp_session: bind port 68 failed, No route to host
2012-08-30 6:13:59.158 PM configd[17]: bootp_client_open_socket: S_get_bootp_socket() failed, No route to host
2012-08-30 6:13:59.158 PM configd[17]: bootp_client_enable_receive(en0): failed
2012-08-30 6:14:00.158 PM configd[17]: bootp_session_delayed_close(): socket is already closed
And I get a self assigned IP.
I hope Apple will have a fix for this soon!
Cheers!
JF

Unable to get ip address from DHCP server for Aironet 1130AG Access Point

I have a network in which DHCP server is enabled. I have read the installation guide also there it is mentioned that 1130G Access point will not have any staic ip assigned to it.So it will automatically get the ip from the DHCP server from the network. I have connected that from the network but it is unable to get the ip address from the same. The same thing i have configured in the netgear it is coming fine. I have seen the sonic wall and used the IPSU tool also from checking the ip address from Mac Address but i am not able to get the same. Please provide me some tips to check where i am wrong in configuration because the first web page also not coming because of the ip address.

narendra,
I would suggest that the AP be connected to a laptop or desktop pc that would run a local dhcp server with a small scope setup...plenty of free ones on the web(this pc would obviously not be connected to your currnet network). This way you can watch the dhcp server hand the AP it's address (this can take a few minutes). Once you have the address use it to access the GUI and give the AP a static address (I find it good pratice to give all my autonomous AP's static addresses for ease of troubleshooting)...Hope that helps.

Unable to get IP address from DHCP

hi all,
I have a AP1131 which cannot get IP from DHCP server. I have tried to configure static IP address and controller IP by lwapp command and the AP can successfully joined the controller. However, after I changed it to DHCP in WLC, it cannot get IP address and all lwapp config is gone. It cannot join the controller anymore only after I reset it and configure a static IP for it. The following error message appears after I changed it to DHCP in the WLC:
*Mar 7 08:44:36.511: RESETTING THE STATIC IP ADDRESS: LWAPP goes back to discovery
%WIDS-6-DISABLED: IDS Signature is removed and disabled.
%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
%LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
Any expert has some idea on it?
Thanks.

Is that AP on the same subnet as the other AP's? The thing is, when you configure the AP with static information, you say the AP is able to join the WLC. This means that there is no issue with the AP. Now when you set the AP to use DHCP and not static, the AP does not obtain a DHCP address? Is that correct? If you have more than one AP on the same switch and on the same vlan, and only one has an issue, then maybe reset that AP to default and see if that fixes it. I'm also assuming that the vlan is being forwarded and you have enough dhcp address in the scope.

Airport Express connecting to xbox360 unable to get IP address

I am hoping someone can assist with this. Currently I have my Comcast Cable going to a uplink port on a NetGear Hub and then from the Hub i have hardwire connections going to the AE and the Xbox.
All computers on this setup get an IP fine but the Xbox cannot. It seems to be a problem the Share a Single IP address (using DHCP and NAT) setting as the Xbox does not like sharing. I have attempted to change this to Share a range of IP addresses (using only DHCP), but when I try to update this it states I require a Static IP address and removes all dynamically assigned addresses from the ISP under the Internet Tab in the Admin Utility.
If someone can please let me know where I am going wrong it would be appreciated.

Curtly, Welcome to the discussion area!
Is the Netgear device truly a 'hub' or is it a 'router'? If it is a hub you need to replace it with a router. Comcast is giving you a single IP address and your AirPort Express (AX) is getting that address. Therefore your Xbox has no connection.
The AX can not share a connection to hardware clients. Therefore the AX can not provide the Xbox with an IP address.

Client unable to get IP address on guest wlan

Hi all, I recently setup a 2504 WLC that has two primary WLANs (internal and guest) which get their IP addresses from a central DHCP server using the local router's broadcast forwarding. Things seem to be working well for the internal wlan, but clients on the guest wlan don't seem to be getting IP addresses. If I give the client a static IP they are able to communicate across the wlan okay.
It is worth noting that I am using LAG between the controller and router and this guest wlan is really just a regular wlan (with PSK) that has an access-list applied to force it to the internet only. The access-list should be allowing dhcp requests through, but in any case, I removed the access-list and it made no difference.
Here is a debug client for a machine connected to the guest vlan (vlan 33). The internal wlan is on the 10.10.10.0/24 network (same as wired and same that the AP's are connected to) and the guest wlan is 10.33.0.0/16.     I don't understand why I am seeing the dhcp request come from the internal vlan/wlan first and it gets an IP address on this network. I then see a request on the guest wlan/vlan at which point it appears to get a valid IP address on the guest network (10.33.0.0), but the client never sees this.
Thoughts?
Thanks,
Bryan
(Cisco Controller) >debug client 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:32.991: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREQUEST (1) (len 308,vlan 1, port 13, encap 0xec03)
*DHCP Socket Task: Feb 25 00:49:32.991: 8c:2d:aa:36:ca:a3 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Feb 25 00:49:32.991: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:32.991: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 0, flags: 0
*DHCP Socket Task: Feb 25 00:49:32.991: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:32.992: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:32.992: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:32.992: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to DS
*DHCP Socket Task: Feb 25 00:49:32.992: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREPLY (2) (len 331,vlan 1, port 13, encap 0xec00)
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP processing DHCP OFFER (2)
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 0, flags: 0
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 10.10.10.165
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 10.10.10.246, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP   server id: 10.10.10.246 rcvd server id: 10.10.10.246
*DHCP Socket Task: Feb 25 00:49:32.993: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to STA
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREPLY (2) (len 308,vlan 33, port 13, encap 0xec00)
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP processing DHCP OFFER (2)
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 0, flags: 0
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:32.994: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 10.33.1.1
*DHCP Socket Task: Feb 25 00:49:32.995: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 10.10.10.246, giaddr: 10.33.0.1
*DHCP Socket Task: Feb 25 00:49:32.995: 8c:2d:aa:36:ca:a3 DHCP   server id: 10.10.10.246 rcvd server id: 10.10.10.246
*DHCP Socket Task: Feb 25 00:49:32.995: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to STA
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREQUEST (1) (len 308,vlan 1, port 13, encap 0xec03)
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 1, flags: 0
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   requested ip: 10.10.10.165
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP   server id: 10.10.10.246 rcvd server id: 10.10.10.246
*DHCP Socket Task: Feb 25 00:49:33.997: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to DS
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREPLY (2) (len 308,vlan 1, port 13, encap 0xec00)
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP processing DHCP NAK (6)
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 0, flags: 8000
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP   server id: 10.10.10.246 rcvd server id: 10.10.10.246
*DHCP Socket Task: Feb 25 00:49:33.998: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to STA
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP received op BOOTREPLY (2) (len 308,vlan 33, port 13, encap 0xec00)
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP processing DHCP NAK (6)
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   xid: 0xbcf5ea3c (3170232892), secs: 0, flags: 8000
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   chaddr: 8c:2d:aa:36:ca:a3
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   siaddr: 0.0.0.0, giaddr: 10.33.0.1
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP   server id: 10.10.10.246 rcvd server id: 10.10.10.246
*DHCP Socket Task: Feb 25 00:49:34.000: 8c:2d:aa:36:ca:a3 DHCP successfully bridged packet to STA
*apfMsConnTask_1: Feb 25 00:49:35.320: Stats update: Non Zero value

One way to test also is to connect a laptop to a port assigned for the guest vlan. If the device gets an IP, then it's something on the WLC you have to configure. If the device doesn't, then it's a network issue or dhcp server issue.
Sent from Cisco Technical Support iPhone App

Snow Leopard 10.6.4 and unable to get IP address from Wireless APs

I have a MacBook Pro with 10.6.4 and just recently ran into an issue in connecting to Wireless APs. Many of my corporate APs with WPA2, etc work great. I even have some great success at customers of mine with Cisco APs and open authentication (ie., Guest access).
However, I have been having alot of problems with generic APs (Linksys, etc.) For example, I have been in two hotels in the past week and I would connect to the AP, but I would only have a self assigned IP address. I have no problems at Starbucks.
I have tried to turn airport on and off, rebooting with no success. I have also disabled my firewall with no luck. The problem is very repeatable.
What do you think?

ChrisBog wrote:
I have been in two hotels in the past week and I would connect to the AP, but I would only have a self assigned IP address.
You might try resetting your connection settings using the steps listed in this message:
http://discussions.apple.com/thread.jspa?messageID=10695921&start=1
They're not guaranteed to solve the problem, but they'll only take a minute or so to try.

Wicd: "Connection failed: Unable to get IP Address"

Hi,
Wicd has suddenly stopped working for me. The only recent change I can think of is updating virtualbox_bin (from AUR). I can successfully connect to my wireless network from an Ubuntu 10.04 machine, so the problem is on my Arch laptop. Here's my /var/log/everything.log from a fresh boot immediately followed by an attempt to connect to my wireless network:
Sep 13 23:35:18 archtop polkitd[2252]: started daemon version 0.96 using authority implementation `local' version `0.96'
Sep 13 23:35:18 archtop pulseaudio[2244]: module-alsa-card.c: Failed to find a working profile.
Sep 13 23:35:18 archtop pulseaudio[2244]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep 13 23:35:19 archtop kernel: fuse init (API version 7.14)
Sep 13 23:35:30 archtop dhcpcd[2627]: dhcpcd not running
Sep 13 23:35:30 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:35:30 archtop dhcpcd[2650]: dhcpcd not running
Sep 13 23:35:31 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:35:31 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:35:31 archtop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 23:35:31 archtop dhcpcd[2678]: dhcpcd not running
Sep 13 23:35:31 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:35:36 archtop kernel: wlan0: authenticate with ${MAC_ADDRESS} (try 1)
Sep 13 23:35:36 archtop kernel: wlan0: authenticated
Sep 13 23:35:36 archtop kernel: wlan0: associate with ${MAC_ADDRESS} (try 1)
Sep 13 23:35:36 archtop kernel: wlan0: RX AssocResp from ${MAC_ADDRESS} (capab=0x431 status=0 aid=3)
Sep 13 23:35:36 archtop kernel: wlan0: associated
Sep 13 23:35:36 archtop kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep 13 23:35:36 archtop kernel: cfg80211: Calling CRDA for country: US
Sep 13 23:35:36 archtop kernel: Intel AES-NI instructions are not detected.
Sep 13 23:35:36 archtop kernel: padlock: VIA PadLock not detected.
Sep 13 23:35:36 archtop kernel: /dev/vmnet: open called by PID 2103 (vmnet-bridge)
Sep 13 23:35:36 archtop kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
Sep 13 23:35:36 archtop kernel: /dev/vmnet: port on hub 0 successfully opened
Sep 13 23:35:36 archtop kernel: bridge-wlan0: up
Sep 13 23:35:36 archtop vmnetBridge: Adding interface wlan0 index:4
Sep 13 23:35:36 archtop vmnetBridge: Started bridge wlan0 to virtual network 0.
Sep 13 23:35:36 archtop kernel: bridge-wlan0: attached
Sep 13 23:35:37 archtop dhcpcd[3483]: version 5.2.7 starting
Sep 13 23:35:37 archtop dhcpcd[3483]: wlan0: broadcasting for a lease
Sep 13 23:35:47 archtop kernel: wlan0: no IPv6 routers present
Sep 13 23:36:07 archtop dhcpcd[3483]: timed out
Sep 13 23:36:07 archtop dhcpcd[3648]: dhcpcd not running
Sep 13 23:36:07 archtop kernel: wlan0: deauthenticating from ${MAC_ADDRESS} by local choice (reason=3)
Sep 13 23:36:07 archtop vmnetBridge: Removing interface wlan0 index:4
Sep 13 23:36:07 archtop kernel: bridge-wlan0: disabling the bridge on dev down
Sep 13 23:36:07 archtop kernel: bridge-wlan0: down
Sep 13 23:36:07 archtop kernel: cfg80211: Calling CRDA to update world regulatory domain
Sep 13 23:36:07 archtop kernel: bridge-wlan0: detached
Sep 13 23:36:07 archtop kernel: /dev/vmnet: open called by PID 2103 (vmnet-bridge)
Sep 13 23:36:07 archtop kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
Sep 13 23:36:07 archtop kernel: /dev/vmnet: port on hub 0 successfully opened
Sep 13 23:36:07 archtop kernel: bridge-wlan0: attached
Sep 13 23:36:07 archtop vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Sep 13 23:36:07 archtop vmnetBridge: Adding interface wlan0 index:4
Sep 13 23:36:07 archtop vmnetBridge: Started bridge wlan0 to virtual network 0.
Sep 13 23:36:07 archtop vmnetBridge: Removing interface wlan0 index:4
Sep 13 23:36:07 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:36:07 archtop kernel: bridge-wlan0: enabling the bridge on dev up
Sep 13 23:36:07 archtop kernel: bridge-wlan0: up
Sep 13 23:36:07 archtop kernel: bridge-wlan0: disabling the bridge
Sep 13 23:36:07 archtop dhcpcd[3657]: dhcpcd not running
Sep 13 23:36:07 archtop kernel: bridge-wlan0: down
Sep 13 23:36:07 archtop kernel: bridge-wlan0: detached
Sep 13 23:36:07 archtop vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Sep 13 23:36:08 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:36:08 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:36:08 archtop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Any ideas?
Thanks!
Last edited by w1ntermute (2010-09-14 04:47:21)

ewaller wrote:Is it possible you have constructed a bridge interface (TAP) and then added one of the VmWare virtual interfaces and wlan0 to that bridge?
I haven't manually set up any interfaces, that's for sure. In VirtualBox my network adapter is set to "Attached to: NAT", not "Attached to: Bridged Adapter".
Did you intend to set up a bridge? I find that NAT works much better (unless you need to use the virtual machine as a network server)
No, I didn't intend to set up anything. I just want wireless and wired to work on my laptop and on my virtual machine, and I want to be able to access shared folders from my host OS in my Windows XP guest OS (which happens via the network sharing functionality in Windows).
Also, today I tried connecting to another wireless network, and I was successful, so maybe it's something about the way that my home wireless settings are configured. I tried rebooting several times yesterday when I couldn't connect at home, so I don't think it was something fixed by me rebooting before I tried connecting to the other wireless network. I'll try again to connect to my home network in a bit, just in case it was.
Last edited by w1ntermute (2010-09-14 23:50:51)

WAP + AD FS Integration - Unable to get Email Address

We integrated our tenant portal to authenticate using AD FS which is working fine. The only issue i am having is that when i query Microsoft.MgmtSvc.Store database to see the users, i do not see their Email address. I see their UPN being populated in the
Name field but email address is NULL.
SELECT *
FROM [Microsoft.MgmtSvc.Store].[mp].[Users]
Am i missing something in the configuration?
Can someone who has AD FS integrated with WAP please set up check their database?

Hi,
I do see in my setup also the UPN, only thing I did is on the OU of the company I configured the uPNSuffixes attribute to match my mail domain:
Best regards, Mark Scholman. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

WRT320N Can't get IP Address - only using 1 wired port - no internet access - web setup pages hang

Just bought Linksys WRT320N to replace Netgear MR814.
Can't get connected to internet using Linksys WRT320N.
Setup:
ISP: Cox Communications (Cable)
Firmware: v1.0.03 build 010 Jul 24, 2009
1 wired - port 1- to Windows XP SP 3 Dell Desktop
Setup Attempts:
1. Tried to setup using install CD. Kept erroring out with Error 302: Internal Error. tried this 3 times
2. Went through the reset, power down, power up procedures.
3. Ping 192.168.1.1 = success
4. Connected to 192.168.1.1 via web browser
5. Set MAC Address = computer's MAC address
6. Set MTU = Auto (1500). Also tried Manual 1492
Was unable to get IP address using IP Address Release and IP Address Renew. Internet IP Address still = 0.0.0.0
Note that the web page will always get stuck after perfoming a couple of actions (like after switching between tabs). Message in bottom of browser is "Wating for http://192.168.1.1/Status_Router.asp". And on the screen the hourglass symbol never goes away.
Note that the old Netgear router still works fine and I am currently connected to the internet using the Netgear router. I'd appreciate any help getting the new Linksys router functioning/connecting to the internet/obtaining and IP address.
Thanks for your help.
Solved!
Go to Solution.

I don't know where I was unclear: you wrote before that you have used the mac address clone function on the WRT to clone the MAC address of the PC. This way the WRT "pretends" to be the PC if you connect the WRT internet port to your modem.
However, the PC is not the device which you used before to connect to the internet. The PC was not the device which was connected before to the modem. If you connect the PC directly to your modem it won't get an IP address either. It won't have internet.
The problem is that your ISP only allows you to have a single active internet connection at any given time. If you simply connect a different device with a different MAC address to your modem this other device won't get an IP address. As you have connected the Netgear router to your modem and you have internet then you have to clone the MAC address of your Netgear router. That's the device which is connected to your internet and that's the MAC address for which your ISP has locked your internet connection.
Thus, one more time: clone the MAC address of the netgear router (the internet or WAN port MAC address) on your Linksys router. Then the Linksys pretends to be the Netgear router and your ISP should accept the Linksys router. The netgear router should have a status page in it's web interface which shows you the correct MAC address to be cloned.

WRVS4400N Unable to get DHCP address via wireless

I am having an issue with the WRVS4400N. I am unable to get a DHCP address via wireless. If I connect directly to the router via RJ45, I get a dhcp address an and able to get to the internet. Has anyone ran into this issue.

This seems to be a problem with the latest firmware (v1.01.03) available from Linksys for this router. The stock firmware for my WRVS4400N router assigned DHCP addresses to wireless devices without any issue. As soon as I upgraded the router to v1.01.03, the router no longer assigns DHCP addresses to wireless devices. I have verified there is no issue with the router itself by rolling back to version 1.00.16 with the recovery utility.
One workaround I noticed with firmware v1.01.03 is that the router will actually assign DHCP addresses to wirelss devices temporarily if it assigns a DHCP address to a device connected to the physical port. This only last for a little before the router stops giving out DHCP address to wireless devices though. It's a shame since I was looking forward to some of the features in the v1.01.03 firmware.
Chuck

HT3477 I am attempting to set up a guest network. When I change the Network settings to DHCP NAT I get a message that tells me that the service has a private IP address and so I must connect using off bridge mode. In this mode I can not connect to the int

I am attempting to set up a guest network on the Airport Extreme Base Station. The Base Station is connected to a DSL Modem. The network is also extended using an Airport Express. When I have attempted to set up the Base Station using DHCP NAT in the netword feature I get a message that because the service has a private IP address the only way that I can connect is in Off Bridge Mode. In this mode I do not seem to be able to connect to the internet using the guest network. Any suggestions would be helpful.

Ok, your Speedport is actually a combination DSL modem and wireless router. In this case you would typically configure a downstream router, like your AirPort Extreme in Bridge mode. Unfortunately, when in Bridge mode, the AirPort does NOT support providing a guest network.
The only possible option is to reconfigure the Speedport as a bridge and use the Extreme as your Internet router. You would still need the DSL modem provided by the Speedport for Internet connectivity.

Router connected to cable modem by Ethernet port cannot get IP address from DHCP.

I have an ethernet cable on Fa0/0 connecting my 1841 router to my cable modem. The issue is that the router cannot obtain an IP address via DHCP when I have the "ACL-OUTSIDE-IN" ACL applied inbound on the Fa0/0 interface. I tried to allow all BOOTP and BOOTPS traffic in my ACL, but still no luck. I really don't want to run the router without a simple ACL firewall and connect it to the internet. When I take off the ACL off of Fa0/0, the router is able to get an IP address via DHCP.
Router#sh run
Building configuration...
Current configuration : 10736 bytes
! Last configuration change at 18:14:42 MST Fri Nov 16 2012 by matt.chan
version 12.4
service nagle
service timestamps debug datetime msec localtime show-timezone year
service timestamps log datetime msec localtime show-timezone year
service password-encryption
hostname Router
boot-start-marker
boot system flash:c1841-advipservicesk9-mz.124-25f.bin
boot-end-marker
logging count
logging userinfo
logging buffered 1048576 informational
enable secret 5 <removed>
aaa new-model
aaa authentication login AUTH-LOCAL local-case
aaa session-id unique
memory-size iomem 25
clock timezone MST -7
ip cef
ip nbar pdlm flash:directconnect.pdlm
ip nbar pdlm flash:citrix.pdlm
ip nbar pdlm flash:bittorrent.pdlm
ip nbar custom steam destination udp range 27000 27030
ip nbar custom rdp destination tcp range 3389 3391 55402
ip domain lookup source-interface FastEthernet0/0
ip name-server 8.8.8.8
ip inspect name fa0/0_inspect_ou icmp router-traffic timeout 10
ip inspect name fa0/0_inspect_ou ftp timeout 300
ip inspect name fa0/0_inspect_ou udp router-traffic timeout 120
ip inspect name fa0/0_inspect_ou tcp router-traffic timeout 300
login block-for 60 attempts 4 within 60
login quiet-mode access-class ACL-ACCESS-QUIET
password encryption aes
crypto pki trustpoint TP-self-signed-1755372391
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1755372391
revocation-check none
rsakeypair TP-self-signed-1755372391
crypto pki certificate chain TP-self-signed-1755372391
certificate self-signed 01
3082023F 308201A8 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 31373535 33373233 3931301E 170D3132 31313137 30313130
35325A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 37353533
37323339 3130819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100D53F 9EB5B123 3103A4D5 82E786F7 F91C2DE5 9E409A22 80AF78F6 812F624A
89FE9103 73C4AAAB 13FF880D F628607D 6888AC49 18BEDD77 778F0DB1 F9A796E9
E92717CD 6DD19450 5066620A 91278C33 E38349EA 92B8C671 80761609 0AC46E6F
2C8C6BCF ABC7E1F7 A64BD28C C85477FE B23F8A7C 555ECDF9 CE461B8D 6C017370
0ED70203 010001A3 67306530 0F060355 1D130101 FF040530 030101FF 30120603
551D1104 0B300982 074E5543 4C455553 301F0603 551D2304 18301680 146CA2E0
936C651F E2ED4DCD D7025FF3 2AB029E0 95301D06 03551D0E 04160414 6CA2E093
6C651FE2 ED4DCDD7 025FF32A B029E095 300D0609 2A864886 F70D0101 04050003
8181004A AFA4D07C 1424DE0E EF3F17F2 BB1EA63B CB17C13D 1AEA31A1 BAB6AF77
DB6EA8A2 2117DCD1 5530A18C 3618D568 CC7EF520 E039ACBD DA906352 BB7E51BD
0954490C B2AB30C2 FBBE4738 C214BE1C CB63FFEA BAFC46E0 3DC419EE 714B9ABD
144A21E3 3E54C103 FF47FAF1 412FE5C4 59ACD1FE FD72356B C8DC04C3 E2EDF275 45954C
quit
username <removed secret 5 <removed>
ip ssh maxstartups 10
ip ssh time-out 60
ip ssh authentication-retries 2
ip ssh port 2226 rotary 1
ip ssh version 2
class-map match-all Zuri-YouTube-Class
match access-group name NAT-Pool-Zuri-WLAN
match protocol http host "*youtube.com*"
policy-map PMAP-QOS-VTI-IN
description QOS FOR TU0
class class-default
shape peak 1512000
policy-map PMAP-QOS-VTI-OUT
description QOS FOR TU0
class class-default
shape peak 512000
crypto isakmp policy 1
encr aes 256
authentication pre-share
group 5
lifetime 43200
crypto isakmp key 6 <removed> address <removed>
crypto isakmp invalid-spi-recovery
crypto isakmp keepalive 10 5 periodic
crypto ipsec transform-set EDGE-TS ah-sha-hmac esp-aes 256
crypto ipsec profile EDGE
set security-association lifetime kilobytes 256000
set transform-set EDGE-TS
set pfs group5
interface Loopback0
no ip address
interface Tunnel0
description "VTI Link"
bandwidth 4000
ip address 172.20.0.2 255.255.255.0
ip mtu 1400
ip nbar protocol-discovery
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1360
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 7 12090011003E5A0C0F186E752220211B4A
keepalive 10 5
tunnel source FastEthernet0/0
tunnel destination <removed>
tunnel mode ipsec ipv4
tunnel path-mtu-discovery
tunnel protection ipsec profile EDGE
service-policy output PMAP-QOS-VTI-OUT
hold-queue 75 out
interface FastEthernet0/0
description "Link to ISP"
bandwidth 4000
ip address dhcp
ip access-group ACL-OUTSIDE-IN in
no ip proxy-arp
ip nbar protocol-discovery
ip nat outside
ip inspect fa0/0_inspect_ou out
ip virtual-reassembly
ip ospf cost 1
duplex auto
speed auto
no keepalive
no cdp enable
interface FastEthernet0/1
description "Link to LAN"
ip address 172.16.0.1 255.255.255.248
ip access-group ACL-INSIDE-IN in
no ip proxy-arp
ip nbar protocol-discovery
ip nat inside
ip virtual-reassembly
ip ospf cost 1
ip ospf priority 255
duplex auto
speed auto
no keepalive
router ospf 1
log-adjacency-changes
redistribute static subnets
passive-interface default
no passive-interface Tunnel0
network 172.20.0.0 0.0.0.3 area 0
ip forward-protocol nd
ip route 10.0.0.0 255.0.0.0 Null0 name "Class A Private"
ip route 172.16.0.0 255.240.0.0 Null0 name "Class B Private"
ip route 172.17.0.0 255.255.0.0 FastEthernet0/1 172.16.0.2 name "Home WLAN"
ip route 172.19.73.31 255.255.255.255 Null0
ip route 172.27.0.0 255.255.0.0 Tunnel0 172.20.0.1 name "IPsec GRE Tunnel"
ip route 192.168.0.0 255.255.0.0 Null0 name "Class C Private"
ip route 192.168.0.0 255.255.255.0 Tunnel0 172.20.0.1 name "VLAN 70"
ip route 192.168.100.1 255.255.255.255 FastEthernet0/0 70.162.0.1 permanent name "CABLE MODEM MANAGEMENT"
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0 dhcp 253
ip dns server
no ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat translation tcp-timeout 300
ip nat translation udp-timeout 120
ip nat translation max-entries 2048
ip nat inside source list ACL-NAT-172.16.0.0/29 interface FastEthernet0/0 overload
ip nat inside source list ACL-NAT-MANAGEMENT interface FastEthernet0/0 overload
ip nat inside source static tcp 172.16.0.4 22 interface FastEthernet0/0 2227
ip nat inside source static tcp 172.16.0.5 3389 interface FastEthernet0/0 3391
ip nat inside source static tcp 172.16.0.3 3389 interface FastEthernet0/0 3390
ip nat inside source static tcp 172.16.0.4 80 interface FastEthernet0/0 8084
ip access-list standard ACL-ACCESS-QUIET
permit 216.161.180.16
permit 172.16.0.0 0.1.255.255
permit 172.27.0.0 0.0.127.255
permit 172.20.0.0 0.0.0.3
ip access-list standard ACL-NAT-172.16.0.0/29
permit 172.16.0.0 0.0.0.7
ip access-list standard ACL-NAT-172.17.0.0/24
permit 172.17.0.0 0.0.0.255
ip access-list standard ACL-NAT-172.17.1.0/24
permit 172.17.1.0 0.0.0.255
ip access-list standard ACL-SNMP
permit 172.16.0.4
ip access-list extended ACL-CRY-MAP
ip access-list extended ACL-INSIDE-IN
deny   ip host 172.16.0.2 172.27.0.0 0.0.127.255
deny   ip host 172.16.0.2 172.20.0.0 0.0.0.3
permit ip 172.17.0.0 0.0.0.255 any
permit ip 172.16.0.0 0.0.0.7 any
permit ip 172.17.1.0 0.0.0.255 any
ip access-list extended ACL-NAT-MANAGEMENT
permit tcp host 172.27.10.11 eq 3389 host 72.166.77.196
ip access-list extended ACL-OUTSIDE-IN
deny   ip 10.0.0.0 0.255.255.255 any
deny   ip 172.16.0.0 0.15.255.255 any
deny   ip 192.168.0.0 0.0.255.255 any
permit tcp any any range 3390 3391
permit udp any any eq bootpc
permit udp any any eq bootps
permit tcp any any range 2226 2228
permit tcp any any range 8081 8084
permit icmp any any echo
permit icmp any any net-unreachable
permit icmp any any host-unreachable
permit icmp any any port-unreachable
permit icmp any any parameter-problem
permit icmp any any packet-too-big
permit icmp any any administratively-prohibited
permit icmp any any source-quench
permit icmp any any ttl-exceeded
deny   icmp any any
deny   ip any any
ip access-list log-update threshold 10
logging history informational
logging trap debugging
logging 172.17.228.17
logging 172.17.228.10
control-plane
line con 0
exec-timeout 15 0
privilege level 15
logging synchronous
login authentication AUTH-LOCAL
line aux 0
login authentication AUTH-LOCAL
line vty 0 4
exec-timeout 60 0
privilege level 15
logging synchronous
login authentication AUTH-LOCAL
rotary 1
transport input ssh
scheduler allocate 20000 1000
ntp clock-period 17178311
ntp source FastEthernet0/0
ntp server 148.167.132.201
end

Hi Matt,
Try adding below line
ip access-list extended ACL-OUTSIDE-IN
permit udp any eq bootpc any eq bootps
Regards
Najaf
Please rate when applicable or helpful !!!

Cisco 891 not getting IP address with DHCP with latest IOS

Hi,
I have a few Cisco 891 routers that are configured as DHCP clients on the WAN interface.
For some reason when I boot the router with a late IOS, the router is not receiving an address.
It works just as expected with the older IOSes.
Any ideas of what changed?
This is how the interface is configured:
interface FastEthernet8
ip address dhcp
no ip redirects
no ip unreachables
no ip proxy-arp
duplex auto
speed auto
no cdp enable
This IOS does not work:
c890-universalk9-mz.154-3.M2.bin
While these do work:
c890-universalk9-mz.150-1.M7.bin
c890-universalk9-mz.151-2.T2.bin
c890-universalk9-mz.152-1.T1.bin
Doing a "show ip interface brief" shows that FastEthernet8 is unassigned with the affected IOS.
With the older IOSes there is an IP address.
I had to downgrade two routers due to this issue, and did not have plenty of time to troubleshoot.
Both of the routers are connected to DSL from the same ISP...
Anyone seen anything like this before?

Add another one to the list.
I have a MacBookPro3,1 that connects to WIFI no problem. It used to connect to ethernet when I originally bought it, however I've been using WIFI exclusively for the past 2 years.
Recently I had a need to connect via ethernet and it wouldn't work at home (apple airport router). I next tried connecting via ethernet at a friends house using a linksys WRT54G, no dice either. I have the computer in the lab today (University Network) and I get the same error. 3 different locations, 3 different routers, all same problem. It used to connect to home and university networks ethernet right away.
IP address assigned is 169.xxx.xxx.xxx - subnet - 255.255.0.0
no other info. It's showing up as connecting to the network, but unable to communicate with DHCP. It does work if I enter all of the information in manually.
At first I thought I had messed something up in networking preferences as I tend to play around with things alot. However I did a complete system format, and fresh install of OSX Lion and I still have the same problem, without any of my meddling around to confuse things.
What gives?

Unable to get IP address DHCP-NAT

Similar Messages

Maybe you are looking for