Reply
New Member
Posts: 16
Registered: ‎09-13-2015

WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

[ Edited ]

Hi,

 

I've been running a rock-solid controller-less UP-AC-PRO at home happily for a couple of years and recently decided to add a Cloud Key and USG 3P to get greater insight into my network. Due to restrictions on my ISP supplied router, I've had to swap in a Draytek Vigor 130 VDSL modem also. With some effort I've managed to get all of this playing together fairly successfully. However, I'm experiencing very regular WAN connectivity drop outs where I lost connectivity to the Internet for minutes at a time. I've pulled the logs from the USG and have found entires that correlate temporally with the dropouts (see below). Can anyone suggest what might be wrong, or what I can do to improve the situation?

 

Configuration:

 

Draytek Vigor 130 (UK) VDSL modem

  • Firmware: 3.8.2 BT
  • Protocol: PPPoE/A disabled, MPoA enabled
  • MAC set to that of the ISP supplied router

USG 3P

  • Firmware: 4.4.18.5052168
  • WAN DHCP enabled
  • IPS, DPI, GeoIP filtering: enabled
  • Additional config for DHCP option 61 (required by ISP):
        configure
        delete interfaces eth0 address dhcp
        commit
        set interfaces ethernet eth0 dhcp-options client-option "send dhcp-client-identifier "authStringExtractedViaWireShark";"
        set interfaces ethernet eth0 address dhcp
        commit
        save

Logs

Apr 15 19:52:07 Router zebra[683]: interface eth0 index 2 changed <UP,BROADCAST,MULTICAST>.
Apr 15 19:52:09 Router zebra[683]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Apr 15 19:52:09 Router kernel: eth0: 1000 Mbps Full duplex, port 0
Apr 15 19:52:16 Router ipsec-dhclient-hook: DHCP address updated to from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:52:16 Router ipsec-dhclient-hook: DHCP address updated to from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:52:17 Router xl2tpd[15521]: death_handler: Fatal signal 15 received
Apr 15 19:52:17 Router xl2tpd[22030]: parse_config: line 3: set_ip: host '' not found
Apr 15 19:52:17 Router xl2tpd[22030]: init: Unable to load config file
Apr 15 19:53:17 Router ipsec-dhclient-hook: DHCP address updated to 176.26.231.19 from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:53:18 Router ipsec-dhclient-hook: DHCP address updated to 176.26.231.19 from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:53:19 Router xl2tpd[22416]: setsockopt recvref[30]: Protocol not available
Apr 15 19:53:52 Router kernel: ALIEN BLOCK: IN=eth0 OUT= MAC=fc:ec:da:04:b3:6f:00:d0:XX:XX:XX:XX:XX:XX src=71.6.135.131 DST=176.26.231.19 LEN=44 TOS=0x00 PREC=0x00 TTL=117 ID=7037 PROTO=TCP SPT=16592 DPT=11211 WINDOW=60166 RES=0x00 SYN URGP=0

Apr 15 19:55:45 Router zebra[683]: interface eth0 index 2 changed <UP,BROADCAST,MULTICAST>.
Apr 15 19:55:45 Router kernel: eth0: Link down
Apr 15 19:55:46 Router zebra[683]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Apr 15 19:55:52 Router ipsec-dhclient-hook: DHCP address updated to from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:55:53 Router ipsec-dhclient-hook: DHCP address updated to from 176.26.231.19: Updating ipsec configuration.
Apr 15 19:55:53 Router xl2tpd[22417]: death_handler: Fatal signal 15 received
Apr 15 19:55:53 Router xl2tpd[23102]: parse_config: line 3: set_ip: host '' not found
Apr 15 19:55:53 Router xl2tpd[23102]: init: Unable to load config file
Apr 15 19:56:40 Router kernel: IPv4: martian destination 0.0.0.0 from 192.168.0.17, dev eth1
Apr 15 19:57:12 Router kernel: last message repeated 3 times
Apr 15 20:01:37 Router ipsec-dhclient-hook: DHCP address updated to 5.65.98.75 from : Updating ipsec configuration.
Apr 15 20:01:38 Router ipsec-dhclient-hook: DHCP address updated to 5.65.98.75 from : Updating ipsec configuration.
Apr 15 20:01:39 Router xl2tpd[24743]: setsockopt recvref[30]: Protocol not available
Apr 15 20:02:27 Router ddclient[6099]: SUCCESS: updating my_dydns_host: good: IP address set to 5.65.98.75

Established Member
Posts: 1,480
Registered: ‎04-22-2016
Kudos: 302
Solutions: 119

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

@teabot

Hi, recently I setup successfully a Vigor 130 and USG 3P for a customer. The biggest hurdle was to find out, which VLAN had to be configured. It was not published on the ISP Website. They expect their subscribers, to use their pre-configuered, all-in-one Huawei Router.

 

I don't know the VDSL and WAN settings for your ISP. There are endless variations with all the ISP's

 

It seems to me, you have part of the VDSL connection setup in the Vigor and another part in the USG.

 

In my case, the first step was to setup the Vigor as a Router with double NAT to the USG. When this was working OK, I knew the correct VDSL and WAN settings.

The second step was to put the Vigor in bridge mode as a VDSL Modem and let the USG handle the WAN connection.

 

Regards, cempa

 

 

 

