Hello,
I was able to solve the problem mentioned in my last update. I modified the
actions for the port 80 traffic by changing the MAC address of the packets
to that of the bridge, and the packets started hitting the kernel and
subsequently the Squid proxy. Also I explicitly gave in_ports in the s
Thanks Ben for the suggestion. This is what I did.
sudo ovs-ofctl add-flow br0 "priority=1,in_port=1,action=output:2"
sudo ovs-ofctl add-flow br0 "priority=1,in_port=2,action=output:1"
sudo ovs-ofctl add-flow br0 "priority=2,tcp,tp_src=80,action=LOCAL"
sudo ovs-ofctl add-flow br0 "priority=2,tcp,t
If you want to route a packet through the Linux routing stack, then you
should deliver the packet to an "internal" network device with an output
action.
On Sun, Apr 08, 2012 at 04:45:53PM +0530, Kaushal Shubhank wrote:
> Thanks Justin for the reply. I should have been more clear about the
> DROP a
Thanks Justin for the reply. I should have been more clear about the
DROP action that I want to use.
The action DROP in ebtables in the 'broute' table actually sends the
packet to be routed while ACCEPT sends it to be bridged. The DROP in
ovs-ofctl actually drops the packet.
By sending the port 8
You can drop packets by using the "drop" action. It's equivalent to not
listing any actions. Keep in mind the rules you've specified overlap, so
you'll need priorities to disambiguate them. (This was just discussed in the
"icmp paket matching ip packet rule" thread.)
--Justin
On Apr 6, 201
Hello,
I was reading about OpenVSwitch and really appreciated the concept. I am a
newbie and do not have a good understanding of OVS yet. I installed OVS and
and I was able to create a bridge reading the instructions.
I read that ebtables is useless in case of OVS and ovs-ofctl can do things
simi
