cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

IP Booter ?

offtrolley
Dabbler
Posts: 18
Thanks: 1
Registered: ‎06-02-2014

IP Booter ?

‎25-03-2020 4:21 PM

My son believes we are being "IP Booted" as our router occasionally disconnects and re-connects. I'm not technical so don't understand if this is possible. He play Fortnight on a PC and believes it's some disgruntled player !!!!

Is the above possible ?

Thanks

 

My router logs show:

16:03:47, 25 Mar. IN: BLOCK [16] Remote administration (TCP [146.88.240.4]:47203-​>[84.92.108.103]:443 on ppp3)
16:03:16, 25 Mar. (5088867.840000) Admin login successful by 192.168.1.91 on HTTP
15:58:39, 25 Mar. IN: BLOCK [16] Remote administration (TCP [162.243.128.185]:48422-​>[84.92.108.103]:22 on ppp3)
15:42:08, 25 Mar. ath10: STA 50:76:af:99:d2:e3 IEEE 802.11: WiFi registration failed
15:39:06, 25 Mar. IN: BLOCK [16] Remote administration (TCP [45.56.91.118]:53484-​>[84.92.108.103]:80 on ppp3)
15:38:47, 25 Mar. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.69]:3074 <-​-​> [84.92.108.103]:3074 -​ -​ -​ [5.71.216.160]:3074 ppp3 NAPT)
15:38:43, 25 Mar. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.69]:3074 <-​-​> [84.92.108.103]:3074 -​ -​ -​ [86.159.88.91]:3074 ppp3 NAPT)
15:38:39, 25 Mar. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.69]:3074 <-​-​> [84.92.108.103]:3074 -​ -​ -​ [94.10.10.27]:3074 ppp3 NAPT)
15:38:27, 25 Mar. (5087378.530000) Lease for IP 192.168.1.121 renewed by host MP1GVEFW (MAC 50:76:af:99:d2:e3). Lease duration: 1440 min
15:38:27, 25 Mar. (5087378.530000) Device connected: Hostname: MP1GVEFW IP: 192.168.1.121 MAC: 50:76:af:99:d2:e3 Lease time: 1440 min. Link rate: 6.5 Mbps
15:38:27, 25 Mar. (5087378.420000) Lease requested
15:38:27, 25 Mar. ath00: STA 50:76:af:99:d2:e3 IEEE 802.11: Client associated
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=2952)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=1480)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=1472)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 74.222.75.113-​>84.92.108.103 fragment_offset=0)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=2952)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=1480)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=2952)
15:38:13, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 74.222.75.113-​>84.92.108.103 fragment_offset=1480)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:12, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:11, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=2960)
15:38:11, 25 Mar. IN: BLOCK [5] Fragmented packet (IP 112.53.82.76-​>84.92.108.103 fragment_offset=1472)
15:38:11, 25 Mar. IN: BLOCK [5] Fragmented packet (UDP 112.53.82.76-​>84.92.108.103 fragment_offset=0)
15:38:08, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:38:07, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:25938 on ppp3)
15:38:06, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:38:05, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:5574 on ppp3)
15:38:04, 25 Mar. BLOCKED 42 more packets (because of Defragmentation failed)
15:38:03, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:46488 on ppp3)
15:38:02, 25 Mar. BLOCKED 4 more packets (because of Defragmentation failed)
15:38:02, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [91.221.52.49]:53-​>[84.92.108.103]:13397 on ppp3)
15:37:59, 25 Mar. BLOCKED 5 more packets (because of Defragmentation failed)
15:37:59, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:7748 on ppp3)
15:37:57, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:37:56, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:7168 on ppp3)
15:37:56, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:37:55, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP Fragment 46.221.0.51-​>84.92.108.103 offset: 1456 on ppp3)
15:37:55, 25 Mar. BLOCKED 4 more packets (because of Defragmentation failed)
15:37:55, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [91.221.52.49]:53-​>[84.92.108.103]:13397 on ppp3)
15:37:53, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:37:52, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:20185 on ppp3)
15:37:52, 25 Mar. BLOCKED 2 more packets (because of Defragmentation failed)
15:37:52, 25 Mar. IN: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [178.176.249.134]:53-​>[84.92.108.103]:30895 on ppp3)
15:37:50, 25 Mar. (5087341.740000) Lease for IP 192.168.1.121 renewed by host MP1GVEFW (MAC 50:76:af:99:d2:e3). Lease duration: 1440 min
15:37:50, 25 Mar. (5087341.740000) Device connected: Hostname: MP1GVEFW IP: 192.168.1.121 MAC: 50:76:af:99:d2:e3 Lease time: 1440 min. Link rate: 866.6 Mbps
15:37:50, 25 Mar. (5087341.620000) Lease requested
15:37:50, 25 Mar. BLOCKED 53 more packets (because of Defragmentation failed)
15:37:50, 25 Mar. ath10: STA 50:76:af:99:d2:e3 IEEE 802.11: Client associated
15:37:50, 25 Mar. ath10: STA 50:76:af:99:d2:e3 IEEE 802.11: Client disassociated
15:37:49, 25 Mar. BLOCKED 14 more packets (because of Defragmentation failed)

Message 1 of 4
(848 Views)
0 Thanks
3 REPLIES 3
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,887
Thanks: 4,979
Fixes: 316
Registered: ‎04-04-2007

Re: IP Booter ?

‎25-03-2020 5:21 PM

Nothing overly suspicious in those logs.

There's some inncoent Xbox gaming traffic from what looks like a handful of Sky Broadband and a BT Broadband customers, some opportunist (and blocked) connection attempts from some Chinese/Russian IP's, a probe from a research scanner, and a few that I can't easily identify. In short though: nothing that should cause your connection to drop.

In fact, assuming I'm looking at the correct account, your line has dropped just once during the last 7 days or so. Is your son's console connected wirelessly? Could we be looking at a Wi-Fi connectivity problem instead?

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Message 2 of 4
(831 Views)
offtrolley
Dabbler
Posts: 18
Thanks: 1
Registered: ‎06-02-2014

Re: IP Booter ?

‎25-03-2020 6:39 PM - edited ‎25-03-2020 6:41 PM

We have both PC and Xbox gamers in the household.

PC and Xbox are both wired. The router is definitely disconnecting as I was unable to connect to it on my tablet as well.

Could it be a virus on the PC that is disconnecting the router (throwing this out there) ?

Thank you for your help

Message 3 of 4
(812 Views)
0 Thanks
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,887
Thanks: 4,979
Fixes: 316
Registered: ‎04-04-2007

Re: IP Booter ?

‎25-03-2020 10:00 PM

The router is categorically not disconnecting from the Internet (although, this assumes I'm looking at the correct account). When the PC or tablet fails, are you able to browse to http://192.168.1.254?
If you are, the link to the router is fine.
The tablet will be connected wirelessly so that's kind of comparing apples to oranges.
A problem like this isn't characteristic of virus/malware, especially if it's affecting multiple devices. No harm running a scan though I suppose.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Message 4 of 4
(779 Views)
0 Thanks