Whirlpool

Hello all,

Since purchasing the Draytek Vigor 2800g in October last year I have frequently been experiencing a problem where the router drops the WAN connection at seemingly random intervals. Sometimes the router will run for two to three days without experiencing any problem then suddenly lose the connection. Other times it might only be running for an hour and the connection will drop.

To try and solve this problem I updated the firmware to: D.57.2.14 Annex A. This hasn't fixed the problem, though since updating the router does attempt to auto-reconnect upon losing the connection.

I setup Syslog to try and see if there were any clues in it that could help me figure out what was going wrong. I've had a look through the various logs but i'm not too tech savvy in this area and most of it doesn't make sense. I am hoping someone on this forum is able to decipher what these logs are saying and perhaps give me some pointers on how I could fix the problem.

Firstly, some info that could be helpful:

i) I use the 2800g to connect to iinet ADSL2
ii) I'm using the router in wireless mode with both an XP and Vista machine connecting to it. A Wii also connects to the router. The Vista machine and Wii are both new and I was experiencing this problem prior to getting it, i.e. when I only had the XP machine connecting.
iii) Current settings are:

Encapsulation Type: VC MUX
Protocol: PPPoA
Modulation: ADSL2 Auto (G.992.3)
Security: WPA (Mixed WPA+WPA2) with PSK, Access Control enabled

Some SysLogs around the time that the router has dropped the connection (two different occassions):

Call Log:
158Jan 22 19:14:46VigorPPP Closed : Remote Terminating (PPPoA)
158Jan 22 19:15:37VigorPPP Start (PPPoA)
158Jan 22 19:15:45VigorPAP Login OK (PPPoA)
158Jan 22 19:15:45VigorIPCP Opening (PPPoA); Own IP Address : 124.168.214.204 Peer IP Address : 203.173.61.88; Primary DNS : 203.0.178.191 Secondary DNS : 0.0.0.0
158Jan 22 20:05:43VigorPPP Closed : Remote Terminating (PPPoA)
158Jan 22 20:06:49VigorPPP Start (PPPoA)
158Jan 22 20:06:51VigorPAP Login OK (PPPoA)
158Jan 22 20:06:51VigorIPCP Opening (PPPoA); Own IP Address : 124.168.197.155 Peer IP Address : 203.173.61.88; Primary DNS : 203.0.178.191 Secondary DNS : 203.215.29.191

In this log, the 'Remote Terminating' appears to be where the router is closing the connection. It then auto reconnects a minute or so later. My question is why is it remote terminating? Does remote terminating mean that the ISP is terminating the connection (hence remote)?

Below is an extract of the WAN log from around when the connection was dropped at 19:14:

150Jan 22 19:09:53VigorWLAN_DBG - MLME Disassoc MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:11:42VigorWLAN_DBG - MLME Associate MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:11:42VigorWLAN_DBG - WPA capable client
150Jan 22 19:11:42VigorWLAN_DBG - Wpa_capability_check: ok
150Jan 22 19:11:42VigorWLAN_DBG - WPA handshake start for 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - send 1st packet in 4-way handshake
150Jan 22 19:11:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:11:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:11:42VigorWLAN_DBG - Rx message 2 in 4-way handshake
150Jan 22 19:11:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - send 3rd packet in 4-way handshake
150Jan 22 19:11:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:11:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:11:42VigorWLAN_DBG - Rx message 4 in 4-way handshake
150Jan 22 19:11:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - send group key
150Jan 22 19:11:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:11:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:11:42VigorWLAN_DBG - Rx group key response
150Jan 22 19:11:42VigorWLAN_DBG - WPA handshake finish for 0:1a:e9:a4:d1:bb
150Jan 22 19:11:42VigorLocal User: 192.168.1.13 DNS -> 203.0.178.191 inquire weather.wapp.wii.com
150Jan 22 19:11:42VigorLocal User: 192.168.1.13 DNS -> 203.0.178.191 inquire weather.wapp.wii.com
150Jan 22 19:11:42VigorLocal User: 192.168.1.13 -> 203.0.178.191 (ICMP) Destination Unreachable
150Jan 22 19:11:43VigorLocal User: 192.168.1.13 DNS -> 203.0.178.191 inquire weather.wapp.wii.com
150Jan 22 19:11:43VigorLocal User: 192.168.1.13:55912 -> 203.206.138.147:80 (TCP)Web
150Jan 22 19:11:43VigorLocal User: 192.168.1.13:55912 -> 203.206.138.147:80 (TCP) close connection
150Jan 22 19:11:54VigorWLAN_DBG - MLME Disassoc MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:13:42VigorWLAN_DBG - MLME Associate MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:13:42VigorWLAN_DBG - WPA capable client
150Jan 22 19:13:42VigorWLAN_DBG - Wpa_capability_check: ok
150Jan 22 19:13:42VigorWLAN_DBG - WPA handshake start for 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - send 1st packet in 4-way handshake
150Jan 22 19:13:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:13:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:13:42VigorWLAN_DBG - Rx message 2 in 4-way handshake
150Jan 22 19:13:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - send 3rd packet in 4-way handshake
150Jan 22 19:13:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:13:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:13:42VigorWLAN_DBG - Rx message 4 in 4-way handshake
150Jan 22 19:13:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - send group key
150Jan 22 19:13:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:13:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:13:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:13:42VigorWLAN_DBG - Rx group key response
150Jan 22 19:13:42VigorWLAN_DBG - WPA handshake finish for 0:1a:e9:a4:d1:bb
150Jan 22 19:13:54VigorWLAN_DBG - MLME Disassoc MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:14:47VigorLocal User: 192.168.1.11:49199 -> 72.165.61.162:27017 (UDP)
150Jan 22 19:15:40VigorLocal User: 192.168.1.11:49199 -> 72.165.61.185:27017 (UDP)
150Jan 22 19:16:42VigorWLAN_DBG - MLME Associate MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:16:42VigorWLAN_DBG - WPA capable client
150Jan 22 19:16:42VigorWLAN_DBG - Wpa_capability_check: ok
150Jan 22 19:16:42VigorWLAN_DBG - WPA handshake start for 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - send 1st packet in 4-way handshake
150Jan 22 19:16:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:16:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:16:42VigorWLAN_DBG - Rx message 2 in 4-way handshake
150Jan 22 19:16:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - send 3rd packet in 4-way handshake
150Jan 22 19:16:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:16:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:16:42VigorWLAN_DBG - Rx message 4 in 4-way handshake
150Jan 22 19:16:42VigorWLAN_DBG - TSN, Send key to: 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - send group key
150Jan 22 19:16:42VigorWLAN_DBG - EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - Wpa_EAPoL_handler, from 0:1a:e9:a4:d1:bb
150Jan 22 19:16:42VigorWLAN_DBG - EAPOL_KEY
150Jan 22 19:16:42VigorWLAN_DBG - parse_EAPOL_Key
150Jan 22 19:16:42VigorWLAN_DBG - Rx group key response
150Jan 22 19:16:42VigorWLAN_DBG - WPA handshake finish for 0:1a:e9:a4:d1:bb
150Jan 22 19:16:54VigorWLAN_DBG - MLME Disassoc MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:24:43VigorWLAN_DBG - MLME Associate MAC 0:1a:ffffffe9:ffffffa4:ffffffd1:ff­ ffffbb
150Jan 22 19:24:43VigorWLAN_DBG - WPA capable client
150Jan 22 19:24:43VigorWLAN_DBG - Wpa_capability_check: ok

Nothing shows up in the Firewall log and the VPN log just shows the logins after disconnect.

Very much appreciate if anyone is able to help.

Thanks!

iiNets recommended setting are PPPoE.
Your encapulation of VS MUX I believe should be LLC.
www.iinet.net.au/support...tings/index.html

ADSL connection settings
* Connection Type - PPPoE LLC
* Authentication Module/Security Protocol - PAP
* VPI - 8
* VCI - 35
* Handshake Protocol/Modulation - G.DMT (ADSL1 modems) Multimode/ADSL2 (ADSL2 modems)

In the end it could be many things, could try an isolation test, install quality central ACS filter, check house phone wiring. You haven't indicated current speed, SNR, Attenuation.

Thanks Cams, i'll give those settings a go!

Under my current settings my stats are:

ADSL Status Mode: ADSL2
State: SHOWTIME
Up Speed: 980900
Down Speed: 6550100
SNR Margin: 11.0
Loop Att: 35.0

Will let you know how it goes with the new settings.

Thanks again!

Using the new settings my stats are now:

ADSL Status Mode: ADSL2
State: SHOWTIME
Up Speed: 869100
Down Speed: 6636100
SNR Margin: 11.0
Loop Att: 35.0

Will wait and see what up time is like.

Unfortunately i'm still having the same issue after changing those settings... except now it won't auto-reconnect when it drops the connection. After the connection is dropped, in the online status page the ADSL information connects but the WAN status hangs at Start PPP. Even if I click Dial PPPoE nothing happens - I had to reboot the router for it to reconnect.

Anyone know what hte problem might be?

ommie writes...

To try and solve this problem I updated the firmware to: D.57.2.14 Annex A

I think that is the wrong firmware to try as it was for "Special firmware for BigPond (Maxon) BP3-USB, BigPond (Maxon) BP3-EXT, Telstra Turbo Modem or other 3G service providers"

I would be trying one of these:
E.67.02.55
E.67.02.52
E.67.02.40
E.67.02.12
Y.1.28.187 for ADSL1 only

Also as said "In the end it could be many things, could try an isolation test, install quality central ACS filter, check house phone wiring"

You could even try another modem, as I suspect you know iiNet wont provide you support for that modem. People tend to claim these are very stable.
Dynalink RTA1025W, Netcomm NB6PLUS4W, SpeedTouch 585, not supprising that they all have the same chipsets.

ommie writes...

Anyone know what hte problem might be?

No idea. However i had the exact same problem with my Vigor2800VG. Here is what happened, the short story.

* Downloaded latest firmware from www.draytek.com.au
* Spoke with TPG about my problems. Over a few weeks, i rang and had settings (their end) changed this way and that.
* Messed around with different modulations. I found that G.DMT was most stable, but slowest.
* Eventually i noticed i had no problem. ADSL2+ mode an everything is fine.

Talk to your isp. Tell them your connection is not stable. ask if they can change some settings. INSIST that they try. TPG were helpful in this regard. If i asked for a change they would do it always.
Eventually we got something right.

/cheers

I have a vigor 2800g with the same problem, I am with AAPT have checked all settings and all ok, have downloaded latest firmware Y.1.28.187 which hasn't helped. I e-mailed Draytek support and they seem to think its a hardware problem and asked me to send the unit back to them. The catch there is they are in NSW and i am in perth, you have to send it at your own expense and be without it for up to 2 or more weeks. Not really the best option.

Would it be anything to do with Vista?

I have similar problems with picking up my wireless LAN on a machine with Vista – seems to hold when connected, but sometimes won't connect at all.

Have an XP machine that has no problems connecting and that is through a wireless usb adapter!

I run this firmware on my 2800vg without issue on an telescum adsl1 dslam

Lifted from the draytek web page

Firmware 2.8.1, ADSL modem code D.57.2.14 is the standard firmware for Vigor2800 series. It is suitable for most ISPs in Australia. However, if you encounter instable connection problems you can try other versions listed below. There is no "best" firmware for any particular ISP; unless if we specify so.
2.8.1

ADSL/ADSL2/ADSL2+/3G/NextG

i just got the stock standard 2800 and i seem to be getting the same problem.

the pppoe drops but the dsl is still connected and cant get the pppoe session to reconnect until i reboot the router.

amnet dslam with infineon chipset
fremantle
ULL/Naked line
port at dslam is locked at 3072/512 with interleave on for stability

tried firmware 2.8.2 D.57.2.14 got occasional sync drops but no above problem and getting the pppoe n sync drops problem with the E.67.36.1.

another weird thing is that with the d.57 version it reports loop att as 48db with the snr varying between 8 to 9 while the e.67 reports loop att as 54db snr between 8 to 14.

any ideas.

havent talked to isp or draytek about it yet.