search for: listen_addresses

Hello all, I encountered a problem when trying to setup a remote portforward using OpenSSH 3.5p1. If the port that I was trying to listen to on the remote side was already in use, a message 'cannot bind to port: 5000' was written to the syslog, but the connection still persisted. I had no way on the client side to know that the listening wasn't taking place. that is, the

FINALLY, it's here. You can now tell SSH which address to bind to for every single port forwarding option! This patch allows you to pass the following as ssh command line options: ssh -L 192.168.1.55:1234:localhost:80 -R ::11:22:aa:bb/80/localhost/80 etc. Or as normal config file options: LocalForward ::11:22:33/1234 localhost/80 RemoteForward 1.2.3.4:80 localhost:80 It will also

...refused Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432? THIS IS MY /VAR/LIB/PGSQL/DATA/POSTGRESQL.CONF # CONNECTIONS AND AUTHENTICATION #--------------------------------------------------------------------------- # - Connection Settings - #listen_addresses = 'localhost' # what IP address(es) to listen on; # comma-separated list of addresses; # defaults to 'localhost', '*' = all port = 5432 max_connections = 100 # note: increasing max_connections costs ~400 bytes of shared memory per # connection slot, plus lock space (see m...

Hi, Just a usecase that I'm sure has been covered before but just in case its not an openssh solution would be very helpful. I was trying to install software on a server that was firewalled so no outbound http connections would work. I was also tunnelling via another server. Outbound ssh connections also were a convenient option. What would have been nice would be a remote version of

Hi folks. postgresql fresh install, roles, users, databases, all done. I can log in after I SSH to the box. I entered my user (myself) in pg_hba.conf: host all rich 192.168.1.4 255.255.255.255 md5 When I nmap the CentOS box, I can?t see that port open. I?ve turned off SELinux, so I?m not sure why I can?t see the open port 5432. What am I missing? It has to be something

v3: - Various changes to dhclient/dhcpcd as discussed on the mailing list.

Hi all, I'm very new in this list, as looking for codes to plug up the lack of functionality of "Protocol 2 Remote Forwardig". Fortunately, I could find it in MARC's archive. Mr. Jarno Huuskonen posted the codes in Sept, last year, and I tried applying it to my FreeBSD box environment. I couldn't apply an original patch, of course, for incompatibility of virsion. The

The patch below implements a couple of features which are useful in an environment where users do not have a regular shell login. It allows you to selectively disable certain features on a system-wide level for users with a certain shell; it also allows you to control and audit TCP forwarding in more detail. Our system is an email server with a menu for the login shell; we selectively allow port

v2: - Make virbr0 configurable. - Fix the tests.

Hi ! Here's a patch to add remote port forwarding support (protocol 2) for openssh. I have tried to test that it works like it should but a more thorough testing is needed. This patch adds both client/server support. The patch should be applied to openssh-2.1.1p4 source tree. Also included is a PortForwarding sshd_config option, new ./configure option --disable-forwarding that should make it

I've attached a patch to OpenSSH 3.0.2p1 that will allow the client side of local port forwarding to be bound to a single address. For my purposes, binding to 127.0.0.1 or (via GatewayPorts) all addresses would not work. I overloaded the "-b local_host" option so that it's address will be used when "-L port:remote_host:remote_port" is also specified. Today is the first

...5.5 - Postgresql 8.4 Installed - startet try to createuser -d- -a -p username get message could not connect to server: Connection refused Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.0"? postrgesql.conf has line listen_addresses = '192.168.0.2' Why sockets (in /tmp are s.PGSQL.5431 ) What goes wrong? I have an other installation on other server with same conf. Files. There works all as I expect (no socket). Any hints welcome Thx Timothy

...etails: http://www.ruby-lang.org/bugreport.html /etc/puppet/utilities: line 735: 12081 Aborted /opt/puppet/bin/puppet apply --no-report --modulepath /opt/puppet/share/puppet/modules -v --exec "class { pe_postgresql: version => ''9.2'', config_hash => { listen_addresses => ''localhost'', ip_mask_allow_all_users => ''0.0.0.0/0'' } }" However, the puppet master started automatically and it is running. But I get errors when verifying my license. I executed "puppet license" and got the following error: /opt/pup...

I am trying to get VSFTPD to listen on a particular IP. The ifconfig output for the host is: eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:aaa.bbb.ccc.26 Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0 inet6 addr: xxxx::xxx:xxx:xxxx:xxxx/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:223374 errors:0 dropped:0

http://bugzilla.mindrot.org/show_bug.cgi?id=1037 Summary: Man page for -L and -R should mention -g Product: Portable OpenSSH Version: 4.0p1 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: Documentation AssignedTo: bitbucket at mindrot.org ReportedBy:

Hi, sorry if it is the wrong approuch to suggest improvments to OpenSSH, but here comes my suggestion: I recently stumbled upon the scponly shell which in it's chroot:ed form is an ideal solution when you want to share some files with people you trust more or less. The problem is, if you use the scponlyc as shell, port forwarding is still allowed. This can of course be dissallowed in

https://bugzilla.mindrot.org/show_bug.cgi?id=2189 Bug ID: 2189 Summary: Client fails to consider hostname when matching rfwd channel opens Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Severity: minor Priority: P5 Component: ssh

I have discovered that the default init script distributed with pgsql v8.1 sets the listening port to 5432 but does not enable tcp/ip connections. One must add the -i switch to the invocation line in the script. I am not sure if this is an oversight or whether there is another way to tell postmaster to start with tcp/ip listening enabled that I am unaware of. However, I thought that this

Hi there and hello to everybody, I am all new to centos but I have good experience working with ubuntu and suse. We are moving a an elderly SuSe box to a virtual machine running centos 7. Now I experience the following problem. I can only access postgres using localhost as host. If I use the IP address (even 127.0.0.1). I found a similar problem when accessing the

I''m working on configuring a master in a lab environment, using Puppet Open Source. My master is running RHEL 6. I want to use modules to manage the master itself as much as possible, so I can use puppet to bootstrap itself as I go forward and move into production. Using puppetlabs/puppetdb to configure puppetdb, I''ve overcome most of my issues but I have two questions. 1)