Vwlc 7.3.101.0 DHCP issue ?
Hello all,
a wireless client can't get an IP address via DHCP.
The controler is configured as "DHCP bridging mode", the DHCP server is a 3750 on the same L2 segment.
The security part is done by ISE 1.1.3, the client get authenticated successfully and debug on the vwlc says :
(Cisco Controller) >*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP xid: 0x7f6910ce (2137592014), secs: 0, flags: 0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP chaddr: 00:26:4a:fd:ed:a4
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP requested ip: 192.168.10.4
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP successfully bridged packet to DS
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP received op BOOTREPLY (2) (len 308,vlan 0, port 1, encap 0xec00)
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP processing DHCP ACK (5)
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP xid: 0x7f6910ce (2137592014), secs: 0, flags: 80
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP chaddr: 00:26:4a:fd:ed:a4
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.10.4
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP server id: 192.168.10.1 rcvd server id: 192.168.10.1
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP successfully bridged packet to STA
however, the wireless client never get the IP address.
See attached .jpg, the IP address seems to be attached to the wireless client.....
Is anyone could help me please ?
Regards.
TM
Ok DHCP Snooping was the issue....
The DHCP message response seems to enter back the switch (from the vwlc to the AP ) on the same port it came from.
(the Sw acts as a DHCP server)
Now I have an IP address assign by DHCP but no connectivity though !!!
Similar Messages
-
Hello All,
I facing a very wierd DHCP issue and would like to know your thoughts on it.
I have my wired clients on vlan 1 and wireless cleints(eap-peap) on VLAN 2.
We are facing an issue where multiple wired clients who were on access port vlan 1 are receiving IP address from wireless subnet(vlan2) -their DHCP server was the WLC virtual gateway IP address(1.1.1.1). This is causing an outage to few wired clients.
The WLC trunk does not have vlan 1 allowed on its ports and all APs are in local mode and all on access vlan.
I'm not entirely sure whats causing this, but only way I think this is possible is that 'A Client' laptop has his network connections bridged - his wired nic on VLAN 1 and wireless NIC on vlan 2, acting like a WGB, which is causing new wired clients(vlan1) DHCP broadcast request forwared through the bidge mode laptop to AP--> WLC. Do you think this is possible??
Havent been able to identify which client is causing this issue yet.
Has anyone faced a similar issue and anyway to block this through WLC/ACS policy?
Thanks
JinoHi,
Might we consider to make use of network monitor to take a look at the traffics for the 1.1.1.1 address?
How to use Network Monitor to capture network traffic
Download link here:
Microsoft Network Monitor 3.4
Best regards
Michael Shao
TechNet Community Support -
We've started 're-vlanning' our main location here, breaking up depts
into their own vlans.
All seems ok so far, aside from a real doozy.
For the IT vlan, we have one address that will not talk to our web
content mgmt appliance. It's the 2nd address in our assignable pool,
and it doesn't matter if it's dhcp or statically assigned, that address
will not talk to that device.
That is the *only* device that cannot be reached from this particular
address in our dept vlan, every other one works fine.
Any ideas on this?
Stevo-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> and it doesn't matter if it's dhcp or statically assigned, that
> address
So.... the title of this thread should actually be 'Very weird non-DHCP
issue', since your own testing confirms this has nothing to do with DHCP?
If you do a LAN trace on this machine as well as your web content
management appliance do you see packets on either side? Both sides? If
not on both sides but you do on the source (workstation) side see
packets going out, then get LAN traces after each network device
(switch, router, firewall, etc.) to see when the packets disappear.
Feel free to post the LAN traces somewhere with descriptions of IPs,
ports, and what you should be seeing, if you want to post them somewhere
for review.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP4jFPAAoJEF+XTK08PnB55aMP/3Rg9u6LX6jFCXGYuex/oXdS
NZ/liqfCgjyIcykWWeKGgdtm2I7JZOcFiG8YW2le55mcltvCL1VJW +1VGng4kZER
0f4hjfyQ3CcQ6HIU3RM6VL5U2Pblb80MsEQe0qo0xgtPXipmjs i7Q0xIv9p0wT7A
7JMkfgM9tfuI5Yro+BDLfSIkFWicKuKs1sKpNugKalPuyyRrzW IiznoalIKFshon
a40ETLJVZmngBYfqfeZL9nPNsFlveFNXrDkdbl2WbaprsHtNnA NwZfVUIlc5kOCT
MknY0GXof4/tk149OVCCLgjEzoRtTIZH0BJTHQwW7ANkWUUNYwi49+Mk46V0o awl
oe1aA+NK9gl2bWXWLCtTro4ERSVMvkcI0OffytrfcBsqdCKg/g3QPMjV3kiVEULI
xnSTsqFgOl2qO8qGaL6FJtk39ZBnCwqDPtmoNt93OK4hAhWBuA Xihc+kiQHrwkpO
O04quZu8qQG6A6qwFDr+r+QqarFR3kielfvi7H6o5iLfZn/sDhvijGOAknJVctH8
j8fezki9PMznkcT+of2Oe4T99K9fChN2WFSgUKdlpkYSjbkmjP fdbWloou+WBjCm
7hHwnAbKPPgoN8aPPfw9rG9E+K/0YW2kt4wRu79BEDvF6eMv0UdDPE1qPuw1ttmm
jg2zzMZDkgIG39A0P3u7
=+fCy
-----END PGP SIGNATURE----- -
Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
network 1.1.1.0 255.255.255.0
default-router 1.1.1.1
dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you. -
DHCP issue on Cisco IOS router
Hi experts,
I recently got complaints that some clients can't get IP address through the DHCP server configured on a Cisco IOS router. I turned on debugging on DHCP events and packets and I see the following logs.
Mar 22 15:33:41: DHCPD: DHCPREQUEST received from client 0100.1b63.f246.8c.
Mar 22 15:33:41: DHCPD: Finding a relay for client 0100.1b63.f246.8c on interface FastEthernet1/0.10.
Mar 22 15:33:41: DHCPD: Seeing if there is an internally specified pool class:
Mar 22 15:33:41: DHCPD: htype 1 chaddr 001b.63f2.468c
Mar 22 15:33:41: DHCPD: remote id 020a0000cf6050011000000a
Mar 22 15:33:41: DHCPD: circuit id 00000000
Mar 22 15:34:02: DHCPD: DHCPREQUEST received from client 0100.1b63.f246.8c.
Mar 22 15:34:02: DHCPD: Finding a relay for client 0100.1b63.f246.8c on interface FastEthernet1/0.10.
Mar 22 15:34:02: DHCPD: Seeing if there is an internally specified pool class:
Mar 22 15:34:02: DHCPD: htype 1 chaddr 001b.63f2.468c
Mar 22 15:34:02: DHCPD: remote id 020a0000cf6050011000000a
Mar 22 15:34:02: DHCPD: circuit id 00000000
Then it will repeat and repeat for this MAC. Any reason why the router is not assigning an IP to it? It actually happens to some other MACs as well... They are from different vendors and located on different switches... I can't really find a pattern for this problem... The DHCP pool hasn't run out and it still has available IPs in it.
ThanksHi Alain, thanks for quick reply. The followings contain the output that you required. I hided the prefix of the IP with a.b.c. Thanks!
interface FastEthernet1/0.10
description : DHCP for EXHIBITION VLAN
encapsulation dot1Q 10
ip address a.b.c.1 255.255.255.128
no ip redirects
no ip unreachables
no ip proxy-arp
end
r#sh ip dhcp pool
Pool EXHIBIT :
Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 126
Leased addresses : 47
Pending event : none
1 subnet is currently in the pool :
Current index IP address range Leased addresses
a.b.c.118 a.b.c.1 - a.b.c.126 47
#sh run | in/be dhcp
no ip dhcp use vrf connected
ip dhcp excluded-address a.b.c.1 a.b.c.11
ip dhcp excluded-address a.b.c.126
ip dhcp excluded-address a.b.c.100 a.b.c.101
ip dhcp excluded-address a.b.c.51
ip dhcp pool EXHIBIT
network a.b.c.0 255.255.255.128
default-router a.b.c.1
dns-server 207.172.3.8 207.172.3.9
domain-name xyz.com
#sh ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
a.b.c.19 0168.7f74.6260.9b Mar 23 2011 01:56 PM Automatic
a.b.c.52 0100.4854.897d.17 Mar 23 2011 12:53 PM Automatic
a.b.c.56 0100.4063.e7b5.b2 Mar 23 2011 03:33 PM Automatic
a.b.c.57 0100.1b63.f246.8c Mar 23 2011 03:34 PM Automatic
a.b.c.68 015c.5948.0b97.d6 Mar 22 2011 05:59 PM Automatic
a.b.c.69 0168.7f74.626d.67 Mar 23 2011 07:07 AM Automatic
a.b.c.70 0198.fc11.5027.1d Mar 22 2011 07:04 PM Automatic
a.b.c.71 01dc.2b61.04ba.af Mar 22 2011 10:26 PM Automatic
a.b.c.72 017c.c537.58e6.64 Mar 22 2011 08:37 PM Automatic
a.b.c.73 017c.6d62.3303.57 Mar 23 2011 03:54 AM Automatic
a.b.c.74 0124.ab81.cda4.68 Mar 23 2011 05:01 AM Automatic
a.b.c.75 0100.1e52.8f11.a5 Mar 23 2011 02:47 PM Automatic
a.b.c.76 0100.264a.5fc8.e3 Mar 23 2011 07:13 AM Automatic
a.b.c.77 017c.6d62.38cd.40 Mar 23 2011 02:06 PM Automatic
a.b.c.78 0100.1d4f.f647.79 Mar 23 2011 02:37 PM Automatic
a.b.c.79 0100.26b0.8637.3d Mar 23 2011 01:16 PM Automatic
a.b.c.81 0130.694b.e9de.82 Mar 23 2011 03:19 PM Automatic
a.b.c.82 0100.21e9.6864.80 Mar 23 2011 12:04 PM Automatic
a.b.c.83 0124.ab81.63e6.b5 Mar 23 2011 09:38 AM Automatic
a.b.c.84 0100.16b6.0455.c2 Mar 23 2011 09:42 AM Automatic
a.b.c.85 0100.1302.4c96.9e Mar 23 2011 09:49 AM Automatic
a.b.c.86 0140.a6d9.741c.e0 Mar 23 2011 12:12 PM Automatic
a.b.c.87 0100.264a.b8e9.50 Mar 23 2011 10:16 AM Automatic
a.b.c.88 0140.a6d9.4911.67 Mar 23 2011 03:19 PM Automatic
a.b.c.89 013c.7437.1e32.96 Mar 23 2011 10:27 AM Automatic
a.b.c.90 01d8.3062.689c.4b Mar 23 2011 11:55 AM Automatic
a.b.c.91 0158.946b.4df8.bc Mar 23 2011 10:49 AM Automatic
a.b.c.92 0100.2215.7368.26 Mar 23 2011 10:23 AM Automatic
a.b.c.93 0100.23df.76ea.90 Mar 23 2011 02:33 PM Automatic
a.b.c.94 0124.ab81.708d.83 Mar 23 2011 03:58 PM Automatic
a.b.c.95 0100.1cb3.163d.5a Mar 23 2011 03:13 PM Automatic
a.b.c.96 01cc.08e0.2aeb.96 Mar 23 2011 01:27 PM Automatic
a.b.c.97 0188.c663.d0d0.55 Mar 23 2011 01:57 PM Automatic
a.b.c.98 0100.1b77.08bb.89 Mar 23 2011 01:15 PM Automatic
a.b.c.99 0100.1ec2.47d7.19 Mar 23 2011 12:43 PM Automatic
a.b.c.102 0100.1310.8e74.78 Mar 23 2011 12:41 PM Automatic
a.b.c.103 0100.24d6.58b0.82 Mar 23 2011 01:44 PM Automatic
a.b.c.104 0100.2608.7df2.68 Mar 23 2011 03:23 PM Automatic
a.b.c.106 01c8.bcc8.1a86.41 Mar 23 2011 03:56 PM Automatic
a.b.c.107 01a4.6706.1e54.94 Mar 23 2011 04:08 PM Automatic
a.b.c.108 017c.c537.46ac.0e Mar 23 2011 02:41 PM Automatic
a.b.c.111 0100.037f.0ea2.19 Mar 23 2011 02:47 PM Automatic
a.b.c.112 01d8.3062.75c5.9c Mar 23 2011 03:33 PM Automatic
a.b.c.113 0021.9116.449e Mar 23 2011 03:36 PM Automatic
a.b.c.114 0100.1ff3.46d9.a9 Mar 23 2011 03:40 PM Automatic
a.b.c.116 0104.1e64.4a0d.a3 Mar 23 2011 04:21 PM Automatic
a.b.c.117 0190.27e4.4ae8.94 Mar 23 2011 04:24 PM Automatic
Thanks! -
VRF and DHCP issue
We have a 6500 ( 12.2 (33) SXH5 ) that has a VRF running for our guest network. On this 6500 resides the DHCP pool with a range defined for our guest network. We have a stack of 3750's (12.2 (46) SE) connected to the 6500 with a L3 connection. The 3750's have a local guest VLAN with its gateway defined in a VLAN interface. This VLAN on the 3750 has an IP helper address pointing to an IP within the VRF on the 6500. When debugging DHCP on the 6500, a request is received and sent back out. The client never receives this request.
If a static IP is applied, the client is able to communicate anywhere within the VRF successfully (including pinging the IP within the helper-address. As many posts have pointed out - there is no VRF <name> under the ip dhcp pool <name> within the 6500. I am just wondering if anyone else has run into this and what their solution was.
Thanks.Hi,
I have tested the dhcp server and vrf on Cisco 3640 and it is working without VRF under the ip dhcp pool. Please ensure that you have configured routing for the dhcp-relay agent(VLAN facing dhcp client on 3750 in your case). -
Hi All,
We have 2 x Nexus 7 cores and several access switches 3750 + 2960 and several VLANs.
All working well until recently we have a couple of users in VLAN say 200 reported they can not get an IP address from our Windows DHCP server.
ie hence they can not log to the Domain and we temporarly assign them a static IP addresses until we figure out what went wrong!!!
We checked the trunk , the DHCP server but can not see anything wrong
How do we troubleshooting this issues ?
Any advices are much appreciated
Thanks
PeterHi ,
Below are part of the Core Nexus 7 config:
ip dhcp relay
port-channel load-balance src-dst ip-l4port-vlan
vpc domain 70
peer-switch
role priority 10
peer-keepalive destination 172.18.111.251 source 172.18.111.250
peer-gateway
track 10
auto-recovery
ip arp synchronize
interface Vlan1
no ip redirects
no ipv6 redirects
interface Vlan100
no ip redirects
ip address 172.18.100.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp100
preempt
priority 130
ip 172.18.100.3
description Servers
no shutdown
interface Vlan101
no ip redirects
ip address 172.18.101.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp101
preempt
priority 130
ip 172.18.101.3
ip dhcp relay address 172.18.100.62
ip dhcp relay address 172.18.100.160
description Workstations Executive
no shutdown
interface Vlan102
no ip redirects
ip address 172.18.102.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp102
preempt
priority 130
ip 172.18.102.3
ip dhcp relay address 172.18.100.62
ip dhcp relay address 172.18.100.160
description Workstations Security
no shutdown
interface Vlan200
no ip redirects
ip address 172.18.200.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp103
preempt
priority 130
ip 172.18.200.3
ip dhcp relay address 172.18.100.62
ip dhcp relay address 172.18.100.174
ip dhcp relay address 172.18.100.160
description Workstations IS
no shutdown
interface Vlan105
no ip redirects
ip address 172.18.105.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp105
preempt
priority 130
ip 172.18.105.3
ip dhcp relay address 172.18.100.62
description Workstations Food and Beverage
no shutdown
interface Vlan111
no ip redirects
ip address 172.18.111.1/24
no ipv6 redirects
hsrp 0
authentication text hsrp111
preempt
priority 130
ip 172.18.111.3
description Device Management
no shutdown
management
interface Vlan112
no ip redirects
ip address 172.18.112.1/23
no ipv6 redirects
hsrp 0
authentication text hsrp112
preempt
priority 130
ip 172.18.112.3
ip dhcp relay address 172.18.100.62
ip dhcp relay address 172.18.100.160
description Workstations General
no shutdown
And the config for the Access switch 3750 below:
Building configuration...
Current configuration : 17076 bytes
version 12.2
no service pad
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
hostname LOADINGDK
boot-start-marker
boot-end-marker
aaa new-model
aaa group server radius Radius
server 172.18.100.113 auth-port 1812 acct-port 1813
server 172.19.100.114 auth-port 1812 acct-port 1813
aaa authentication login default group Radius local
aaa authorization console
aaa authorization exec default group Radius local
aaa session-id common
clock timezone AEST 10
clock summer-time AEST recurring 1 Sun Oct 2:00 1 Sun Apr 2:00
switch 1 provision ws-c3750g-24ps
switch 2 provision ws-c3750-24ts
system mtu routing 1500
udld enable
ip subnet-zero
errdisable recovery cause bpduguard
errdisable recovery cause psecure-violation
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree portfast bpduguard default
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
vlan internal allocation policy ascending
lldp run
ip ssh version 2
class-map match-all avaya-voice-control-
match access-group name avaya-voice-control-
class-map match-all AutoQoS-VoIP-RTP-Trust
match ip dscp ef
class-map match-all AutoQoS-VoIP-Control-Trust
match ip dscp cs3 af31
class-map match-all avaya-voice-
match access-group name avaya-voice-
policy-map avaya-ip-phone-input-
class avaya-voice-
set dscp cs2
police 1000000 8000 exceed-action policed-dscp-transmit
class avaya-voice-control-
set dscp cs3
police 1000000 8000 exceed-action policed-dscp-transmit
class class-default
set dscp default
policy-map AutoQoS-Police-CiscoPhone
class AutoQoS-VoIP-RTP-Trust
set dscp ef
police 320000 8000 exceed-action policed-dscp-transmit
class AutoQoS-VoIP-Control-Trust
set dscp cs3
police 32000 8000 exceed-action policed-dscp-transmit
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk native vlan 111
switchport trunk allowed vlan 102,105,111,112,116,117,142,160-162,184,200,302
switchport mode trunk
interface GigabitEthernet1/0/1
switchport access vlan 200
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/2
switchport access vlan 102
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/3
switchport access vlan 142
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/4
switchport access vlan 105
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/5
switchport access vlan 105
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/6
switchport access vlan 160
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/7
switchport access vlan 160
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/8
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/9
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/10
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/11
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/12
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/13
switchport access vlan 302
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/14
switchport access vlan 102
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/15
switchport access vlan 302
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/16
switchport access vlan 302
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/17
switchport access vlan 162
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/18
switchport access vlan 162
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/19
switchport access vlan 162
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/20
switchport access vlan 162
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/21
switchport access vlan 112
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/22
switchport access vlan 142
switchport mode access
switchport voice vlan 184
spanning-tree portfast
interface GigabitEthernet1/0/23
description device doesn't like poe
power inline never
switchport access vlan 117
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/24
switchport access vlan 116
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface GigabitEthernet1/0/25
switchport trunk encapsulation dot1q
switchport trunk native vlan 111
switchport trunk allowed vlan 105,111,112,116,117,142,160-162,184,200,302
switchport mode trunk
shutdown
speed nonegotiate
interface GigabitEthernet1/0/26
description - coresw2 uplink -
switchport trunk encapsulation dot1q
switchport trunk native vlan 111
switchport trunk allowed vlan 102,105,111,112,116,117,142,160-162,184,200,302
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/27
shutdown
interface GigabitEthernet1/0/28
shutdown
interface FastEthernet2/0/1
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/2
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/3
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/4
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/5
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/6
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/7
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/8
switchport access vlan 161
switchport mode access
spanning-tree portfast
interface FastEthernet2/0/9
interface FastEthernet2/0/10
interface FastEthernet2/0/11
interface FastEthernet2/0/12
interface FastEthernet2/0/13
switchport access vlan 102
switchport mode access
switchport voice vlan 184
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
priority-queue out
mls qos trust dscp
spanning-tree portfast
service-policy input avaya-ip-phone-input-
interface FastEthernet2/0/14
interface FastEthernet2/0/15
interface FastEthernet2/0/16
interface FastEthernet2/0/17
interface FastEthernet2/0/18
interface FastEthernet2/0/19
interface FastEthernet2/0/20
interface FastEthernet2/0/21
interface FastEthernet2/0/22
interface FastEthernet2/0/23
interface FastEthernet2/0/24
interface GigabitEthernet2/0/1
description - coresw1 uplink -
switchport trunk encapsulation dot1q
switchport trunk native vlan 111
switchport trunk allowed vlan 102,105,111,112,116,117,142,160-162,184,200,302
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet2/0/2
shutdown
interface Vlan1
no ip address
no ip route-cache
no ip mroute-cache
shutdown
interface Vlan111
ip address 172.18.111.13 255.255.255.0
no ip route-cache
no ip mroute-cache
ip default-gateway 172.18.111.3
ip classless
no ip http server
no ip http secure-server
ip access-list extended avaya-voice-control-
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.18.184.0 0.0.3.255 range 2048 3329 dscp cs3
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.19.184.0 0.0.0.255 range 2048 3329 dscp cs3
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.17.43.0 0.0.0.255 range 2048 3329 dscp cs3
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.18.181.0 0.0.0.255 range 2048 3329 dscp cs3
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.19.181.0 0.0.0.255 range 2048 3329 dscp cs3
deny ip any any
ip access-list extended avaya-voice-
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.18.184.0 0.0.3.255 range 2048 3329 dscp ef
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.19.184.0 0.0.0.255 range 2048 3329 dscp ef
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.17.43.0 0.0.0.255 range 2048 3329 dscp ef
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.18.181.0 0.0.0.255 range 2048 3329 dscp ef
permit udp 172.18.184.0 0.0.3.255 range 2048 3329 172.19.181.0 0.0.0.255 range 2048 3329 dscp ef
deny ip any any
ip radius source-interface Vlan111
logging history informational
logging trap notifications
logging facility syslog
logging 172.18.100.103
logging 172.18.100.191
snmp-server location C3.01
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps cluster
snmp-server enable traps entity
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps flash insertion removal
snmp-server enable traps port-security
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps license
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps hsrp
snmp-server enable traps bridge newroot topologychange
snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
snmp-server enable traps syslog
snmp-server enable traps vlan-membership
snmp-server host 172.18.100.191 ..traps..
control-plane
banner login ^CCCCCC
Authorized access only! Disconnect IMMEDIATELY if you are not an authorized user! ^C
ntp clock-period 36029332
ntp server 172.18.111.2
ntp server 172.18.111.1
end
Thanks
Peter -
DNS / DHCP Issues in Server 2008R2 Domain
Hi folks,
We’ve been having an ongoing issue for a while now in that some PCs and laptops (Win 7) in our company can’t be contacted by hostname i.e. if we try and RDP from one Windows 7 PC to another the RDP session fails as if the PC isn’t turned on, but it
is indeed turned on and connected to the network.
Even if we ping the host name of a particular computer that is on it fails to reply but if I go into DHCP I can find the hostname bit it has a different IP address assigned to it other than what is listed in DNS for that host name.
So for some reason when some computers get switched on and be allocated a new dynamic IP address through DHCP the corresponding record in DNS doesn’t seem to get updated meaning we need to go into DNS and manually amend the Host A record with the new
IP address that it has been given so we can RDP onto that computer using the hostname.
At present aging and scavenging isn’t enabled in our environment as we are afraid to in case it removes live DNS entries that just haven’t been turned on in a wee while. Does aging and scavenging just ignore static DNS entires and does aging and
scavenging work in DHCP as well?
One other thing I noticed is that if I delete an incorrect DNS Host A record and create it manually and assign the hostname and the correct IP address it says static rather than having a timestamp on it. When I create the new record I always click on our
domain in the Forward Lookup Zone and on creation I always select Create the associated pointer (PTR) record so not sure why the manual record doesn’t get a time stand.
So any help/advice or suggestions would be greatly appreciated.
Thanks,
BonemisterHi David,
Thanks for your reply and for clarifying those things for me. Unfortunately in my workplace when I add a manual DNS Host A record it does become a static entry and doesn't have the '0'
you mention, do you have any idea why that would be as I'm worried about it affecting things if I were to enable aging and scavenging.
Is it possible to just enable aging and have it remove entries before a time of my choosing or does scavenging need to be enabled also?
I still can't understand why the relationship between DHCP and DNS isn't working correctly. Sure if DNS has an A record for a computer and the IP address changes via DHCP there is bound to be
a way to setup DNS to be able to update the records it holds - do you know if my reading of this is correct.
By the way, I can confirm that my adapters TCP/IP DNS settings are the same on of the PCs that had the DNS fault as in your screenshot the only different is we have the tick in Append parent suffixes... - would that make a difference.
Thanks also for that other link, it seems very interesting and I'll have a good read through it carefully before doing anything!!
Thanks again for you reply and I look forward to seeing any responses.
Regards,
Bonemister -
[Solved] Several installs and issues with DHCP issue every time.
Edited: more concise information!
Hi folks,
I was using Arch fine for months but decided to reinstall it fresh at the new year, but since then I have been plagued by connection issues. I install Arch and follow many of the tips found in these Wikis to set it up how I like then install preload and readahead.
Post-Installation Tips
http://wiki.archlinux.org/index.php/Pos … ation_Tips
- LCD filtered fonts
- Disable IPv6 (I use Chorus/NTL and they have a tip for improving Firefox that disables IPv6, so I think that this is not to blame)
Laptop
http://wiki.archlinux.org/index.php/Laptop
- Battery state monitoring utilities (acpi)
- Laptop-mode-toold
- Powernowd
Maximising Performance
http://wiki.archlinux.org/index.php/Max … erformance
- Swapiness
- Mount /tmp to RAM
My internet connection works fine, even when rebooting, but later I turn on my computer and WICD or networkmanager fails on "obtaining IP address. I really think that there is something in one of these tips that is causing this problem, but I am at a loss as to what. Like I say, I was using it happily for many months before these current issues. The only thing I did differently was systematically set up my computer with all the tips detailed above, where as before, I collected these tips over a period of time and did not do them all straight after installation. I have tried rolling back the changes and this has not fixed the issue.
I have had this issue over many reinstalls, using networkmanager or WICD and each time I was hoping that I was doing something wrong. I have an Ubuntu and work Windows laptop that both work fine, so I don.t think it is anything to do with the connection itself.
I am not sure what information you would need so I thought I would post both of these files. If you would like anything else, give me a shout and i can post it.
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_GB.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Dublin"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq vboxdrv coretemp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="laptop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(preload syslog-ng hal wicd @powernowd @laptop-mode @fam @alsa @sensors @readahead-list)
/etc/resolv.conf
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
Thanks for your help,
Scott
Last edited by ScottArch (2010-02-14 12:30:25)Hey Scott!
I don't know if it is helpful in any way but I have a similar problem with my desktop PC.
I have two ethernet controllers installed and somtimes I had a Ip address assigned and sometimes I didn't.
One which is connected to the router and a 2nd one I use sporadically to connect additional computers.
The dhcpcd would fail to load even if I followed steps suggested from other forum members.
My temporary fix was to run:
# dhcpcd
manually.
If this helps you might consider adding "dhcpcd" at the end of
/etc/rc.d/network
I know it's not really a fix but it helps me to get a working connection whoch otherwise would fail - or work if lucky but i don't like lucky with network/internet ^^ -
2100 wireless LAN controller intermittant DHCP issue does not respond to clients
Hi everyone,
I have been struggling with a difficult problem for some time now:
The cisco 2100 wlan controller I have is configured with a dhcp scope in the same ip address range as its WLAN. The configuration works and on a good day I have up to 200 clients connecting with out issue. In the web interface they display as associated and authenticated
On a bad day I find I will begin seeing about 50-80% of all new devices that attempt to join the WLAN show up as associated but not authenticated. These clients end up self assigning themselves a 169.254.0.0/16 (APIPA) address
When my controller / WLAN enters into this state: if clients leave the WLAN they typically fail to get back on and successfully authenticate. By the end of a day around 80-90% of all devices are essentially without Internet access due to this issue.
Rebooting the controller and or APs typically makes no difference or makes things worse – although sometimes it appears to resolve the issue. The same holds for disabling the entire wlan for about 10 minutes and then re enabling it.
Im using 1130 cisco aironet APs with the controller. I have checked extensively for interference and congestion – I think I have congestion – some APs typically host 40 to 90 devices. However as mentioned on a good day the wlan will host 200 devices all day without any issue and some APs will host 50 to 70 devices without major issue.
I can provide more specifics if anyone should need – eg firmware, IP addresses, exact model numbers etc.
Please let me know if anyone has seen something like this before ?
I believe the 2100 is rated to handle up to 350 devices and its recommended not to load a 1130 AP with more than 25 devices ??
Regards
MatthewHi Amijad, Hi George:
Thank you both for your time in considering my situation.
I will think about implementing an independant DHCP server; im really wondering if the equipment is just overloaded
- What software versoin the WLC uses?
Product Version.................................. 6.0.199.4
RTOS Version..................................... 6.0.199.4
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
PID: AIR-WLC2106-K9, VID: V05
- What ports of the WLC are connected to the neighbor swtich? one or more?
2 ports connect to the neighbor switch on separate vlans
- port 1 is vlan 0 and hosts the management and ap-management IPs for the wlan controller
- port 2 is vlan 1 and hosts the wlan
- the controller has one dhcp scope defined on port 2 for the WLAN
- What is the security of your WLAN?
WPA+WPA2
AES
PSK
- Do you have "DHCP required" enabled on the WLAN?
yes DHCP required is enabled in the WLAN
please let me know if you have any additional advice.
regards
Matthew -
Hi All
I am installing a 3750 switch with integrated controller and 12 x Cisco 1140 AP's. I have configured the 3750 WLC with a management and AP Manager IP address along with 3 WLAN profiles and security settings. I am confident that these are correct, and in any case are, I believe, not related to the problem I have.
None of my AP's would connect to the controller and when I checked the DHCP (Windows Server) server they had not been issued with an IP address. I logged into an AP via the console and saw the following message "Not sending discovery request AP does not have an ip" If I plug a laptop into the port the AP connects to I pick up an IP address without a problem from the DHCP server. This is not a faulty AP issue as none of the AP's are getting an IP address.
The only other relevant fact is that the Windows DHCP server is on a different subnet (VLAN)though I have enabled DHCP forwarding which obviously works as my laptop gets an IP address.
I have raised this with Cisco TAC and their first response has been to get me to configure Option 43. I will try this but am not expecting it to work as the only thing this will do is to return the IP address of the controller. My AP's however are not getting any response.
Any suggestions as to how to resolve would be gratefully received.Wouldn't option 43 only work when the AP's are actually getting an IP address?
Could you post an extended capture of the AP output during the boot and lack of join?
To make sure you connectivity is what it should be, you could always try manually assigning an IP address to the AP, and also manually tell the AP the controller IP address. If that works, then you likely have a problem with your DHCP server or scope definition. Do you have any MAC assignments/reservations in the DHCP scope? Have you tried reserving the AP IP addresses by MAC address within the relevant DHCP scope? -
When I connect to my wireless router (D-Link WBR-2310 I believe) using my mac, it gets the default self-assigned address instead of DHCP-assigned address. My PC connects fine wirelessly and wired over ethernet. If the router is reset, it works fine. If I assign manual address to iBook wireless, it works fine (by "works fine" I mean that I can connect to the internet).
Had similar problem with my old Linksys router (Linksys WRT54G) where the following devices had issues connecting to the internet iPod Touch, iBook, PowerBook, and MacBook. This was under unsecured, WEP and WPA settings.It seems that the issue is resurfacing with my current router.
Currently, I am using WPA security (I don't like WEP and neither does my PC). I would rather not switch security settings to unsecured due to the close proximity of my neighbours (yes it's canadian spelling!).
Any suggestions?I have encountered this same router and issue visiting my future in-laws for the holidays. DHCP with manual address appears to work, but I also still encounter occasional drops. The router is setup for WPA2 security, and support a mix of Mac and Win clients. I haven't put a lot of time into trying to fix it, but here is what I know so far:
1) Sometimes it does just work with DHCP
2) DHCP with manual address works, but will still drop occasionally for brief periods
3) Sometimes, just turning the airport off then on again will resolve the issue and pull an address
4) Just waiting about 30-60 seconds also seems to work -- usually
5) Plugging into the wire works great!
I haven't sat by the router and worked on this, but it seems that occasionally the router just drops the signal, and with it the DHCP assignments. Something about the DHCP implementation is very slow, and it just take a while to get around to assigning an address to my machine. I haven't looked into firmware updates since it's not my box and I don't want to mess it up further and then leave, but that's certainly something to check into.
We also have an 12" PB that cannot even connect to the wireless with the "Error joining wireless network" message. Haven't been able to figure that one out at all.
They may just be getting an Airport or Linksys as a late x-mas gift here... (as my connection drops again while I type this! Airport off, airport on, wait 30 sec, and we're back)
Cheers, and good luck! -
Using X3500 as a Wireless Extender DHCP issue iPhone 6
Hi
Hopefully a simple question with a simple answer.
Background:
I've transitioned away from my ADSL ISP to a cable provider (VirginMedia). My new ISP comes with a cable modem (SuperHub 2 ac) and I've connected the two devices together to extend my home wireless network. The cable modem is The two routers are physically remote from each other - connected via just their Ethernet ports - via power-line technology (Devolo dLAN 1200+). The two routers have the same broadcast SSID albeit on separate channels.
Issue:
All devices in my house, laptops tablets, phones roam between the two wi-fi zones seamlessly *except* the iPhone 6 (iOS8.1), this works on the cable modem wi-fi - but not on the X3500 wi-fi. I also have an iPad Mini 2 (also iOS8.1) which also works - so rightly / wrongly I've ruled out iO8.1 as the issue. Oddly the iPhone 6 connects to the x3500 but doesn't obtain an IP address (the cable modem is the DHCP server). Even setting a static IP address doesn't help.
Observation(s):
If the X3500 is setup as a DHCP server, the iPhoen connects (and gets an IP address), but then the default gateway is incorrect (gatway is the IP address of the X3500 not the remote cable modem). I can't find anywhere to specify a default gateway in the setup.
Question
I'm beginning to think this is an issue with the iPhone 6 (knowing all other devices work correctly), but I just want to make sure I'm configuring the X3500 correctly. I'm specifically interested in the whether I'm using the right "Mode"ADSL / Ethernet. I've tried "Bridged Mode Only" (ADSL) and "Automatic DCHP Only" (Ethernet) but neither seem to resolve the issue that the iPhone 6 is having.
any suggestions on how to resolve / troubleshoot would be most welcomed.
Thanks!
Solved!
Go to Solution.Yes, there's a way for you to override the IP Address. It is on Router Address under Network Setup on the Basic Setup tab. If I'm not mistaken, one end of the Ethernet cable should be connected to the regular Ethernet port of the cable modem and the other end to the cable port of the X3500.
But if it's just the iPhone that won't connect to the X3500, it might be okay to retain the current configuration of the router, but try adjusting the wireless security mode or set the wireless channel to 11 and observe what happens. -
I am sorry a am i newbie in dhcp.
I have a v490 server ,with 4g memory,the server is to be configured as a dhcp server.And i add subnets to the server ,and then distribute IPs for each subnet.
The are about 50 subnets and 8000 IPs in each subnet,but when i tried to add the 51th subnet,there is a error:
Error editing the macro 10.212.192.0,message from the server was :Non-memory resources unavailable
I tried to add another subnet,but the issue persists.Is there anybody could help me???Well it looks like you did as much as you can. I would try to do this next. Configure a temporary dhcp on the access point and see if you can you get an IP Address. Also place a sniffer and monitor the port to see if you can see any request or replies. Other than that, you can always try to load a different IOS version and see if that works for you.
-
Cisco ACS 4.2.1(15) AND wind 7 DHCP issues
Hi All,
I am having issue with wirelss client using win 7 over 802.1x using MS-PEAP. The ACS server shows that client are authenticate,but client can't get IP address from the DHCP server(from multiple subnets and subnets are berely use, so there are enough IPs for all the clients). BTW not all clients are having issue. I kow this was a bug with XP and there was a fix for it. Can't find anything on Microsoft site which acknowledge the issue, but I don't thinks that is an ACS issue either.
Has anyone in the forums had or having this issue? If so, can you please share the solution.
Thanks,
Jean Paul.---Hi Surenda,
Thanks for your reply. Nop, there is no WLC yet, but the WLC will be installed shortly.
Thanks,
Jean Paul
Maybe you are looking for
-
Why do I need Cellular Data turned on to send/receive MMS?
So after over 3 hours on the phone with Verizon, Apple, then Verizon again trying to figure out why I can't send or receive mms messages unless Cellular Data is on, doing a hundred soft/hard/network/every reset imaginable, a Verizon rep this morning
-
Dear All, At the time of MIRO entry, the system has automatically generated the invoice for some other vendor and not from the PO. We have checked the partner functions also...it is same PO vendor. Ordering Address Ship to Party Invoice to party Thes
-
Is there any way to clone a machine using boot camp running WinXP. The Mac side is running Snow Leopard. I want to clone a newly set up machine on to a number of machines in a student lab. I am wanting to clone both particians
-
My Iphone 5 has completly stopped working, have tried holding the sleep wake buttons etc but still no responce, there is an apple icon that appears but it then just goes agsin, any ideas.
-
Cannot drag and drop when screen sharing
When i try to drag and drop files, whilst i'm screen sharing with my mac at work, i just get a message in the file transfer window, saying that 'ichat waiting for mac to accept file transfer'. But i don't get a dialogue box asking me to accept the fi