Re: [flalug] odd behavior with new router

From: Eben King (eben1@tampabay.rr.com)
Date: Sun Jun 27 2004 - 13:13:28 EDT


On Sun, 27 Jun 2004, Larry Brown wrote:

> On Sun, 2004-06-27 at 03:50, Eben King wrote:
> > OK, got it. It was "IP: TCP Explicit Congestion Notification support",
> > which, until I recompile, I can turn off by "echo 0 >
> > /proc/sys/net/ipv4/tcp_ecn". Once I do that, TCP works. Thank you all
> > for your help.
>
> Man, that was my next question!... NOT! :-0 How in the hell did that
> get turned on?

I guess it worked with the USR router.... One of those things I tried
(because it seemed to add a bit of security?), and it worked, so I left
it on.

> By the way, using iptables on a machine behind a firewall you control is
> a bit redundant.

OK, thought so. The only ports allowed through the NAT firewall are 22
(SSH), 81 (nonstandard HTTP) and 2074/2074 (Speak Freely),

> The reasons I asked where the behaviour and the fact that RH and SuSe
> both default to setting one up on install.

If you do a "Custom" install (which I always do), it gives you the option
of High/Medium/Low/None security. I chose None. Presumably on one of the
higher levels, you get iptables.

-- 
-eben      ebQenW1@EtaRmpTabYayU.rIr.OcoPm      home.tampabay.rr.com/hactar
An ASCII character walks into a bar and orders a double. "Having a bad day?"
asks the barman. "Yeah, I have a parity error," replies the ASCII character.
The barman says, "Yeah, I thought you looked a bit off." -- Skud



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:07:20 EDT