Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2.0] bug with capture #1656

Closed
Raizo62 opened this issue Nov 11, 2016 · 26 comments
Closed

[2.0] bug with capture #1656

Raizo62 opened this issue Nov 11, 2016 · 26 comments
Labels
Milestone

Comments

@Raizo62
Copy link

Raizo62 commented Nov 11, 2016

I use an empty config of GNS3

  • I put a vpcs connected to an ethernet switch. I don't start theses devices.
  • I put wireshark on the link.
  • I start the device.
  • On the VPCS, i do "ip dhcp".

On wireshark, i should see the DHCPDiscover. I see nothing

@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Nov 11, 2016
@julien-duponchelle
Copy link
Contributor

I made a quick test and it's work my mac. We need to test on Linux.

@Raizo62
Copy link
Author

Raizo62 commented Nov 17, 2016

Have you can test on Linux ? (just to know that you can reproduce it ;-) )

@julien-duponchelle
Copy link
Contributor

I just tested the exact scenario on ubuntu 16.10 and it's work without problem.

@julien-duponchelle
Copy link
Contributor

Other captures work?

@Raizo62
Copy link
Author

Raizo62 commented Nov 17, 2016

I have the bug also with Debian.
But with Router Cisco, i see the DHCPDiscover.

If you want, tonight i create a live with last files of GNS3 and i send you the iso. You will can test.

@julien-duponchelle
Copy link
Contributor

How do you install VPCS?

On Thu, Nov 17, 2016 at 4:32 PM Raizo62 notifications@github.com wrote:

I have the bug also with Debian.
But with Router Cisco, i see the DHCPDiscover.

If you want, tonight i create a live with last files of GNS3 and i send
you the iso. You will can test.


You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#1656 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVFXQALyScqGhVsGoaVEIsjkpyjdOAdks5q_HNEgaJpZM4KvpAI
.

@Raizo62
Copy link
Author

Raizo62 commented Nov 17, 2016

(I sent you the link with the live)

How do you install VPCS?

cd vpcs/src
./mk.sh

must i change ?

@julien-duponchelle
Copy link
Contributor

Ok I found the issue.

Your version of VPCS is broken. The 0.8X series is not yet stable and we don't recommend it.

We recommend to use VPCS 0.6.1 (VPCS 0.6 + some back ported patch by us)

@Raizo62
Copy link
Author

Raizo62 commented Nov 18, 2016

I have tested with the last source "master" from github of GNS3.
I have always the bug.

Is it correct that the version of your vpcs is 0.8c ?

@julien-duponchelle
Copy link
Contributor

It should be 0.6.1

Le ven. 18 nov. 2016 20:34, Raizo62 notifications@github.com a écrit :

I have tested with the last source "master" from github of GNS3.
I have always the bug.

Is it correct that the version of your vpcs is 0.8c ?


You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#1656 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVFXeP5pHTgoLzSUfxMaVnEj_3krLCtks5q_f2bgaJpZM4KvpAI
.

@Raizo62
Copy link
Author

Raizo62 commented Nov 18, 2016

In this file : vpcs of gns3
const char *ver = "0.8c";

@ghost
Copy link

ghost commented Nov 18, 2016

https://github.com/GNS3/vpcs/releases/tag/v0.6.1 gives you access v0.6.1 (linux binary, OS X binary and source).

@ghost
Copy link

ghost commented Nov 18, 2016

Don't know, if it's helpful, but on v1.5.3dev1 vpcs running in my own debian stretch based GNS3VM works with both versions (0.6.1 and 0.8c) in your scenario. I can't test with 2.0, as currently I need a stable GNS3.

@Raizo62
Copy link
Author

Raizo62 commented Nov 18, 2016

Me too, this scenario works with vpcs 0.8c and GNS3 v1.5.3dev1 on Debian Jessie Backport.

@Raizo62
Copy link
Author

Raizo62 commented Nov 19, 2016

And vpcs issue does not explain why i have also this bug when i replace vpcs by my Debian Vbox (but, yes, i know that we can have more of 1 bug ;-) )

@Raizo62
Copy link
Author

Raizo62 commented Nov 19, 2016

I have tested with vpcs v0.6.1 : always, no DHCPDiscover

@julien-duponchelle
Copy link
Contributor

Did you install it with our packet? It was working for me with LiveRaizo and the GNS3 vpcs packet.

I'm mostly sure 0.8c has a memory issue because it's just crash on OSX. But we didn't manage to isolate the issue with VPCS author.

@Raizo62
Copy link
Author

Raizo62 commented Nov 21, 2016

I think that your "debian package" is for ubuntu OS (ppa).
I have compiled VPCS 6.1 (but, perhaps, i have used the bad commit)

Be careful, i didn't say that vpcs crashs : if i put also an DHCP Server (with VM), vpcs has an IP. But, wireshark doesn't show the packets. For me, the bug is with "wireshark capture"

I am surprised that it was working for you with LiveRaizo v8 : i have tested on my portable PC and on VirtualBox on another PC.

Tonight, i will try to use your ppa : perhaps you have a different option of compilation

@julien-duponchelle
Copy link
Contributor

PPA for ubuntu work for debian.

Each version of ubuntu is base on a version of Debian, you just need to use the correct:
https://gns3.com/support/docs/linux-installation

That 's strange because before changing VPCS it was just not working for me. No capture, No DHCP. After changing it I no longer have issue. I test again with your LiveRaizo and it's work even with the 0.8:
capture d ecran 2016-11-21 a 14 48 17

If you have DHCP but no packets captures. Could be an issue with ubridge. Or Wireshark is not correctly installed (your user need to be a member of the wireshark group).

@Raizo62
Copy link
Author

Raizo62 commented Nov 21, 2016

your user need to be a member of the wireshark group

only if we don't use the capability ? (I use capability with Live Raizo)
I have tested for see on an old v8, but not changing

I don't understand if it works with your Live Raizo v8
Are you configure the capture before to start the lab ? (if i do it after, i see the packets)

@julien-duponchelle
Copy link
Contributor

I's work with the LiveRaizo you provide me. I can start the capture before I start the lab.

@Raizo62
Copy link
Author

Raizo62 commented Nov 21, 2016

I have do several tests to understand why you don't have the same issue as me with the same OS.

I use vpcs 6.1 (not yet ppa)

Perhaps i have the explain :

  • If i connect the cable first on the ethernet switch, wireshark shows packet (i see also one ipv6 router solicitation)
  • If i connect the cable first on the vpcs, wireshark shows nothing

How do you make ?

@julien-duponchelle
Copy link
Contributor

Ok I confirm in this order it's not working in LiveRaizo (need to test on other hosts)

@julien-duponchelle
Copy link
Contributor

Ok in this oder it's not working on any OS.

Good catch

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Nov 22, 2016
@julien-duponchelle
Copy link
Contributor

Big patch:

Now:

  • capture is not possible if one one the node is not running
  • when we choose the best node for running capture we start by node always running
  • if you stop the node where capture is running the capture stop

Should cover all the use cases.

@Raizo62
Copy link
Author

Raizo62 commented Nov 22, 2016

Ouf.... I was beginning to believe that i was fool ;-)
Thanks :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants