>It's been almost a year since I've visited this mailing-list... And
>(un)fortuantely, I'm back and need your help.
>
>My current setup is a IP Masq box with Slackware v3.4 with the 2.0.33
>kernel. IP Masq works great however, an old problem has crept back (...
>actually, probably never left). I've sifted thru DejaNews and archives of
>the IPMasq mailing list but didn't find a solution. Here's the problem:
>
>ppp0 goes up and IP Masq is started. I do some lynx and telnet from the IP
>Masq box. Soon after, all out-going connections from the clients *on* the
IP
>Masq can no longer open connections. However, nslookup and ping still work.
>But I cannot telnet or ftp or www out *from* the IP Masq box.
>
>However, all the machines that are using the IP Masq box can still do
>everything. Web. Telnet. FTP. RealAudio/Video. But for the life of me,
>connections time out if I use telnet, ftp or lynx *on* the IP Masq.
>
>Now you're probably wondering... "Then don't use another computer going
thru
>IP Masq box to telnet/ftp/www out." Which is fine... But I now have 9
>machines on this LAN over a whimpy 31.2 kbps connection (Note: I'm waiting
>patiently for US West for ADSL within' the next month to fix that ;) And I
>recently decided to use Apache v1.3b6 as a caching proxy-server.
>
>Well guess what... The Apache caching proxy-server works great for about 5
>minutes... Then it stops working. Then I get errors in the error_log
saying:
>
>[Sun May 24 19:14:40 1998] connect: 207.18.199.6 port 80: Connection timed
>out
>[Sun May 24 19:14:40 1998] connect: 207.18.199.6 port 80: Connection timed
>out
>
>Which coincides with when I'm no longer able to open telnet/ftp/www *from*
>the IP Masq box. Please remember that all the other machines BEHIND the IP
>Masq box going thru it is still working perfectly fine. I'm assuming the
>problem is Apache is trying to open a port from the IP masq box to the
>outside world... and it times out after about 2 minutes. Before the IP Masq
>box decides to stop allowing me to open-connections from it, it works GREAT
>:)
>
>I've tried changing the MTU/MRU settings to match and mis-match (1500/1500,
>1500/576, 576/576) with no-avail. So now I'm hoping someone has run into
>this problem before and got it solved. :) If someone needs my
>/usr/src/linux-2.0.33/.config, let me know. But I think I've compiled the
>kernel correctly for networking and IP Masq.
>
>Incidentally, I remembered that if I didn't "turn-on" IP Masq, that the
>problem never occurs...
>
Daniel,
I had the same problem. The solution for me was to delete al ipautofw rules.
I never found the reason why and when I investigated the problem this week
(yes I want to use ipautofw) the problem did'nt occur anymore :-)
The only thing I changed to my linux config was that I now use named as a
caching only nameserver. I don't know why it works now but mayby
removing all ipautofw rules solves this problem for you too. You probably
also want to use ipautofw but whitout it the masquarading may work better.
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
