"Recent posts
#1
26.1, 26,4 Series / Re: error message after update...
Last post by allddd - Today at 10:13:38 PMi guess dhcp was just kind of slow?
warning: https://github.com/opnsense/core/blob/3acfb5f2a7d58bdd21f7d5f23e285235853c04d4/src/etc/inc/system.inc#L674-L688
error: https://github.com/opnsense/core/blob/3acfb5f2a7d58bdd21f7d5f23e285235853c04d4/src/etc/inc/system.inc#L703-L723
you later got an ip, /usr/local/etc/rc.newwanip ran and configured everything
warning: https://github.com/opnsense/core/blob/3acfb5f2a7d58bdd21f7d5f23e285235853c04d4/src/etc/inc/system.inc#L674-L688
error: https://github.com/opnsense/core/blob/3acfb5f2a7d58bdd21f7d5f23e285235853c04d4/src/etc/inc/system.inc#L703-L723
you later got an ip, /usr/local/etc/rc.newwanip ran and configured everything
#2
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by odites999 - Today at 08:15:46 PMThe last post was not correct. The problem continues. I'll try to disable IPv6 globally to see if that helps.
#3
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by odites999 - Today at 07:55:50 PMI'm going to add some information. I just noticed that the problem occurs when the laptop is connected via Ethernet cable. When it's connected via Wi-Fi, it works perfectly. In this case, since there are more components involved (Ethernet adapter, cable, access point), I'll have to investigate further.
#4
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by odites999 - Today at 07:26:30 PMI just restored a backup of version 26.1.6 (without _2) and everything is back to normal. Thanks to everyone for your help. If the same thing happens again when I update to a newer version, we'll revisit the issue.
#5
26.1, 26,4 Series / Re: error message after update...
Last post by ayanami_rei - Today at 06:26:55 PMDHCP, and later in the log are these:
-notice: /usr/local/etc/rc.newwanip: ROUTING: setting inet default route to 192.168.178.1
-notice: /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan
as far as i see now everything is working, so i dont understand the error and warning message.
greetings
-notice: /usr/local/etc/rc.newwanip: ROUTING: setting inet default route to 192.168.178.1
-notice: /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan
as far as i see now everything is working, so i dont understand the error and warning message.
greetings
#6
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by odites999 - Today at 06:19:05 PMAfter letting it rest for a while, I tried again this afternoon, and it wasn't responding to the DNS requests I was sending from my client. I restarted Opnsense and tried again, and this time it responded to requests sent to Opnsense's IPv6 LAN address but not to the IPv4 address. Upon restarting, I noticed that I had enabled the option to use the ISP's DNS servers (it wasn't active before the update). I disabled it and restarted. I switched the initial client (Linux) to Windows, and on Windows, it still displays the "performing tls..." message, but it doesn't freeze; it loads the page in just over a second.
My ISP (Movistar) doesn't have CG-NAT, as far as I know. Regarding IPv6 issues, although it's a beta version, I haven't had any problems for over a year.
My ISP (Movistar) doesn't have CG-NAT, as far as I know. Regarding IPv6 issues, although it's a beta version, I haven't had any problems for over a year.
#7
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by odites999 - Today at 06:16:17 PMQuote from: meyergru on Today at 02:48:05 PMThe provider test is crap, for me, it shows "OPALTELECOM-AS TalkTalk Communications Limited, GB", while I am in Germany.
If you still use the parameter in Firefox, the test should probably fail, because that setting essentially disables IPv6.
There were several changes in 26.1.6 for IPv6. If you only did an 26.1.6 -> 26.1.6_2 upgrade, everything should work.
What do you mean by "the DNS server is the upstream router"? Do you use a router-behind-router setup, do you mean the ISP router or your OpnSense? If so, its IPv4 or IPv6 address? Please be more specific.
I mean Opnsense
#8
26.1, 26,4 Series / Re: error message after update...
Last post by Patrick M. Hausen - Today at 06:14:28 PMHow is your WAN configured?
#9
26.1, 26,4 Series / Re: 26.1.6_2 Multiple Pugins S...
Last post by franco - Today at 06:09:00 PMWhat happened on reinstall.. you didn't post the log
> pkg-2.5.1 repository mismatch: FreeBSD
> pkg-2.5.1 version mismatch, expected 2.3.1_1
Still the same problem exactly as I mentioned.
The command line works as well:
# opnsense-revert pkg
Or maybe it's trashing on itself while trying to downgrade. In any case a real world log snippet of the operation would help.
Cheers,
Franco
> pkg-2.5.1 repository mismatch: FreeBSD
> pkg-2.5.1 version mismatch, expected 2.3.1_1
Still the same problem exactly as I mentioned.
The command line works as well:
# opnsense-revert pkg
Or maybe it's trashing on itself while trying to downgrade. In any case a real world log snippet of the operation would help.
Cheers,
Franco
#10
26.1, 26,4 Series / Re: Constant delay in TLS hand...
Last post by meyergru - Today at 06:03:38 PMCG-NAT does not handle IPv6, which is the problem at hand if it can be fixed by using IPv4 only or by instructing the browser to disregard IPv6 in the first place.
Movistar in Spain is known to have issues with IPv6, there are lots of reports on this (also from this year, BTW).
Movistar in Spain is known to have issues with IPv6, there are lots of reports on this (also from this year, BTW).
