[server_lb] ERROR: packet (dns) parsing answers: Bad address format

[capachivas]

When I run pyretic.py pyretic.pyresonance.main --config=./pyretic/pyresonance/global.config --mode=manual

with server_lb activated in global.config

this error appears (alterning these two and continuously appearing):
ERROR: packet (dns) parsing answers: Bad address format (error1)
ERROR: packet (dns) parsing authoritative name servers: Bad address format (error2)

PD: I have been testing and I found that the error 1 comes from the file addresses.py (/pox/pox/lib) and it is a raise RuntimeError exception but I do not know more
Also, error 2 comes pox/pox/lib/packet/dns.py self._exc(e, 'parsing authoritative name servers')
Thanks in advance

[hyojoonkim]

Hello,

I am not able to replicate this problem. Seems it has some problems with POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM, or Pyretic VM, or your own environment?
• Does this happen only when you run server_lb? How are other apps running?
• Did you get the latest POX code? If you have the VM environment, you can go to "/home/mininet/pox", and do "git pull". Also, make sure you are on the "carp" branch. This is by default in the VMs. Giving a command "git branch" should tell you which branch you are on.
• Also, please get the latest Pyretic code by doing "git pull" in "/home/mininet/pyretic".

Thanks,
Joon

[capachivas]

Hello

• Where are you running this? Is it in the provided Pyresonance VM, or
  Pyretic VM, or your own environment?

is in my own VM environment (ubuntu 13.10)

• Does this happen only when you run server_lb? How are other apps
  running?

I only run server_lb nothing else (the other modules work well)

• Did you get the latest POX code? If you have the VM environment, you
  can go to "/home/mininet/pox", and do "git pull". Also, make sure you are
  on the "carp" branch. This is by default in the VMs. Giving a command "git
  branch" should tell you which branch you are on.

Maybe the branch I use is not correct I will check it

• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Is the latest code, in fact I had to reinstall it again for making
pyresonance work

Thanks for your support

2013/11/25 Hyojoon Kim notifications@github.com

Hello,

I am not able to replicate this problem. Seems it has some problems with
POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM, or
  Pyretic VM, or your own environment?
• Does this happen only when you run server_lb? How are other apps
  running?
• Did you get the latest POX code? If you have the VM environment, you
  can go to "/home/mininet/pox", and do "git pull". Also, make sure you are
  on the "carp" branch. This is by default in the VMs. Giving a command "git
  branch" should tell you which branch you are on.
• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Thanks,
Joon

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29233085
.

José Manuel Sánchez

[capachivas]

I have checked : I am in carp branch in POX, maybe I will have to get the
last version

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

Hello

• Where are you running this? Is it in the provided Pyresonance VM, or
  Pyretic VM, or your own environment?

is in my own VM environment (ubuntu 13.10)

• Does this happen only when you run server_lb? How are other apps
  running?

I only run server_lb nothing else (the other modules work well)

• Did you get the latest POX code? If you have the VM environment, you
  can go to "/home/mininet/pox", and do "git pull". Also, make sure you are
  on the "carp" branch. This is by default in the VMs. Giving a command "git
  branch" should tell you which branch you are on.

Maybe the branch I use is not correct I will check it

• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Is the latest code, in fact I had to reinstall it again for making
pyresonance work

Thanks for your support

2013/11/25 Hyojoon Kim notifications@github.com

Hello,

I am not able to replicate this problem. Seems it has some problems with
POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM,
  or Pyretic VM, or your own environment?
• Does this happen only when you run server_lb? How are other apps
  running?
• Did you get the latest POX code? If you have the VM environment,
  you can go to "/home/mininet/pox", and do "git pull". Also, make sure you
  are on the "carp" branch. This is by default in the VMs. Giving a command
  "git branch" should tell you which branch you are on.
• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Thanks,
Joon

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29233085
.

José Manuel Sánchez

José Manuel Sánchez

[capachivas]

When I run mininet topology provided in pyresonance mininet_topo folder, it
starts giving those errors

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

I have checked : I am in carp branch in POX, maybe I will have to get the
last version

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

Hello

• Where are you running this? Is it in the provided Pyresonance VM,
  or Pyretic VM, or your own environment?

