I just mean that there is no OpenFlow "NAT" action in the same way as there is
an output action, for example. NAT is a higher-level idea which is only ever
fully expressed at the controller, which results in lower-level things (e.g.,
IP rewriting) happening at the switch.
As for another way of
Hello,
Thank you for your comments
But i did not understand how NAT is not an action
Is there a way of doing NATing other than what i post in my email; if there is
may you help me in how to do it.
Best regards,
Amer
في ٣١/٠٨/٢٠١٣، الساعة ١١:٣٧ م، كتب "Murphy McCauley"
:
> On Aug 31, 2013
On Aug 31, 2013, at 4:12 AM, AMER AL-GHADHBAN wrote:
> I am using pox with mininet v2.0
> the main code in my controller is ideal-pairwise-switch
Is this something you wrote, or something you found? It's not one of POX's
packaged components.
> My topology is 2 connected switches and 3 hosts i
I apologize for the lack of information
I am using pox with mininet v2.0
the main code in my controller is ideal-pairwise-switch
My topology is 2 connected switches and 3 hosts in each
i am trying to do NAT between the switches# i do not know should I exclude ARP
pkts from NATing #
I have adde
Please see the final entry of the POX FAQ:
https://openflow.stanford.edu/display/ONL/POX+Wiki
-- Murphy
On Aug 30, 2013, at 2:19 PM, AMER AL-GHADHBAN wrote:
> Hello,
>
> Hope you the best of wealth :)
>
> Some times I am facing this error:
> AttributeError: 'ipv4' object has no attribute 'p
Hello,
Hope you the best of wealth :)
Some times I am facing this error:
AttributeError: 'ipv4' object has no attribute 'protodst'
if i do:
h2 ping -c3 h1 # i received no echo messages at all
and after some seconds when i try it again it is pinging without any errors
best wishes
Eng Amer A
