Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Roland Häder" <r.haeder@web.de>
To: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
Cc: netfilter@vger.kernel.org
Subject: Re: Bastille/netfilter with Linux 2.6.28 blocks connections
Date: Mon, 05 Jan 2009 14:41:40 +0100	[thread overview]
Message-ID: <664670418@web.de> (raw)

> Hi!
Hi,

> Why you said "now". It has never worked? When it's start to had problems?
It has worked on earlier days and with an older kernel, I cannot recall the exact version number, so maybe it was 2.6.18 which I have also used a long time. But once I have upgraded it to newer kernels, and double-checked the config, these routing problems starts.

Okay, anyway. As I have promised before I have uploaded some more details:

First here is the requested logfile (syslog) with the relevant ports:
http://www.mxchange.org/downloads/firebox/tor-drops_syslog.log

Okay, two thinks I was mentioning before where wrong, sorry about that. :( First INPUT DROP 8 is dropping the packets and second they came from outside as you can see in the logs.

Here are some more files for inspection:

My actually used kernel config:                                                                                                                              
http://www.mxchange.org/downloads/firebox/config-2.6.28-vanilla

Output of "route -n": (it should be fine, I suppose)
http://www.mxchange.org/downloads/firebox/route.txt

That x.x.x.x was me. It is the PPP partner IP of my ISP.

This directory contains my extra-scripts for the corresponding Bastille "hooks":
http://www.mxchange.org/downloads/firebox/firewall.d/

That directory should be found in /etc/Bastille/.
>
> You have to say us what you want to leave pass from that firewall... tor
> from internet, from lan? tor on localhost wants to connect to your-self
> by 127 or 192 ?
192.168.1.1 is my router, 192.168.1.1x are my clients, both have a "default gateway" set to 192.168.1.1 and /etc/resolve.conf has a nameserver entry pointing only to 192.168.1.1

I want to pass through from my LAN (eth1) to Internet (eth0/ppp0) regular things like Mail, Newsgroups and such things. So I need to masq my private network 192.168.1.0 on eth1 to the Internet. And this is no longer working.
  
I want to route traffic from Internet on TCP/UDP port 31017 which is being used by Descent2-Rebirth to my client 192.168.1.17. I used PREROUTE and FORWARD for this.
                                                                                                                                                             
Like I wrote above it *has* worked, until I have upgraded the farly outdated kernel which should be done on regular basis. I guess you know why. :)

> Too short description and no logs.
Hope that helps a bit more? :)

Roland

__________________________________________________________________
Deutschlands größte Online-Videothek schenkt Ihnen 12.000 Videos!*
http://entertainment.web.de/de/entertainment/maxdome/index.html


             reply	other threads:[~2009-01-05 13:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 13:41 Roland Häder [this message]
2009-01-05 14:37 ` Bastille/netfilter with Linux 2.6.28 blocks connections Michele Petrazzo - Unipex srl
2009-01-07 15:16 ` Mart Frauenlob
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07 21:55 Roland Häder
2009-01-07 22:16 ` Mart Frauenlob
2009-01-07  1:16   ` Roland Haeder
2009-01-07 21:09 Roland Häder
2009-01-07 21:04 Roland Häder
2009-01-07 20:04 Roland Häder
2009-01-07 20:15 ` Mart Frauenlob
2009-01-07 15:45 Roland Häder
2009-01-07 19:43 ` Mart Frauenlob
2009-01-05 16:52 Roland Häder
2009-01-05 16:37 Roland Häder
2009-01-07  8:51 ` Michele Petrazzo - Unipex srl
2009-01-03 21:02 Roland Häder
2009-01-05 11:47 ` Michele Petrazzo - Unipex srl

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=664670418@web.de \
    --to=r.haeder@web.de \
    --cc=michele.petrazzo@unipex.it \
    --cc=netfilter@vger.kernel.org \
    /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