SmallNetGuy
Regular Contributor
Hi,
I'm sorry if I sound paranoid or stupid (or both)... My router/networking knowledge is rather limited. I've checked my router logs, and among usual things, I found couple of lines that I did not see before. I am from Canada, and these "Client" IPs (139.162.102.46 and 80.82.77.139) are not mine for sure. Should I be worried and I'd greatly appreciate if someone could tell me how to secure my connection. I have quite long login password using alphanumeric characters combined with some special characters. Not sure if there is anything in my router settings that I could disable to make it more secure.
Thanks in advance to any good soul who is willing to help this idiot here
This is few parts from my router logs:
Oh, and another little thing... last couple of logging attempts, I am getting a notification about "Login not secure". I've never seen that in the past. Both, Chrome and Firefox are giving me same notification. Screenshot attached.
I'm sorry if I sound paranoid or stupid (or both)... My router/networking knowledge is rather limited. I've checked my router logs, and among usual things, I found couple of lines that I did not see before. I am from Canada, and these "Client" IPs (139.162.102.46 and 80.82.77.139) are not mine for sure. Should I be worried and I'd greatly appreciate if someone could tell me how to secure my connection. I have quite long login password using alphanumeric characters combined with some special characters. Not sure if there is anything in my router settings that I could disable to make it more secure.
Thanks in advance to any good soul who is willing to help this idiot here
This is few parts from my router logs:
Apr 3 12:33:52 pptpd[8662]: CTRL: Client 139.162.102.46 control connection started
Apr 3 12:33:52 pptpd[8662]: CTRL: EOF or bad error reading ctrl packet length.
Apr 3 12:33:52 pptpd[8662]: CTRL: couldn't read packet header (exit)
Apr 3 12:33:52 pptpd[8662]: CTRL: CTRL read failed
Apr 3 12:33:52 pptpd[8662]: CTRL: Client 139.162.102.46 control connection finished
Apr 3 13:02:39 dnsmasq-dhcp[2531]: DHCPDISCOVER(br0) 02:1b:b3:70:c3:11
Apr 3 13:02:39 dnsmasq-dhcp[2531]: DHCPOFFER(br0) 192.168.1.15 03:1a:b3:30:b0:31
Apr 3 13:02:40 dnsmasq-dhcp[2531]: DHCPREQUEST(br0) 192.168.1.15 03:1a:b3:72:b0:31
Apr 3 13:02:40 dnsmasq-dhcp[2531]: DHCPACK(br0) 192.168.1.15 00:1b:c3:70:b2:13
Apr 3 13:24:32 dnsmasq-dhcp[2531]: DHCPREQUEST(br0) 192.168.1.153 d3:96:4e:28:4a:48
Apr 3 13:24:32 dnsmasq-dhcp[2531]: DHCPACK(br0) 192.168.1.153 d4:42:9e:23:8a:58
Apr 3 13:55:37 dnsmasq-dhcp[2531]: DHCPREQUEST(br0) 192.168.1.21 44:64:95:55:a3:2d
Apr 3 13:55:37 dnsmasq-dhcp[2531]: DHCPACK(br0) 192.168.1.21 33:64:95:53:a2:2b
.
.
Apr 18 20:13:11 pptpd[32235]: CTRL: Client 139.162.102.46 control connection started
Apr 18 20:13:12 pptpd[32235]: CTRL: EOF or bad error reading ctrl packet length.
Apr 18 20:13:12 pptpd[32235]: CTRL: couldn't read packet header (exit)
Apr 18 20:13:12 pptpd[32235]: CTRL: CTRL read failed
Apr 18 20:13:12 pptpd[32235]: CTRL: Client 139.162.102.46 control connection finished
.
.
Apr 21 08:33:25 pptpd[8959]: CTRL: Client 80.82.77.139 control connection started
Apr 21 08:33:25 pptpd[8959]: CTRL: EOF or bad error reading ctrl packet length.
Apr 21 08:33:25 pptpd[8959]: CTRL: couldn't read packet header (exit)
Apr 21 08:33:25 pptpd[8959]: CTRL: CTRL read failed
Apr 21 08:33:25 pptpd[8959]: CTRL: Client 80.82.77.139 control connection finished
.
.
Apr 21 10:03:00 pptpd[9187]: CTRL: Client 139.162.102.46 control connection started
Apr 21 10:03:00 pptpd[9187]: CTRL: EOF or bad error reading ctrl packet length.
Apr 21 10:03:00 pptpd[9187]: CTRL: couldn't read packet header (exit)
Apr 21 10:03:00 pptpd[9187]: CTRL: CTRL read failed
Apr 21 10:03:00 pptpd[9187]: CTRL: Client 139.162.102.46 control connection finished
.
.
Apr 22 00:22:20 zcip client: configured 169.254.164.23
Apr 22 00:22:20 miniupnpd[861]: HTTP listening on port 42323
Apr 22 00:22:20 miniupnpd[861]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 22 00:22:21 miniupnpd[861]: shutting down MiniUPnPd
Apr 22 00:22:21 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Apr 22 00:22:22 miniupnpd[886]: HTTP listening on port 53852
Apr 22 00:22:22 miniupnpd[886]: Listening for NAT-PMP/PCP traffic on port 5351
Oh, and another little thing... last couple of logging attempts, I am getting a notification about "Login not secure". I've never seen that in the past. Both, Chrome and Firefox are giving me same notification. Screenshot attached.
Attachments
Last edited: