in boot up i get  tcp in out, which is firewall blocking  someting..
how do i id what it blocked and  then il add it to my router to block
for  good.

[ Post a follow-up to this message ]

On Sun, 19 Aug 2007 11:24:55 -0500, josh wrote:

> in boot up i get  tcp in out, which is firewall blocking  someting..
> how do i id what it blocked and  then il add it to my router to block
> for  good.

42.

--
"Bother!" said Pooh, as Christopher Robin pleaded to be spanked again.

[ Post a follow-up to this message ]

josh wrote:
> in boot up i get  tcp in out, which is firewall blocking  someting..
> how do i id what it blocked and  then il add it to my router to block
> for  good.

read up on iptables, which is what Linux uses for firewalls & NAT.

[ Post a follow-up to this message ]

On 08/19/2007 01:39 PM, Gary Dale wrote:
> josh wrote: 
>
> read up on iptables, which is what Linux uses for firewalls & NAT.

Josh, iptables is somewhat complicated. Firestarter and Shorewall are
easier ways to setup a firewall, and they are included with Debian (use
aptitude).

[ Post a follow-up to this message ]

Mumia W. wrote:
> On 08/19/2007 01:39 PM, Gary Dale wrote: 
[vbcol=seagreen]
> Josh, iptables is somewhat complicated. Firestarter and Shorewall are
> easier ways to setup a firewall, and they are included with Debian (use
> aptitude).

Firestarter and Shorewall both are just GUIs for iptables. And the OP
doesn't want to setup a firewall, he wants to find out what is blocked
at the boot process. Firestarter and Shorewall are useless for this task.

Alex

[ Post a follow-up to this message ]

On 08/20/2007 05:11 AM, Alexander Schestag wrote:
> Mumia W. wrote: 
> 
>
> Firestarter and Shorewall both are just GUIs for iptables. And the OP
> doesn't want to setup a firewall, he wants to find out what is blocked
> at the boot process. Firestarter and Shorewall are useless for this task.
>
> Alex

You're probably right about what the OP was saying. I could barely
understand him/her and shouldn't have responded.

[ Post a follow-up to this message ]

On Sun, 19 Aug 2007 11:24:55 -0500, josh wrote:

> in boot up i get  tcp in out, which is firewall blocking  someting.. how
> do i id what it blocked and  then il add it to my router to block for
> good.

Isn't the info you're looking for in sylog?

[ Post a follow-up to this message ]

On Mon, 20 Aug 2007 07:37:12 -0700, Rodney wrote:

> On Sun, 19 Aug 2007 11:24:55 -0500, josh wrote:
> 
>
> Isn't the info you're looking for in sylog?

Oops, my bad. Was a typo that should have been syslog.

[ Post a follow-up to this message ]

Rodney your r ight  here is  system log error>
> 08/19/2007 02:57:48 PM	localhost	kernel	DROPPED IN= OUT=eth0 SRC=192.168.0
.101 DST=192.168.0.255 LEN=242 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP S
PT=138 DPT=138 LEN=222
>
> 08/19/2007 02:57:57 PM	localhost	pppd[2214]	Timeout waiting for PADO p
ackets
>
> 08/19/2007 02:58:31 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=232
 TOS=0x00 PREC=0x00 TTL=128 ID=6856 PROTO=UDP SPT=138 DPT=138 LEN=212
>
> 08/19/2007 02:58:32 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6859 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:33 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6860 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:33 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6861 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:33 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6862 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:33 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6863 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:33 PM	localhost	kernel	DROPPED IN=eth0 OUT= MAC=ff:ff:ff:
ff:ff:ff:00:0c:76:58:6b:89:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=96 
TOS=0x00 PREC=0x00 TTL=128 ID=6864 PROTO=UDP SPT=137 DPT=137 LEN=76
>
> 08/19/2007 02:58:48 PM	localhost	kernel	DROPPED IN= OUT=eth0 SRC=192.168.0
.101 DST=192.168.0.255 LEN=242 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP S
PT=138 DPT=138 LEN=222
>
thats it

[ Post a follow-up to this message ]