From: Christian Mayrhuber (christian.mayrhuber_at_gmx.net)
Date: Wed 07 Jan 2004 - 17:09:35 GMT
Luís Miguel Silva wrote:
> It looks to me like some problem with the hardware! :o)
>
>
> Best,
> +-------------------------------------------
> | Luís Miguel Silva
> | Network Administrator@ ISPGaya.pt
> | Rua António Rodrigues da Rocha, 291/341
> | Sto. Ovídio • 4400-025 V. N. de Gaia
> | Portugal
> | T: +351 22 3745730/3/5 F: +351 22 3745738
> | G: +351 93 6371253 E: lms_at_ispgaya.pt
> | H: http://lms.ispgaya.pt/
> +-------------------------------------------
> -----Original Message-----
> From: vserver-admin_at_list.linux-vserver.org
> [mailto:vserver-admin_at_list.linux-vserver.org] On Behalf Of Alexander Goeres
> Sent: quarta-feira, 7 de Janeiro de 2004 16:30
> To: vserver_at_list.linux-vserver.org
> Subject: Re: [Vserver] [Release] vs1.00, vs1.22 and vs1.3.3 for 2.4.24
>
> For my problem, I don't think it's vserver-related. Today I could compile a
> vanilla 2.4.23-kernel on the relevant host-server without any vserver
> implementation. After a reboot in this kernel I did a "telnet
> remote.mail.server 25" from the host-server and it timed out as before. It
> looks as if it's a firewall-problem on the remote side but the admins in
> charge there of course claim, that it's not so.. I can't look into their
> firewall, but a more agressive approach with
> 1. "nmap -p 25 -sS remote.mail.server" and
> 2. "nmap -p 25 -sA remote.mail.server"
> from one of my host-servers showed for 1.: "port 25 open" and for 2.:"port
> 25
> filtered". That sounds exactly like your explanation. But for my
> host-servers
> it occurs no matter if they have a vserver-patched kernel running or not.
>
> Too bad, for a short time I thought I might have tracked this problem down
> and
> could accuse Herbert and the developers here of doing bad work instead of
> fighting alien admins.. :-)
Funny thing!
I've tried earlier to telnet on port 25 from a 2.4.18 debian machine and
from a pix firewall and it worked.
All my vserver kernel were 2.4.20 onwards...
Now I've tried it from a RedHat 9 with a 2.4.24 kernel and RedHat 7.3
with a 2.4.20-RH kernel and trough a telnet proxy. Guess what - no go!
Great that this thing sorted out not to be vserver related :-)
Let's go firewall admin bashing...
-- lg, Chris _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver