Michael Weickel - iQom Business wrote:
Thanks a lot for your response but this seems to be not running form my issues.I´ll try to give an example.Subnet A 10.0.0.0/24 connected to switch I port 1 (vlan 5) Host A 10.0.0.1/24 belongs to subnet A Subnet B 10.0.0.0/24 connected to switch I port 2 (vlan 10) Host B 10.0.0.1/24 belongs to subnet BSwitch I port 3 is a trunk which gives the both subnets to shorewall eth2.Eth2 is virtualized into interface vlan5 (10.0.0.254) and interface vlan10 (10.0.0.254). Both vlan interfaces belong to eth2. Vlan5 has an own routing table 2, vlan10 has an own routing table 3. Host A and Host B can ping vlan5 and vlan10 on shorewall with "ip rule add from 10.0.0.254 table 2" and "ip rule add from 10.0.0.254 table 3". This seems to be one problem to me. Linux and shorewall does not recognize that the one ip belongs to vlan5 and the other to vlan10.
Why don't you "ip rule add iif vlan5 table 2" and "ip rule add iif vlan10 table 3"?
I have a hope that shorewall has a hint to solve my problem, due to the fact that I believe that ip tools are not able to. Normally I would say for sure, that ip is able to, but I don´t know how to go on.
Shorewall is just a configuration tool that uses the ip tools to activate the configuration. There is nothing magic about Shorewall.
-Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
