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

Similar Messages

Clients are unable to get DHCP Addresses

Hi, I have a setup where managment interface is in different vlan, ap-manager is in different vlan, APs are in different vlan and the clients are on their own vlans respectively. Everything works except for when I try to associate a client to an ap on the floor. It doesn't get an IP address..Here is a debug of DHCP on the controller.
any help would be greatly apreciated...

I got it to work, I had to create seperate AP groups and virtual interface for each client vlan and point it to the DHCP server.

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.

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

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.

Macbooks unable to get DHCP from Wireless Network

Our PC Laptops can connect to our Cisco Wireless Network (using wireless controllers and lightweight AP's) without issue.
However Macbooks and several other devices are able to connect and get an IP address via DHCP. If I manually put an IP in the Macbooks wireless configuration it can connect without issue, if I don't do this the Macbooks timeout and say using self assigned ip address and will not get on the network.
Any thoughts on what is causing this and how to fix?
Jim

Make sure you don't have client load balancing enabled on the WLAN advanced tab.
Sent from Cisco Technical Support iPhone App

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 can no longer get DHCP address

Hello,
I'm at the point of dumping the airport base station in the trash, but thought I would try this first.
I have broadband internet service. It worked - until mid morning today. Suddenly it will not work. The base station (old one, white - snow?), though set for DHCP, now defaults to a self-addressed 169... address. I have tried:
- powering off the base station, the cable modem, powering up one at a time, etc etc. Internet provider (insight, IL) says they don't know why the apple base station is unable to renew the DHCP lease.
- The Airport Admin Utility is set to Ethernet, using DHCP. There is no "renew DHCP lease" button there, but I have switched it to connect using modem and then switched backed to Ethernet, hit Update, and back comes Using DHCP ... with a 169.254 address.
- I can connect through the cable modem with my powerbook without a problem. The address starts with 74.134.
I take it the self-assigned IP means there was a timeout or the airport was otherwise unable to get what it considered a valid IP.
Is the base station toast?
Should I buy a router and hook it to that? Seems redundant, with my setup (two laptops, one desktop connected to base station LAN port)
I've spent several hours reading (via direct connect to the cable modem) and trying different wiring / reset combinations, and have about had it. Any thoughts most welcome.
Thanks,
Brian

It is a long while since I tried Google Toolbar, I am not sure what it changes. But I would not expect it to totally remove your options to use the ordinary toolbars.
■ Try
* press the''' alt '''key on the keyboard, that may return the menu bar
* once you have the menubar '''View -> Toolbars ->''' and select which you need
* you may also use View-> Toolbars -> Customise and drag items back or use the restore default set option.
* right clicking on the toolbars also gets you to the customise and show toolbars options
■ have a look at [[Back and forward or other toolbar items are missing]]
PS
I hope you do not need to resort to editing registry settings, the firefox 'dragons' in prefs are user friendly compared with Windows registry. Messing up firefox prefs only really affects firefox normally; whereas errors in a registry edit may prevent you from even booting the computer.

1811W router unable to get DHCP IP from Speedstream 4100

I have a Yahoo-ATT DSL installation with 1 dynamic IP address. It uses an ISP supplied speedstream 4100 DSL modem. The 4100 appears to take care of all the PPOE duties and DHCP connections from PCs or low-end routers (I'm temporarily using a NetGear unit) work fine.
BUT, when I swap the Netgear out for my new 1811W, the cisco unit is unable to obtain a DHCP address from the modem. I can see the request on the modem lights when I do a "no shutdown fastethernet0"...but I never get an IP address.
The speedstream appears to support 100Mbps and I have tried 100, 10 and Auto on the 1811W. I can look at the log on the modem and it does not show any activity by the modem's dhcp service. However, when I swap back to the netgear unit, I can see appropriate entries in the modem log.
The 1811 is new and I strongly suspect its working ...I tested it on a different DSL line that had static IP. I see a number of similar issues in this forum; but have not seen any resolution that seems to fit my situation.
Any help/suggestions would be appreciated...my next step will be log the DHCP packets with a sniffer. I think I know what I"ll see...1811W DHCP broadcast...no response. But, that won't help me resolve the issue.
Thanks,
Chuck McP

Hi, this would a config example once you configure the dsl modem for bridging:
http://www.cisco.com/en/US/tech/tk175/tk15/technologies_configuration_example09186a0080126dc0.shtml
look at the 2600 part. you can omit these commands that are for older versions:
vpdn enable
no vpdn logging
vpdn-group 1
request-dialin
protocol pppoe
Hope this helps, please rate post if it does!

VWLC clients getting DHCP address from management VLAN

Hi,
We have a strange scenario whereby some wireless employees are obtaining addresses from the management VLAN.
Some details:
DHCP managed by MS DHCP 2008 R2 (in remote data centre)
Cisco vWLC AIR-CTVM-K9 running v7.6.110.0
AP's are a mix of 2602 and 3702 (46 and 2 of each respectively)
SSID's are employee, guest, and production devices (all mapped to their own interface with relevant VLAN tag as per normal)
AP's all in FlexConnect mode as per vWLC caveats
Some employees are receiving addresses in the wireless management VLAN. This network only has six DHCP addresses available as it is solely for AP's, WLC and HSRP gateway. Obviously this gets exhausted very quickly leaving us with a scenario where clients are not obtaining DHCP addresses.
I understand that with FlexConnect mode, it will assign IP's from the native VLAN. What I don't understand is why most clients receive addresses in the correct VLAN, but a handful do not, and then cannot get an address from DHCP. Obviously the ideal scenario would be to put the AP's into local mode but unless this has changed in a SW release then I don't believe it's possible...
My question is: How do I get ALL the employees to obtain addresses from their interface and not the management VLAN?
Thanks in advance.

Hi,
I think we need a closer look to your configurarion to eliminate some possibilities:
- What is the WLAN security you choose?
- What is the interface that is configured under the WLAN?
- Does your WLAN have local switching enabled?
- If your security is using RADIUS server, do you have AAA override enabled under the WLAN config?
- If your security is using RADIUS server, do you send any attributes to the users?
- You have eliminate that clients that got management vlan IPs are always on same AP or they can be on any AP.
HTH
Amjad

Hyper-V - Legacy NIC not getting DHCP address at boot, but when OS loads the NIC gets a DHCP address

Hi, I have a strange issue with DHCP.
I have a lab environment on a single Hyper-v 2012 Server. AD, DNS & DHCP exist on a single virtual machine, I have a flat network 192.168.1.x, all VM's are on this network. I have authorised DHCP and Setup the scope.
A VM has a legacy adaptor, the legacy nic is configured in the boot order as the first device.
When I boot the machine I do not get a DHCP address, however when the OS boots the Legacy NIC then gets a DHCP address??
I need to use a legacy NIC as I need to PXE boot the VM, however I should get an IP address at boot time, which I don't get.
I have run Wireshark on the DHCP server, I can see the legacy NIC do a "DHCP Discover and the DHCP Server respond with a DHCP Offer" however all communication ends there. I have disable all firewalls and I see no reason for this not to work.
I have done tis before with no issues but I am unable to get this to work on this server!!!!!

Hi
According to your description , it is recommended to make sure or do :
        In your environment , there is no any other valid DHCP, BOOTP or proxy DHCP offers.
        Make sure if the DHCP server is overload.
        So suggest to test that creating a new “internal virtual switch” and change the settings of VM which provide DHCP service to connect to the new “virtual switch”.
        Then create a new VM use legacy NIC also connect to the new “internal virtual switch” and try to PXE Boot.
Hope this helps.
Best Regards
Elton ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Not getting DHCP address on HP 8000 Elite

I'm using the Feb 2010 CD. Windows 2003 DHCP server
Boot with the cd and no dhcp address.
If I type "dhcpcd eth0 -n" enough times I will eventually get an address, although the first time it's usually "err, eth0: Failed to lookup hostname via DNS: Name or service not known"
The same CD works OK with a HP dc7900, dc7800, etc. It looks like they all have the same Intel e1000e nic, but maybe no?

I'm starting to investigate issues that may be similar to yours and I had a
thought that I thought I'd share with you ;-)
In what may be a related situation one of our admins is having issues with
the dhcp client on an openSUSE 11.1 (and 11.2) during and after the install
on some Dell servers. Sometimes the dhcp client will not get an ip address.
After some poking he found that there are in fact two dhcp clients available
: dhcpcd (dhcp client daemon) and dhclient (package is called dhcp-client).
The default client in openSUSE - and presumably the Linux environment of
ZENworks Imaging - is dhcpcd v3.x. It seems that there are a number of
reports of this client being problematic. The maintainer of this client has
recently released v5.x which may resolve the issues with v3.x.
In our testing on openSUSE dhclient works much more reliably than dhcpcd,
where "more" is equal to 100%. None of this helps us of course, but it is
background info that leads up to my idea: is it possible to use the other
client, dhclient in the ZEN Linux environment? I don't know if this client
is even included in the ZEN Imaging Linux environment or not. If it isn't
then maybe it might be possible to modify the initrd/root/linux files to
include it. This would at least let you have another means of acquiring a
dhcp ip address. I'm sorry that I do not have the Linux skills to do more
than make a suggestion...
Cheers,
Ron
PS I have submitted an enhancement request via the openFATE website to have
the dhcp client daemon upgraded to v5.x. Maybe if you think it a good idea
you could login to the openFATE portal and vote it up!

MBP not getting IP address using wireless

I am seeing a number of new MacBooks and MBPs coming to campus and not being able to get an IP address. They will see our wireless network and, in most cases, connect fine. However, when I go to Network properties, I have an amber light next to the wireless connection. When I go unded TCP/IP, there is no IP address. I click Renew IP address, and it still shows blank. But, yet, I can connect in most cases and surf the net. I am seeing this in Snow Leopard mostly.
Any ideas?

Do you see the DHCP server getting DHCP Discover/Req. packets from the client ?
Here's an easy way to check :
Launch Terminal on a client and type:
sudo tcpdump -i enX -s0 -vv port bootps
(where X is the adapter number. Mostly en1 on the MB and MBP )
Now reconnect the client to the wireless network and look at Terminal to check if the client is sending out DHCP packets. Paste the output here if you need help decoding it.
Another option is to do this in Terminal:
sudo tcpdump -i enX -s0 -vv -w ~/Desktop/test.pcap
and then after reproducing the issue a couple times upload the test.pcap file someplace and i can take a look at it.

WRVS4400N Unable to get DHCP address via wireless

Similar Messages

Maybe you are looking for