Rob:
Heya. Some quick answers (am posting this on-list, as
you suggested)
1. Actually, echowall is the one doing more filtering, not less. Charles'
default script lets many of the broadcast-noise stuff go thru to the
end, where it gets logged by the last "catch and log everything that
mad
Many thanks for clarifying that Scott, I'm now the proud owner
of a ES2B with echowall :-)
Thanks
Rob
-Original Message-
From: Scott C. Best [mailto:[EMAIL PROTECTED]]
Sent: 02 July 2001 18:16
To: Rob Moore
Cc: [EMAIL PROTECTED]
Subject: RE: [Leaf-user] Eigerstein2Beta packe
Rob:
Heya. Glad to here the multicast rules flew. Regarding
echowall and ES2B playing nicely together, I built echowall
on and for that system specifically. So, when it installs
itself, it gently brushes aside the default firewall of ES2B
and puts itself in place instead. When/if you de-i
L PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Leaf-user] Eigerstein2Beta packet log silent deny
Rob:
Heya. Victor's answer is spot-on:
> > Jul 1 00:44:38 pdrtr kernel: Packet log: input DENY eth0 PROTO=2
> > 192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x T=1
ECTED]; [EMAIL PROTECTED]
Subject: Re: [Leaf-user] Eigerstein2Beta packet log silent deny
Rob:
Heya. Victor's answer is spot-on:
> > Jul 1 00:44:38 pdrtr kernel: Packet log: input DENY eth0 PROTO=2
> > 192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x T=1 (#9)
&g
Rob:
Heya. Victor's answer is spot-on:
> > Jul 1 00:44:38 pdrtr kernel: Packet log: input DENY eth0 PROTO=2
> > 192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x T=1 (#9)
>
> These are multi-cast packets, possibly from your ISP or a misconfigured
> clown on your cable network
Rob Moore wrote:
> Hello there a few questions; thanks in advance:-
>
> 1. router - which is a 486-PCI board using two 3com 3c905b nics
> and a SURFboard SB4100 cable modem. Internal network is 192.168.1.0/24
> external net 62.x.x.x provided by DHCP from ISP. All is working fine
> but I have an a
