<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: cipe-1.5.4, kernel 2.4.19, kernel messages
From: "Steve Ripps" <stever,AT,sttc,DOT,net,DOT,au>
Date: Wed, 14 Aug 2002 10:59:32 +0200
In-reply-to: <3D598878.28343.34C5DB@localhost>

On 14 Aug 2002 at 0:42, ewheeler,AT,kaico,DOT,com wrote:

> What about the simple test?
> 
> iptables -F
> iptables -F -t nat
> iptables -F -t mangle
> 
> Does it work flushed?
> 
> --Eric
> 
> On Tue, 13 Aug 2002, Steve Ripps wrote:
> 
> > Hi Roberto.
> > I've tried a few of your suggestions.  See below.  I'll try the others a 
>bit later when
> > I have more time.  Even if I can avoid it by changing iptables rules, 
>surly it has to
> > be considered a bug?  (It certainly bugs me :)
> > 
> > On 13 Aug 2002 at 12:16, Roberto Nibali wrote:
> > 
> > > Cheers mate,
> > > 
> > > > GW: kernel 2.2.20
> > > > ppp2: 203.52.103.254
> > > > cipcb0: 10.2.0.254
> > > > 
> > > > tux: kernel 2.4.19 
> > > > ppp0: 203.52.103.193
> > > > cicb0: 10.2.1.254
> > > > 
> > > > Does cipe need to be updated slightly to work OK with kernel 2.4.19?
> > > 

Flushing iptables doesn't help...

root@gw:~# pkcipe -c 203.52.103.193:pkcipe
root@gw:~# ping -c2 10.2.1.254

root@tux:~# tail -n 30 /var/log/messages.log
Aug 14 18:37:51 tux login[441]: ROOT LOGIN on `tty2'
Aug 14 18:38:45 tux ipop3d[1353]: connect from 10.0.0.198
Aug 14 18:40:17 tux pkcipe[1383]: connect from 203.52.103.254
Aug 14 18:40:18 tux kernel: cipcb: CIPE driver vers 1.5.4 (c) Olaf Titz 
1996-2000, 100 channels, debug=1
Aug 14 18:40:18 tux kernel: cipcb: cipe_alloc_dev 0
Aug 14 18:40:18 tux kernel: cipcb0: alloc
Aug 14 18:40:18 tux kernel: cipcb0: setpar
Aug 14 18:40:18 tux kernel: cipcb0: setkey
Aug 14 18:40:18 tux kernel: cipcb0: attach
Aug 14 18:40:18 tux kernel: cipcb0: opened
Aug 14 18:40:18 tux kernel: cipcb0: cipe_sendmsg
Aug 14 18:40:18 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:40:18 tux kernel: cipcb0: cipe_sendmsg
Aug 14 18:40:18 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:40:18 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:40:26 tux ipop3d[1393]: connect from 10.0.0.198
Aug 14 18:41:14 tux kernel: ip_finish_output: bad owned skb = cda04500: 
POST_ROUTING
Aug 14 18:41:14 tux kernel: skb: pf=2 (owned) dev=ppp0 len=132
Aug 14 18:41:14 tux kernel: PROTO=17 203.52.103.193:32772 203.52.103.254:1291 
L=132 S=0x00 I=46917 F=0x0000 T=64
Aug 14 18:41:14 tux kernel: cipcb0: cipe_sendmsg
Aug 14 18:41:14 tux kernel: cipcb0: setkey
Aug 14 18:41:14 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:41:14 tux kernel: cipcb0: setkey
Aug 14 18:41:14 tux kernel: cipcb0: cipe_sendmsg
Aug 14 18:41:14 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:41:15 tux kernel: cipcb0: setkey
Aug 14 18:41:15 tux kernel: cipcb0: cipe_recvmsg
Aug 14 18:41:15 tux kernel: ip_finish_output: bad owned skb = cda04500: 
POST_ROUTING
Aug 14 18:41:15 tux kernel: skb: pf=2 (owned) dev=ppp0 len=132
Aug 14 18:41:15 tux kernel: PROTO=17 203.52.103.193:32772 203.52.103.254:1291 
L=132 S=0x00 I=46918 F=0x0000 T=64

Table: filter
-------------
Chain INPUT (policy ACCEPT 1621 packets, 562K bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain FORWARD (policy DROP 4 packets, 244 bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain OUTPUT (policy ACCEPT 1793 packets, 577K bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain account (0 references)
 pkts bytes target     prot opt in     out     source               
destination         

Chain in_filter (0 references)
 pkts bytes target     prot opt in     out     source               
destination         

Chain log_drop (0 references)
 pkts bytes target     prot opt in     out     source               
destination         

Chain out_filt (0 references)
 pkts bytes target     prot opt in     out     source               
destination         

Table: nat
----------
Chain PREROUTING (policy ACCEPT 9 packets, 657 bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain POSTROUTING (policy ACCEPT 25 packets, 1507 bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain OUTPUT (policy ACCEPT 32 packets, 2277 bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Table: mangle
-------------
Chain PREROUTING (policy ACCEPT 1687 packets, 569K bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain INPUT (policy ACCEPT 1620 packets, 562K bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain FORWARD (policy ACCEPT 67 packets, 7212 bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain OUTPUT (policy ACCEPT 1792 packets, 577K bytes)
 pkts bytes target     prot opt in     out     source               
destination         

Chain POSTROUTING (policy ACCEPT 5900 packets, 1125K bytes)
 pkts bytes target     prot opt in     out     source               
destination         





<< | Thread Index | >> ]    [ << | Date Index | >> ]