Yes, it has always done that but I like to match any changes in the router to the laptop and trying 1.1.1.1 did time out after Waiting for...
I've just run http://netalyzr.icsi.berkeley.edu/ (requires Java) but don't know if the DNS report would have any bearing.
The ICSI Netalyzr
Start » Analysis » Results
Result Summary + – (help)
host-92-30-194-94.as13285.net / 92.30.194.94
Recorded at 06:30 EST (11:30 UTC), Feb 20 2014. Permalink. Referrer. Client/server transcript.
Summary of Noteworthy Events + –
Major Abnormalities –
•Your DNS resolver returns IP addresses for names that do not exist
Minor Aberrations –
•Certain TCP protocols are blocked in outbound traffic
•Network packet buffering may be excessive
Address-based Tests + –
port sequence plot
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests + –
TCP connectivity (?): Note –
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is prohibited.
This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is blocked.
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is allowed.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties + –
Network performance (?): Latency: 110 ms, Loss: 0.5% +
TCP connection setup latency (?): 130ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 760 Kbit/s, Download 4.9 Mbit/s +
Network buffer measurements (?): Uplink 700 ms, Downlink 60 ms –
We estimate your uplink as having 700 ms of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time.
We estimate your downlink as having 60 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
HTTP Tests + –
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
DNS Tests + –
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 190 ms +
Internal Server Error on Test Report
DNS glue policy (?): OK +
port sequence plot
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): Warning –
Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 92.242.132.16, which resolves to unallocated.barefruit.co.uk. You can inspect the resulting HTML content here.
There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.
The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.
The following lists your DNS server's behavior in more detail.
•www.{random}.com is mapped to 92.242.132.16.
•www.{random}.org is mapped to 92.242.132.16.
•fubar.{random}.com is mapped to 92.242.132.16.
•www.yahoo.cmo [sic] is mapped to 92.242.132.16.
•nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 92.242.132.16.
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): OK +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols + –
DNSSEC Support from the DNS Roots (?): OK +
Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
WNIC Failing in 7800N ?
-
Tomken
- Posts: 467
- Joined: Tue Jul 26, 2011 10:31 am
- Location: Co Durham
-
Tomken
- Posts: 467
- Joined: Tue Jul 26, 2011 10:31 am
- Location: Co Durham
Re: WNIC Failing in 7800N ?
Well, I've never had this happen before and perhaps it is a sign of something failing.
While browsing using a WiFi connection, I got the page that I was no longer connected to the Internet.
Saw a sunburst in the system tray and the router resetting, yet when I logged into the router to see what speed it had come back in with, the up time was still showing as over 10hrs from when it was last reset with DNS changes and the speed was exactly the same as well and while the System Log shows a request for about 10.40pm, it's similar to just booting up as when I'd done so earlier in the day although it still needed Windows Trouble Shooter to reset the adapter for it to reconnect even after all the lights on the router came back on.
I think that tomorrow I'll stick the D-Link 3780 on that TalkTalk have sent me as a replacement for the 3680 and just keep the 7800N as an emergency spare, but it would be nice if there was some sort of explanation for what has been happening with the 7800N.
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: Reset PCI Card
Jan 01 00:00:26 user kernel: ADDR0 = 10000008, ADDR1 = 10100008
Jan 01 00:00:26 user kernel: CMD = 0016, STATUS = 04a0
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: ### LATENCY = 20, CACHE LINE SIZE = 08
Jan 01 00:00:26 user kernel: PDMA_RST_IDX = 0
Jan 01 00:00:26 user kernel: PDMA_GLO_CFG = 00000020
Jan 01 00:00:26 user kernel: TX_MAX_CNT0 = 00000080
Jan 01 00:00:26 user kernel: 2. reg = 00000020
Jan 01 00:00:26 user kernel: 2. PDMA_GLO_CFG = 00000065, reg = 00000065
Jan 01 00:00:26 user kernel: Op mode = 1
Jan 01 00:00:26 user kernel: BssidNum=1
Jan 01 00:00:26 user kernel: Wait for boot done...
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_NOTIFY
Jan 01 00:00:26 user kernel: Open file: /etc/Wireless/RT2880/iNIC_ap.bin
Jan 01 00:00:26 user kernel: Open file: /var/iNIC_ap.dat
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(2)
Jan 01 00:00:26 user kernel: Send Init Cfg Data Done(3 packets)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(2)
Jan 01 00:00:27 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: CRC:01 08 14 18 f3 ba d7 75 22 32 2e 35 2e 30 2e 31 22 00 00 00 32 30 31 32 30 33 30 38 00 00 00 00 00 00 00 00 f0 45 06 00
Jan 01 00:00:27 user kernel: Send RT2880iNIC Firmware Done
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel: version: "2.5.0.1"
Jan 01 00:00:27 user kernel: size: 411120 bytes
Jan 01 00:00:27 user kernel: date: 20120308
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: Send STARTUP to RT2880iNIC
Jan 01 00:00:27 user kernel: Close Firmware file
Jan 01 00:00:27 user kernel: RACFG_CMD_BOOT_STARTUP
Jan 01 00:00:29 user kernel: Update MAC(0)=00:04:ed:18:fd:b1
Jan 01 00:00:29 user syslog: ifconfig ra0 up 2>/dev/null
Jan 01 00:00:29 user syslog: brctl addif br0 ra0 2>/dev/null
Jan 01 00:00:29 user kernel: device ra0 entered promiscuous mode
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:29 user kernel: br0: topology change detected, propagating
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user syslog: ethctl eth0 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: ethctl eth1 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: rmmod vnet 2>/dev/null
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering forwarding state
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering forwarding state
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:32 daemon UPNPD[525]: HTTP listening on port 2800
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:33 daemon pppd[533]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:00:33 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:33 user kernel: br0: port 1(eth0) entering disabled state
Jan 01 00:00:34 user kernel: Line 0: ADSL link down
Jan 01 00:00:39 user kernel: Line 0: xDSL G.994 training
Jan 01 00:00:43 daemon DHCP SERVER: DHCP request from 70:5a:b6:81:d0:d3
Jan 01 00:00:43 daemon DHCP SERVER: DHCP ack to 70:5a:b6:81:d0:d3
Jan 01 00:00:48 user kernel: Line 0: ADSL G.992 started
Jan 01 00:00:52 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:55 user syslog: web: ::ffff:192.168.1.100 login
Jan 01 00:00:58 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:58 user kernel: Line 0: ADSL link up, Path 0, us=904, ds=6607
Jan 01 00:01:00 daemon pppd[533]: PPPoE: Terminating on signal 15.
Jan 01 00:01:00 daemon pppd[533]: Exit.
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:01:02 daemon pppd[838]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:01:02 daemon pppd[838]: PPP: Start to connect ...
Jan 01 00:01:02 daemon pppd[838]: Using interface ppp0_0_38_1
Jan 01 00:01:02 daemon pppd[838]: Connect: ppp_0_0_38_1 <-->
Jan 01 00:01:02 daemon pppd[838]: Couldn't increase MTU to 1500.
Jan 01 00:01:09 daemon pppd[838]: PPP LCP UP.
Jan 01 00:01:09 daemon pppd[838]: Remote message: CHAP authentication success, unit 36301
Jan 01 00:01:09 daemon pppd[838]: local IP address 92.23.127.15
Jan 01 00:01:09 daemon pppd[838]: remote IP address 92.23.112.1
Jan 01 00:01:09 daemon pppd[838]: primary DNS address 62.24.243.4
Jan 01 00:01:09 daemon pppd[838]: secondary DNS address 62.24.202.70
Jan 01 00:01:09 user kernel: KLOB extended to 4 pools
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:09 daemon pppd[838]: Received valid IP address from server. Connection UP.
Jan 01 00:01:10 user syslog: begin: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:10 daemon UPNPD[525]: received signal 15, good-bye
Jan 01 00:01:12 daemon UPNPD[989]: HTTP listening on port 2800
Jan 01 00:01:14 user syslog: end: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:20 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Jan 01 00:01:20 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 12:41:22 user syslog: web: ::ffff:192.168.1.100 logout
Feb 20 13:39:41 syslog -- MARK --
Feb 20 14:39:41 syslog -- MARK --
Feb 20 15:39:41 syslog -- MARK --
Feb 20 15:48:40 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:48:40 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:48:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:48:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:05 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:57:05 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:57:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:13 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:09 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:12 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:48 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:50 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:53 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:39:41 syslog -- MARK --
Feb 20 16:42:50 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:42:50 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:42:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:42:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:54 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:36 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:30 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:59:55 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:59:55 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:59:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:00:02 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:40 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:06:58 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 17:06:58 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 17:07:01 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:07:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:34 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:41 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:44 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:39:41 syslog -- MARK --
Feb 20 18:39:41 syslog -- MARK --
Feb 20 19:39:41 syslog -- MARK --
Feb 20 20:16:53 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 20:16:53 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 20:16:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:17:00 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:21:03 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 20:21:13 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 20:26:26 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:26:29 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:39:41 syslog -- MARK --
Feb 20 21:39:41 syslog -- MARK --
Feb 20 22:07:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:07:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:07:49 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:07:52 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:08:53 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:09:23 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 22:12:52 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:12:52 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:12:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:12:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:08 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:11 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:35 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:38 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:39:41 syslog -- MARK --
Feb 20 22:40:32 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:32 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:47 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:17 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:20 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:15 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:18 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:52:59 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:54:04 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 23:02:04 user syslog: web: ::ffff:192.168.1.220 login
While browsing using a WiFi connection, I got the page that I was no longer connected to the Internet.
Saw a sunburst in the system tray and the router resetting, yet when I logged into the router to see what speed it had come back in with, the up time was still showing as over 10hrs from when it was last reset with DNS changes and the speed was exactly the same as well and while the System Log shows a request for about 10.40pm, it's similar to just booting up as when I'd done so earlier in the day although it still needed Windows Trouble Shooter to reset the adapter for it to reconnect even after all the lights on the router came back on.
I think that tomorrow I'll stick the D-Link 3780 on that TalkTalk have sent me as a replacement for the 3680 and just keep the 7800N as an emergency spare, but it would be nice if there was some sort of explanation for what has been happening with the 7800N.
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: Reset PCI Card
Jan 01 00:00:26 user kernel: ADDR0 = 10000008, ADDR1 = 10100008
Jan 01 00:00:26 user kernel: CMD = 0016, STATUS = 04a0
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: ### LATENCY = 20, CACHE LINE SIZE = 08
Jan 01 00:00:26 user kernel: PDMA_RST_IDX = 0
Jan 01 00:00:26 user kernel: PDMA_GLO_CFG = 00000020
Jan 01 00:00:26 user kernel: TX_MAX_CNT0 = 00000080
Jan 01 00:00:26 user kernel: 2. reg = 00000020
Jan 01 00:00:26 user kernel: 2. PDMA_GLO_CFG = 00000065, reg = 00000065
Jan 01 00:00:26 user kernel: Op mode = 1
Jan 01 00:00:26 user kernel: BssidNum=1
Jan 01 00:00:26 user kernel: Wait for boot done...
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_NOTIFY
Jan 01 00:00:26 user kernel: Open file: /etc/Wireless/RT2880/iNIC_ap.bin
Jan 01 00:00:26 user kernel: Open file: /var/iNIC_ap.dat
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(2)
Jan 01 00:00:26 user kernel: Send Init Cfg Data Done(3 packets)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(2)
Jan 01 00:00:27 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: CRC:01 08 14 18 f3 ba d7 75 22 32 2e 35 2e 30 2e 31 22 00 00 00 32 30 31 32 30 33 30 38 00 00 00 00 00 00 00 00 f0 45 06 00
Jan 01 00:00:27 user kernel: Send RT2880iNIC Firmware Done
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel: version: "2.5.0.1"
Jan 01 00:00:27 user kernel: size: 411120 bytes
Jan 01 00:00:27 user kernel: date: 20120308
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: Send STARTUP to RT2880iNIC
Jan 01 00:00:27 user kernel: Close Firmware file
Jan 01 00:00:27 user kernel: RACFG_CMD_BOOT_STARTUP
Jan 01 00:00:29 user kernel: Update MAC(0)=00:04:ed:18:fd:b1
Jan 01 00:00:29 user syslog: ifconfig ra0 up 2>/dev/null
Jan 01 00:00:29 user syslog: brctl addif br0 ra0 2>/dev/null
Jan 01 00:00:29 user kernel: device ra0 entered promiscuous mode
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:29 user kernel: br0: topology change detected, propagating
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user syslog: ethctl eth0 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: ethctl eth1 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: rmmod vnet 2>/dev/null
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering forwarding state
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering forwarding state
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:32 daemon UPNPD[525]: HTTP listening on port 2800
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:33 daemon pppd[533]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:00:33 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:33 user kernel: br0: port 1(eth0) entering disabled state
Jan 01 00:00:34 user kernel: Line 0: ADSL link down
Jan 01 00:00:39 user kernel: Line 0: xDSL G.994 training
Jan 01 00:00:43 daemon DHCP SERVER: DHCP request from 70:5a:b6:81:d0:d3
Jan 01 00:00:43 daemon DHCP SERVER: DHCP ack to 70:5a:b6:81:d0:d3
Jan 01 00:00:48 user kernel: Line 0: ADSL G.992 started
Jan 01 00:00:52 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:55 user syslog: web: ::ffff:192.168.1.100 login
Jan 01 00:00:58 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:58 user kernel: Line 0: ADSL link up, Path 0, us=904, ds=6607
Jan 01 00:01:00 daemon pppd[533]: PPPoE: Terminating on signal 15.
Jan 01 00:01:00 daemon pppd[533]: Exit.
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:01:02 daemon pppd[838]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:01:02 daemon pppd[838]: PPP: Start to connect ...
Jan 01 00:01:02 daemon pppd[838]: Using interface ppp0_0_38_1
Jan 01 00:01:02 daemon pppd[838]: Connect: ppp_0_0_38_1 <-->
Jan 01 00:01:02 daemon pppd[838]: Couldn't increase MTU to 1500.
Jan 01 00:01:09 daemon pppd[838]: PPP LCP UP.
Jan 01 00:01:09 daemon pppd[838]: Remote message: CHAP authentication success, unit 36301
Jan 01 00:01:09 daemon pppd[838]: local IP address 92.23.127.15
Jan 01 00:01:09 daemon pppd[838]: remote IP address 92.23.112.1
Jan 01 00:01:09 daemon pppd[838]: primary DNS address 62.24.243.4
Jan 01 00:01:09 daemon pppd[838]: secondary DNS address 62.24.202.70
Jan 01 00:01:09 user kernel: KLOB extended to 4 pools
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:09 daemon pppd[838]: Received valid IP address from server. Connection UP.
Jan 01 00:01:10 user syslog: begin: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:10 daemon UPNPD[525]: received signal 15, good-bye
Jan 01 00:01:12 daemon UPNPD[989]: HTTP listening on port 2800
Jan 01 00:01:14 user syslog: end: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:20 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Jan 01 00:01:20 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 12:41:22 user syslog: web: ::ffff:192.168.1.100 logout
Feb 20 13:39:41 syslog -- MARK --
Feb 20 14:39:41 syslog -- MARK --
Feb 20 15:39:41 syslog -- MARK --
Feb 20 15:48:40 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:48:40 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:48:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:48:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:05 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:57:05 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:57:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:13 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:09 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:12 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:48 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:50 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:53 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:39:41 syslog -- MARK --
Feb 20 16:42:50 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:42:50 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:42:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:42:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:54 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:36 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:30 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:59:55 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:59:55 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:59:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:00:02 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:40 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:06:58 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 17:06:58 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 17:07:01 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:07:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:34 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:41 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:44 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:39:41 syslog -- MARK --
Feb 20 18:39:41 syslog -- MARK --
Feb 20 19:39:41 syslog -- MARK --
Feb 20 20:16:53 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 20:16:53 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 20:16:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:17:00 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:21:03 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 20:21:13 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 20:26:26 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:26:29 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:39:41 syslog -- MARK --
Feb 20 21:39:41 syslog -- MARK --
Feb 20 22:07:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:07:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:07:49 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:07:52 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:08:53 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:09:23 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 22:12:52 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:12:52 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:12:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:12:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:08 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:11 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:35 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:38 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:39:41 syslog -- MARK --
Feb 20 22:40:32 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:32 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:47 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:17 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:20 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:15 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:18 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:52:59 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:54:04 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 23:02:04 user syslog: web: ::ffff:192.168.1.220 login
-
billion_fan
- Posts: 5398
- Joined: Tue Jul 19, 2011 4:30 pm
Re: WNIC Failing in 7800N ?
Tomken wrote:Well, I've never had this happen before and perhaps it is a sign of something failing.
While browsing using a WiFi connection, I got the page that I was no longer connected to the Internet.
Saw a sunburst in the system tray and the router resetting, yet when I logged into the router to see what speed it had come back in with, the up time was still showing as over 10hrs from when it was last reset with DNS changes and the speed was exactly the same as well and while the System Log shows a request for about 10.40pm, it's similar to just booting up as when I'd done so earlier in the day although it still needed Windows Trouble Shooter to reset the adapter for it to reconnect even after all the lights on the router came back on.
I think that tomorrow I'll stick the D-Link 3780 on that TalkTalk have sent me as a replacement for the 3680 and just keep the 7800N as an emergency spare, but it would be nice if there was some sort of explanation for what has been happening with the 7800N.
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: Reset PCI Card
Jan 01 00:00:26 user kernel: ADDR0 = 10000008, ADDR1 = 10100008
Jan 01 00:00:26 user kernel: CMD = 0016, STATUS = 04a0
Jan 01 00:00:26 user kernel: INT LINE = 39
Jan 01 00:00:26 user kernel: ### LATENCY = 20, CACHE LINE SIZE = 08
Jan 01 00:00:26 user kernel: PDMA_RST_IDX = 0
Jan 01 00:00:26 user kernel: PDMA_GLO_CFG = 00000020
Jan 01 00:00:26 user kernel: TX_MAX_CNT0 = 00000080
Jan 01 00:00:26 user kernel: 2. reg = 00000020
Jan 01 00:00:26 user kernel: 2. PDMA_GLO_CFG = 00000065, reg = 00000065
Jan 01 00:00:26 user kernel: Op mode = 1
Jan 01 00:00:26 user kernel: BssidNum=1
Jan 01 00:00:26 user kernel: Wait for boot done...
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_NOTIFY
Jan 01 00:00:26 user kernel: Open file: /etc/Wireless/RT2880/iNIC_ap.bin
Jan 01 00:00:26 user kernel: Open file: /var/iNIC_ap.dat
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_INITCFG(2)
Jan 01 00:00:26 user kernel: Send Init Cfg Data Done(3 packets)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(0)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(1)
Jan 01 00:00:26 user kernel: RACFG_CMD_BOOT_UPLOAD(2)
Jan 01 00:00:27 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: CRC:01 08 14 18 f3 ba d7 75 22 32 2e 35 2e 30 2e 31 22 00 00 00 32 30 31 32 30 33 30 38 00 00 00 00 00 00 00 00 f0 45 06 00
Jan 01 00:00:27 user kernel: Send RT2880iNIC Firmware Done
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel: version: "2.5.0.1"
Jan 01 00:00:27 user kernel: size: 411120 bytes
Jan 01 00:00:27 user kernel: date: 20120308
Jan 01 00:00:27 user kernel: ===================================
Jan 01 00:00:27 user kernel:
Jan 01 00:00:27 user kernel: Send STARTUP to RT2880iNIC
Jan 01 00:00:27 user kernel: Close Firmware file
Jan 01 00:00:27 user kernel: RACFG_CMD_BOOT_STARTUP
Jan 01 00:00:29 user kernel: Update MAC(0)=00:04:ed:18:fd:b1
Jan 01 00:00:29 user syslog: ifconfig ra0 up 2>/dev/null
Jan 01 00:00:29 user syslog: brctl addif br0 ra0 2>/dev/null
Jan 01 00:00:29 user kernel: device ra0 entered promiscuous mode
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:29 user kernel: br0: topology change detected, propagating
Jan 01 00:00:29 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user syslog: ethctl eth0 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: ethctl eth1 vport query 2>/var/vcfgerr
Jan 01 00:00:30 user syslog: rm /var/vcfgerr
Jan 01 00:00:30 user syslog: rmmod vnet 2>/dev/null
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering disabled state
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering learning state
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 3(ra0) entering forwarding state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 2(eth1) entering forwarding state
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering learning state
Jan 01 00:00:30 user kernel: br0: topology change detected, propagating
Jan 01 00:00:30 user kernel: br0: port 1(eth0) entering forwarding state
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:31 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:32 daemon UPNPD[525]: HTTP listening on port 2800
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm
Jan 01 00:00:33 daemon pppd[533]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.4.4#53
Jan 01 00:00:33 daemon dnsmasq[92]: using nameserver 8.8.8.8#53
Jan 01 00:00:33 daemon pppd[533]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:00:33 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:33 user kernel: br0: port 1(eth0) entering disabled state
Jan 01 00:00:34 user kernel: Line 0: ADSL link down
Jan 01 00:00:39 user kernel: Line 0: xDSL G.994 training
Jan 01 00:00:43 daemon DHCP SERVER: DHCP request from 70:5a:b6:81:d0:d3
Jan 01 00:00:43 daemon DHCP SERVER: DHCP ack to 70:5a:b6:81:d0:d3
Jan 01 00:00:48 user kernel: Line 0: ADSL G.992 started
Jan 01 00:00:52 user kernel: Line 0: ADSL G.992 channel analysis
Jan 01 00:00:55 user syslog: web: ::ffff:192.168.1.100 login
Jan 01 00:00:58 user kernel: Line 0: ADSL G.992 message exchange
Jan 01 00:00:58 user kernel: Line 0: ADSL link up, Path 0, us=904, ds=6607
Jan 01 00:01:00 daemon pppd[533]: PPPoE: Terminating on signal 15.
Jan 01 00:01:00 daemon pppd[533]: Exit.
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm
Jan 01 00:01:02 daemon pppd[838]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:01:02 daemon pppd[838]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:01:02 daemon pppd[838]: PPP: Start to connect ...
Jan 01 00:01:02 daemon pppd[838]: Using interface ppp0_0_38_1
Jan 01 00:01:02 daemon pppd[838]: Connect: ppp_0_0_38_1 <-->
Jan 01 00:01:02 daemon pppd[838]: Couldn't increase MTU to 1500.
Jan 01 00:01:09 daemon pppd[838]: PPP LCP UP.
Jan 01 00:01:09 daemon pppd[838]: Remote message: CHAP authentication success, unit 36301
Jan 01 00:01:09 daemon pppd[838]: local IP address 92.23.127.15
Jan 01 00:01:09 daemon pppd[838]: remote IP address 92.23.112.1
Jan 01 00:01:09 daemon pppd[838]: primary DNS address 62.24.243.4
Jan 01 00:01:09 daemon pppd[838]: secondary DNS address 62.24.202.70
Jan 01 00:01:09 user kernel: KLOB extended to 4 pools
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:09 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:09 daemon pppd[838]: Received valid IP address from server. Connection UP.
Jan 01 00:01:10 user syslog: begin: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.202.70#53
Jan 01 00:01:10 daemon dnsmasq[92]: using nameserver 62.24.243.4#53
Jan 01 00:01:10 daemon UPNPD[525]: received signal 15, good-bye
Jan 01 00:01:12 daemon UPNPD[989]: HTTP listening on port 2800
Jan 01 00:01:14 user syslog: end: interface: ppp_0_0_38_1 go to up
Jan 01 00:01:20 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Jan 01 00:01:20 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
Jan 01 00:01:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 12:41:22 user syslog: web: ::ffff:192.168.1.100 logout
Feb 20 13:39:41 syslog -- MARK --
Feb 20 14:39:41 syslog -- MARK --
Feb 20 15:39:41 syslog -- MARK --
Feb 20 15:48:40 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:48:40 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:48:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:48:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:05 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 15:57:05 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 15:57:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 15:57:13 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:09 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:00:12 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:48 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:23:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:50 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:38:53 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:39:41 syslog -- MARK --
Feb 20 16:42:50 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:42:50 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:42:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:42:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:24 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:45:27 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:54 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:47:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:50:36 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:30 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:54:33 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:43 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:55:46 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 16:59:55 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 16:59:55 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 16:59:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:00:02 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:01:40 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:04:10 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:06:58 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 17:06:58 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 17:07:01 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:07:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:34 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:08:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:41 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:10:44 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 17:39:41 syslog -- MARK --
Feb 20 18:39:41 syslog -- MARK --
Feb 20 19:39:41 syslog -- MARK --
Feb 20 20:16:53 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 20:16:53 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 20:16:57 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:17:00 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:21:03 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 20:21:13 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 20:26:26 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:26:29 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 20:39:41 syslog -- MARK --
Feb 20 21:39:41 syslog -- MARK --
Feb 20 22:07:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:07:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:07:49 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:07:52 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:08:53 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:09:23 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 22:12:52 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:12:52 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:12:56 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:12:59 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:08 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:15:11 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:04 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:23:07 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:35 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:38:38 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:39:41 syslog -- MARK --
Feb 20 22:40:32 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:32 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:37 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:43 daemon DHCP SERVER: DHCP request from 70:f1:a1:46:75:3a
Feb 20 22:40:43 daemon DHCP SERVER: DHCP ack to 70:f1:a1:46:75:3a
Feb 20 22:40:47 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:40:51 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:17 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:42:20 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:15 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:45:18 daemon DHCP SERVER: DHCPINFORM from 192.168.1.220
Feb 20 22:52:59 user syslog: web: ::ffff:192.168.1.220 login
Feb 20 22:54:04 user syslog: web: ::ffff:192.168.1.220 logout
Feb 20 23:02:04 user syslog: web: ::ffff:192.168.1.220 login
From looking at system log, the router never went through the reset procedure or a restart (if it did, the system up time will reset, and also the system log will be reset also, that is not the case from looking at your system log)
Normally if the device was suffering from a wireless failure, this will be listed within the system log, (I can't see this listed within your system log) I don't even see a wireless restart which normally is done without intervention of the user, I can see the normal start up messages from the wireless card, at the right time listed within the system log.
Have you tried the normal things?? eg wireless channel change, channel width change etc??
-
Tomken
- Posts: 467
- Joined: Tue Jul 26, 2011 10:31 am
- Location: Co Durham
Re: WNIC Failing in 7800N ?
I haven't tried the Channel Width change but the router definitely went through a reset procedure as I watched it do so and the nearest other user to my Channel 6 is just one on Channel 1.
Anyway, I've stuck the D-Link 3780 on now and there aren't any yellow alerts on boot with DHCP and the router set to TalkTalk's specific DNS severs again, although I haven't yet changed the laptop from auto DNS.
Anyway, I've stuck the D-Link 3780 on now and there aren't any yellow alerts on boot with DHCP and the router set to TalkTalk's specific DNS severs again, although I haven't yet changed the laptop from auto DNS.
-
Tomken
- Posts: 467
- Joined: Tue Jul 26, 2011 10:31 am
- Location: Co Durham
Re: WNIC Failing in 7800N ?
Event Viewer gave the reason for this as the DHCP Client rejecting the DHCP assigned IP address even though only one machine is being used at a time and just on WiFi so it looks like the 7800N is okay other than for not showing the reset in the System Log, although this has occurred on two laptops now, but with similar programs installed and on the second, just yesterday.
MS's fixit for this is an ipconfig /release and renew, but doesn't work.
Yesterday I restored from a 3 day old external system image and for now, the problem has gone on this one - the other machine has been sent away for repair for an obscure problem but that will be factory reset when I get it back.
It occurred this time with the ISP's D-Link 3780 but I'll wait until I get my other laptop back before I hook the 7800N back up.
MS's fixit for this is an ipconfig /release and renew, but doesn't work.
Yesterday I restored from a 3 day old external system image and for now, the problem has gone on this one - the other machine has been sent away for repair for an obscure problem but that will be factory reset when I get it back.
It occurred this time with the ISP's D-Link 3780 but I'll wait until I get my other laptop back before I hook the 7800N back up.