Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: cerowrt-users@lists.bufferbloat.net
Subject: [Cerowrt-users] no xt_TRACE in kernel
Date: Mon, 4 Mar 2013 21:01:11 -0800	[thread overview]
Message-ID: <20130305050111.GB15079@merlins.org> (raw)

Since it's a router distrib for advanced routing, would it be possible to
add more modules in the kernel build?

For instance, I have to debug why a packet forward/rewrite isn't working,
and I can't easily:
root@wireless:~# iptables -t raw -A PREROUTING -p tcp --dport 10443 -j TRACE
iptables v1.4.12.2: Couldn't load target `TRACE':No such file or directory

More generally, I have his:
root@wireless:~# iptables -t nat -L -v -n 
Chain PREROUTING (policy ACCEPT 4067K packets, 760M bytes)
 pkts bytes target     prot opt in     out     source               destination         
4068K  760M prerouting_rule  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
 704K  190M zone_wan_prerouting  all  --  ge00   *       0.0.0.0/0            0.0.0.0/0           
    0     0 zone_guest_prerouting  all  --  gw00   *       0.0.0.0/0            0.0.0.0/0           
    0     0 zone_guest_prerouting  all  --  gw10   *       0.0.0.0/0            0.0.0.0/0           
3364K  570M zone_lan_prerouting  all  --  br-lan *       0.0.0.0/0            0.0.0.0/0           


Chain zone_lan_prerouting (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   29  1740 DNAT       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:10443 to:192.168.205.72:443
3364K  570M prerouting_lan  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain zone_wan_prerouting (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   14   840 DNAT       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:10443 to:192.168.205.72:443
 704K  190M prerouting_wan  all  --  *      *       0.0.0.0/0            0.0.0.0/0    

telnet wan-ip 10443 works if the packet comes from the outside and arrieves on ge00.

But if I do this from the lan, it shoul darrive on br-lan and be re-forwarded out 
on the br-lan interface, but that's not working.

Being able to do packet tracing as described here
http://backreference.org/2010/06/11/iptables-debugging/

Would have made my job much easier :)

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

             reply	other threads:[~2013-03-05  5:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05  5:01 Marc MERLIN [this message]
2013-03-05  6:07 ` Marc MERLIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130305050111.GB15079@merlins.org \
    --to=marc@merlins.org \
    --cc=cerowrt-users@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox