Hot answers tagged

42

Problem solved: $ ssh -L 7000:127.0.0.1:7000 user@host -N -v -v ...apparently, 'localhost' was not liked by the remote host. Yet, remote /etc/hosts contains: ::1 localhost localhost. 127.0.0.1 localhost localhost. while the local network interface is lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33184 ...


21

Although OP's problem has already been solved, I decided to share the solution for my problem, because I got the same error message from ssh and I didn't find any solution on other sites. In my case I had to connect to the service which listens only on IPv6. I tried: ssh -f root@192.168.0.18 -L 51005:127.0.0.1:51005 -N ssh -f root@192.168.0.18 -L 51005:...


9

I would first try this. $ ssh -L 7000:127.0.0.1:7000 user@host -N -v -v You can use "-v" up to 3 times to increase verbosity. I think this error message can arise if a firewall blocks port 7000, but you had already ruled that out. (If later readers haven't ruled that out, look at the output of netstat --numeric-ports.) I think I might have seen this ...


8

Well vSphere 4.x only supports FreeBSD 6.x-8.x while vSphere 5.x also supports Mac OSX 10.6-10.7 - so one of those, anything else isn't supported.


4

From practical experience I can tell you all of the Big 3 BSDs (FreeBSD, OpenBSD, NetBSD) will run in VMWare, but as Chopper3 said, only FreeBSD and Apple's OS X (Mach/BSD Hybrid) are officially supported by VMWare. If this is going to be a production system and support from the VMWare folks is important to you I would stick to a stripped-down version ...


4

http://www.fwbuilder.org/ Firewall Builder supports a wide range of firewall platforms, including Cisco ASA & PIX, Linux iptables, BSD pf and many more. You’re not confined to one platform—or locked into a single vendor. See the intro: http://www.fwbuilder.org/4.0/docs/firewall_builder_intro.html


4

You are using KVM -- Please be aware that virtio support may still (AFAIK) be pretty patchy under NetBSD. I think this explains the performance difference between Linux and FreeBSD (both have virtio support) and NetBSD.


4

NetBSD does not support the pw command in its default install. You can: Compile the pw command for NetBSD and install it on your systems Write a utility that performs the equivalent functionality Update the password by manipulating the shadow file directly Note that depending on your script you should probably be using -H (and supplying an appropriately-...


3

You could do it in three different ways as i see it - There are most likely many other ways to do it as well! The best method would be to attach a audit tool to the kernels sysexec calls so it would be untraceable by the user etc. The two other ways would simply be to modify the shell environment to log it. Instead of me (grabbing the code/answers from ...


3

I encountered this error when I was forwarding ports with a full domain name instead of localhost: ssh -L 5900:host.name.com:5900 x11vnc The port was being opened only for localhost, so to accept connections with a fully qualified name, I had to add a binding port description: ssh -L *:5900:host.name.com:5900 x11vnc which would allow connections from ...


3

I encountered this same error while trying to connect to mysql on another server via an ssh tunnel. I found that the bind-address parameter in /etc/my.cnf on the target server was bound to my external ip (dual NIC server) rather than internal, which I had no use for. When I set bind-address=127.0.0.1, I could successfully use my ssh tunnel as follows: ssh ...


3

"...apparently, 'localhost' was not liked by the remote host. Yet, remote /etc/hosts contains:" Except you were running ssh on the client, so 'localhost' was not liked by your client. The remote /etc/hosts file is for the remote connecting out not incoming connections.


2

Why not run benchmarks on your particular server hardware and figure out what is best for your combination of hardware and file usage? One tip: RAID5 will take forever to rebuild an array on modern size hard disks (2TB or higher), and during that time the performance of the RAID array will be compromised. Modern setups use stripes of mirrored hard disks: ...


2

Timestamp format is indeed hardcoded in make_timestamp() function: http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/syslogd/syslogd.c?annotate=HEAD


2

Here's a script that you can use to capture the userid and other info to put in a logfile before kicking off the ssh. I tested it with several very complicated multiline ssh commands. #!/bin/bash # Title......: ssh (wrapper) # Description: this script replaces the ssh binary and runs the real binary after logging the connection attempt # variables #-------...


2

For me adding leading ":" works so command in your case would look like this: ssh -L :7000:localhost:7000 user@host -N -v


2

You can use the file(1) command on the CD-ROM device. For example, I have a NetBSD 7 iso in my CD-ROM drive: $ sudo file -s /dev/cd0d /dev/cd0d: # ISO 9660 CD-ROM filesystem data 'NETBSD_70_BETA' (bootable) The Volume ID here is 'NETBSD_70_BETA' You can also install isoinfo from pkgsrc (sysutils/cdrtools) and sed/grep the data you need: $ sudo isoinfo -...


2

If you didn't tweak MTU, you may have post-fragmentation issues (fragmentation occuring after encryption) that is well explained in this documentation: http://www.cisco.com/c/en/us/td/docs/interfaces_modules/services_modules/vspa/configuration/guide/ivmsw_book/ivmvpnb.html#wp2047965 You should try to reduce MTU inside the tunnel by 82 bytes (GRE + IPSec ...


1

I'm assuming this machine has an additional 'admin' network port in addition to the ports used for routing traffic? npf.conf(5) mentions: procedure "log" { # Note: npf_ext_log kernel module should be loaded, if not built-in. # Also, the interface created, e.g.: ifconfig npflog0 create log: npflog0 } which implies you should be ...


1

Use usermod with -p switch. It's included with base system, no need to build pw.


1

Alternative interpretation is, in my case, your typing it wrong. user@host ~ $ ssh -vvvNL 4444:127.0.0.0.1:4444 ... channel 2: open failed: connect failed: Name or service not known What happens here is the IP address has one too many zeroes, thus not being a valid address. So ssh treats it as a domain name instead which it can't resolve. Oops! PS: I ...


1

For me, I was trying ssh -L <port>:<remote server IP>:<port> <login>@<remote server IP> when I should have been doing ssh -L <port>:127.0.0.1:<port> <login>@<remote server IP>. I hope this helps someone!


1

I received the same error message: channel 3: open failed: connect failed: Connection refused And the cause was human error - me trying to access a different port on the remote host than the one I specified. Just thought I'll share that, although this is probably not the reason why most of you are experiencing this error.


1

??? channel 2: open failed: connect failed: Connection refused At user@host there's nothing listening port 7000, that's simple and that's all.


1

Such conversion is not always possible, since different packet filters have different logic and packet processing scheme. For example, there is no simple and straight way to convert iptables rules (with all those tables and chains) to ipfw or pf rules. It's better to just write new ruleset for needed firewall type with knowing what you need to get in the end....


1

Keep in mind that if you're dealing with big throughputs, you might be CPU-constrained with a software solution. By saying you want to use "ZFS" i assume you want to use a software solution using ZFS as the filesystem of choice for the raid volume (with all the perks that it brings to the table). If you are CPU-constrained, leave the raid management to ...


1

ZFS can be raid-z{1,2,3}, stripe, mirror, and even RAID-10. Meanwhile RAID-5 is always just RAID-5. Hence you're comparing juice to apple. RAID-5 is efficient capacity user, but very laggy data writer. RAID-10 is often preferable instead.


1

You didn't mention if the hardware raid controller has a battery backup module on it or not. If so, the controller will be able to commit writes as soon as they're in RAM on the controller... if not, it will have to wait until they are actually committed to disk. Depending on your workload, this can make a major difference in performance of the raid ...


Only top voted, non community-wiki answers of a minimum length are eligible