Sorry, what happens is the source address of the GRE tunnel is set to the IP of
the 10.0.1.0/24 interface, resulting in the packets being seen on that
interface using tcpdump. eth0 is configured as 10.0.1.27 and eth1 is
192.168.1.2 (desired egress interface).
09:48:00.315878 IP 10.0.1.27 > 192.16.1.3: GREv0, length 802: gre-proto-0x6558
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.0.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth3
192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth1
192.168.1.1 * 255.255.255.255 UH 0 0 0 eth1
OFPT_FEATURES_REPLY (xid=0x1): dpid:0000000c29c1a8f3
n_tables:255, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST
SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
1(eth2): addr:00:0c:29:c1:a8:f3
config: 0
state: 0
current: 10GB-FD COPPER
advertised: COPPER
supported: 1GB-FD 10GB-FD COPPER
speed: 10000 Mbps now, 10000 Mbps max
2(eth3): addr:00:0c:29:c1:a8:fd
config: 0
state: LINK_DOWN
current: COPPER
advertised: COPPER
supported: 1GB-FD 10GB-FD COPPER
speed: 100 Mbps now, 10000 Mbps max
4(test0): addr:4a:3f:b0:79:f1:98
config: 0
state: 0
speed: 100 Mbps now, 100 Mbps max
LOCAL(br0): addr:00:0c:29:c1:a8:f3
config: PORT_DOWN
state: LINK_DOWN
speed: 100 Mbps now, 100 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=198.248s, table=0, n_packets=350795, n_bytes=305734399,
idle_age=1, in_port=1 actions=output:4
> On Mon, Jan 7, 2013 at 7:38 PM, Jeff Welsch <j...@jeffwelsch.com> wrote:
>> Hello,
>>
>> Is there a way to specify the egress interface for a GRE tunnel? I am
>> matching flows and sending them to a tunnel using an output action. This
>> works fine when my remote IP is on eth0, but I would like to send some
>> tunnels out through eth1, depending on their destination address. I am
>> trying to accomplish this with static routes in Linux, but they do not seem
>> to be followed (probably the expected behavior with OVS). I cannot find a
>> way to also send the tunnel traffic out a specific interface using a flow
>> mod. How would I accomplish this?
>
> OVS should follow the Linux routing table, so static routes are the
> right way to accomplish this. Why do you say they don't work?
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
