search

netgroup / srv6-mininet-extensions

Mininet extensions for SRv6
Apache License 2.0
15 stars 5 forks source link

Connection Error #3

Open jorgesysg036 opened 5 years ago

jorgesysg036 commented 5 years ago

Hi.

I continue working in the project, I solved a mistake with Quagga, it is working and the links is UP, this is my scenarie.

Links

"lhs_intf": "sur1-eth2", "lhs_ip": "fdf0:0:0:2::2", "rhs_intf": "sur1-eth1", "rhs_ip": "fdf0:0:0:1::2", "lhs_intf": "ads2-eth1", "lhs_ip": "fdf0::2", "rhs_intf": "ads2-eth2", "rhs_ip": "fdf0:0:0:2::1", "rhs_intf": "ads1-eth1", "rhs_ip": "fdf0::1", "lhs_intf": "ads1-eth2", "lhs_ip": "fdf0:0:0:1::1",

When I connect to ads1, and there I do a ping to ads2 (fdf0:0:0:2::1), it work, but when I add the route SRv6

ip -6 r a fdf0:0:0:2::1/128 encap seg6 mode encap segs 2002::3 dev ads1-eth1

I lost the connection, the ping does not have reply, after i delete the route

ip -6 r d fdf0:0:0:2::1/128 encap seg6 mode encap segs 2002::3 dev ads1-eth1

it work again.

Can you please help me?, Do i have to do addiotional configuration?

cscarpitta commented 4 years ago

Hi, you are trying to steer the traffic destined to fdf0:0:0:2::1 through 2002::3, but I guess this address is not assigned to any interface in the network. Therefore the router drops the ping packets.

Please, could you provide a valid segment list and try to ping again?

For example, you can steer the traffic destined to fdf0:0:0:2::1 through the interface ads2-eth1 by installing the SRv6 route: ip -6 r a fdf0:0:0:2::1 encap seg6 mode encap segs fdf0::2 dev ads1-eth1

Regards, Carmine

jorgesysg036 commented 4 years ago

Thank you so much.

That was the problem, it is working. Thank you and sorry but i new in this.

jorgesysg036 commented 4 years ago

HI. thanks for your help. I am working witout problems, I can see how the performance is. The topology has accepted the SRv6 Policies. It is working, but I am confused about the routing in this project(https://github.com/netgroup/srv6-mininet-extensions), when i load your default topology "example_srv6_topology.json", There, the nodes have a connection via eth0 to br-mgmt, is this a SDN controller or is quagga who gives the routing functions to the nodes?

cscarpitta commented 4 years ago

Hi, br-mgmt is a virtual switch running OVSBridge which creates a management network 2000::/24. Each node has a eth0 interface connected to this management network. Our SDN controller prototype (https://github.com/netgroup/srv6-controller) communicates out-of-band with the nodes through the management network.

This figure shows the topology that you are trying to emulate: image

Regards, Carmine