is in my own VM environment (ubuntu 13.10)

• Does this happen only when you run server_lb? How are other apps
  running?

I only run server_lb nothing else (the other modules work well)

• Did you get the latest POX code? If you have the VM environment,
  you can go to "/home/mininet/pox", and do "git pull". Also, make sure you
  are on the "carp" branch. This is by default in the VMs. Giving a command
  "git branch" should tell you which branch you are on.

Maybe the branch I use is not correct I will check it

• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Is the latest code, in fact I had to reinstall it again for making
pyresonance work

Thanks for your support

2013/11/25 Hyojoon Kim notifications@github.com

Hello,

I am not able to replicate this problem. Seems it has some problems with
POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM,
  or Pyretic VM, or your own environment?
• Does this happen only when you run server_lb? How are other apps
  running?
• Did you get the latest POX code? If you have the VM environment,
  you can go to "/home/mininet/pox", and do "git pull". Also, make sure you
  are on the "carp" branch. This is by default in the VMs. Giving a command
  "git branch" should tell you which branch you are on.
• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Thanks,
Joon

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29233085
.

José Manuel Sánchez

José Manuel Sánchez

José Manuel Sánchez

[hyojoonkim]

Ah, I see.

Can you give the exact command when you are running mininet? Are you
giving the controller address not to 127.0.0.1 but somewhere else?

-Joon

On 11/25/2013 02:45 PM, capachivas wrote:

When I run mininet topology provided in pyresonance mininet_topo
folder, it
starts giving those errors

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

I have checked : I am in carp branch in POX, maybe I will have to
get the
last version

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

Hello

• Where are you running this? Is it in the provided Pyresonance VM,
  or Pyretic VM, or your own environment?

is in my own VM environment (ubuntu 13.10)

• Does this happen only when you run server_lb? How are other apps
  running?

I only run server_lb nothing else (the other modules work well)

• Did you get the latest POX code? If you have the VM environment,
  you can go to "/home/mininet/pox", and do "git pull". Also, make
  sure you
  are on the "carp" branch. This is by default in the VMs. Giving a
  command
  "git branch" should tell you which branch you are on.

Maybe the branch I use is not correct I will check it

• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Is the latest code, in fact I had to reinstall it again for making
pyresonance work

Thanks for your support

2013/11/25 Hyojoon Kim notifications@github.com

Hello,

I am not able to replicate this problem. Seems it has some
problems with
POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM,
  or Pyretic VM, or your own environment?
• Does this happen only when you run server_lb? How are other apps
  running?
• Did you get the latest POX code? If you have the VM environment,
  you can go to "/home/mininet/pox", and do "git pull". Also, make
  sure you
  are on the "carp" branch. This is by default in the VMs. Giving a
  command
  "git branch" should tell you which branch you are on.
• Also, please get the latest Pyretic code by doing "git pull" in
  "/home/mininet/pyretic".

Thanks,
Joon

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/10#issuecomment-29233085
.

José Manuel Sánchez

José Manuel Sánchez

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
#10 (comment).

-Joon

[capachivas]

this is the command

sudo mn --controller=remote,ip=127.0.0.1 --custom
mininet_topos/example_topos.py --topo ratelimit --link=tc --mac --arp

no matter what topology of the three available I run (linear, ratelimit or
server_lb) It does the same.

The problem starts when I run mininet, until the controller is running
withouth mininet is fine

2013/11/25 Hyojoon Kim notifications@github.com

Ah, I see.

Can you give the exact command when you are running mininet? Are you
giving the controller address not to 127.0.0.1 but somewhere else?

-Joon

On 11/25/2013 02:45 PM, capachivas wrote:

When I run mininet topology provided in pyresonance mininet_topo
folder, it
starts giving those errors

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

I have checked : I am in carp branch in POX, maybe I will have to
get the
last version

2013/11/25 José Manuel Sánchez Vílchez <
jose.manuel.sanchez.vilchez@gmail.com>

Hello

• Where are you running this? Is it in the provided Pyresonance VM,

or Pyretic VM, or your own environment?

is in my own VM environment (ubuntu 13.10)

• Does this happen only when you run server_lb? How are other apps

running?

I only run server_lb nothing else (the other modules work well)

• Did you get the latest POX code? If you have the VM environment,

you can go to "/home/mininet/pox", and do "git pull". Also, make
sure you
are on the "carp" branch. This is by default in the VMs. Giving a
command
"git branch" should tell you which branch you are on.

Maybe the branch I use is not correct I will check it

• Also, please get the latest Pyretic code by doing "git pull" in

"/home/mininet/pyretic".

Is the latest code, in fact I had to reinstall it again for making
pyresonance work

Thanks for your support

2013/11/25 Hyojoon Kim notifications@github.com

Hello,

I am not able to replicate this problem. Seems it has some
problems with
POX. So I have some questions:

• Where are you running this? Is it in the provided Pyresonance VM,

or Pyretic VM, or your own environment?

• Does this happen only when you run server_lb? How are other apps
  running?
• Did you get the latest POX code? If you have the VM environment,

you can go to "/home/mininet/pox", and do "git pull". Also, make
sure you
are on the "carp" branch. This is by default in the VMs. Giving a
command
"git branch" should tell you which branch you are on.

• Also, please get the latest Pyretic code by doing "git pull" in

"/home/mininet/pyretic".

Thanks,
Joon

—
Reply to this email directly or view it on
GitHub<
#10 (comment)

.

José Manuel Sánchez

José Manuel Sánchez

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
<
#10 (comment)
.

-Joon

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29235327
.

José Manuel Sánchez

[hyojoonkim]

I will look into this more. I may have to ask Josh, who is the Pyretic
developer.

For information, can you give me your Python version, and your Mininet
version?

mn --version
python --version

commands would do.

Thanks,
Joon

On 11/25/2013 02:54 PM, capachivas wrote:

this is the command

sudo mn --controller=remote,ip=127.0.0.1 --custom
mininet_topos/example_topos.py --topo ratelimit --link=tc --mac --arp

no matter what topology of the three available I run (linear,
ratelimit or
server_lb) It does the same.

The problem starts when I run mininet, until the controller is running
withouth mininet is fine

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
#10 (comment).

-Joon

[capachivas]

of course,

mininet 2.1.0 master branch

python 2.7.5+

thank you again

2013/11/25 Hyojoon Kim notifications@github.com

I will look into this more. I may have to ask Josh, who is the Pyretic
developer.

For information, can you give me your Python version, and your Mininet
version?

mn --version
python --version

commands would do.

Thanks,
Joon

On 11/25/2013 02:54 PM, capachivas wrote:

this is the command

sudo mn --controller=remote,ip=127.0.0.1 --custom
mininet_topos/example_topos.py --topo ratelimit --link=tc --mac --arp

no matter what topology of the three available I run (linear,
ratelimit or
server_lb) It does the same.

The problem starts when I run mininet, until the controller is running
withouth mininet is fine

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
<
#10 (comment)
.

-Joon

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29237408
.

José Manuel Sánchez

[hyojoonkim]

Cool.

Just in case we cannot find the problem, you can go ahead and use these
VMs with VirtualBox.

http://resonance.noise.gatech.edu/data/PyResonance_0.2.0_32bit.ova
http://resonance.noise.gatech.edu/data/PyResonance_0.2.0_64bit.ova

Also, in case we cannot replicate your errors, it would help if you can
export and send us your VM in OVA format (if you have a storage space
where I can download it from)

Thanks,
Joon

On 11/25/2013 03:16 PM, capachivas wrote:

of course,

mininet 2.1.0 master branch

python 2.7.5+

thank you again

2013/11/25 Hyojoon Kim notifications@github.com

I will look into this more. I may have to ask Josh, who is the Pyretic
developer.

For information, can you give me your Python version, and your Mininet
version?

mn --version
python --version

commands would do.

Thanks,
Joon

On 11/25/2013 02:54 PM, capachivas wrote:

this is the command

sudo mn --controller=remote,ip=127.0.0.1 --custom
mininet_topos/example_topos.py --topo ratelimit --link=tc --mac --arp

no matter what topology of the three available I run (linear,
ratelimit or
server_lb) It does the same.

