or use an iptables rule
my friend can only go "out" on port 23, so I added this...
iptables -t nat -A PREROUTING -i eth1 -p tcp -m tcp --dport 23 -j DNAT
--to-destination 192.168.0.254:22
(eth1 is the "public" interface)
which is probably a little extreme the way I have it laid out, but it wor
Well, I thought about that.
I have 3 other boxes that I connect through. So three boxes with a port
option or one from work.
I know I can set up identities for each box and not have to type the
port number every time, but the redirect should work. it has worked in
past versions.
The less set up
Why bother with a redirect, just run your sshd with a "-p 21" option.
Guy
Greg Gatlin wrote:
I updated my xinetd to the newest version with up2date and my redirect is
no longer functioning.
I upgraded to xinetd-2.3.7-5.
My redirect is so I can get to my box from work. They block port 22 and
le
Several people do run sendmail through xinetd. It's not as effecient as
standalone but you get all the control xinetd offer such as access lists. I
don't have a xinetd entry for sendmail but I seen one come throught the
xinetd list last week.
-eric wood
- Original Message -
From: "jdow"
On Wed, 13 Nov 2002, Javier Gostling wrote:
> On Wed, Nov 13, 2002 at 10:43:28AM -0800, jdow wrote:
>
> > Xinetd is what spawns some of the connections, such as mail,
> > telnet, or ftp.
>
> Not mail. Both sendmail and postfix are standalone programs. Unless you
> have switched to another mail p
IMAP and POP3 mail, silly.
{^_-}
- Original Message -
From: "Javier Gostling" <[EMAIL PROTECTED]>
On Wed, Nov 13, 2002 at 10:43:28AM -0800, jdow wrote:
> Xinetd is what spawns some of the connections, such as mail,
> telnet, or ftp.
Not mail. Both sendmail and postfix are standalone pr
On Wed, Nov 13, 2002 at 10:43:28AM -0800, jdow wrote:
> Xinetd is what spawns some of the connections, such as mail,
> telnet, or ftp.
Not mail. Both sendmail and postfix are standalone programs. Unless you
have switched to another mail package which does not come in the RH CDs.
Cheers,
--
Javi
Disconnect the network. Put up a really "thick" firewall. Stop all traffic
to the machine in any case. Is xinetd still busy? Run chkrootkit on the
machine. Is it REALLY clean? A little more history of the machine might be
useful. Xinetd is what spawns some of the connections, such as mail,
telnet,