Please reward people who have helped you with kudo's and mark your thread as solved when you receive a solution to your issue.
New Member
Posts: 3
Registered: ‎06-01-2018

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Did you manage to fix this? I'm having exactly the same issues (Sky Fibre, Dratek Vigor 130 and USG 4 Pro 4.4.22.5086057).  

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Not quite. I traced this back to the vigor resyncing on the VDSL line. The negotiated speeds fell over time and the drops continued. I checked the vigor logs, firmware, etc. but couldn’t improve reliability. Eventually I switched back to the skybox and soon I was back up to full speed for my line and no resyncs (which were the cause of the drop outs). I’m currently double NATing the USG and the sky router which isn’t ideal but I’ve been able to get ddns working on the USG despite this. The vigor is probably going to sit in a cupboard until I switch providers and then I’ll give it another try.

New Member
Posts: 3
Registered: ‎06-01-2018

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Thanks  very much for the info. Half the battle seems to be working out where the problem lies.  May I ask how you tracked it down to be a Modem issue.  Of course whenever I sit down to trouble shoot the connection has no issues at all!

I've found Xdsl Reset Times on the Modem. Will that increase everytime it resyncs?

Good to know plugging the sky box back in works with the double nat.  That might be the direction I have to go if things don't settle down on the line.

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

I noticed on the USG log that the WAN port would go down for a couple of seconds. This would cause a bunch of services on the USG to reset, causing a few minutes of outage. I figured either a WAN cable issue (unlikely) or that the vigor was pulling the WAN eth link down. I next looked on the vigor diagnostics and then logs (had to turn this on in the CLI). This is when I saw the VDSL resyncing, and at times that correlated with the issues in the USG log. There was no real hardware troubleshooting that I could think of at that point, so I put the skybox back in to see if it was a line fault, which doesn’t seem to be the case. I suspect that some vigor configuration might help, but I couldn’t find anything that seemed appropriate.

New Member
Posts: 3
Registered: ‎06-01-2018

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Thanks again for the helpful reply.

I finally found the stat that showed the modem resyncing and it was indeed happening at the same time the gateway was losing its net connection.  I've therefore admitted defeat and stuck the usg on the Sky box DMZ which will hopefully solve most double nat problems.

I did find some recommended settings on the Draytek website for Sky Fibre but it just made it worse if anything.  I actually suspect I've got a line fault somewhere as download speed is steady as a rock and never changes from resync to resync but upload is all over the place.  It was 9 up for years but now it's dropped to 4.5 over the last few months.

I'll get sky to look at it now I've got their hub back in place and maybe try again with the Vigor if they can sort it.

New Member
Posts: 15
Registered: ‎08-30-2016
Kudos: 5
Solutions: 1

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

I've had similar issues with the Vigor 130. Think I've fixed them. It's a bug with the firmware I think and having to fragment packets. If you change the settings of the router to enable baby jumbo frames and an MTU of 1508, mine at least has become stable.

 

https://community.ubnt.com/t5/UniFi-Routing-Switching/Unifi-USG-and-Draytek-Vigor-130-connection-dro...

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

[ Edited ]

Thanks for the information @mnotgninnep, in a Sky setup I believe the eth0 address is simply of type DHCP and not PPPoE, with the Vigor set to MPoA mode. In this scenario, I assume the following stanza is not relevant?

 

"pppoe": {
  "0": {
    "mtu": "1500"
  }
}

I'll give this a try soon and report back on how I get on. 

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

[ Edited ]

I've had no such luck. Firstly, I'm using MPoA on the Vigor side with PPPoE client disabled (required by my ISP). Secondly, the MTU on my Vigor was set to 1520. I dropped the MTU on the Vigor to 1500 and set the MTU on the USG to 1508. I also discarded the pppoe mtu stanza, as its inclusion seemed to prevent the modem/router connection from initiating.

 

Looked good for 5 minutes, then the WAN connection started dropping out again as before. Any thoughts?

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Ok, also upgraded USG 3P to 4.4.22.5086045 and my experience is now slightly different. My Vigor 130 is still frequently retraining, but the USG is not reporting the WAN interface eth0 down and so is subsequently not restarting/reconfiguring services for minutes each time. This is an improvement, as clients on my network see second long blips instead of outages of many minutes. I suspect my line issues now center on the Vigor.

 

I've also purchased a Netgear DM200 to see if that is more 'atuned' to my VDSL line, but while I can connect to by service provider, I'm having trouble getting the USG online with it. That is another thread however.

New Member
Posts: 15
Registered: ‎08-30-2016
Kudos: 5
Solutions: 1

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

I’m keeping an eye on this. I’m still getting frequent dropouts, maybe 10 per day but my provider has said they have detected a copper line fault and want to send an engineer to repair to fix it. Perhaps the draytek is more sensitive to line problems. I’ll let you know how I get on. Watch this space. 

New Member
Posts: 15
Registered: ‎08-30-2016
Kudos: 5
Solutions: 1

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

[ Edited ]

Engineer visted yesterday and resolved a copper fault on my line. It's been up since 4:15pm yesterday and no dropouts so far. Seems stable, so hope it stays that way.

 

Might be worth getting your line investigated.

New Member
Posts: 16
Registered: ‎09-13-2015

Re: WAN drop outs: USG 3P + Draytek Vigor 130 + Sky Fibre (UK)

Fingers crossed. I’m now on my third modem (a TP-Link W9970) which I chose because the chipset matches that used in the cabinet. The line seems solid, but to be fair, the stats and diagnostics from this budget modem are so sparse that it’s hard to tell if it’s retraining or not.

 

I'm loath to involve my ISP or engineers because anything other than their supplied router is not supported.

Reply