The problem starts when I run mininet, until the controller is
running
withouth mininet is fine

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
<

#10 (comment)

.

-Joon

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/10#issuecomment-29237408
.

José Manuel Sánchez

—
Reply to this email directly or view it on GitHub
#10 (comment).

-Joon

[capachivas]

The error is given by the topology, not by server_lb module. In fact, I consider is a POX-related problem.

sudo mn --controller=remote,ip=127.0.0.1 --custon mininet_topos/example_topos.py --topo ratelimit --link=tc --mac --arp

Because, when I run it with auth and ids in golbal.config with the same topology it also gives the error.

What is more, I think that when the topology has more than one switch it gives this error:

I ran linear topologies and in all the cases with more than one switch (linear 2,3 and 4) it gives me the error.
When I run linear with one switch, the error is not present.

To discard that the error is given by more than one host I also ran a tree topology:
--topo=tree, 1 (only one switch and two hosts) but not error is present
--topo=tree, 2 (3 switches and 4 hosts) the error appears.

Appearantly, the error seems to be due to the fact that it has to deal with more than one switch.

I hope this may help to find the error

[hyojoonkim]

Sorry for the late reply. I am still looking into this.

Can you try to run a Pyretic program? Run:
pyretic.py pyretic.modules.mac_learner

And then start a mininet topology with 3 switches.
sudo mn --controller=remote,ip=127.0.0.1 --topo=linear,3 --link=tc --mac --arp

Does that also give you an error? Then it seems to be a problem not related to PyResonance.

Also, try starting a mininet topology without an external controller (i.e., POX)
sudo mn --topo=linear,3 --link=tc --mac --arp

This should use the local ovs-controller instead. Does this produce any errors?

Make sure you do "sudo mn -c" when mininet topology was not teared down normally.

[capachivas]

I answer you in each of the questions:

2013/12/2 Hyojoon Kim notifications@github.com

Sorry for the late reply. I am still looking into this.

Can you try to run a Pyretic program? Run:
pyretic.py pyretic.modules.mac_learne

And then start a mininet topology with 3 switches.
sudo mn --controller=remote,ip=127.0.0.1 --topo=linear,3 --link=tc --mac
--arp

Does that also give you an error? Then it seems to be a problem not
related to PyResonance.

When I connect the mininet environment it gives the same error.ERROR :
packet (dns) parsing answers: bad format address (strange symbols written
beside)

As complementary information, if you launch a one-switched network in
mininet likesudo mn --controller=remote,ip=127.0.0.1 --topo=linear,1
--link=tc --mac --arpsudo mn --controller=remote,ip=127.0.0.1 --topo=tree,1
--link=tc --mac --arp

No error is shown in the Pyretic window

Also, try starting a mininet topology without an external controller
(i.e., POX)
sudo mn --topo=linear,3 --link=tc --mac --arp

This should use the local ovs-controller instead. Does this produce any
errors?

This step does not give any errors at all.

—

Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-29590968
.

José Manuel Sánchez

[hyojoonkim]

Hmm.. So it really looks like it's an issue with POX. Just to confirm, try this inside the pox directory.
python pox.py pox.forwarding.l2_learning

then spawn mininet:
sudo mn --controller=remote,ip=127.0.0.1 --topo=linear,3 --link=tc --mac --arp

If this gives you the same errors, it's likely to be some problem with POX and Mininet not working well together in your VM environment, and not about Pyretic and Pyresonance. It's hard for me to debug this because I cannot replicate it, and I don't know all the details about the POX controller. You may have better luck asking the POX community. I could not find any related issues in the pox-dev mailing list though (dns bad address format issue).

Sorry I cannot provide better help. Were you at least able to run without problems with the provided pre-built VM?

-Joon

[pnnngchg]

Hi，I have some similar problems like capachivass . And I downloaded hyojoonkims .ova file to test . But when I run it in my virtual machine , it asked me to login and input password . Could you tell me the username and password , so I could test my code with the .ova file ? It`s been a long time , could you please reply to me ? Thanks a lot !

[hyojoonkim]

Hi, Please try: username: mininet password: mininet Thanks, Joon

[pnnngchg]

Thanks a lot !