DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Unable to get LAN -> WAN internet on Vigor2762
- nathan_3565
- Topic Author
- Offline
- New Member
Less
More
- Posts: 2
- Thank you received: 0
24 Nov 2020 23:12 #97795
by nathan_3565
Unable to get LAN -> WAN internet on Vigor2762 was created by nathan_3565
Hi,
I really feel I must be missing something obvious, but I am pulling my hair out.
I have a Vigor2762 running firmware 3.9.4_BT. I have WAN 2 setup as static internet IP internet connection for a BT ethernet circuit. WAN 1/WAN 3 are disabled. I can see the WAN 2 connection is online. Ping and traceroute tests to internet locations from the diagnostics in the web interface work fine.
On the LAN side of things I have the default of router ip 192.168.1.1 with DHCP enabled. My lan devices obtain an address via DHCP successfully and I can see them showing as registered against the router.
The lan devices can ping and traceroute to the router itself (192.168.1.1), however none of the lan devices can ping, dns lookup or traceroute any external internet addresses. The traceroute stops at the first hop of 192.168.1.1 although I know the IP address being traced would otherwise show the full hops.
So it seems like perhaps some firewall setting is blocking all outbound traffic from LAN to WAN. I've run the firewall diagnostics and this doesn't appear to show anything. I have also restored to factory default several times and with the standard "factory rules" I can't get any connection from LAN to WAN.
The routing table looks correct:-
Key Destination Gateway Interface
* 0.0.0.0/ 0.0.0.0 via x.x.x.142 WAN2
C x.x.x.140/ 255.255.255.252 directly connected WAN2
C~ 192.168.1.0/ 255.255.255.0 directly connected LAN1
(have replaced IP address with x).
I'd like to think I was doing some silly, but I can't work it out.
Any ideas very gratefully appreciated. Thank you in advance. Nathan
I really feel I must be missing something obvious, but I am pulling my hair out.
I have a Vigor2762 running firmware 3.9.4_BT. I have WAN 2 setup as static internet IP internet connection for a BT ethernet circuit. WAN 1/WAN 3 are disabled. I can see the WAN 2 connection is online. Ping and traceroute tests to internet locations from the diagnostics in the web interface work fine.
On the LAN side of things I have the default of router ip 192.168.1.1 with DHCP enabled. My lan devices obtain an address via DHCP successfully and I can see them showing as registered against the router.
The lan devices can ping and traceroute to the router itself (192.168.1.1), however none of the lan devices can ping, dns lookup or traceroute any external internet addresses. The traceroute stops at the first hop of 192.168.1.1 although I know the IP address being traced would otherwise show the full hops.
So it seems like perhaps some firewall setting is blocking all outbound traffic from LAN to WAN. I've run the firewall diagnostics and this doesn't appear to show anything. I have also restored to factory default several times and with the standard "factory rules" I can't get any connection from LAN to WAN.
The routing table looks correct:-
Key Destination Gateway Interface
* 0.0.0.0/ 0.0.0.0 via x.x.x.142 WAN2
C x.x.x.140/ 255.255.255.252 directly connected WAN2
C~ 192.168.1.0/ 255.255.255.0 directly connected LAN1
(have replaced IP address with x).
I'd like to think I was doing some silly, but I can't work it out.
Any ideas very gratefully appreciated. Thank you in advance. Nathan
Please Log in or Create an account to join the conversation.
- hornbyp
- Offline
- Big Contributor
Less
More
- Posts: 1323
- Thank you received: 0
25 Nov 2020 00:14 #97796
by hornbyp
That looks slightly different to my 2860 (using its built-in VDSL modem)
or my 2830 (using WAN 2 to Zyxel modem)
There seems to be an entry for the ISP's Default Gateway missing. You also seem (from that .252 subnet mask), to have a pair of IP addresses available, which is something I've not configured on a Vigor. Have you manually entered these parameters into "WAN >> Internet", or has BT returned them via DHCP?
Does "Diagnostics >> Route Policy Diagnosis" help you at all?
Replied by hornbyp on topic Re: Unable to get LAN -> WAN internet on Vigor2762
nathan_3565 wrote:
The routing table looks correct:-
Key Destination Gateway Interface
* 0.0.0.0/ 0.0.0.0 via x.x.x.142 WAN2
C x.x.x.140/ 255.255.255.252 directly connected WAN2
C~ 192.168.1.0/ 255.255.255.0 directly connected LAN1
That looks slightly different to my 2860 (using its built-in VDSL modem)
Code:
> ip route status
Codes: C - connected, S - static, R - RIP, * - default, ~ - private, B - BGP
* 0.0.0.0/ 0.0.0.0 via 51.148.72.22, WAN1
* 51.148.72.22/ 255.255.255.255 via 51.148.72.22, WAN1 (Zen D.G.)
S w2.x9.y8.z52/ 255.255.255.255 via w2.x9.y8.z52, WAN1 (Actual IP address)
C~ 192.168.100.0/ 255.255.255.0 is directly connected, LAN1
//snipped//
or my 2830 (using WAN 2 to Zyxel modem)
Code:
> ip route status
Codes: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 51.148.72.24, WAN2
* 51.148.72.24/ 255.255.255.255 via 51.148.72.24, WAN2 (Zen D.G.)
S w2.x9.y6.z48/ 255.255.255.255 via w2.x9.y6.z48, WAN2 (Actual IP address)
C~ 192.168.200.0/ 255.255.255.0 is directly connected, LAN1
//snipped//
There seems to be an entry for the ISP's Default Gateway missing. You also seem (from that .252 subnet mask), to have a pair of IP addresses available, which is something I've not configured on a Vigor. Have you manually entered these parameters into "WAN >> Internet", or has BT returned them via DHCP?
Does "Diagnostics >> Route Policy Diagnosis" help you at all?
Please Log in or Create an account to join the conversation.
- nathan_3565
- Topic Author
- Offline
- New Member
Less
More
- Posts: 2
- Thank you received: 0
25 Nov 2020 08:57 #97799
by nathan_3565
Replied by nathan_3565 on topic Re: Unable to get LAN -> WAN internet on Vigor2762
hornbyp - you are a hero thank you for your prompt reply!! all working now and i've been kicking myself.
Indeed I have changed my WAN subnet to include just my single fixed IP - before I had it as 255.255.255.252 so as to include my fixed IP and also the gateway which was the mistake. Changing this to 255.255.255.255 has resolved the issue.
Thanks again.
Indeed I have changed my WAN subnet to include just my single fixed IP - before I had it as 255.255.255.252 so as to include my fixed IP and also the gateway which was the mistake. Changing this to 255.255.255.255 has resolved the issue.
Thanks again.
Please Log in or Create an account to join the conversation.
Moderators: Chris, Sami
Copyright © 2024 DrayTek