All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Remus" <rmocius@auste.elnet.lt>
To: lartc@vger.kernel.org
Subject: [LARTC] UDP port 1194 marking/routing problem
Date: Wed, 06 Apr 2005 10:51:16 +0000	[thread overview]
Message-ID: <0b6701c53a96$8ef69fc0$6e69690a@RIMAS> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]


Hi folks,

I have OpenVPN (respect for it developers) running on my FW.
Is has two external NICs and on internal everything is fine, except
I want OpenVPN (UDP port 1194) going not via default route/network interface.

I use such commands:

iptables -t mangle -D POSTROUTING -o eth0 -p udp --dport 1194 -j MARK --set-mark 0x990                                             
ip rule add fwmark 0x990 table openvpn1                                                                                           
ip route add default via $P2 dev eth0 table openvpn1 

eth0 is FW's not default external NIC.

I have in use very similar iptables rules for my email server (TCP ports) and etc.
Everything works fine. 
What I'm doing wrong with marking/routing the UDP port?

Regards

Remus


[-- Attachment #1.2: Type: text/html, Size: 2762 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-04-06 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 10:51 Remus [this message]
2005-04-06 11:23 ` [LARTC] UDP port 1194 marking/routing problem Wang Jian
2005-04-06 13:48 ` Remus
2005-04-06 14:03 ` Wang Jian

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='0b6701c53a96$8ef69fc0$6e69690a@RIMAS' \
    --to=rmocius@auste.elnet.lt \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.