I have been trying to search for this and was not able to find any topic so far.
Is it possible to log URL traffic hotspot username based instead of their IP addresses
firstly you should determine the where to save your log file.remote device or same hotspot rb.if same rb you have to upgrade your memory cache like microsd.
if remote: system–logging—actions—remote=== set your remote syslog device ip.(ex. dude in windows)
system–logging—rules=== add new rule here.( add firewall to remote)
than:
ip—firewall —select protocol–tcp and udp (depends on you normally tcp)— chain forward----connection state new—action log.
thats it. than you should see the tcp connections in log part …
I have set up a web proxy on port 80 to 8080 and done the system-logging steps as detailed above.
Now it looks like I am logging all traffic through the proxy, but I am also getting bucketfuls of other stuff.
The traffic I want to see is prefixed GET and the other stuff is prefixed POST.
My LAN IP is 192.168.88.1
My comp is on 192.168.88.252
Logging is set up like this:
Enabled: Y
Topics: web-proxy
! debug
Prefix: wpx
Action: memory
I’m getting a log full of these (2 or 3 every second):
Time: Aug/11/2013 21:33:01
Buffer: Memory
Topics: web-proxy account
Message: wpx: 192.168.88.252 POST http://192.168.88.1/jsproxy action=allow cache=MISS
I simply can’t get rid of them, and I only get them from my IP, not from other IPs on the same subnet.
If anyone could point me in the right direction, I’d be very grateful.
Not sure if you know… Your logging config (Topics: web-proxy ! debug Prefix: wpx) does not log just the traffic marked with the wpx prefix. It will furthermore add this prefix to every log entry…
You could use a log parser script (examples around here in the Forums) to filter for GET and POST and just write those to the syslog server.
While typing this i just noticed that this post is 3 years old. Nevertheless, this were my 2 cents…
With thanks to Dash for the recent response to my enquiry.
I had actually sourced an alternative solution, but I am now thinking of going back to the Mikrotik option. I will start reading up on your suggestion.