IPv6 Issue

Started by walkerx, January 19, 2019, 07:08:34 PM

Previous topic - Next topic
I've recently upgraded my motherboard and at same time upgraded opnsense to 18.7.10 and have noticed that i'm unable to get ipv6 from my wan.

I've checked my settings in the wiki for sky fibre setup and the configuration is correct, so unsure of why not receiving any ipv6 settings and when test via ipv6 test site, it reports that ipv6 is not supported.

is there anything else that needs doing to get this working again

Still having issues with IPv6, it started working other day, but again it's back to IPv4 only

ISP is Sky Fibre and I'm using Vigor 130 with Opnsense 18.x

Can you, if you have not already, set debug on for dhcp6c. Restart Opnsense and and see what happens. When ipv6 fails send send me the \var\log\dhcp.log to take a look at.



OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: marjohn56 on January 23, 2019, 10:12:06 AM
Can you, if you have not already, set debug on for dhcp6c. Restart Opnsense and and see what happens. When ipv6 fails send send me the \var\log\dhcp.log to take a look at.
I'll check this tonight when get home, but will be late on, but are these settings just in the dhcpv6 section?

I only noticed issue last night when watching a movie on apple 4k tv box and it stopped streaming, but was fine through youtube and netflix, so rebooted and still no go, so thought it might be something with opnsense as have been experiencing issues where after a while i lost all connection.

This is when I noticed I had no ipv6 addressing listed under the lan interface, but the wan interface was showing up for both ipv4 and ipv6. i tried restarting the dhcpv6 service and this never resolved the problems and even reapplied the lan interface.

I'm also using the GA-J3455N-D3H motherboard

The WAN v6 address should only be a link local  fe* address, as Sky do not give out a global v6 address, so that means very little. The key is looking at the dhcp6c logs.


I've emailed skyeci ( user on the Skyuser forum ) who does much of the testing for Sky ipv6 for me and he reports no issues with 18.7.10.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

January 23, 2019, 01:44:17 PM #5 Last Edit: January 23, 2019, 01:52:58 PM by walkerx
Quote from: marjohn56 on January 23, 2019, 01:06:12 PM
The WAN v6 address should only be a link local  fe* address, as Sky do not give out a global v6 address, so that means very little. The key is looking at the dhcp6c logs.


I've emailed skyeci ( user on the Skyuser forum ) who does much of the testing for Sky ipv6 for me and he reports no issues with 18.7.10.

yeh, he sent me some info on setting on the vigor 130 to work with Sky

when i replaced the motherboard with the j3455N, I performed a fresh install of Opnsense and had to use hint.hpet.0.clock=0 to boot it, then once installed had to change the conf.local file. I restored my settings from a backup of Opnsense, reinstalled the relevant plugins (use uPnP and Unbound as have multiple xbox's configured on the system). and ensured the wan/lan ports were set to re0/re1.

me network is setup in the following way

internet <-> vigor 130 <-> OpnSense <-> Samknows <-> Switch <-> Wifi and devices

also is there a way to enable shell access from the gui interface, so can use putty or winscp to get the files across, or is telnet option always active for local lan

Yup, go to System->Settings->Administration


OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Hi,

Got home and performed ipv6 test and this stated not supported, checked the dashboard and under lan it showed my ipv4 and ipv6 address (this wasn't showing yesterday)

the dhcpv6 service was showing stopped and when re-enabled I was still unable to get ipv6

I enabled the telnet option, then went into Interfaces -> Wan and in the section DHCPv6 client configuration checked the checkbox for Enable Debug, then saved this, then clicked apply for the settings to take effect.

Next the test for ipv6 was working this was without rebooting Opnsense

you mention the following \var\log\dhcp.log but in the folder the file is \var\log\dhcpd.log

Is that the file you need or must I do a full reboot?

thanks

Yes, sorry my typo.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Sorry half a message there.. I would go for a reboot.

OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

thanks,

i rebooted it last night when got home and it kept it's ipv6 settings, will check nightly now when I get home and if the internet goes down again


Update: ipv6 has disappeared again, but all services are showing as running - unable to send you the log file as no option to attach it

You could cut and then paste using the insert code button above like this


Jan 25 13:31:56 dhcpd: Sending Reply to fe80::1028:4bee:96e2:b7c port 546
Jan 25 13:31:56 dhcpd: Wrote 13 NA, 0 TA, 0 PD leases to lease file.


OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

Quote from: nivek1612 on January 25, 2019, 02:33:21 PM
You could cut and then paste using the insert code button above like this


Jan 25 13:31:56 dhcpd: Sending Reply to fe80::1028:4bee:96e2:b7c port 546
Jan 25 13:31:56 dhcpd: Wrote 13 NA, 0 TA, 0 PD leases to lease file.


hi,

already sorted, been sorting with marjohn56 and skyeci

I've either got a faulty motherboard or the system is not compatible with Opnsense, so its going back and i'm getting a qotom instead


Good old Martina and Ned :-)

Yes the Qotom is superb - see my sig
OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)