You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
Since I changed the default gateway of my WLAN K2A hangs on every Internet access even if all other apps have no problem.
Since I changed the gateway of my subnet 192.168.1.0/24 from 192.168.1.1 to 192.168.1.3 K2A stalls on every access to Internet. As I'm using Google Drive I cannot even open it as it probably checks for changes.
I can work around it on phones by temporarily disabling WLAN and do it on Mobile Connection but for one thing it's cumbersome and on the tablet where I only have WLAN I'm out of options other then manually downloading/uploading via Google Drive App but it's very error prone.
The gateway is set by the DHCP Server with Option 3,192.168.1.3 and my laptop as well as Android itself (other apps) are working perfectly fine but it somehow rendered K2A to a non working state.
My old working network settings were:
DHCP: 192.168.1.1 (Openwrt Router)
Gateway: 192.168.1.1 (not explicitly set)
DNS: 192.168.1.36 (pihole set by DHCP Option 6,192.168.1.36)
My new broken network settings are:
DHCP: 192.168.1.1 (Openwrt Router)
Gateway: 192.168.1.3 (set by DHCP Option 3,192.168.1.3 pointing to a new WAN gateway)
DNS: 192.168.1.36 (pihole set by DHCP Option 6,192.168.1.36)
So the only change is setting different gateway through DHCP.
I have no clue why only K2A has issues with a different gateway set by DHCP. Maybe it tries to Fallback to ipv6 but I don't know if the advertised gateways work as my ISP is still ipv4 only so they are generated by the Openwrt router and for internal use only.
But it must be doing something weird as it worked with old gateway when it was not explicitly set by DHCP even with those ipv6 settings, now it stalls. The Openwrt router is now doing DHCP + DNS only as the WAN Link is through some fiber Box hence it must be advertised through DHCP otherwise I would have double Nat. But double NAT is definitely not an option especially not for port forwards to internal services like SSH, FTP, REST API. And it would also cripple the fiber speed as the openwrt router only has 1GBit ports whereas the fiberbox has 10GB.
I'm happy to share more information like logfiles etc or try out some APKs but I hope it's fixed soon as this is clearly a severe bug.
Describe what you expected to happen:
I want K2A to also use the gateway advertised by DHCP to not stall.
Thanks a lot,
Marc
What version of Keepass2Android are you using?
1.19-pre
Which version of Android are you on?
14
The text was updated successfully, but these errors were encountered:
I am currently working on updating several libraries which KP2A is using. The next release will definitely contain a new okhttp library version. However, I am currently not updating Google Drive (there is some evaluation from Google going on and they say during that I shouldn't update the code related to GDrive). So I'm not sure if that update will change something or not. Can you use Change database => Open database => System file picker > Google Drive in the meanwhile?
Checks
Describe the bug you encountered:
Since I changed the default gateway of my WLAN K2A hangs on every Internet access even if all other apps have no problem.
Since I changed the gateway of my subnet 192.168.1.0/24 from 192.168.1.1 to 192.168.1.3 K2A stalls on every access to Internet. As I'm using Google Drive I cannot even open it as it probably checks for changes.
I can work around it on phones by temporarily disabling WLAN and do it on Mobile Connection but for one thing it's cumbersome and on the tablet where I only have WLAN I'm out of options other then manually downloading/uploading via Google Drive App but it's very error prone.
The gateway is set by the DHCP Server with Option 3,192.168.1.3 and my laptop as well as Android itself (other apps) are working perfectly fine but it somehow rendered K2A to a non working state.
My old working network settings were:
DHCP: 192.168.1.1 (Openwrt Router)
Gateway: 192.168.1.1 (not explicitly set)
DNS: 192.168.1.36 (pihole set by DHCP Option 6,192.168.1.36)
My new broken network settings are:
DHCP: 192.168.1.1 (Openwrt Router)
Gateway: 192.168.1.3 (set by DHCP Option 3,192.168.1.3 pointing to a new WAN gateway)
DNS: 192.168.1.36 (pihole set by DHCP Option 6,192.168.1.36)
So the only change is setting different gateway through DHCP.
I have no clue why only K2A has issues with a different gateway set by DHCP. Maybe it tries to Fallback to ipv6 but I don't know if the advertised gateways work as my ISP is still ipv4 only so they are generated by the Openwrt router and for internal use only.
But it must be doing something weird as it worked with old gateway when it was not explicitly set by DHCP even with those ipv6 settings, now it stalls. The Openwrt router is now doing DHCP + DNS only as the WAN Link is through some fiber Box hence it must be advertised through DHCP otherwise I would have double Nat. But double NAT is definitely not an option especially not for port forwards to internal services like SSH, FTP, REST API. And it would also cripple the fiber speed as the openwrt router only has 1GBit ports whereas the fiberbox has 10GB.
I'm happy to share more information like logfiles etc or try out some APKs but I hope it's fixed soon as this is clearly a severe bug.
Describe what you expected to happen:
I want K2A to also use the gateway advertised by DHCP to not stall.
Thanks a lot,
Marc
What version of Keepass2Android are you using?
1.19-pre
Which version of Android are you on?
14
The text was updated successfully, but these errors were encountered: