Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware)
-
Are you sure it´s just a minute, looking on the column time it shows 30 minutes to me (it took about 30 minutes to issue the RENEW during capture, as I was waiting for it to stop capturing).
It´s a 3600s lease.
-
I have been running Wireshark between my firewall and cable modem and have noticed some differences. For example on yours, you go through several solicit/advertise frames, when the normal process is solicit/advertise/request/reply. Then you get one request/reply and then a bunch of renews. On my system, I just get a single solicit/advertise/request/reply sequence and there has been nothing else for 20 minutes so far. Also, both your preferred and valid lifetimes are 3600 seconds, whereas mine are 148853 and 580853. So, I would expect a renewal attempt at just over 43 hours, not 1 as you have. I'll leave my test config up for the rest of the day, but I doubt I'll see anything, given that 43 hour wait for the next request.
Incidentally, the way I'm monitoring this is through a "data tap" or "network tap" I made with a 5 port managed switch. I placed it between my pfSense firewall and cable modem and use a notebook computer, running Wireshark to capture the traffic.
Here's the instructions I posted for making one:
Creating a "data tap" -
@Katan said in Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware):
It´s a 3600s lease.
Take a look at the times in Wireshark. Everything there happened in a half hour.
-
@JKnott
Unfortunatly, I only have a 24 port procurve switch that is on the lan side. -
Still, Packet Capture showed what was happening on the WAN side and it doesn't look right to me. I just glanced at the computer where I'm running Wireshark and still haven't seen anything happening in over an hour.
Also, those 5 port managed switches are cheap. I keep mine in my computer bag, so that it will be handy when I need it. It's just part of my toolkit, along with my Ethernet cable tester and punch tools.
-
One other thing I've noticed. You're requesting and receiving a /64 prefix. Is that all your ISP provides? It shouldn't cause a problem though.
-
@JKnott said in Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware):
One other thing I've noticed. You're requesting and receiving a /64 prefix. Is that all your ISP provides? It shouldn't cause a problem though.
They provide a /56, but for their router, and it delegates in turn /64 prefixes.
Unfortunetly it does not have the option to run as bridge (at least with the user provided with the router).For IPv4 I have to live with a double NAT.
-
????
How are you getting a prefix for your LAN? That's normally done with DHCPv6-PD, but that's generally not provided by gateways.
However, that might explain the strange things in your packet capture. Your prefix is 2804:d57:4b04:6200::. Is your WAN address within that range?
-
-
Changed some settings at the gateway and now got this
But still lost connectivity after the lease expires...
The same on the capture, no responde to RENEW, REBIND and SOLICIT after the interface is UP. -
@Katan said in Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware):
But still lost connectivity after the lease expires...
That's because something strange is happening when those renews start. I haven't seen those before but, then again, I haven't looked. I've been leaving my notebook running Wireshark all day and having seen anything since the original DHCP sequence when I rebooted my firewall this morning. I expect I'll see something happen in the middle of the night tomorrow. As I mentioned, Packet Capture times out long before that, so I have to use my "data tap" and notebook computer to watch for that. What's the lease time for IPv4 DHCP? One hour seems short.
-
I just got something a little over a half hour ago. I see 2 renews and 2 replies, all within about 1/10 second, with both the renews and replies using my link local address.
-
I changed last night the gateway from OPT1 to WAN port (mvneta1 to mvneta2) and the dhcp client seem to be working on this port, dhcpv6 is using link-local address and is getting responses for SOLICIT and RENEW at least, without restarting the interface.
Looks like it´s something related to the OPT1 port.
now the computers no LAN side get a global IP of the provided prefix, but does not have connectivity.
-
Next you have to look at filters and routing. IIRC, only the interface you originally configure as WAN works out of the box. Beyond that, you have to configure to allow the traffic to pass.
-
-
One thing that caught my eye is that fe80::1 gateway. Is that actually what you're supposed to use? My ISP uses a regular link local address.
-
@JKnott said in Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware):
One thing that caught my eye is that fe80::1 gateway. Is that actually what you're supposed to use? My ISP uses a regular link local address.
That´s what came from DHCPv6, but I can change the HG8245Q2 link-local address.
If I run a Ping from PFSense interface to ipv6.google.com ir works, but not from LAN.
And thanks for your help so far.
-
@Katan said in Loosing IPV6 connectivity after 1 hour with HG8245Q2 (OI Firmware):
And thanks for your help so far.
I don't know what you've done so far, but sometimes it's easier to start from scratch,rather than try to find the cause of a problem, particularly if you've been trying a lot of things.
