[Mikrotik] dhcp-client always "searching"

Josh Luthman josh at imaginenetworksllc.com
Mon Apr 16 20:37:50 CDT 2012


D'oh

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Apr 16, 2012 9:32 PM, "Bill Prince" <part-15 at skylinebroadbandservice.com>
wrote:

> bozo alert.
>
> The SM through which the mikrotik was talking was filtering bootp client.
>  Turned that off and things work much better.
>
>
> bp
>
>
> On 4/16/2012 6:20 PM, Bill Prince wrote:
>
>> So I started the DHCP server alert on the client 'tik, and it's reporting
>> nothing?
>>
>> Yet the neighbor next door that has just a plain SM sees it just fine.
>>
>> This does not compute.  I think the server is running because the SMs see
>> it, register, and work.
>>
>> What I don't think is working is the DHCP client.
>>
>> bp
>>
>>
>> On 4/16/2012 3:51 PM, Josh Luthman wrote:
>>
>>> Just enable it on an interface.  It will pop up with a list of MACs
>>> that have a dhcp server on them (that the client sees).
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>>
>>>
>>> On Mon, Apr 16, 2012 at 6:47 PM, Bill Prince
>>> <part-15@**skylinebroadbandservice.com<part-15 at skylinebroadbandservice.com>>
>>>  wrote:
>>>
>>>> I've never used the dhcp-server alert tool.  Is there a wiki page or
>>>> something on the care and feeding?
>>>>
>>>> However, I've got the log open, as well as  the leases list open on the
>>>> server.  I never see an offer or anything on the server, so I suspect
>>>> the
>>>> DHCP request is never happening.
>>>>
>>>> bp
>>>>
>>>>
>>>>
>>>> On 4/16/2012 3:36 PM, Josh Luthman wrote:
>>>>
>>>>> Shouldn't, no.  My home router has an IP static and then I use DHCP
>>>>> for testing and such.
>>>>>
>>>>> Does the dhcp-server alert tool complain that there is a DHCP server
>>>>> found?  Does the DHCP server create any lease and say it offered a
>>>>> lease?
>>>>>
>>>>> Josh Luthman
>>>>> Office: 937-552-2340
>>>>> Direct: 937-552-2343
>>>>> 1100 Wayne St
>>>>> Suite 1337
>>>>> Troy, OH 45373
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 16, 2012 at 6:27 PM, Bill Prince
>>>>> <part-15@**skylinebroadbandservice.com<part-15 at skylinebroadbandservice.com>>
>>>>>    wrote:
>>>>>
>>>>>> What I'm wondering is whether the existing IP is getting in the way?
>>>>>>
>>>>>> The old setup was a static IP on ether1.  We're renumbering everything
>>>>>> (new
>>>>>> block from ARIN), and rather than do statics, I thought it would save
>>>>>> time
>>>>>> to just set them to dhcp clients on a subnet-by-subnet basis.
>>>>>>
>>>>>> The existing IP has a default route set.
>>>>>>
>>>>>> So I did not delete or disable the old IP, I just wanted to test the
>>>>>> dhcp.
>>>>>>
>>>>>>
>>>>>> bp
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 4/16/2012 3:13 PM, Bill Prince wrote:
>>>>>>
>>>>>>> The working clients are just plain Canopy SMs.  Set to DHCP client
>>>>>>> w/NAT
>>>>>>> and the DNS passing through to the LAN.
>>>>>>>
>>>>>>> There are 6 APs attached to a CMM micro between the Mikrotik and the
>>>>>>> APs.
>>>>>>>  Same collision domain.  One of the mikrotik clients is on the same
>>>>>>> AP
>>>>>>> as
>>>>>>> one of the Canopy SM clients.  The other mikrotik client is on a
>>>>>>> different
>>>>>>> AP, but same collision domain.
>>>>>>>
>>>>>>> I can ping the IP of the mikrotik router from the client.
>>>>>>>
>>>>>>> bp
>>>>>>>
>>>>>>>
>>>>>>> On 4/16/2012 3:07 PM, Josh Luthman wrote:
>>>>>>>
>>>>>>>> The clients that are working - what are they?  Are they in the same
>>>>>>>> collision domain?
>>>>>>>>
>>>>>>>> What's the network look like between the dhcp server and the working
>>>>>>>> and non working clients?
>>>>>>>>
>>>>>>>> Josh Luthman
>>>>>>>> Office: 937-552-2340
>>>>>>>> Direct: 937-552-2343
>>>>>>>> 1100 Wayne St
>>>>>>>> Suite 1337
>>>>>>>> Troy, OH 45373
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Apr 16, 2012 at 6:01 PM, Bill Prince
>>>>>>>> <part-15@**skylinebroadbandservice.com<part-15 at skylinebroadbandservice.com>>
>>>>>>>>      wrote:
>>>>>>>>
>>>>>>>>> I believe the server is ready and waiting.  There are other
>>>>>>>>> (non-mikrotik)
>>>>>>>>> clients working on the subnet, and there are approximately 198
>>>>>>>>> unused
>>>>>>>>> IPs.
>>>>>>>>>
>>>>>>>>> The Mikrotik DHCP server is running on ROS 3.11.  I've got one
>>>>>>>>> mikrotik
>>>>>>>>> client on ROS 3.17, and another on ROS 4.17; neither one of them is
>>>>>>>>> working.
>>>>>>>>>  They're both just "searching".
>>>>>>>>>
>>>>>>>>> bp
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 4/16/2012 2:57 PM, Josh Luthman wrote:
>>>>>>>>>
>>>>>>>>>> Something is blocking it then.  Are you sure you have the client
>>>>>>>>>> on
>>>>>>>>>> the correct interface?  Is the server ready to go with IPs left in
>>>>>>>>>> the
>>>>>>>>>> pool?
>>>>>>>>>>
>>>>>>>>>> Josh Luthman
>>>>>>>>>> Office: 937-552-2340
>>>>>>>>>> Direct: 937-552-2343
>>>>>>>>>> 1100 Wayne St
>>>>>>>>>> Suite 1337
>>>>>>>>>> Troy, OH 45373
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Apr 16, 2012 at 5:53 PM, Bill Prince
>>>>>>>>>> <part-15@**skylinebroadbandservice.com<part-15 at skylinebroadbandservice.com>>
>>>>>>>>>>        wrote:
>>>>>>>>>>
>>>>>>>>>>> I've never used the dhcp-client until today.  However, it doesn't
>>>>>>>>>>> seem
>>>>>>>>>>> to
>>>>>>>>>>> be
>>>>>>>>>>> working.  All it does is "searching", and there is no hint of a
>>>>>>>>>>> request
>>>>>>>>>>> on
>>>>>>>>>>> the dhcp-server side.
>>>>>>>>>>>
>>>>>>>>>>> What am I missing?
>>>>>>>>>>>
>>>>>>>>>>> If there is a valid (and working) IP (on a different subnet) on
>>>>>>>>>>> the
>>>>>>>>>>> same
>>>>>>>>>>> interface does the dhcp-client get wiggy or something?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> bp
>>>>>>>>>>>
>>>>>>>>>>> ______________________________**_________________
>>>>>>>>>>> Mikrotik mailing list
>>>>>>>>>>> Mikrotik at mail.butchevans.com
>>>>>>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>>>>>>
>>>>>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to
>>>>>>>>>>> Mikrotik
>>>>>>>>>>> RouterOS
>>>>>>>>>>>
>>>>>>>>>> ______________________________**_________________
>>>>>>>>>> Mikrotik mailing list
>>>>>>>>>> Mikrotik at mail.butchevans.com
>>>>>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>>>>>
>>>>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to
>>>>>>>>>> Mikrotik
>>>>>>>>>> RouterOS
>>>>>>>>>>
>>>>>>>>>>  ______________________________**_________________
>>>>>>>>> Mikrotik mailing list
>>>>>>>>> Mikrotik at mail.butchevans.com
>>>>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>>>>
>>>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to
>>>>>>>>> Mikrotik
>>>>>>>>> RouterOS
>>>>>>>>>
>>>>>>>> ______________________________**_________________
>>>>>>>> Mikrotik mailing list
>>>>>>>> Mikrotik at mail.butchevans.com
>>>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>>>
>>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>>>>>>> RouterOS
>>>>>>>>
>>>>>>>>  ______________________________**_________________
>>>>>>> Mikrotik mailing list
>>>>>>> Mikrotik at mail.butchevans.com
>>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>>
>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>>>>>> RouterOS
>>>>>>>
>>>>>>>  ______________________________**_________________
>>>>>> Mikrotik mailing list
>>>>>> Mikrotik at mail.butchevans.com
>>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>>
>>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>>>>> RouterOS
>>>>>>
>>>>> ______________________________**_________________
>>>>> Mikrotik mailing list
>>>>> Mikrotik at mail.butchevans.com
>>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>>
>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>>>> RouterOS
>>>>>
>>>>>  ______________________________**_________________
>>>> Mikrotik mailing list
>>>> Mikrotik at mail.butchevans.com
>>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>>
>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>>> RouterOS
>>>>
>>> ______________________________**_________________
>>> Mikrotik mailing list
>>> Mikrotik at mail.butchevans.com
>>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>>
>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>> RouterOS
>>>
>>>  ______________________________**_________________
>> Mikrotik mailing list
>> Mikrotik at mail.butchevans.com
>> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>>
>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>> RouterOS
>>
>>  ______________________________**_________________
> Mikrotik mailing list
> Mikrotik at mail.butchevans.com
> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
>
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.butchevans.com/pipermail/mikrotik/attachments/20120416/d4dad36e/attachment.html>


More information about the Mikrotik mailing list