+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 21
Wireless Networks Thread, meru reporting restricted ip addresses being issued in Technical; Greetings, When browsing through the station list on my meru controller I'm disturbed to see IP addresses that are excluded ...
  1. #1

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14

    meru reporting restricted ip addresses being issued

    Greetings,

    When browsing through the station list on my meru controller I'm disturbed to see IP addresses that are excluded from distribution being allocated. We've had a lot of problems lately with networking whereby student phones seem to be taking addresses which are statically assigned to to servers. In my dhcp address pool I have those addresses specifially excluded from use so i cant understand why they are being reported as used.

    Im not sure where the fault lies, im posting about it here because its only on the meru controller that ive noticed this problem.

    Any advice would be welcome.
    James

  2. #2

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    Hi all,

    Still getting this problem, does anyone have an idea what may be causing this?

    Thanks
    James

  3. #3

    Join Date
    Apr 2012
    Location
    Northwest, UK
    Posts
    41
    Thank Post
    0
    Thanked 4 Times in 3 Posts
    Rep Power
    6
    Is your DC not also your DHCP server?
    what does DHCP server report?

  4. #4

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    Yes its our dhcp server. Its not showing those addresses being leased because theyre excluded from distribution. The meru controller however does show theyre being issued. I had the same problem today, my nas storage was playing up, i did an arp /a to show what mac was assigned to that address and it showed the nas box. I shut down the nas box, cleared the arp cache and after 5 mins checked again, lo and behold a different mac address which turned out to be a students phone on the wireless. Something is definitely not right.

  5. #5

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    When this has happened in the past, ive checked to see if the offending devices had static addresses, they did not. They were on dhcp.

  6. #6
    clareq's Avatar
    Join Date
    Dec 2005
    Location
    Doncaster
    Posts
    763
    Thank Post
    56
    Thanked 193 Times in 128 Posts
    Rep Power
    102
    Have you a rogue DHCP server anywhere? We had a member of staff plug in a home broadband router for some reason once, and saw a similar issue.

  7. #7

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    Interesting thought, how would i go about finding out? Although, if was something from home use i expect it would be a different gateway and subnet being assigned. Ive got noone complaining about network access problems so far.

  8. #8
    clareq's Avatar
    Join Date
    Dec 2005
    Location
    Doncaster
    Posts
    763
    Thank Post
    56
    Thanked 193 Times in 128 Posts
    Rep Power
    102
    I can't remember how we tracked it down, I'm afraid.

  9. #9

    Join Date
    Jul 2006
    Location
    London
    Posts
    1,273
    Thank Post
    114
    Thanked 244 Times in 195 Posts
    Blog Entries
    1
    Rep Power
    75
    Stick Wireshark on a port and mirror the traffic coming from the Meru controller to the DHCP server (filter for DHCP traffic)

    When you hit a conflict take a look in the traffic capture - at the very least you should be able to confirm whether your DHCP server issued the IP. If it didn't then you need to take a look at your Wireless Controller, as it can also act as a DHCP server.
    Last edited by psydii; 10th June 2014 at 10:31 PM.

  10. #10

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    Thanks for your replies guys. Ive had a check at the meru controller setup, one option confuses me a little. Here is the blurb from the manual regarding dhcp passthrough. Currently we have this option turned on, from what is said below please can you confirm whether that is correct as im thinking it should be off.


    1. In the DHCP Relay Passthrough, select one of the following:
      • On: Enables the DHCP Passthrough; the default setting where DHCP packets are passed through the controller unchanged. With this option, you must configure DHCP relay on any routers between the 802.11 clients and the DHCP server. With this setting, the DHCP Server IP address field in Step 6. is ignored.
      • Off: Disables the DHCP Passthrough. With this setting, DHCP relay

  11. #11

    Join Date
    Jul 2006
    Location
    London
    Posts
    1,273
    Thank Post
    114
    Thanked 244 Times in 195 Posts
    Blog Entries
    1
    Rep Power
    75
    Our core switch does the routing between subnets/VLANs and has the DHCP relay configured.

    Our Meru has DHCP Relay pass through set to 'On'.

  12. #12

    Join Date
    Apr 2012
    Location
    Northwest, UK
    Posts
    41
    Thank Post
    0
    Thanked 4 Times in 3 Posts
    Rep Power
    6
    I haven't used any meru kit before but it seems like you've got the correct settings for DHCP pass through.
    you need to dig deeper, get wireshark on like psydii suggested. you may just have a rogue DHCP server somewhere.
    have you checked the switches for any DHCP config?

  13. #13

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    there arent any odd settings on the switches.. Gonna try wireshark and see what happens. Thanks guys

  14. #14

    Join Date
    Oct 2008
    Location
    Southampton, England
    Posts
    213
    Thank Post
    39
    Thanked 10 Times in 6 Posts
    Rep Power
    14
    ive run wireshark today and the only server i can see responding to dhcp requests is my main dhcp server. I did however notice something odd.

    I started a ping log to a client which reported a duplicate address again this morning (log attached), since id switched it off to make sure it wasnt responding to the ping request i was getting the usual "destination host unreachable" by the ip address of my computer. However. every so often, the ping request timed out and my meru controller responded with "destination host unreachable" instead before it went back to normal. If im correct this should not be happening.
    Pinging 192.168.0.14 with 32 bytes of data:
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Request timed out.
    Reply from 192.168.0.10: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Request timed out.
    Reply from 192.168.0.10: Destination host unreachable.
    Reply from 192.168.0.10: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.
    Reply from 192.168.3.79: Destination host unreachable.

  15. #15

    Join Date
    Jul 2006
    Location
    London
    Posts
    1,273
    Thank Post
    114
    Thanked 244 Times in 195 Posts
    Blog Entries
    1
    Rep Power
    75
    What happens when you run continuous ping to host which is actually on? Maybe you are seeing genuine packet loss?



SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Extricom issues possibly IP address?
    By columbiers in forum Network and Classroom Management
    Replies: 1
    Last Post: 18th May 2012, 06:21 PM
  2. Replies: 11
    Last Post: 6th May 2010, 11:21 AM
  3. IP Address Issue
    By Andie in forum Wireless Networks
    Replies: 7
    Last Post: 23rd March 2009, 03:12 PM
  4. Restricting Access to an IP Address
    By enjay in forum Network and Classroom Management
    Replies: 1
    Last Post: 22nd October 2008, 11:19 AM
  5. Replies: 26
    Last Post: 7th February 2007, 05:33 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •