Idea is to embed the port numbers of the path in the packet and carry out
source routing
From floodlight I get the normal port numbers. If I embed these regular
port numbers then the difficulty is that the switches recognise only the
datapath port numbers. So I cannot carry out routing as I expect.
> On Nov 15, 2015, at 10:36 PM, Sree Vidya S D wrote:
>
> Hey Justin,
> Thanks for your time
>
> The mapping I need is datapath port number.
There's no way to control the datapath port number. (You can, however, control
the OpenFlow port number through OVSDB.) But why do you care about the
Hey Justin,
Thanks for your time
The mapping I need is datapath port number.
Is there any way in which I can make the datapath port numbers sequential?
eg system@ovs-system:
lookups: hit:155 missed:948 lost:0
flows: 4
masks: hit:4052 total:5 hit/pkt:3.67
port 0: ovs-system (internal)
port 1: s1
> On Nov 15, 2015, at 9:35 PM, Sree Vidya S D wrote:
>
> Hey,
>
> Snap of *sudo ovs-dpctl show *output for a random topology
>
>
> system@ovs-system:
> lookups: hit:2069 missed:2861 lost:0
> flows: 0
> masks: hit:7849 total:1 hit/pkt:1.59
> port 0: ovs-system (internal)
> port 1: s38 (interna
Hey,
Snap of *sudo ovs-dpctl show *output for a random topology
system@ovs-system:
lookups: hit:2069 missed:2861 lost:0
flows: 0
masks: hit:7849 total:1 hit/pkt:1.59
port 0: ovs-system (internal)
port 1: s38 (internal)
port 2: s38-eth1
port 3: s38-eth2
port 4: s38-eth3
port 5: s45 (internal)
por
