Re: Policy routing problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

>If you create separate routing tables you must
>duplicate to it the same device routes as you have in main for these
>interfaces or/and play with src option.

Ok, somehow that works without making too many problems, but I would
really like to find a solution that simulates these device routes only if
the source port is 67.

In the meanwhile, I found out that my solution with for example "ip rule
add fwmark 114 table 114", "ip route add to 129.217.14.0/24 dev eth1.114
table 114" and "iptables -t mangle -A OUTPUT -p udp --source-port bootps
-d 129.217.14.0/24 -j MARK --set-mark 114" works in so far that unicast
DHCP replies are sent from the same device where the request came in, but
still the wrong IP is used. This does not change when I use a specific
source address in "ip route". I tried to set the correct IP address with
SNAT, but it seems that SNAT refuses to use the same port where some
application is listening on. So, if I use "iptables -t nat -A POSTROUTING
... --to-source 129.217.14.81:67", nothing is sent, in contrast to other
ports.

Regards
  Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Newbie]     [Audio]     [Hams]     [Kernel Newbies]     [Util Linux NG]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Device Drivers]     [Samba]     [Video 4 Linux]     [Git]     [Fedora Users]

  Powered by Linux