Issue Details (XML | Word | Printable)

Key: CORE-6349
Type: Improvement Improvement
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Eric Himmer
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Firebird3 - Disable ipv6 support option when no network connection

Created: 01/Jul/20 07:18 PM   Updated: 02/Jul/20 09:53 PM
Component/s: None
Affects Version/s: 3.0.5
Fix Version/s: None

Environment: Windows 10, Delphi 10.3.3, FireDAC

QA Status: No test


 Description  « Hide
Related to CORE-5679.

Our product is designed for use by computer illiterate people using Windows devices most likely not connected to the internet. Based on the report in bug report CORE-5679, support was added for ipv6 which causes a failure to be able to connect to the local database on a localhost without an internet connection unless a user, makes changes to their Windows settings. This is not something our users are likely capable of doing, especially out in the field with no internet connection.

Can a setting be added to override the ipv6 support when there is no active internet connection? This is truly a show stopper for us. Not easy for us to back down to FB 2.5 at this late stage. I did not notice any warning in the FB3 description that FB3 requires an internet connection even for embedded-like usage unless you disable Windows Media Sense by using RegEdit and adding the DisableDHCPMediaSense key to disable it and not sure if I want our setup to disable something in Windows itself that the user or other applications might want enabled:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Dimitry Sibiryakov added a comment - 01/Jul/20 07:24 PM
This failure is not limited to IPv6, IPv4 is affected as well. If you want reliable connection to local server - use XNET.

Sean Leyne added a comment - 01/Jul/20 07:38 PM
Eric,

1- Is your product using embedded or full engine for local database access?

2- What connection string are you using to the local database? (As Dimitry outlined, you should be able to use direct/XNET connection to avoid "localhost:..." in connection string)

Eric Himmer added a comment - 01/Jul/20 07:39 PM
Seems I can trap for the error and not display it since it appears to not cause any harm as it seems the database access is OK. The errors were coming from some design time queries used in a dashboard. The dynamically created ones work fine once those errors are skipped.

So I guess, nevermind.

Eric Himmer added a comment - 01/Jul/20 07:51 PM
To answer your questions:

1 - As I understood it, there is no embedded version for FB3 like there was for FB2. Am I wrong? I use the full engine and use SuperClassic. FireDAC is set to use fbclient.dll

2 - I am using FireDAC pooled connections (except for the design time queries). I just set properties to make the connection and let FireDAC generate the proper connection string AFAIK. for the design time queries: Protocol is ipLocal and the Server is localhost which are the defaults.

Eric Himmer added a comment - 01/Jul/20 11:52 PM
I replaced the design time FDQuery components for my dashboard with my normal dynamic pooled connection queries and all is good. My only guess is that FireDAC has an issue with their FDQuery component (only difference I can see between the two). I do not get the error anymore when disconnected from the internet.

You can close the ticket.

Vlad Khorsun added a comment - 02/Jul/20 09:10 PM
To not left question unanswered :

> 1 - As I understood it, there is no embedded version for FB3 like there was for FB2. Am I wrong?

please, read carefully chapter "Remodelled Architecture" in Release Notes:
http://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html#d0e12188

Eric Himmer added a comment - 02/Jul/20 09:53 PM
Thanks. What I was referring to was that there is no longer an fbembed.dll in FB3 as there was in FB2. I will re-review the link you provided as I have a feeling I might not be connecting the way I think I wanted to be.