User comments on ISPs
  >> EE (Everything Everywhere) and Orange


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User glossywhite
(member) Thu 17-Jul-14 00:10:27
Print Post

[Bright Box 2] *appalling* (read: non-existant) WiFi


[link to this post]
 
[EDIT] Before we start, let's all have a giggle at the outrageously optimistic marketing spiel:

--> https://farm6.staticflickr.com/5566/14485958160_18e4... <---


So, I thought the Bright Box 1 was bad... until now. I've had a whole day of sheer frustration with this new fandangled device. So far, I have waste one whole day:


#1 Had a woman in India tell me outright "the Bright Box 2 is not ADSL compatible", and that was why I was having problems, even though I kept, politely and calmly re-affirming I AM HAVING WIFI ISSUES NOT ADSL ISSUES and that if, as she kept saying, it wasn't ADSL compatible, when why are the specs listing an ADSL modem, why does the manufacturer's web page state that it IS and why does the "wizard" allow me to select ADSL... AND WHY AM I CONNECTED, VIA IT, TO ADSL? Inane conversation ensued until I eventually hung up on her - not something I like to do unless I feel I am about to say something I would not want to (and later regret).

#2 Attempting to connect via WiFi, using 4 different devices (can't even get 192.168.1.1 page)

#3 Allowing EE's "tech support", upon their (stubborn insistence to do so) to access my router and then access my PC (whereby he did NOTHING AT ALL, except hover his mouse over my tabs, and sit watching and waiting for the .1.1 page to load - he evidently didn't take my word for it, as they never seem to)

#4 Change WiFi channels to 1, 6 and 11 (1 seeming the best, as all my neighbours appear to be on the default channel 11 - I live in a small village, so not many APs locally [2 or 3])

#5 Changing encryption types, cyper suites, etc etc until I was losing my cool by now (and this summer heat didn't make it any better, haha)

#6 Reboot, reboot, reset, click this, change that... argh!


Has anyone else had an equally (or more) frustrating experience with the WiFi on the Bright Box 2? Please document it below - I'd like to know what, if any, of the common issues seem to be.

As a side note, it appears that the BB 2 is using some modified build of Open-WRT... or am I mistaken? I've just got a hunch that it is... it was a phrase that the box threw up yesterday in the boot log (something about "web info waiting for connection on socket 0") ... hmmmm



So, after a day being wasted... I put back the Bright Box 1... and whaddayaknow?! IT'S PERFECT AGAIN...

Investigation is ongoing smile

Thank you good folks of router land.

>___<


PS: Want a giggle? One Indian guy (the guy who remotely accessed my PC and did nothing at all), agreed to replace my Bright Box 2... WITH A BRIGHT BOX 1!! - I then proceeded to put it to him that he may like to consider that the very reason I requested the Bright Box 2 - and why it was sent - was that EE have sent me around NINE Bright Box 1's over the last year or so, which kept dropping out WiFi and ADSL, and gave the analogy "If you were given a BMW and it wouldn't start, would you expect the dealership to replace it with a Ford Escort?" - I think he got the gist then, spoke to his manager and placed the Bright Box 2 (replacement, replacement) order.

Crazy...

Edited by glossywhite (Thu 17-Jul-14 00:33:00)

Standard User glossywhite
(member) Thu 17-Jul-14 00:13:24
Print Post

Bright Box 2 - system log from new.


[re: glossywhite] [link to this post]
 
PS: Here's the Bright Box 2's system log, fwiw:

Content-Type: application/octet-stream
Cookie: urn=43600; menu_sel=2; defpg=system%5Fadv%2Ehtm; menu_adv=1
CONTENT-LANGUAGE: en
Connection: close

