[tproxy] Re: tproxy kernel panic

[Alexandre Fenzke]

I have the same problem, how you it solved? somebody knows the solution?

Alexandre Fenzke
  ----- Original Message ----- 
  From: Sai Bathina 
  To: TProxy mailing list 
  Sent: Wednesday, March 08, 2006 2:15 PM
  Subject: [tproxy] Re: tproxy kernel panic


  I also thought providing my kernel configuration(esp NETFILTER stuff)
  information would be a good idea.
  CONFIG_NETFILTER=y
  # CONFIG_NETFILTER_DEBUG is not set
  CONFIG_BRIDGE_NETFILTER=y
  # CONFIG_NETFILTER_NETLINK is not set

  #
  # IP: Netfilter Configuration
  #
  CONFIG_IP_NF_CONNTRACK=y
  CONFIG_IP_NF_CT_ACCT=y
  CONFIG_IP_NF_CONNTRACK_MARK=y
  # CONFIG_IP_NF_CONNTRACK_EVENTS is not set
  # CONFIG_IP_NF_CT_PROTO_SCTP is not set
  CONFIG_IP_NF_FTP=y
  CONFIG_IP_NF_DOS=m
  CONFIG_IP_NF_IRC=y
  # CONFIG_IP_NF_NETBIOS_NS is not set
  CONFIG_IP_NF_TFTP=y
  CONFIG_IP_NF_AMANDA=y
  # CONFIG_IP_NF_PPTP is not set
  CONFIG_IP_NF_TPROXY=y
  CONFIG_IP_NF_MATCH_TPROXY=y
  CONFIG_IP_NF_TARGET_TPROXY=y
  CONFIG_IP_NF_QUEUE=m
  CONFIG_IP_NF_IPTABLES=y
  CONFIG_IP_NF_MATCH_LIMIT=y
  CONFIG_IP_NF_MATCH_IPRANGE=y
  CONFIG_IP_NF_MATCH_MAC=y
  CONFIG_IP_NF_MATCH_PKTTYPE=y
  CONFIG_IP_NF_MATCH_MARK=y
  CONFIG_IP_NF_MATCH_MULTIPORT=y
  CONFIG_IP_NF_MATCH_TOS=y
  CONFIG_IP_NF_MATCH_RECENT=y
  CONFIG_IP_NF_MATCH_ECN=y
  CONFIG_IP_NF_MATCH_DSCP=y
  CONFIG_IP_NF_MATCH_AH_ESP=y
  CONFIG_IP_NF_MATCH_LENGTH=y
  CONFIG_IP_NF_MATCH_TTL=y
  CONFIG_IP_NF_MATCH_TCPMSS=y
  CONFIG_IP_NF_MATCH_HELPER=y
  CONFIG_IP_NF_MATCH_STATE=y
  CONFIG_IP_NF_MATCH_CONNTRACK=y
  CONFIG_IP_NF_MATCH_OWNER=y
  CONFIG_IP_NF_MATCH_PHYSDEV=y
  CONFIG_IP_NF_MATCH_ADDRTYPE=y
  CONFIG_IP_NF_MATCH_REALM=y
  # CONFIG_IP_NF_MATCH_SCTP is not set
  # CONFIG_IP_NF_MATCH_DCCP is not set
  CONFIG_IP_NF_MATCH_COMMENT=y
  CONFIG_IP_NF_MATCH_CONNMARK=y
  # CONFIG_IP_NF_MATCH_CONNBYTES is not set
  CONFIG_IP_NF_MATCH_HASHLIMIT=y
  # CONFIG_IP_NF_MATCH_STRING is not set
  CONFIG_IP_NF_FILTER=y
  CONFIG_IP_NF_TARGET_REJECT=y
  CONFIG_IP_NF_TARGET_LOG=y
  CONFIG_IP_NF_TARGET_ULOG=y
  CONFIG_IP_NF_TARGET_TCPMSS=y
  # CONFIG_IP_NF_TARGET_NFQUEUE is not set
  CONFIG_IP_NF_NAT=y
  CONFIG_IP_NF_NAT_NEEDED=y
  CONFIG_IP_NF_TARGET_MASQUERADE=y
  CONFIG_IP_NF_TARGET_REDIRECT=y
  CONFIG_IP_NF_TARGET_NETMAP=y
  CONFIG_IP_NF_TARGET_SAME=y
  # CONFIG_IP_NF_NAT_NRES is not set
  CONFIG_IP_NF_NAT_SNMP_BASIC=y
  CONFIG_IP_NF_NAT_IRC=y
  CONFIG_IP_NF_NAT_FTP=y
  CONFIG_IP_NF_NAT_TFTP=y
  CONFIG_IP_NF_NAT_AMANDA=y
  CONFIG_IP_NF_MANGLE=y
  CONFIG_IP_NF_TARGET_TOS=y
  CONFIG_IP_NF_TARGET_ECN=y
  CONFIG_IP_NF_TARGET_DSCP=y
  CONFIG_IP_NF_TARGET_MARK=y
  CONFIG_IP_NF_TARGET_CLASSIFY=y
  # CONFIG_IP_NF_TARGET_TTL is not set
  CONFIG_IP_NF_TARGET_CONNMARK=y
  CONFIG_IP_NF_TARGET_CLUSTERIP=y
  CONFIG_IP_NF_RAW=y
  CONFIG_IP_NF_TARGET_NOTRACK=y
  CONFIG_IP_NF_ARPTABLES=y
  CONFIG_IP_NF_ARPFILTER=y
  CONFIG_IP_NF_ARP_MANGLE=y

  Thanks



  > I am using a 2.6.14 kernel with the 2.0.3 patch. I am using a proxy
  > server to connect transparently using tproxy. While the traffic is
  > flowing I did a cat /proc/net/tproxy and I saw a kernel panic. The
  > trace I could see was:
  >
  > pipe_writev
  > pipe_write
  > vfs_write
  > sys_write
  > syscall_call
  >
  > Sorry I do not get better informtion. But I was wondering if this is a
  > known issue or something that is new.
  >
  > Thanks
  > Sai
  >
  _______________________________________________
  tproxy mailing list
  tproxy at lists.balabit.hu
  https://lists.balabit.hu/mailman/listinfo/tproxy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/tproxy/attachments/20060723/c42e20df/attachment.html