vigor 2800G firmware upgrade query

hello folks, I came on here because I found another thread on this topic and router model, though very old, so thought you might be able to advise.

A friend has asked us to help. The situation is that she has been on wireless broadband, with the Vigor 2800G router and without any problems for some time, but recently her ISP, OneTel has decided she needs to migrate over to TalkTalk, the two being part of the same organisation now, and they sent her an ethernet modem and CD with which to do it. No good to her as she is wireless, so she got the details from the company as to how to configure her current router (Vigor), but didn't know how to get into the router, so called us in.

We put all the right configs into the router, got that confirmed, but still can't get on the net, as the router reckons it cannot find the server IP's, even though we know they are right. We phoned the techy call centre,and the lady on the other end of the phone says that everything is fine their end, and confirmed all the details entered into the router were right, so the only other option she could suggest is that the router needs to have a firmware upgrade.

Fine.

As we can't get on the net through the Vigor router, we can only download the firmware upgrade to our own computer at home and then transfer it to the laptop via a usb stick. Will the installation process allow us to initiate the install from the desktop?
I understand that I have to go for the .rst option, not the .all option, but I get the impression I need to be online via ethernet to complete the task, and as we are not able to get on line... ( our own setup here at home is cable, not dsl, so we can't attach the router to run it from home via our ISP....)

appreciate any words of wisdom :)

Yes. You are better off using the upgrade tool that comes with the router (and for choice use the one that matches the firmware you are replacing - the one that came on the CD ROM with teh router). The procedure is simple - start the upgrade client on the PC, and select the file you want to upload, then open the web page on the router and in maintenance cl;ick on the upgrade firmware, then on the PC start the transfer.

However, before you do that, have you tried doing a hard reset back to the factory defaults?

Which firmware is installed at the moment?

You shouldn't need to enter the DNS server address, they should be picked up by the router from the ISP, and it then acts as a DNS relay. That said, I had intermittent problems with that with the earlier firmware (2.5) but the upgrade to 2.8 has fixed it - well worth doing (and lots of new features too)

The rst file will wipe all configuration settings, so you will need to re-enter those. The .all file does not wipe the configuration.

I assume that you are using windows on the PC. If you are not, you will need to download a TFTP client.

Once you have flashed the router, download and install the latest version of the router tools.

Hello Peter, thank you for coming back. :)

I can't use the upgrade tool from the CD that came with the router 'cos the folk don't know where that is - or if they ever had it since someone else first installed the router for them.
I have downloaded the one from the Draytek page, RTSv37.

You say "Start the upgrade client on the PC"

Do you mean the Tool exe?

I shall select the .rst - I have a copy of the configs I have to put in for the new ISP.
Then I go to maintenance in the router setup and click on the upgrade firmware, and then click on the tool thing to start transfer, is that right?

I expect it will be clear enough when I do it.

Two other things concern me a bit;

In the read me notes that comes with the router tools, in 'known issues' it says, quote 'there is an interoperability issue if wireless security is mixed mode ( WEP or AWPA/WPA2-PSK) and clients baed (misprint?) on the Ralink RT2571 or RT2561 chipsets' end quote.

This doesn't mean much to me - I assume the chipset mentioned is in the router? - but I do have a WEP key active, and there is a choice of that or WPA, if I remember rightly, and by mixed mode, does it mean the wireless capability like B or G etc, which I have set it to, though I could set it to G only.

The other thing is that there is a note for those in PPPoA setup ( which is what we are in on the Draytek). It says 'be sure to select the correct modulation type to ensure quickest line synchronisation. For regular ADSL or ADSLMax, the setting is G.DMT'

can you offer any guidance on what that means please?

ps yes we did do a factory reset and the current firmware is 2.6.1.1_D794214 .OS is XP :)

There are some better written instructions on how to upgrade here

http://www.draytek.co.uk/support/kb_...h.html#reflash

if you haven't already found them! You should be OK with the upgrade tool - I don't think it has changed, but if the original disk has been lost, you don't really have much choice!

Saving the config file shgould be OK - but there is a (small) risk that if it is corrupted, reloading it might again prevent the router from operating properly. However in that case a full reset top factory defaults will clear it.

You MUST do the upgrade via hard wired link - not over the wireless link.

I think the misprint should be 'based' and refers to the chipset in the wireless adaptor in the PC. If that is an issue, don't use mixed mode.

