Skip to content
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

Merovingian: allow binds to given ip/interface #2407

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Merovingian: allow binds to given ip/interface #2407

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
enhancement New feature or request Server Tools wontfix This will not be worked on

Comments

@monetdb-team
Copy link

Date: 2005-05-29 04:21:33 +0200
From: @grobian
To: Merovingian devs <>
Version: -- development
CC: alexo15, ashishk, @hannesmuehleisen, @PedroTadim, shady.shen.sh

Last updated: 2019-07-29 15:05:13 +0200

Comment 13421

Date: 2005-05-29 16:21:33 +0200
From: @grobian

It would be nice if it were possible to let Mapi, SQL
server and XQuery server bind to another address than
127.0.0.1. In many cases 127.0.0.1 is too restrictive
to be of any use, and the other extreme (0.0.0.0) far
too wide. It would be nice if these connections could
be bound to an interface or ipaddress.

Comment 13422

Date: 2006-07-23 11:16:04 +0200
From: @mlkersten

Logged In: YES
user_id=490798

Is this feature request still relevant?

Comment 13423

Date: 2006-07-23 16:15:33 +0200
From: @grobian

Logged In: YES
user_id=963970

yes, because we only do local or any. We should have a
config option that defines to with interface or IP to bind.

Comment 13424

Date: 2007-11-10 17:40:47 +0100
From: @grobian

Logged In: YES
user_id=963970
Originator: YES

In fact this is still an issue. Merovingian just suffers from the same problem, either all or just local.

Comment 13425

Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <>

This bug was previously known as tracker item 1210805 at http://sourceforge.net/support/tracker.php?aid=1210805

Comment 13987

Date: 2010-05-04 13:05:17 +0200
From: @grobian

Since M5 is wrapped by Merovingian, this really only is an issue for Merovingian.

Comment 17771

Date: 2012-10-09 14:03:35 +0200
From: @grobian

*** Bug #3156 has been marked as a duplicate of this bug. ***

Comment 17776

Date: 2012-10-09 17:39:25 +0200
From: Ashish Kumar Singh <>

is there any way as of now to make MonetDB listen on localhost only on linux platforms ? from description of this ticket I am guessing there might be a way??

Comment 17777

Date: 2012-10-09 17:42:28 +0200
From: @grobian

No, monetdbd can only bind to all interfaces. Unless you hack its sources (should be relatively easy, see connections.c). It needs code/options to define how to listen on what.

From your bug description, I think perhaps a simpler route, which switches on an ip/hostname (and thus allows only binding to 1 IP or all via 0.0.0.0) would already provide a start.

Comment 17778

Date: 2012-10-09 17:45:40 +0200
From: Ashish Kumar Singh <>

Thanks for reply , I will have a look.

But it would be nice to have it configurable OTB by monetdb, what do you think?

Regards,
Ashish

Comment 17779

Date: 2012-10-09 18:27:01 +0200
From: @grobian

it would be a monetdbd property, and a nice to have, indeed

Comment 21753

Date: 2016-01-28 09:44:31 +0100
From: @hannesmuehleisen

Indeed this is still an issue. Monetdbd by defaults listens on all interfaces. The default should be that it only listens on localhost, with an option to listen to another or all interfaces. Given the well-known default admin user/pass combination, this is a potentially security risk and should be avoided.

Comment 21755

Date: 2016-01-28 12:36:11 +0100
From: MonetDB Mercurial Repository <>

Changeset 0299a8888992 made by Hannes Muehleisen hannes@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0299a8888992

Changeset description:

monetdbd binds to localhost by default, new settable property listenaddr for dbfarm
Bug #2407

Comment 22159

Date: 2016-05-23 10:57:29 +0200
From: @sjoerdmullender

Feature has been implemented in the Jun2016 branch.

Comment 26054

Date: 2018-01-02 06:39:51 +0100
From: shady.shen.sh

In windows environment, server is not started with monetdbd and thus this fix is not valid. listenaddr parameter doesn't take effect and the server always listen to 127.0.0.1, which doesn't work in most cases.

Please help fix the issue for windows environment.

Thanks and Best Regards
Shady

Comment 26656

Date: 2018-10-25 18:31:09 +0200
From: Alex Ossipov <>

This is also an issue on Linux configured with ipv6 only.
Per documentation:

listenaddr

This property specifies an address that is allowed to connect to the server. The user can specify one IP(v6) address, or use the 0.0.0.0 notation to allow connections from everywhere. Defaults to localhost (127.0.0.1).

Attempt to set to ipv6 fails with address not recognized.

Comment 27191

Date: 2019-07-29 15:05:13 +0200
From: @PedroTadim

In default branch is now possible to bind to IPv6 addresses. However binding to a specified interface is not possible yet.

@monetdb-team monetdb-team added enhancement New feature or request Server Tools labels Nov 30, 2020
@sjoerdmullender sjoerdmullender added this to the NEXTRELEASE milestone Aug 15, 2022
@sjoerdmullender sjoerdmullender added the wontfix This will not be worked on label Aug 15, 2022
@sjoerdmullender sjoerdmullender removed this from the NEXTRELEASE milestone Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Server Tools wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants