RV320 not routing IPV6....

[Tom416]

I read the posts that exist, however am getting very frutrated as I cannot find a solution.

I can ping the google DNS server using IPV6 from the RV320. My internal computers can ping the RV320 IP address. Mw WAN IPV6 address has a /64, so the left address on it is the same as my internal /64 addresses. However my default gateway only shows an fe80 address. Is this correct or the issue? My WAN adapters are stateless address autoconfig, My DHCP for IPV6 is disabled, under DHCP my IPV6 address is populated, also to a /64, but only for the first 64 bits is there something there. 

Where should I look to see why the RV320 won't route packets?

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

> However my default gateway only shows an fe80 address. Is this correct or the issue?

This is how it should be, so not a problem.

Can you ping the google DNS server from the internal computers?

Do you have a DNS server address configured on the internal computers?

Regards,

[Tom416]

Ok, great gateway is not needed.

No, I cannot ping the google DNS server internally, I can from the RV320 utilities.

Yes, I have a DNS server configured for internal computers.

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

Can you please provide a snapshot from the workstation (ifconfig /all). This would make it easier for us to help.

Regards,

[Tom416]

Yes, pasted below

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : 
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
Physical Address. . . . . . . . . : 00-16-41-71-AB-80
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2607:fea8:135e:8200:340c:88cd:50ad:fae4(Preferred)
Temporary IPv6 Address. . . . . . : 2607:fea8:135e:8200:9584:9d2e:46df:bf56(Preferred)
Link-local IPv6 Address . . . . . : fe80::5c2e:d9b1:f09a:9498%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.5.162(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : December 19, 2023 11:02:46 PM
Lease Expires . . . . . . . . . . : December 23, 2023 6:52:52 AM
Default Gateway . . . . . . . . . : fe80::d6c9:3cff:fe18:5710%15
192.168.5.5
DHCP Server . . . . . . . . . . . : 192.168.5.5
DHCPv6 IAID . . . . . . . . . . . : 65066334
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-05-A4-13-00-16-41-71-AB-80
DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888
8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

The IPv6 configuration on the host looks good. Could you please post the RV320 IPv6 configuration.

Regards,

[Tom416]

Yes,

IPv6 under system summary is:

WAN1 WAN2

IP Address:	2607:fea8:135e:8200:d6c9:3cff:fe18:5711/64 fe80::d6c9:3cff:fe18:5711/64	2607:fea8:135e:8200:d6c9:3cff:fe18:5712/64 fe80::d6c9:3cff:fe18:5712/64
Default Gateway:	fe80::9a52:4aff:feb0:9c7f	fe80::9a52:4aff:feb0:9c7f
LAN IPv6 Address:	2607:fea8:135e:8200:0:0:0:1	2607:fea8:135e:8200:0:0:0:2

Under, setup/Network

Prefix Table

IPV6 Address         Prefix    DHCP Mode

2607:fea8:135e::

48

DHCP Server

WAN1	Stateless Address Autoconfiguration

WAN2	Stateless Address Autoconfiguration

DHCP Setup, DHCP is disabled

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

I find it rather unusual to see both the WAN and LAN prefixes to be the same. They would normally be different. Did your service provider tell you the LAN prefix you should use? 

Regards,

[Tom416]

My provider didn't give anything, however if I log into their router, the local IP network has this: 

Link Local Gateway Address (IPv6):fe80::9a52:4aff:feb0:9c7f

Global Gateway Address (IPv6):2607:fea8:135e:8200:9a52:4aff:feb0:9c7f

Delegated prefix (IPv6):2607:fea8:135e:8200::/64

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

I understand the issue now. The RV320 is behind your service provider (SP) router. The WAN interface gets configured via SLAAC from the prefix from the SP. 

I am afraid you will not be able to get it to work with an additional router behind the one provided by the SP. It would work if you used a L2 switch behind the SP router, but it will not work with the RV320 since it has two L3 interfaces (WAN and LAN) and your SP only provides one IPv6 prefix (2607:fea8:135e:8200::/64).

Regards,

[Tom416]

Thank you so much for your help, if I take away one of my links from the RV320 to the SP router, would that get it working?

Thanks,

Tom

[Harold Ritter]

Hi @Tom416 ,

Taking one link away will not change the outcome. You still have a WAN and a LAN interface and both need an IPv6 subnet.

Can you please let us know why you need to use the RV320 behind the SP router? 

Regards,

[Tom416]

I don't trust the SP router, prefer to have something more secure, never had an issue with the IPV4 only implementation....

Thanks,

Tom

[Harold Ritter]

hi @Tom416 ,

> I don't trust the SP router, prefer to have something more secure

I see.

> never had an issue with the IPV4 only implementation....

This is because you use NAT on the IPv4 side. You might be able to get away with the implementation if NAT is supported for IPv6 as well, but I doubt it is. You need to refer to the RV320 documentation to see if it does.

Regards,