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

How to know, if Odin is sending any response to the Agent #12

Open
uhlik1889 opened this issue Feb 26, 2019 · 3 comments
Open

How to know, if Odin is sending any response to the Agent #12

uhlik1889 opened this issue Feb 26, 2019 · 3 comments

Comments

@uhlik1889
Copy link

I have successfully connected agent with controller in Mininet-Wifi environment, but I have one problem. Controller has shown me that new agent is on 127.0.0.1 as expected. When I create probe request, the agent shows that it has a right essid and that it is sending the request to the controller. I can see this message in the wireshark as well, in the form of UDP packet. But from this point, I don't know, what controller did with this message. On his terminal it is showing no new messages, just that one with the new agent connected.

Any ideas?

@josemariasaldana
Copy link
Member

One idea could be to follow the Sanity Check: https://github.com/Wi5/odin-wi5/wiki/Sanity-check

@uhlik1889
Copy link
Author

Ok I am checking those, but everything seems to be fine. One thing there is troubling me, and that is in the initializing agent.

agent.cli:88: While initializing ‘from_dev1 :: FromDevice’:
warning: mon1: no IPv4 address assigned

I know it has no IP address, I wasn't assigning any. Should I?
and

|WARN|system@ovs-system: failed to add mon0 as port: Invalid argument
|INFO|mon0 device has unknown hardware address family 803

After I turned that into monitoring mode, it has problem with address family.

@josemariasaldana
Copy link
Member

Hi,

I have checked and my wlan1 does NOT have an IP address.

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

No branches or pull requests

2 participants