Ostinato-drone picks wrong interface in EVE-NG

[bardi...@gmail.com]

Hi Srivats,

First of all thank you for your efforts in creating this amazing tool!

I have a test setup in EVE-NG with Ostinato-drone ver 0.8.

When I create a port-group with the drone mgmt address Ostinato automatically picks the interface which is pointing towards mgmt interface (pnet0 cloud) not the Lab.

I'm not able to change it anyhow

Could you please help with this?

Cheers

Anton

[Srivats P]

Anton,

I suspect you are using the same IP address as what you use to telnet into the ostinato-drone console as the port group address in the Ostinato GUI.

You need to telnet into the ostinato-drone's console and get the IP address assigned to eth0. Then use that IP address as the port group in Ostinato GUI.

HTH,

Srivats (Author, Ostinato)

--
Get Ostinato News and Updates on Twitter - Follow @ostinato (http://twitter.com/ostinato)
---
You received this message because you are subscribed to the Google Groups "ostinato" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/3b7d6ce1-5956-4e3c-b661-1b293d073620o%40googlegroups.com.

--

Srivats P (Author, Ostinato)

[bardi...@gmail.com]

Thanks for the quick response

I did a few attempts and found out that a drone always picks Eth1 in a port-group.

So if a eve-ng drone node has Eth0 and Eth1, Eth1 will be selected in a port-group despite of assigned IP address.

It's not a big deal as I simply swapped the interfaces in the Ostinato eve-ng node - so all good.

The reason for using one interface for the drone management and the other interface for traffic generation/capture is to get get the drone management out-of-band so not to affect testing results. 

Thanks again 

[Srivats P]

Anton,

I'm a little confused.

By default, EVE-NG's drone image will use eth0 as the mgmt interface and eth1 for data traffic generation. To do that, the eth0 on the drone VM gets a DHCP assigned IP address which you specify when you do a Add Port Group in the Ostinato GUI. eth1 on the drone VM will not have any IP address by default - you can assign one manually if you want - but it is still used for data traffic only, not for mgmt.

e.g. in my EVE-NG installation, the EVE-NG web interface is accessible at 192.168.1.9 - when I add a drone image to it, it tells me the console of the drone is accessible at telnet://192.168.1.9:32769 - if I telnet to that, I get the drone VM console. I type ifconfig and notice that eth0 has been assigned 192.168.1.14 by DHCP and eth1 has no IP address. In Ostinato GUI, I add a port group by specifying 192.168.1.14

Is it different in your case? What are the various IP addresses in your case?

Srivats (Author, Ostinato)

--

Get Ostinato News and Updates on Twitter - Follow @ostinato (http://twitter.com/ostinato)
---
You received this message because you are subscribed to the Google Groups "ostinato" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/d994318d-cd7f-4b2b-bad1-7ca4e7f4e351o%40googlegroups.com.

[Anton Bardin]

HI Srivats,

apologies for not coming back earlier - a bit under the pump at work now.

Here is my cases illustrated below:

Case 1 - eth 1 is the data generation interface, eth0 - mgmt

Case 2 - is a vice versa with eth1 to be the mgmt while eth0 is for data generation however drone always picks eth1 in a port group regardless.

You have mentioned this is the default behaviour  for eth1 to generate / eth0 - mgmt)so I'm all clear now about the drone's logic

THank you! 

 

Case 2

Anton