Issue Details (XML | Word | Printable)

Key: CORE-6151
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Attila Molnár
Votes: 0
Watchers: 3
Operations

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

v2.5.9 Regression: MON$Attachments.MON$Remote_Address now includes the remote TCP port number

Created: 04/Oct/19 06:09 AM   Updated: 13/Oct/19 12:06 PM
Component/s: Engine
Affects Version/s: 2.5.9
Fix Version/s: None

QA Status: No test


 Description  « Hide
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.


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Vlad Khorsun added a comment - 04/Oct/19 03:51 PM

Sean Leyne added a comment - 04/Oct/19 07:39 PM
CORE-2493 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

Vlad Khorsun added a comment - 13/Oct/19 12:06 PM
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
b) Remote port is specific for TCP protocol and have no sense for other protocols
c) To create new field in system table there must be much more serious reason