Different 'flavours of ADSL have different modulation protocols. If your are on plain ADSL, then G.DMT is the one to use. If you are on a higher speed link (ADSL+) then you should choose multimode. It may take longer to sync, but when it does you can check the modulation type in the online status page (bottom line - under mode) and change the setting in the set up page. It means that the router will be quicker to sync of the connection drops for any reason.

thank you Peter, I shall save your reply and refer to it tomorrow. i shall put the config in afresh as I have all the details to hand. I think this is adsl2 - but I will check that out tomorrow. I had found that guide and I have printed it off. Yes, we will do it via ethernet :). If the mixed mode refers to the B and G wireless types, I will set it to G. No idea what the chip is on the adaptor. Guess I will puzzle it all out tomorrow. Will come back on here to let you know how it went :)

Hello again. :) The upgrade went ok and it now has the 2.8 upgrade in place - but the problem is still there.
The problem seems to be in the WAN settings area - as you would expect.

All of the configuration details are in place in the router setup as required by TalkTalk, and with those being correct we OUGHT to be able to connect to the net, but it is not happening.
I have tried multimode, but switched back to G.DMT as that IS what is required.
I have disabled security ( for now), and set it to wireless G only.
In the status screen on the router setup, all is green except for Link ( is that on the status page?) which is stated to be disconnected and is in red). However, in the WAN settings all the info is in red except for a line down the bottom. The Tx and Rx are red, as you would expect, the IP is blank, as you would expect, since no connection to the outside world has yet been made. PPPoA is also in red BUT the line of writing in green down the bottom of that page is describing a changing state which, for one moment, says PPP ( Sending Message) and then, second or so later, after a progress bar has run its length,says PPP (shutting down). It goes on doing this.
It seems to me that that is a clue to the problem, but I do not know how to interpret it. Can you help please?

We swapped the router for TalkTalks ethernet and got on with no problems at all, so the trouble has to lie within the Draytek router. Wireless connection is essential in that household and the folk are getting very anxious, so any suggestions will be very much appreciated. :)

At the online status (below Quick start Wizard) can you confirm what is showing red and what is showing green?

If state is indicating showtime, then the router is syncing with the ADSL line OK.

If anything in WAN status is showing red, then the problem lies with the settings to connect to talk talk.

It does sound as if the router is syncing, but failing to authenticate with talk talk.

In internet access under PPPoA/PPPoE settimgs

Multi PVC channel can be left at one (not relevant)
VPI should be 0
VPC should be 38
Encapsulating type should be VC MUX
Protocol should be PPPoA


ISP name can be left blank
user name should be that provided by talk talk
Password (case sensitive) should be that provided by talk
Authentication should be PAP or CHAP
Tick always on
Select dynamic IP
Select default MaC

The router should then connect.

The only possible reasons are if Talk Talk use different VCI VPI numbers or if they look at the Mac address of the router. If the VPI/VCI settings are correct, then you could set the MAC address of the router to the same as the modem they have supplied.

Again these setting have to be supplied via a cable connection - we can worry about wireless when we get the basics done!

Peter, the router does show SHOWTIME. Please read on though.This MIGHT be relevant.

I have just made a discovery. The DNS numbers we were given by a techy over the phone, and which are on the CD, are not the same as the ones published as the correct ones on TalkTalks website.

Now THAT would make a difference I would assume - but if the first set they gave us were wrong ( 62.24.199.13/23) how could it be that the ethernet got on without trouble via the talktalk modem?

The set on the webpage is 62.24.128.17/18. If anyone else here has TalkTalk, I would be pleased to know which DNS addresses they have....

Peter, all the config settings you have listed are in place. The VCI and VPI numbers are 0 and 38, which is what they require. If the DNS isn't it, then I must get the MAC address from the ethernet router and use it in place of the default MAC address which is current now on the Vigor - is that right? I shall be going back there tomorrow I expect (sigh) and will try that if the DNS isn't the problem. Thanks :)

You shouldn't need to enter DNS settings - the router normally gets those from the ISP when it connects.

Were the rest of the settings on the Status page showing green - if they aren't it is an authentication failure which is nothing to do with DNS!

In particular under wan status, all the enries should be gree - mode should be PPPoA - therre should be an IP address shown. There should also be a DNS address shown.

Under LAN - General Set up on the right hand side Primary and secondary DNS should be blank. You only need to complete ythose if the router doesn't pick them up automatically as part of the authentication process to talk talk (or if you want to use a different (public) DNS server.

