Recommend Me a Router

Is it any sort of line? A fishing line? Maybe the chief whip in a political party has one? No doubt printers used to have one too, and railway engineers, and geometers, and cocaine users...

The possibilities are such that the term does not seem such a good idea to me. Excuse me while I put my ancestry away in my linebox.
 
"Linebox" seems a stupid name for it to me. It doesn't say what it does. I would expect a linebox to be a junction box somewhere in the line rather than providing master socket functionality. Perhaps that's why I've only ever seen/heard them referred to as master sockets.
 
Black Hole said:
"Linebox" seems a stupid name for it to me. It doesn't say what it does. I would expect a linebox to be a junction box somewhere in the line rather than providing master socket functionality. Perhaps that's why I've only ever seen/heard them referred to as master sockets.
Click to expand...
Master socket is only meaningful from the consumer's point of view. From the network pov (end of) line box makes more sense. And for connections along the line junction box is pretty good.
 
Black Hole said:
"Linebox" seems a stupid name for it to me. It doesn't say what it does. I would expect a linebox to be a junction box somewhere in the line rather than providing master socket functionality. Perhaps that's why I've only ever seen/heard them referred to as master sockets.
Click to expand...
It is only maybe a linebox from the telecom pov. From my pov, it's a master socket.
 
Mike0001 said:
192.168.1.254/setup.cgi?todo=debug
Click to expand...
This worked. I had to submit the admin user name and password (which I have changed), but then I got a "Debug enabled" web page, and Telnet login (same credentials) gives me a command prompt.

Not sure what to do with that knowledge, but another time...

I wonder how you turn it off again? Reboot, probably.
 
Code: 
# find / -name RST_stattbl.htm
/www.eng/RST_stattbl.htm
#
Don't know what to do now though, I need to find a way to access this file with a web browser.
 
Look what I found in my router log!:

Code: 
[admin login] from source 192.168.1.104 Saturday, May 06,2017 09:07:09           
[DoS attack: ACK Scan] from source: 177.124.128.65:80 Saturday, May 06,2017 07:58:10           
[DoS attack: ACK Scan] from source: 74.91.116.223:80 Saturday, May 06,2017 07:54:28           
[DoS attack: RST Scan] from source: 218.24.171.223:2979 Saturday, May 06,2017 07:10:08           
[DoS attack: ACK Scan] from source: 177.124.128.250:80 Saturday, May 06,2017 06:13:16           
[DoS attack: ACK Scan] from source: 177.124.128.143:80 Saturday, May 06,2017 06:07:39           
[DHCP IP: (192.168.1.102)] to MAC address 1C:4B:D6:8D:A1:3E Saturday, May 06,2017 04:06:08           
[DHCP IP: (192.168.1.100)] to MAC address 64:EB:8C:78:16:3A Saturday, May 06,2017 03:39:48           
[DoS attack: ACK Scan] from source: 213.32.45.158:9987 Saturday, May 06,2017 02:30:49           
[Time synchronized with NTP server time-g.netgear.com] Saturday, May 06,2017 02:10:04           
[DoS attack: ACK Scan] from source: 23.39.200.227:443 Saturday, May 06,2017 01:17:57           
[DoS attack: ACK Scan] from source: 23.39.200.227:443 Saturday, May 06,2017 01:17:13           
[DoS attack: ACK Scan] from source: 65.20.0.43:993 Saturday, May 06,2017 01:00:13           
[DHCP IP: (192.168.1.104)] to MAC address 84:89:AD:1C:1B:F8 Friday, May 05,2017 22:01:39             
[DoS attack: ACK Scan] from source: 193.70.100.91:2002 Friday, May 05,2017 21:52:49             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 21:38:16             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 21:33:32             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 21:32:02             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 21:19:32             
[DoS attack: ACK Scan] from source: 5.9.74.251:29000 Friday, May 05,2017 21:19:05             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 21:15:32             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 21:08:14             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 20:47:53             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 20:38:13             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 20:24:35             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 20:10:39             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 20:08:11             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 19:54:32             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 19:08:07             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 19:07:42             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 18:56:11             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 18:38:06             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 18:25:40             
[DoS attack: ACK Scan] from source: 5.158.97.59:80 Friday, May 05,2017 18:25:07             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 18:08:04             
[DoS attack: ACK Scan] from source: 54.182.5.29:80 Friday, May 05,2017 18:01:44             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 17:38:02             
[DoS attack: ACK Scan] from source: 52.85.193.238:80 Friday, May 05,2017 17:35:53             
[DoS attack: ACK Scan] from source: 109.101.199.184:56283 Friday, May 05,2017 17:21:29             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 17:18:13             
[DoS attack: RST Scan] from source: 46.105.79.113:443 Friday, May 05,2017 16:37:59             
[DoS attack: ACK Scan] from source: 46.105.77.64:25565 Friday, May 05,2017 16:20:24             
[DoS attack: ACK Scan] from source: 60.214.107.18:80 Friday, May 05,2017 16:08:53

- etc -
 
Most of those look like the router is misidentifying packets due to network lag.
Particularly since a number of those are cloudfront addresses.
 
It isn't, it's sending reply packets to web requests from inside your network but they're arriving out of order, duplicated or too late and so not being associated with an established connection.

Cloudfront is a content delivery network. Lots of web sites use it to host components.
 
You must log in or register to reply here.
Back
Top