Community discussions

MikroTik App
 
firebat
Member
Member
Topic Author
Posts: 389
Joined: Mon Apr 11, 2005 8:38 am

DUDE is still probing telnet even though service was deleted

Tue Oct 10, 2006 4:14 am

I running Beta 10. I ran discover on a Trango AP and it discoverd Ping, telnet, etc serivces. I deleted all of the services except Ping. I thought everything was working find until the AP rebooted itself (another issue :)) . I had the AP set to not enter operational state if you telnet to the unit within 30 seconds of the reboot. When the AP rebooted by itself, it came up in non-operational state. I rebooted the unit again myself and it again returned to non-operational state. I went ahead and out the unit in operational state and looked at the event log. The event log showed
service telnet down and then up again for the AP. This explains the behavior of the AP not entering operational mode on a reboot. How can you tell if DUDE is probing services that have been deleted from the elements serivces tab?

BTW, how do you copy lines from the event log? Ctrl-C doesn't work and there is no right-click copy option.
 
BobT
just joined
Posts: 11
Joined: Wed Oct 11, 2006 4:49 am
Location: Dallas, TX, USA
Contact:

Wed Oct 11, 2006 5:07 am

I can't help you with the telnet service not turning off but to copy event log information you can open the actual Event Log file with a text editor (Notepad, Wordpad, etc.) and easily copy any event or series of events you desire. The actual Event Log is found in the "\Program Files\Dude\data\files directory. It is typically named "Event-2006-10-10-13-35.log" with the numbers part of the filename being the date and time the log file was created.
 
firebat
Member
Member
Topic Author
Posts: 389
Joined: Mon Apr 11, 2005 8:38 am

Wed Oct 11, 2006 7:17 am

Thanks Bob. That seems to be a decent workaround at the moment.

Uldis: For the telnet issue, I'm running torch and I can see DUDE performing the telnet probe for this one AP. If I shut down DUDE, its stops. I added and deleted the telnet service for the AP and that didn't help. I deleted the AP all together and readded it with just ping as a service (no discovery) and DUDE again is probing telnet. I even deleted all services from the AP and it still probes telnet. I then looked in the DUDE services tab and saw a telnet to that specific AP still listed as a service. Should this service still be active if it was deleted from the device? I didn't manually add it to the list. I went ahead and deleted it from the DUDE services list and that fixed the issue.

After further examination of the services list, I saw duplicate entries for a couple of services. I have a a duplicate ping service for the same AP noted above as well as a duplicate ping service for DUDE. I think there is something awry with services creation as I didn't manually create any of these services. They were all created via discovery.
 
firebat
Member
Member
Topic Author
Posts: 389
Joined: Mon Apr 11, 2005 8:38 am

Thu Oct 12, 2006 10:09 am

I'm not sure what is happening now. After I deleted the telnet and extra ping services for the AP from the DUDE-services tab, they are reappearing after some time (within an hour..not sure exactly). How do I figure out what is going on? I have no elements setup to monitor this IP with telnet and a 2nd ping and this telnet service is appearing from somewhere.

Uldis: Any suggestions?
 
uldis
MikroTik Support
MikroTik Support
Posts: 3446
Joined: Mon May 31, 2004 2:55 pm

Thu Oct 12, 2006 1:07 pm

you must have periodic auto discovery element added. See in Network Map settings that device is in.