Just to be more precise, I have
host1--switch1--switch2-host2
and on both switches I have
ofdatapath --detach punix:/var/run/dp0 -d -i br-lan
ofprotocol unix:/var/run/dp0 tcp:10.92.0.100:6633 --fail=closed
Thanks a lot! waiting forward for some ideas,
regards,
diana
On Sat, Jun
Hello,
I tried to set in ofprotocol the argument: "--fail=closed" , but nothing
has changed in the behavior of the switch. (I checked the list of arguments
that you can pass to ofprotocol using "--help arguments" and tryed to set
the max_backoff and the no-spt and the result was the same.
Also I
I believe when your switch connects to NOX , NOX sends a flow_mod to delete
whatever's in your flow_table so I don't think your solution would work
unless you installed a permanent flow right before you disconnected your
controller. That said I'm not sure what the behavior of this particular
switch
Thank you Aaron,
I would like in the beginning to set my switch to do nothing, meaning not
to forward any traffic if I don't have the controller started or flows
installed.
Then I would like to use NOX and set some flows or set them directly with
dpctl. Now, if I use a flag OFP_FLOW_PERMANENT dos
That means that the switch fails open aka will act as a normal L2 learning
switch if it loses its connection with the controller.
>From the 1.0 spec -- NORMAL: Process the packet using the traditional
forwarding path
supported by the switch (i.e., traditional L2, VLAN, and L3 processing.)
The swit
Hello all,
I've been using a bit of Mininet and you know that when just creating a
network and trying to ping for example this dosen't work, Than you start
the controller and miracle happens. On the other hand on real devices
(Linksys and TP-link with openwrt and openflow 1.0) this is not the case