OK - but why does TalkTalk require them to be in place then?
I shall try leaving them blank.
No the entries in the WAN status are red - except for the changing message down the bottom. There is no IP shown - I can't recall now if there was a DNS, but I think not else I would have taken a note of its numbers.

I can't recall what was in the LAN status - I was working principally with the quick setup and WAN status, however, the only DNS I put in were those TalkTalk indicated from phone contact and from CD. I shall make it blank next time.
I guess I will have to try these things tomorrow. It HAS to be to do with connecting with TalkTalk doesn't it, as the Router is Green for SHOWTIME.
Thank you for your continued support Peter. I will get back to you.

The Green to showtime showsd that there is a physical connection between the router and the exchange equipment. The WAN staus (PPP connection is the logical connection to talk talk's servers. It is that connection process that identifies you as a talk talk customer and allocates the IP address to your router and the DNS server IP addresses. If the WAN status is green, with an IP address shown, then the connection to talk talk is OK and the router should get the DNS server addresses at that time.

That is helpful Peter. How does that tie in with the message in green at the bottom of the WAN status, which said that the PPP was sending and then that the PPP was shutting down? I guess it wasn't finding TalkTalk and if it can't find the ISP, the DNS addresses don't come back. There was no IP address in the WAN status just red dashes. No packets sent or received (Tx Rx). PPPoA was in red.

Will leaving the DNS boxes blank sort this? Everything else is happy and green I think - except it said 'disconnected' next to Link in one of the status windows, and that too was in red.

ps the authentication is CHAP

Leaving the DNS boxes blank won't sort it - DNS addresses are allocated AFTER authentication with talk talk.

When you say the authentication is CHAP, is that what the router is set to, or is that what talk talk requires?

I'm not sure if the router can be set to CHAP only (I can't find that setting anywhere - I suspect it doesn't exist!) but under Internet Access - PPPoA/PPPoE setup, on the right hand side, set PPP authentication to PAP or CHAP (Choices are PAP only or PAP or CHAP)

peter, on the draytek troubleshooting flowchart it seems to indicate that the problem lies in -
DSL settings ISP(SNR /UK2)

Is that three possible sources of the problem or two?

Signal to Noise - would the ethernet modem have got through if that was the problem?

What does /UK2 mean - don't get that bit at all, and what are DSL settings I wonder... :(

both... I think it only had CHAP in the box; I did not have to enter it, t'was already there. What do you think about the flowchart thing? (See above) Ah, the DSL settings are all the config entered and microfilters in place I understand.
Peter, I think I have occupied too much of your evening and ought to say thank you and not ask any more questions - but please may you just tell me what the UK2 thing means?

Not sure - I'll have to look it up - but not tonight - but I don't think it is relevant - the problem lies in the authentication, not the ADSL side. My 2800VG doesn''t have provision for CHAP only, the coices are PAP or PAP/CHAP in the drop down box I referred to earlier.

http://img.photobucket.com/albums/v5...linestatus.jpg
http://img.photobucket.com/albums/v5...tek2800lan.jpg
http://img.photobucket.com/albums/v5...00internet.jpg

Ok thats my settings for my 2800G with the 2.8 firmware with my provider Entanet

As mentioned, you shouldnt need to enter any DNS details, but it's weird that the supplied kit works, but with the same details, it doesnt on the Draytek.

I see you have already posted on the draytek forums :)

PeterB - thankyou for trying to help _ really appreciate it. Authentication seems to be 'it' - maybe tomorrow will bring further light. I have to go out in day but will check on here before I go back to the Draytek to see if anyone has posted.

Madman, I will see if I can copy your configs to print out and compare - thank you :) Yes, I found the Draytek forum earlier this evening and thought it might be useful - am getting a bit desperate now, tomorrow will be our fourth visit to the problem and I don't think I am going to be able to crack it :(

If you can, it might be worth taking another wireless router with you, perhaps a netgear one?

Andy

Andy, we are on cable at home so do not have any adsl wireless routers. Your status sheets are going to be really useful though - we shall go through each one and compare, and prior to that open up the ethernet modem and see if we can match those configs since that one is working fine. PeterB also said about swapping Mac addresses, so that might be something, and there is the blanking of the DNS, even though that is not immediately pertinent. We will try all we got so far, and report back when we get back here.thank you :)

Madman - Thanks for posting that - it is the same as my set up (apart fromISP/password details )

Pawz - proof thgat a picture is worth a thousand words - I was going to invesigate posting a couple of screen shots today - madman beat me to it! :) )

