New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.5.9 Regression: MON$Attachments.MON$Remote_Address now includes the remote TCP port number [CORE6151] #6400
Comments
Commented by: Sean Leyne (seanleyne) CORE2493 is about the firebird.log, IMO that should have nothing to do with the value stored in the mon$attachments.mon$remote_address. The TCP port used by the remote system should be in a new/separate field |
Modified by: Sean Leyne (seanleyne)description: Hi! Before 2.5.9 mon$attachments.mon$remote_address returned just IP, e.g.: "192.168.0.1". It made broke some of our code. (We are comparing mon$remote_address to outer source IP without port) It this intentional, a side effect or a bug? Changelog doesn't mentions this change. Thank you! => Before 2.5.9 mon$attachments.mon$remote_address returned just IP, e.g.: "192.168.0.1". It made broke some of our code. (We are comparing mon$remote_address to outer source IP without port) It this intentional, a side effect or a bug? Changelog doesn't mentions this change. summary: Firebird 2.5.9 mon$attachments.mon$remote_address => v2.5.9 Regression: MON$Attachments.MON$Remote_Address now includes the remote TCP port number |
Commented by: @hvlad a) Remote port is a part of remote address, passed from network server to the engine as part of remote address and presented to the end user as part of remote address |
FB4.0 returns IPv6 adress. + port number in MON$REMOTE_ADDRESS. Is there a way to get IPv4 address + port? |
I believe that depends on whether the connection is established using IPv6 or IPv4. |
@mrotteveel , yep. Using IPv4 in connection string instead of computername reported IPv4. Thank you. |
You can close this issue. Thank you. |
You can also explicitly enforce IPV4 by using the inet4 connection string: inet4://host:port/database |
Submitted by: Attila Molnár (e_pluribus_unum)
Before 2.5.9 mon$attachments.mon$remote_address returned just IP, e.g.: "192.168.0.1".
With 2.5.9 it returns IP + port number, e.g.: "192.168.0.1/55970".
It made broke some of our code. (We are comparing mon$remote_address to outer source IP without port)
It this intentional, a side effect or a bug? Changelog doesn't mentions this change.
The text was updated successfully, but these errors were encountered: