New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Depending on how you usually run Dropbear. What I normally do is to use xinetd and then run dropbear using the inet mode. For example using this file under /etc/xinet.d/dropbear
service ssh { type = UNLISTED socket_type = stream port = 22 only_from = 0.0.0.0 wait = no user = root protocol = tcp server = /usr/sbin/dropbear server_args = -i disable = no }To use dropbear on a different port, I would
dropbear12345port = 12345xinetd would then bind to both ports, and serve
dropbear -ifrom either of them.Thanks
Not different port but 2 ports please.
edit: We discussed this on the old site but there the discussion was for a change or port numbers as well.
That's exactly what I was trying to demonstrate. You ended up having multiple "sshxxxx" files inside your
xinetd.ddirectory with differentport = xxxxlines. When xinetd starts it reads all of them and binds all those ports, where all of them would invoke dropbear.I use the init daemon on my servers and use this to add extra ports to my server :P
sed -i -e 's/-p "$DROPBEAR_PORT" -W/-p "$DROPBEAR_PORT" -p 110 -W/g' /etc/init.d/dropbear
Replace 110 with the port you wish to use :P
dropbear has an option '-p' for specifying port on which it should listen. It allows for multiple '-p' options (up to 10). It looks like there is no way to specify multiple ports like -p 22,222.
In debian the configuration can be done via /etc/default/dropbear. There you can specify one port by
The additional ports you can be specified by
I don't need dropbear on two ports, but I want it on IPv4 & IPv6, and it's only working on IPv4. The changelog says IPv6 support was added in 2005, but the man page doesn't mention it.
@ efball
I have dropbear on 2 vpses . 1st one is Debian Lenny (dropbear V0.51). out of the box it supports IPv6 and works like a charm.
2nd one is Debian Squeeze.(dropbear V0.52). in this vps , everything else support ipv6 except dropbear. for supporting ipv6 , i used 6tunnel ,this program forward ipv6 traffic to ipv4. I couldn't find dropbear problem in this vps.
I'm using Debian squeeze with dropbear 0.52-5.
netstat shows dropbear on IPv4 only, no errors anywhere.
Sound like a bug.
I think dropbear can't detect ipv6 in new kernels.
On Debian Lenny , when you run "lsmod " command , you see "ipv6" kernel module in the list , but in Debian Squeeze you don't, so dropbear thinks that your kernel doesn't support ipv6, but it does.
I got the src for dropbear and it doesn't appear to look for an ipv6 module, and on an openvz vps lsmod doesn't work anyway - so that wouldn't work in Lenny.
I found this bug report: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/468020
Ubuntu ipv6 also broke when they went from .51 to .52
Also there is a patch posted here:
https://lists.openwrt.org/pipermail/openwrt-devel/2009-May/004299.html
It's from two years ago, and they say they submitted it to dropbear, but it's not in 0.52
0.53-1 of dropbear doesn't have the patch either.
Thanks for the info.
I usually don't compile the sources , so i have to use packages in Debian Repositories (also backports).
BTW , Both of my vpses are Xen PV. in Squeeze lsmod doesn't show ipv6 module, but there is no problem with ipv6.