Incidentally, I think the UK2 reference was to a special version of firmware 2.5.9 designed for lines with a poor SNR - not relevant as you are now on firmware 2.8.

hello, back again, not got to the Draytek yet, that is next. Been looking at Draytek's Troubleshooting .pdf - didn't realise there were comments under the chart - very useful.
It says in there - which confirms what you have said - 'WAN status will report when it is trying to authenticate with the message 'Starting PPP' and if it has failed to Authenticate, with the message 'PPP Shutdown'

That IS what I am seeing

It goes on 'In addition, if the failure to authenticate was caused by CHAP Login Failure, this will be reported as UserName/Password Error'

I am not seeing that

'When the PPPoE/PPPoA Client is enabled there will be a Dial PPPoA button on the right hand side of the WAN Status'.

Yes, that is there.

So, the problem is failure to authenticate, probably caused by incorrect DSL settings - but all the settings the troubleshooter lists are as entered. It then says that if all these are correct, to consider SNR and loop atten. Hubs thinks he remembers they were within good margins - the exchange is just down the road - and anyway, the ethernet modem had no problems.

I feel like I am staring at a blank wall, but the solution MUST be in there some where.
So, we are going to look at the ethernet setup to see if we can glean any info from that, then we are going to go through the Draytek status sheets one by one and compare them with Andy's. Will report back later if that is OK :)

I am back, tried blank dns's and swapping the MAC, and compared the router status pages with Andy's and have not been able to identify any incorrect settings. I have saved three logs from Syslog - wan, call and user access, and put them on the Draytek forum - should I put them on here as well? They do not make much sense to me.... :(

Yes - post them here

this is the WAN log I think - I didn't give it a descriptive name on first save. Had to shorten it to post.

158Jan 1 00:20:36Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:20:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:20:47Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:20:52VigorPPP Start (PPPoA)
158Jan 1 00:20:54Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:03Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:09VigorPPP Start (PPPoA)
158Jan 1 00:21:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:19Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:25VigorPPP Start (PPPoA)
158Jan 1 00:21:34Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:43VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:45Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:51VigorPPP Start (PPPoA)
158Jan 1 00:21:53Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:04Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:22:09VigorPPP Start (PPPoA)
158Jan 1 00:22:10Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:25VigorPPP Start (PPPoA)
158Jan 1 00:22:27Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:35VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:46VigorPPP Start (PPPoA)
158Jan 1 00:22:47Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:56VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:58Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:04VigorPPP Start (PPPoA)
158Jan 1 00:23:05Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:14VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:16Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:23:21VigorPPP Start (PPPoA)
158Jan 1 00:23:31VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:32Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:38VigorPPP Start (PPPoA)
158Jan 1 00:23:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:49VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:56VigorPPP Start (PPPoA)
158Jan 1 00:23:57Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:16VigorPPP Start (PPPoA)
158Jan 1 00:24:18Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:26VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:30Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:24:36VigorPPP Start (PPPoA)
158Jan 1 00:24:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:50Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:24:56VigorPPP Start (PPPoA)
158Jan 1 00:24:58Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:08Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:25:14VigorPPP Start (PPPoA)
158Jan 1 00:25:15Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:24VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:24Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:25:30VigorPPP Start (PPPoA)
158Jan 1 00:25:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:48VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:58VigorPPP Start (PPPoA)
158Jan 1 00:25:59Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
150Jan 1 00:20:32VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:33VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:35VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:39VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:41VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:42VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:43VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:47VigorLocal User: 192.168.1.10:1087 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:20:49VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:01VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:03VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:07VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:17VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:18VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:19VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:21VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:25VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:46VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:47VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:49VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:21:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:02VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:04VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:05VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:08VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:12VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:13VigorLocal User: 192.168.1.10:1088 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:22:22VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:23VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:24VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:26VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:30VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:50VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:51VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:52VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:54VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:58VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:08VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:09VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:10VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:12VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:16VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:24VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:25VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:26VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:26VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:27VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:28VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:28VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:30VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:32VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:34VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:39VigorLocal User: 192.168.1.10:1089 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:23:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:55VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:56VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:02VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:12VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:13VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:14VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:14VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:16VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:20VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:30VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:31VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:32VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:34VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:38VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:50VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:24:51VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:24:52VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:24:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:24:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com


this is the call log, also shortened.

158Jan 1 00:20:36Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:20:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:20:47Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:20:52VigorPPP Start (PPPoA)
158Jan 1 00:20:54Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:03Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:09VigorPPP Start (PPPoA)
158Jan 1 00:21:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:19Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:25VigorPPP Start (PPPoA)
158Jan 1 00:21:34Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:43VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:45Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:51VigorPPP Start (PPPoA)
158Jan 1 00:21:53Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:04Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:22:09VigorPPP Start (PPPoA)
158Jan 1 00:22:10Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:25VigorPPP Start (PPPoA)
158Jan 1 00:22:27Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:35VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:46VigorPPP Start (PPPoA)
158Jan 1 00:22:47Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:56VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:58Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:04VigorPPP Start (PPPoA)
158Jan 1 00:23:05Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:14VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:16Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:23:21VigorPPP Start (PPPoA)
158Jan 1 00:23:31VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:32Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:38VigorPPP Start (PPPoA)
158Jan 1 00:23:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:49VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:56VigorPPP Start (PPPoA)
158Jan 1 00:23:57Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:16VigorPPP Start (PPPoA)
158Jan 1 00:24:18Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:26VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:30Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:24:36VigorPPP Start (PPPoA)
158Jan 1 00:24:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:50Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:24:56VigorPPP Start (PPPoA)
158Jan 1 00:24:58Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:08Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:25:14VigorPPP Start (PPPoA)
158Jan 1 00:25:15Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:24VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:24Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:25:30VigorPPP Start (PPPoA)
158Jan 1 00:25:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:48VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:58VigorPPP Start (PPPoA)
158Jan 1 00:25:59Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:08VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:18VigorPPP Start (PPPoA)
158Jan 1 00:26:19Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:29VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:32Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:26:37VigorPPP Start (PPPoA)
158Jan 1 00:26:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:47VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:58VigorPPP Start (PPPoA)
158Jan 1 00:27:09VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:10Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:27:16VigorPPP Start (PPPoA)
158Jan 1 00:27:18Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:27:27VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:28Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:27:34VigorPPP Start (PPPoA)
158Jan 1 00:27:35Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:27:44VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:45Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:27:51VigorPPP Start (PPPoA)
158Jan 1 00:28:00Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:09VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:10Vigor>>> Dial-up triggered by user : 192.168.1.11 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:28:15VigorPPP Start (PPPoA)
158Jan 1 00:28:17Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:26VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:28Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:28:34VigorPPP Start (PPPoA)
158Jan 1 00:28:35Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:44VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:47Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:28:52VigorPPP Start (PPPoA)
158Jan 1 00:28:54Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
150Jan 1 00:20:32VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:33VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:35VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:39VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:41VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:42VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:43VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:47VigorLocal User: 192.168.1.10:1087 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:20:49VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:01VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:03VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:07VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:17VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:18VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:19VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:21VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:25VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:46VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:47VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:49VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:21:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:02VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:04VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:05VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:08VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:12VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:13VigorLocal User: 192.168.1.10:1088 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:22:22VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:23VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:24VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:26VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:30VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:50VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:51VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:52VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:54VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:58VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:08VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:09VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:10VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:12VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:16VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:24VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:25VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:26VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:26VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:27VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:28VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:28VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:30VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:23:32VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:23:34VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:39VigorLocal User: 192.168.1.10:1089 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:23:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:55VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:56VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:23:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:02VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:12VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:13VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:14VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:14VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:16VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:24:20VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:24:30VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com

this is user access log, also shortened

158Jan 1 00:20:36Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:20:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:20:47Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:20:52VigorPPP Start (PPPoA)
158Jan 1 00:20:54Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:03Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:09VigorPPP Start (PPPoA)
158Jan 1 00:21:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:19Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:25VigorPPP Start (PPPoA)
158Jan 1 00:21:34Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:21:43VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:21:45Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:21:51VigorPPP Start (PPPoA)
158Jan 1 00:21:53Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:04Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:22:09VigorPPP Start (PPPoA)
158Jan 1 00:22:10Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:25VigorPPP Start (PPPoA)
158Jan 1 00:22:27Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:35VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:46VigorPPP Start (PPPoA)
158Jan 1 00:22:47Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:22:56VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:22:58Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:04VigorPPP Start (PPPoA)
158Jan 1 00:23:05Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:14VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:16Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:23:21VigorPPP Start (PPPoA)
158Jan 1 00:23:31VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:32Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:23:38VigorPPP Start (PPPoA)
158Jan 1 00:23:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:23:49VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:23:56VigorPPP Start (PPPoA)
158Jan 1 00:23:57Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:16VigorPPP Start (PPPoA)
158Jan 1 00:24:18Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:24:26VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:30Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:24:36VigorPPP Start (PPPoA)
158Jan 1 00:24:46VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:24:50Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:24:56VigorPPP Start (PPPoA)
158Jan 1 00:24:58Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:06VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:08Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:25:14VigorPPP Start (PPPoA)
158Jan 1 00:25:15Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:24VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:24Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:25:30VigorPPP Start (PPPoA)
158Jan 1 00:25:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:25:48VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:25:58VigorPPP Start (PPPoA)
158Jan 1 00:25:59Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:08VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:18VigorPPP Start (PPPoA)
158Jan 1 00:26:19Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:29VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:32Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480
158Jan 1 00:26:37VigorPPP Start (PPPoA)
158Jan 1 00:26:39Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:26:47VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:26:58VigorPPP Start (PPPoA)
158Jan 1 00:27:09VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:10Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:27:16VigorPPP Start (PPPoA)
158Jan 1 00:27:18Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:27:27VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:28Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:27:34VigorPPP Start (PPPoA)
158Jan 1 00:27:35Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:27:44VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:27:45Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:27:51VigorPPP Start (PPPoA)
158Jan 1 00:28:00Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:09VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:10Vigor>>> Dial-up triggered by user : 192.168.1.11 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:28:15VigorPPP Start (PPPoA)
158Jan 1 00:28:17Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:26VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:28Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.109.6.66 port=13568
158Jan 1 00:28:34VigorPPP Start (PPPoA)
158Jan 1 00:28:35Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:28:44VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:28:47Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:28:52VigorPPP Start (PPPoA)
158Jan 1 00:28:54Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:29:02VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:29:10VigorPPP Start (PPPoA)
158Jan 1 00:29:11Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:29:19VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:29:23Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
158Jan 1 00:29:28VigorPPP Start (PPPoA)
158Jan 1 00:29:29Vigor<<< Incoming Call : fs=6,Ps=5,ph=1,d=1,0
158Jan 1 00:29:38VigorCHAP Login Failed (PPPoA) -
158Jan 1 00:29:41Vigor>>> Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568
150Jan 1 00:20:32VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:33VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:35VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:39VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:20:41VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:42VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:43VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:20:47VigorLocal User: 192.168.1.10:1087 -> 216.49.88.118:80 (TCP)Web
150Jan 1 00:20:49VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:20:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:01VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:03VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:07VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:17VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:18VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:19VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:21VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:25VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:45VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:46VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:47VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:49VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:21:54VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:21:58VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:21:59VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:00VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:02VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com
150Jan 1 00:22:04VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:05VigorLocal User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com
150Jan 1 00:22:06VigorLocal User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com

Here I have given a very abbreviated WAN log, missing repetitive bits out in the hopes of making the procedures easier to follow.

Incoming Call : fs=6,Ps=5,ph=1,d=1,0&#172;
CHAP Login Failed (PPPoA) -&#172;
Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480&#172;
PPP Start (PPPoA)&#172;

Incoming Call : fs=6,Ps=5,ph=1,d=1,0&#172;
CHAP Login Failed (PPPoA) -&#172;
Dial-up triggered by user : 192.168.1.10 ; proto=udp, to 194.98.0.1 port=13568&#172;
PPP Start (PPPoA)&#172;

Incoming Call : fs=6,Ps=5,ph=1,d=1,0&#172;
CHAP Login Failed (PPPoA) -&#172;
Dial-up triggered by user : 192.168.1.10 ; proto=tcp, to 216.49.88.118 port=20480&#172;
PPP Start (PPPoA)&#172;

Local User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com&#172;
Local User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com&#172;
Local User: 192.168.1.10 DNS -> 194.109.6.66 inquire updatekeepalive.mcafee.com&#172;
Local User: 192.168.1.10 DNS -> 194.98.0.1 inquire updatekeepalive.mcafee.com&#172;
Local User: 192.168.1.10 DNS -> 194.98.0.1 inquire dss1.siteadvisor.com&#172;
Local User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com&#172;
Local User: 192.168.1.10:1087 -> 216.49.88.118:80 (TCP)Web&#172;
Local User: 192.168.1.10 DNS -> 194.109.6.66 inquire dss1.siteadvisor.com&#172;
PoE ==> Protocol:LCP(c021) ConfReq Identifier:0x01 MRU: 1500 ##&#172;
PoE <== Protocol:LCP(c021) ConfReq Identifier:0x60 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE ==> Protocol:LCP(c021) ConfAck Identifier:0x60 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE <== Protocol:LCP(c021) ConfReq Identifier:0x61 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE ==> Protocol:LCP(c021) ConfAck Identifier:0x61 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE <== Protocol:LCP(c021) ConfReq Identifier:0x62 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE ==> Protocol:LCP(c021) ConfAck Identifier:0x62 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE ==> Protocol:LCP(c021) ConfReq Identifier:0x02 MRU: 1500 ##&#172;
PoE <== Protocol:LCP(c021) ConfAck Identifier:0x02 MRU: 1500 ##&#172;
PoE <== Protocol:CHAP(c223) Challenge Identifier:0xB4 10 8f c8 28 7a 6d 85 d3 e2 65 c1 8d 60 00 36 08 8c 45 52 58 31 35 2e 4d 69 6c 74 6f 6e 6b 65 79 6e 65 73 32 ##&#172;
PoE ==> Protocol:CHAP(c223) Response Identifier:0xB4 10 91 6c 6f 3a 48 e5 26 a8 60 2d 31 b6 cb 64 52 78 31 37 33 30 38 39 32 31 36 37 40 74 61 6c 6b 74 61 6c 6b 2e 6e 65 74 ##&#172;
PoE <== Protocol:LCP(c021) ConfReq Identifier:0x6A MRU: 1400 Authentication Type: CHAP 05 Magic Number: 0x6ecdc1d ##&#172;
PoE ==> Protocol:LCP(c021) ConfReq Identifier:0x03 MRU: 1500 ##&#172;
PoE <== Protocol:CHAP(c223) Challenge Identifier:0x01 10 92 d6 fe 34 20 87 37 06 a1 40 4a 48 a5 0c c3 43 62 72 61 30 30 32 2e 62 72 65 ##&#172;
PoE ==> Protocol:CHAP(c223) Response Identifier:0x01 10 47 02 c4 af f3 0b 45 a2 ff 4a ca b4 a5 34 7a 56 31 37 33 30 38 39 32 31 36 37 40 74 61 6c 6b 74 61 6c 6b 2e 6e 65 74 ##&#172;
PoE <== Protocol:CHAP(c223) Failure Identifier:0x01CHAP authentication failure, unit 19539 ##&#172;
PoE ==> V:1 T:1 PADT ID:0&#172;
PoE ==> Protocol:LCP(c021) TermReq Identifier:0x05 ##&#172;
Vigor&#172; ISDN B3075 ==> Unknown: 11 a7 00 06 00 00 ##&#172;
Vigor&#172; ISDN B3075 ==> Unknown: 11 a7 00 06 00 00 ##&#172;
Vigor&#172; PoE ==> V:1 T:1 PADI ID:0&#172;
Vigor&#172; PoE <== V:1 T:1 PADO ID:0&#172;
Vigor&#172; ISDN B3075 ==> Unknown: 11 a7 00 06 00 00 ##&#172;
Vigor&#172; PoE <== V:1 T:1 PADO ID:0&#172;
Vigor&#172; PoE ==> V:1 T:1 PADR ID:0&#172;
Vigor&#172; PoE <== V:1 T:1 PADS ID:1536&#172;
Vigor&#172; PoE <== V:1 T:1 PADS ID:1536&#172;
Vigor&#172; PoE ==> Protocol:LCP(c021) ConfReq Identifier:0x00 MRU: 1500 ##&#172;
Vigor&#172; PoE <== Protocol:LCP(c021) ConfReq Identifier:0x08 Authentication Type: CHAP 05 Magic Number: 0x1d0f765a ##&#172;
Vigor&#172; PoE ==> Protocol:LCP(c021) ConfAck Identifier:0x08 Authentication Type: CHAP 05 Magic Number: 0x1d0f765a ##&#172;
Vigor&#172; PoE <== Protocol:LCP(c021) ConfReq Identifier:0x09 Authentication Type: CHAP 05 Magic Number: 0x1d0f765a ##&#172;
Vigor&#172; PoE ==> Protocol:CHAP(c223) Response Identifier:0x94 10 44 05 af af 18 ee 79 15 05 3c f9 95 c4 7d 30 ec 31 37 33 30 38 39 32 31 36 37 40 74 61 6c 6b 74 61 6c 6b 2e 6e 65 74 ##&#172;
166&#172; Jan 1 00:21:17&#172; Vigor&#172; PoE <== Protocol:CHAP(c223) Challenge Identifier:0x8E 10 d7 bd ed 72 66 6b 91 be dc dd 4d 59 ed 57 26 b5 45 52 58 31 35 2e 4d 69 6c 74 6f 6e 6b 65 79 6e 65 73 32 ##&#172;
166&#172; Jan 1 00:21:17&#172; Vigor&#172; PoE ==> Protocol:CHAP(c223) Response Identifier:0x8E 10 21 aa 34 c7 5f fd 1e 7f 77 10 ea 92 3e 4e 83 4b 31 37 33 30 38 39 32 31 36 37 40 74 61 6c 6b 74 61 6c 6b 2e 6e 65 74 ##&#172;

The logs all look very similar to me - are you sure they are different?

Are you sure that the settings under the PPPoA/PPPoE set up under ISP setup are correct - in particular the always on box is ticked. (As a last resort, are you saving the settings using the save settings box at the bottom of the page?

I have also posted on the Draytek forum, but if all the settings are correct, then there is the possibility that the router has developed a fault (although you say it was working until the talk talk migration).

As the poster on the Draytek forum says, there should have been no need to do anything to the PC - you sid that the talk talk supplied device is an ethernet modem - is it ethernet or USB? (Not that that should affect anything as the router simply uses the ethernet port)

Can you report back the SNR and attenuation settings?

I installed syslog and then saved the data from three - WAN, User access and Call ( I think)
Yes, sure the settings are right - been through it so many times, and today we went through Madman's ( Andy's) status pages - and everything matches.

Could this line be important do you think Peter?

PoE <== Protocol:CHAP(c223) Failure Identifier:0x01CHAP authentication failure, unit 19539 ##&#172;

I have tried sending a query to Draytek but it will not go, returns an error - not my week is it.
I did not see a save box in setup, but 'Next' Boxes and Finish box when going through the QuickStart setup, and when you go back in it is all there in the statuspanels and overview. If we were to suggest getting another router ( though there is nothing wrong with this one), would we still get the same problem do you think?

I cannot recall the SNR and attenuation now, though we wrote them down - however, when we looked at the troubleshooter doc for the Vigor, the values were well within the acceptable range.

The talktalk modem is ethernet. Thank you Peter.

I have just tried the Draytek forum again but cannot get on - internal error it says.

OK - I have just had a look at Talk Talks support pages. There are some things I don't fully understand - one is that when using talk talks software and modem/router, it implies that there is a two stage connection process - a connection to talk talk ISP and THEN a login using phonenumber@talktalk and a password - but it isn't clear if that is also the initial password. I don't think the Draytek router is at fault, but it may be that you are not getting all the information from talk talk. In particular I am wary of statements that say that talk talk won't allow you to connect without their software on your computer - implying some other security system that may only work with their hardware.

I don't think I can help any further - anyone else here who has had experience of connecting a draytek router to talk talk may be able to help, so it may be worth starting a new thread. (Something like "Problems connecting a Draytek router to Talk Talk ISP) and state what you have done (you might want to cross reference to this thread) It might also be worth posting a similar thread on the Draytek forums as it is no longer an upgrade issue.

Otherwise I tthink the best sources of help are (in this order) Talk Talk's help desk and then the Draytek support line - but I don't think it is a Draytek issue.

If that doesn't resolve it, then either use Talk talk supplied hardware (I see they sell a wireless router) or change to another ISP.

I'm sorry this hasn't worked out for you - but this is definitely an authentication issue and one that I think only talk talk can offer authorative advice.

PeterB ( and all those who have tried to help ) - we got something of a result today. First I must explain that in the early stages of this effort to help, we brought the Draytek router home so that we could connect it via ethernet and find out how to access via the browser address. That was accomplished quite easily and I thought it would save us time to put the required settings in here so that we would be up and running when we went back to connect it via ADSL. Good

I used a somewhat battered laptop we had acquired to put the info in, and therein lies the clue... although we had gone over the settings again and again, we had not checked the username and password as they were carefully entered exactly as was done for the ethernet modem, but what had happened is that the very first digit of the username had not actually registered when I hit the key, and then it got hidden as the typing pushed the line to the left and that number went out of sight. I knew I had entered it properly - but the 0 key on that laptop had not registered. Once we realised that, we corrected the error and voila we were on the net!

However, despite our delight and my pink cheeks, we are not quite out of the woods, and I would value your advice in a new thread to do with security keys and upgrade issues and disappearing Gateway IP's on the client side of the router.

Phew - I am SOOO pleased! - I'll go and have a look at the other thread (Rushes off - stage left)

peterb :)