You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone, I'm trying to implement a firewall in click and I m facing an issue.
Here is a schema:
And my click configuration
//Inputs and outputs
in::FromDevice(ens4, PROMISC true)
out::ToDevice(ens5)
//c::Counter;
//Classifier
cw::Classifier(
12/0800, //IP packets
- // Other
);
// IP Filtering
f::IPFilter(
0 src host 192.168.110.0 && ip proto 1 or ip proto 17,
1 all);
cw[0]->CheckIPHeader(14)->f;
cw[1]->Print("The packet was dropped")->Discard
in->cw;
f[0]->IPPrint("pass")->Queue->out;
f[1]->Print("Discard")->Queue->Discard;
What I want to achieve is when I ping the address 192.168.110.119, then "firewall-vnf" should route the traffic to 192.168.109.23 (i.e. VM3)
I capture the traffic using tcpdump on the output interface (ens5) but as I expected the traffic is not traversing to 192.168.109.23
What else should add to the click configuration file in order to achieve this forwarding?
Or can I do this with iptables rules on the ens5 interface;
Thank you in advance
The text was updated successfully, but these errors were encountered:
Its probably worth looking at the Layer2 headers. The way I read the config the packets are going to leave ens5 with the same L2 headers as received on ens4, so even if the packet is forced onto the VM3 interface, VM3 will receive the packet with a destination mac that it probably does not own.
Hello everyone, I'm trying to implement a firewall in click and I m facing an issue.
Here is a schema:
And my click configuration
What I want to achieve is when I ping the address 192.168.110.119, then "firewall-vnf" should route the traffic to 192.168.109.23 (i.e. VM3)
I capture the traffic using tcpdump on the output interface (ens5) but as I expected the traffic is not traversing to 192.168.109.23
What else should add to the click configuration file in order to achieve this forwarding?
Or can I do this with iptables rules on the ens5 interface;
Thank you in advance
The text was updated successfully, but these errors were encountered: