routers / syslog
Discussion
Hi folks,
Doing a bit of routine messing around with my connection remembered that I'd switched access control off on my Draytek Vigor 2600We when my brother was using his laptop with it.
When I checked the DHCP IP Assignment table (whereby you can tell what machines have been using the router) there were at least 2 machine names that I didn't recognise
I have just set up and run some syslog monitoring software - but is there any way I can tell who'd been using the machine and when retrospectively?
I have the local IP address they've been using on my router, machine names, MAC addresses, and "Leased time" whatever that is, in the format xxx:xx:xx.xxx
Doing a bit of routine messing around with my connection remembered that I'd switched access control off on my Draytek Vigor 2600We when my brother was using his laptop with it.
When I checked the DHCP IP Assignment table (whereby you can tell what machines have been using the router) there were at least 2 machine names that I didn't recognise

I have just set up and run some syslog monitoring software - but is there any way I can tell who'd been using the machine and when retrospectively?
I have the local IP address they've been using on my router, machine names, MAC addresses, and "Leased time" whatever that is, in the format xxx:xx:xx.xxx
Sending them a message, if this were many years ago before firewalls being needed, I'd have suggested net send, but even if they are Windows machines they'll probably be SP2'd and thus firewalled to stop this.
Personally, I'd just treat it as one of those things, reenable your AC and shrug.
Until the kiddie fiddler squad kick your back door in and demand answers... obviously
Personally, I'd just treat it as one of those things, reenable your AC and shrug.
Until the kiddie fiddler squad kick your back door in and demand answers... obviously
If they're still there on your local network, then I'd suggest that they're stealing your bandwidth, therefore naughty little thieves and it's playtime 
Download something called Nessus. Put their IP addresses into the software and scan 'em - you may find that they're not up to date with patches etc. and have exploitable vulnerabilities. It's not subtle, if they know what they're doing then they'll spot your scanning a mile off but it will send out the right message.
Equally, if they're clueless and you fancy playing dirty then, depending on the vulnerability, either bust their machine or break in to leave a nice 'get off my network' file on their disk.
If you're not into this sort of hacking then ignore my post, turn on access control, use WPA2 if you can, use a big complicated password and implement MAC address filtering on the router. To answer your question, unless you've been running a packet sniffer on a local ethernet port on the router itself then you won't be able to retrospectively see what they've been doing. All you have is the time they've been given an IP by the DHCP server. Syslog on most of these routers will only send particular events (admin access to router, reboots, port scan detection, etc.) rather than detailed activity.

Download something called Nessus. Put their IP addresses into the software and scan 'em - you may find that they're not up to date with patches etc. and have exploitable vulnerabilities. It's not subtle, if they know what they're doing then they'll spot your scanning a mile off but it will send out the right message.
Equally, if they're clueless and you fancy playing dirty then, depending on the vulnerability, either bust their machine or break in to leave a nice 'get off my network' file on their disk.
If you're not into this sort of hacking then ignore my post, turn on access control, use WPA2 if you can, use a big complicated password and implement MAC address filtering on the router. To answer your question, unless you've been running a packet sniffer on a local ethernet port on the router itself then you won't be able to retrospectively see what they've been doing. All you have is the time they've been given an IP by the DHCP server. Syslog on most of these routers will only send particular events (admin access to router, reboots, port scan detection, etc.) rather than detailed activity.
Thanks guys 
My router does give detailed info on all events, syslog running currently.
Router reset last night and one of the machines has connected at some stage today...
Would have liked to try a netsend type thing before reenabling MAC addressing. It doesn't support WPA/WPA2, only WEP which I have had problems with...
Might have a go at some of the suggestions while I have some time tonight. Otherwise I'll just stick the MAC addressing back.
Cheeky barstewards!
Edit: The only IP address I have for them is the internal one assigned by my router - is that all Nessus will need?
My router does give detailed info on all events, syslog running currently.
Router reset last night and one of the machines has connected at some stage today...
Would have liked to try a netsend type thing before reenabling MAC addressing. It doesn't support WPA/WPA2, only WEP which I have had problems with...
Might have a go at some of the suggestions while I have some time tonight. Otherwise I'll just stick the MAC addressing back.
Cheeky barstewards!
Edit: The only IP address I have for them is the internal one assigned by my router - is that all Nessus will need?
Edited by NiceCupOfTea on Monday 16th July 21:24
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff



