Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jun 2009 11:29:26 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Sam Wun <swun2010@gmail.com>
Cc:        freebsd-net@freebsd.org, freebsd-jail@freebsd.org
Subject:   Re: Can't login Jailed system
Message-ID:  <20090629112655.R22887@maildrop.int.zabbadoz.net>
In-Reply-To: <736c47cb0906290422y756a6a74i9029b4d27d2ade34@mail.gmail.com>
References:  <736c47cb0906290422y756a6a74i9029b4d27d2ade34@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Jun 2009, Sam Wun wrote:

Hi,

we've got a freebsd-jail list that I am Cc:ing.


> With FreeBSD 7.2Stable,
> I have done this many times before.
> After about a month left the "jail" behind, now when I done a
> "/etc/rc.d/jail start" and ssh into it, I ended up login to the host
> system.
> Here is the network configuraiton of the host system and the jail system:
>
> # ifconfig
> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=8<VLAN_MTU>
>        ether 00:00:21:ef:27:f7
>        media: Ethernet autoselect (100baseTX <full-duplex>)
>        status: active
> rl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=8<VLAN_MTU>
>        ether 00:50:fc:65:78:c0
>        media: Ethernet autoselect
>        status: no carrier
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=8<VLAN_MTU>
>        ether 00:13:20:65:a9:be
>        inet 192.168.1.246 netmask 0xffffff00 broadcast 192.168.1.255
>        inet 192.168.1.245 netmask 0xffffff00 broadcast 192.168.1.255
>        inet 192.168.1.235 netmask 0xffffff00 broadcast 192.168.1.255
>        inet 192.168.1.242 netmask 0xffffffff broadcast 192.168.1.242
>        media: Ethernet autoselect (100baseTX <full-duplex>)
>        status: active
> plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> metric 0 mtu 1500
> enc0: flags=0<> metric 0 mtu 1536
> pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33204
> pfsync0: flags=0<> metric 0 mtu 1460
>        syncpeer: 224.0.0.240 maxupd: 128
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
>        inet6 ::1 prefixlen 128
>        inet 127.0.0.1 netmask 0xff000000
> twp1:# jls
>   JID  IP Address      Hostname                      Path
>     5  192.168.1.242   twp5.ip6.com.au               /usr/jail2/twp5
>
> 192.168.1.242 is the jailed system,
> twp1 is the host system.
>
> After I login 192.168.1.242, I ended up logged in twp1 which is my host system.
> Now I am stuck. I don't know how I logged in the jailed system a month ago.
>
> Can anyone shred some lights on me?

Try to jexec 5 /bin/sh (5 is the jailID from the jls output)  and check
with ps if sshd is running inside the jail, and check the usual things
are up and there.


/bz

-- 
Bjoern A. Zeeb                      The greatest risk is not taking one.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090629112655.R22887>