21:30:46, 16 Jul. admin login success from 192.168.1.77
21:30:30, 16 Jul. admin timeout from 192.168.1.77
21:30:30, 16 Jul. admin logout from 192.168.1.77
21:29:24, 16 Jul. admin login success from 192.168.1.77
21:29:16, 16 Jul. admin logout from 192.168.1.77
21:26:13, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
21:26:12, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
21:24:27, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
21:24:27, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
21:21:15, 16 Jul. Time is synced to NTP server
21:21:01, 16 Jul. PPP connection up (ADSL)
21:21:00, 16 Jul. PPP: IPCP up
21:21:00, 16 Jul. PPP: IPCP received CONFACK
21:21:00, 16 Jul. PPP: IPCP sending CONFREQ
21:21:00, 16 Jul. PPP: IPCP received CONFNAK
21:21:00, 16 Jul. PPP: IPCP sending CONFREQ
21:21:00, 16 Jul. PPP: IPCP received CONFREJ
21:21:00, 16 Jul. PPP: IPCP sending CONFACK
21:21:00, 16 Jul. PPP: IPCP received CONFREQ
21:21:00, 16 Jul. PPP: IPCP sending CONFREQ
21:21:00, 16 Jul. PPP: CHAP authentication succeeded
21:21:00, 16 Jul. PPP: LCP up
21:21:00, 16 Jul. PPP: LCP sending CONFACK
21:21:00, 16 Jul. PPP: LCP received CONFREQ
21:20:58, 16 Jul. PPP: LCP received CONFACK
21:20:58, 16 Jul. PPP: LCP sending CONFREQ
21:20:58, 16 Jul. PPP: LCP received CONFNAK
21:20:58, 16 Jul. PPP: LCP sending CONFREQ
21:20:58, 16 Jul. PPP: Starting PPP daemon
21:20:56, 16 Jul. WAN link up (ADSL)
21:20:55, 16 Jul. WAN link down (ADSL)
21:20:55, 16 Jul. PPP connection down (ADSL)
21:20:46, 16 Jul. PPP: Stopped PPP daemon(0,1,5)
21:20:45, 16 Jul. PPP: LCP received TERMACK
21:20:45, 16 Jul. PPP: LCP sending TERMREQ
21:20:45, 16 Jul. PPP: IPCP down
21:20:45, 16 Jul. PPP: LCP down
21:19:49, 16 Jul. admin login success from 192.168.1.77
21:19:46, 16 Jul. Intelligent Wireless Channel Change to 36(80MHz) (5 GHz) Auto Scan - Low Traffic Mode
21:19:42, 16 Jul. admin login error from 192.168.1.77
21:19:37, 16 Jul. Time is synced to NTP server
21:19:21, 16 Jul. PPP connection up (ADSL)
21:19:20, 16 Jul. PPP: IPCP up
21:19:20, 16 Jul. PPP: IPCP received CONFACK
21:19:20, 16 Jul. PPP: IPCP sending CONFREQ
21:19:20, 16 Jul. PPP: IPCP received CONFNAK
21:19:20, 16 Jul. PPP: IPCP sending CONFREQ
21:19:20, 16 Jul. PPP: IPCP received CONFREJ
21:19:20, 16 Jul. PPP: IPCP sending CONFACK
21:19:20, 16 Jul. PPP: IPCP received CONFREQ
21:19:20, 16 Jul. PPP: IPCP sending CONFREQ
21:19:20, 16 Jul. PPP: CHAP authentication succeeded
21:19:20, 16 Jul. PPP: LCP up
21:19:20, 16 Jul. PPP: LCP sending CONFACK
21:19:20, 16 Jul. PPP: LCP received CONFREQ
21:19:20, 16 Jul. PPP: LCP received CONFACK
21:19:20, 16 Jul. PPP: LCP sending CONFREQ
21:19:20, 16 Jul. PPP: LCP received CONFNAK
21:19:20, 16 Jul. PPP: LCP sending CONFREQ
21:19:19, 16 Jul. PPP: Starting PPP daemon
21:19:16, 16 Jul. WAN link up (ADSL)
21:19:13, 16 Jul. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
21:18:37, 16 Jul. System start
00:01:38, 01 Jan. admin login success from 192.168.1.77
00:01:28, 01 Jan. admin login error from 192.168.1.77
00:01:04, 01 Jan. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
00:00:26, 01 Jan. System start
21:11:36, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
21:11:36, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
21:04:30, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
21:04:29, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
21:04:09, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
21:04:08, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
20:53:54, 16 Jul. Device connected: 192.168.1.251, 78:92:9c:39:ab:ac, Family-Asus, lease time is 172800 seconds
20:53:53, 16 Jul. Received a DHCP request from 78:92:9c:39:ab:ac, Family-Asus
20:53:46, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
20:53:45, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
20:53:21, 16 Jul. Time is synced to NTP server
20:53:05, 16 Jul. PPP connection up (ADSL)
20:53:04, 16 Jul. PPP: IPCP up
20:53:04, 16 Jul. PPP: IPCP sending CONFREQ
20:53:04, 16 Jul. PPP: IPCP received CONFNAK
20:53:04, 16 Jul. PPP: IPCP sending CONFREQ
20:53:04, 16 Jul. PPP: IPCP received CONFREJ
20:53:04, 16 Jul. PPP: IPCP received CONFREQ
20:53:04, 16 Jul. PPP: IPCP sending CONFREQ
20:53:04, 16 Jul. PPP: CHAP authentication succeeded
20:53:04, 16 Jul. PPP: LCP up
20:53:04, 16 Jul. PPP: LCP sending CONFACK
20:53:03, 16 Jul. PPP: LCP received CONFREQ
20:53:01, 16 Jul. admin login success from 192.168.1.77
20:53:01, 16 Jul. PPP: LCP received CONFACK
20:53:01, 16 Jul. PPP: LCP sending CONFREQ
20:53:01, 16 Jul. PPP: LCP received CONFNAK
20:53:01, 16 Jul. PPP: LCP sending CONFREQ
20:53:01, 16 Jul. PPP: Starting PPP daemon
20:52:59, 16 Jul. WAN link up (ADSL)
20:52:53, 16 Jul. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
20:52:16, 16 Jul. System start
20:21:27, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
20:21:26, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
20:15:39, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
20:15:38, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
20:13:44, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
20:13:44, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
20:12:40, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
20:12:40, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
20:02:38, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
20:02:38, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
20:02:37, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
20:02:37, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
20:01:59, 16 Jul. Time is synced to NTP server
20:01:45, 16 Jul. PPP connection up (ADSL)
20:01:44, 16 Jul. PPP: IPCP up
20:01:44, 16 Jul. PPP: IPCP received CONFACK
20:01:44, 16 Jul. PPP: IPCP sending CONFREQ
20:01:44, 16 Jul. PPP: IPCP received CONFNAK
20:01:44, 16 Jul. PPP: IPCP sending CONFREQ
20:01:44, 16 Jul. PPP: IPCP received CONFREJ
20:01:44, 16 Jul. PPP: IPCP sending CONFACK
20:01:44, 16 Jul. PPP: IPCP received CONFREQ
20:01:44, 16 Jul. PPP: IPCP sending CONFREQ
20:01:44, 16 Jul. PPP: CHAP authentication succeeded
20:01:44, 16 Jul. PPP: LCP up
20:01:44, 16 Jul. PPP: LCP sending CONFACK
20:01:44, 16 Jul. PPP: LCP received CONFREQ
20:01:43, 16 Jul. PPP: LCP received CONFACK
20:01:43, 16 Jul. PPP: LCP sending CONFREQ
20:01:43, 16 Jul. PPP: LCP received CONFNAK
20:01:43, 16 Jul. PPP: LCP sending CONFREQ
20:01:43, 16 Jul. PPP: Starting PPP daemon
20:01:42, 16 Jul. WAN link up (ADSL)
20:01:28, 16 Jul. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
20:00:49, 16 Jul. System start
19:40:21, 16 Jul. Possible DoS attack detected from 110.249.208.16
19:25:48, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
19:25:48, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
18:31:18, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
18:31:17, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
18:24:18, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
18:24:18, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
18:09:52, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
18:09:52, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
18:09:32, 16 Jul. Device connected: 192.168.1.32, 34:15:9e:dc:ee:7c, Mums-iPhone, lease time is 172800 seconds
18:09:32, 16 Jul. Received a DHCP request from 34:15:9e:dc:ee:7c, Mums-iPhone
17:44:35, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
17:44:35, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
17:38:10, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
17:38:09, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
17:35:05, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
17:35:05, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
17:33:37, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
17:33:36, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
16:34:27, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
16:34:27, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
16:34:23, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
16:34:23, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
15:36:16, 16 Jul. admin login success from 192.168.1.57
15:25:33, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:25:32, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:23:50, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:23:49, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:22:40, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:22:40, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:22:25, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:22:24, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:22:18, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:22:18, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:21:50, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:21:49, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:20:12, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:20:11, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:18:13, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:18:13, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:16:29, 16 Jul. Possible DoS attack detected from 185.5.174.123
15:15:56, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:15:56, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:09:50, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:09:50, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:09:22, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:09:22, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:08:52, 16 Jul. Device connected: 192.168.1.57, 80:56:f2:84:1f:53, , lease time is 172800 seconds
15:08:52, 16 Jul. Received a DHCP request from 80:56:f2:84:1f:53, Unknown
15:08:08, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
15:08:08, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
15:07:23, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
15:07:23, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
14:45:05, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
14:45:05, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
11:18:41, 16 Jul. Possible DoS attack detected from 94.102.63.117
10:34:37, 16 Jul. Device connected: 192.168.1.186, 28:98:7b:fa:38:ae, , lease time is 172800 seconds
10:34:36, 16 Jul. Received a DHCP request from 28:98:7b:fa:38:ae, Unknown
05:34:46, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
05:34:45, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
02:14:59, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
02:14:57, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
01:53:15, 16 Jul. admin timeout from 192.168.1.77
01:41:12, 16 Jul. admin login success from 192.168.1.77
00:37:16, 16 Jul. admin timeout from 192.168.1.77
00:37:15, 16 Jul. admin timeout from 192.168.1.77
00:27:26, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
00:27:26, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
00:24:54, 16 Jul. admin login success from 192.168.1.77
00:24:51, 16 Jul. admin timeout from 192.168.1.77
00:07:28, 16 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
00:07:27, 16 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
23:55:50, 15 Jul. admin login success from 192.168.1.77
23:55:41, 15 Jul. admin logout from 192.168.1.77
23:55:08, 15 Jul. admin login success from 192.168.1.77
23:54:59, 15 Jul. admin login success from 192.168.1.77
23:42:25, 15 Jul. Device connected: 192.168.1.186, 28:98:7b:fa:38:ae, , lease time is 172800 seconds
23:42:25, 15 Jul. Received a DHCP request from 28:98:7b:fa:38:ae, Unknown
23:37:04, 15 Jul. admin timeout from 192.168.1.77
23:31:01, 15 Jul. Device connected: 192.168.1.50, 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e, lease time is 172800 seconds
23:31:00, 15 Jul. Received a DHCP request from 14:30:c6:8b:d6:70, android-488e9d7e97ffda0e
23:28:28, 15 Jul. Device connected: 192.168.1.47, dc:3a:5e:c5:a3:6f, NP-1MK43X067868, lease time is 172800 seconds
23:28:28, 15 Jul. Received a DHCP request from dc:3a:5e:c5:a3:6f, NP-1MK43X067868
23:12:54, 15 Jul. Intelligent Wireless Channel Change to 44(80MHz) (5 GHz) Auto Scan - Low Traffic Mode
23:12:48, 15 Jul. Time is synced to NTP server
23:12:33, 15 Jul. PPP connection up (ADSL)
23:12:33, 15 Jul. PPP: IPCP up
23:12:33, 15 Jul. PPP: IPCP received CONFACK
23:12:33, 15 Jul. PPP: IPCP sending CONFREQ
23:12:33, 15 Jul. PPP: IPCP received CONFNAK
23:12:33, 15 Jul. PPP: IPCP sending CONFREQ
23:12:33, 15 Jul. PPP: IPCP received CONFREJ
23:12:33, 15 Jul. PPP: IPCP sending CONFACK
23:12:33, 15 Jul. PPP: IPCP received CONFREQ
23:12:33, 15 Jul. PPP: IPCP sending CONFREQ
23:12:33, 15 Jul. PPP: CHAP authentication succeeded
23:12:32, 15 Jul. PPP: LCP up
23:12:32, 15 Jul. PPP: LCP sending CONFACK
23:12:32, 15 Jul. PPP: LCP received CONFREQ
23:12:32, 15 Jul. PPP: LCP received CONFACK
23:12:32, 15 Jul. PPP: LCP sending CONFREQ
23:12:32, 15 Jul. PPP: LCP received CONFNAK
23:12:32, 15 Jul. PPP: LCP sending CONFREQ
23:12:31, 15 Jul. PPP: Starting PPP daemon
23:12:30, 15 Jul. WAN link up (ADSL)
23:11:18, 15 Jul. admin login success from 192.168.1.77
23:11:05, 15 Jul. admin login success from 192.168.1.77
23:06:51, 15 Jul. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
23:06:17, 15 Jul. System start
00:11:27, 01 Jan. admin login success from 192.168.1.80
00:04:00, 01 Jan. admin login success from 192.168.1.80
00:01:04, 01 Jan. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
00:00:59, 01 Jan. admin login success from 192.168.1.80
00:00:26, 01 Jan. System start
00:34:17, 01 Jan. admin login success from 192.168.1.80
00:34:04, 01 Jan. admin timeout from 192.168.1.80
00:33:21, 01 Jan. admin login success from 192.168.1.80
00:33:06, 01 Jan. admin login error from 192.168.1.80
00:32:15, 01 Jan. admin logout from 192.168.1.80
00:31:57, 01 Jan. admin login success from 192.168.1.80
00:31:41, 01 Jan. Intelligent Wireless Channel Change to 11 (2.4 GHz) Auto Scan - Low Traffic Mode
00:16:32, 01 Jan. Intelligent Wireless Channel Change to 36(80MHz) (5 GHz) Auto Scan - Low Traffic Mode
00:10:30, 01 Jan. admin login success from 192.168.1.80
00:05:38, 01 Jan. admin logout from 192.168.1.80
00:02:09, 01 Jan. admin login success from 192.168.1.80
00:01:01, 01 Jan. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
00:00:26, 01 Jan. System start
00:01:02, 01 Jan. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
00:00:54, 01 Jan. Device connected: 192.168.1.82, 00:1d:7d:a6:0a:3e, Q6600, lease time is 172800 seconds
00:00:53, 01 Jan. Received a DHCP request from 00:1d:7d:a6:0a:3e, Q6600
00:00:26, 01 Jan. System start
00:00:59, 01 Jan. System up, firmware version: v0.01.47.0001-OT (Thu Jan 16 12:53:50 2014)
00:00:26, 01 Jan. System start
00:02:15, 01 Jan. admin login success from 192.168.1.25
00:01:03, 01 Jan. System up, firmware version: v0.01.42.0001-OT (Mon Aug 26 13:10:37 2013)
00:00:26, 01 Jan. System start

Edited by glossywhite (Thu 17-Jul-14 00:13:57)

  Print Thread

Jump to