DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

Unable to connect to Vigor 130

cezmunsta
Topic Author
User

25 Nov 2017 01:04 #1 by cezmunsta

Unable to connect to Vigor 130 was created by cezmunsta

Hi,

I've recently purchased a Vigor 130, but no matter what I have tried, the only evidence of the device being there is I can see it respond to ARP to give out its MAC address when connected via RJ45, but both DHCP and a static 192.168.2.0/24 IP on my laptop with 192.168.2.1 as the gateway fail to give access to its web interface. Attempting to connect via the modem using PPoE also seems to fail (consisten PADI timeout). Numerous factory resets as well as trying 3 different laptops without success.

I emailed support, but the response was not at all helpful. Does anyone have any idea what the issue could be?

Thanks

o/

Please Log in or Create an account to join the conversation.

adrianh54
User

25 Nov 2017 17:49 #2 by adrianh54

Replied by adrianh54 on topic Re: Unable to connect to Vigor 130

Static on the laptop should be in the range 192.168.2.2-254

Try setting a static on your PC of 192.168.2.10 with a subnet mask of 255.255.255.0 and the gateway: 192.168.2.1.

Please Log in or Create an account to join the conversation.

cezmunsta
Topic Author
User

27 Nov 2017 22:54 #3 by cezmunsta

Replied by cezmunsta on topic Re: Unable to connect to Vigor 130

Thanks for the reply. My previously stated IP was missing a digit! It was 192.168.2.10/24



Code:
$ ip addr show enp3s0f1
2: enp3s0f1:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 192.168.2.10/24 brd 192.168.2.255 scope global noprefixroute enp3s0f1
    inet6 fe80::82fa:5bff:fe11:d047/64 scope link

$ ip route show | egrep "^(default|192.168.2.)"
default via 192.168.2.1 dev enp3s0f1 proto static metric 20100
192.168.2.0/24 dev enp3s0f1 proto kernel scope link src 192.168.2.10 metric 100

Whilst connected, I can arping and get a response from the Vigor:



Code:
22:38:20.171871 ARP, Ethernet (len 6), IPv4 (len 4), Reply _gateway is-at 00:1d:aa:8c:e7:90 (oui Unknown), length 46

.. but that is all. If I watch the interface whilst trying to connect via port 80, or 443 I only see my requests and no response:



Code:
$ tcpdump -i enp3s0f1 -Avv host 192.168.2.1 and tcp port 443 -c 4
tcpdump: listening on enp3s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes
22:42:05.238473 IP (tos 0x0, ttl 64, id 22501, offset 0, flags [DF], proto TCP (6), length 60)
    slave.47096 > _gateway.https: Flags [S], cksum 0xe485 (correct), seq 3598222911, win 29200, options [mss 1460,sackOK,TS val 1002183142 ecr 0,nop,wscale 7], length 0
22:42:05.451808 IP (tos 0x0, ttl 64, id 34654, offset 0, flags [DF], proto TCP (6), length 60)
    slave.47098 > _gateway.https: Flags [S], cksum 0x1768 (correct), seq 3549058419, win 29200, options [mss 1460,sackOK,TS val 1002183356 ecr 0,nop,wscale 7], length 0
22:42:17.273343 IP (tos 0x0, ttl 64, id 21407, offset 0, flags [DF], proto TCP (6), length 60)
    slave.47100 > _gateway.https: Flags [S], cksum 0x0b75 (correct), seq 1685889605, win 29200, options [mss 1460,sackOK,TS val 1002195177 ecr 0,nop,wscale 7], length 0
22:42:18.278464 IP (tos 0x0, ttl 64, id 21408, offset 0, flags [DF], proto TCP (6), length 60)
    slave.47100 > _gateway.https: Flags [S], cksum 0x0788 (correct), seq 1685889605, win 29200, options [mss 1460,sackOK,TS val 1002196182 ecr 0,nop,wscale 7], length 0
4 packets captured
4 packets received by filter
0 packets dropped by kernel

.. same for port 80. The DSL and LAN lights remain pertty solid, the DoS is out and the ACT blinks slowly.

Please Log in or Create an account to join the conversation.

adrianh54
User

28 Nov 2017 07:15 #4 by adrianh54

Replied by adrianh54 on topic Re: Unable to connect to Vigor 130

The lights sound correct.

Reading around the net the only thing I can see was this in answer to a similar query :

Clear the ARP Cache on the computer.

If there were another host on the network which had the same IP address as the router's, the computer may resolve the IP address incorrectly due to the ARP Cache. To clear the ARP Cache and refresh the ARP table on your computer, run Command Prompt (as administrator) and enter the command “arp -d”.

Does the V130 connect to the internet and work as a modem ?

The V130 I use has always been a simple plug and play , I run an Asus RT-AC3200 and that combination allows me to access the V130 in a browser without the need for any cable shuffling.

Please Log in or Create an account to join the conversation.

cezmunsta
Topic Author
User

28 Nov 2017 07:39 #5 by cezmunsta

Replied by cezmunsta on topic Re: Unable to connect to Vigor 130

The ARP cache shouldn't be the issue, as arping gets a response and also that subnet is otherwise not in use.

So far as I can tell, it is not connecting to the ADSL line. My router fails to establish a PPoE connection, so does my laptop. Unfortunately, as I haven't anything else to try with I can't confirm if either of those normally work, but being unable to access the modem itself points at the Vigor failing.

Please Log in or Create an account to join the conversation.

adrianh54
User

28 Nov 2017 10:48 #6 by adrianh54

Replied by adrianh54 on topic Re: Unable to connect to Vigor 130

If the DSL light is up and solid then that would suggest you are connected.

Lights on my unit are : ACT pulses slowly , LAN flickers with traffic , DoS is not used on the is model , DSL solid when connected .

Either the ISP connection is not complete , or the Vigor is faulty , or the only other daft thing ( it has happened to me) is the RJ45 lead .

Crazy I know , I have a brand new Cat6 lead that will work on 3 x PC's to my router but not on my laptop .

Can you borrow a modem to test the line ? I always keep a spare BT unit for testing and emergency.

Please Log in or Create an account to join the conversation.