Thanks, this solves the issue.
-Tapio
From: ext Murphy McCauley [mailto:jam...@nau.edu]
Sent: Saturday, September 17, 2011 11:55 AM
To: Partti, Tapio (NSN - FI/Espoo)
Cc: nox-dev@noxrepo.org
Subject: Re: [nox-dev] python flow fetcher request with network address
fields specified
No
It's destiny and I tested with the latest updates. I'm on 64 bit
machine.
-Tapio
From: ext Murphy McCauley [mailto:jam...@nau.edu]
Sent: Friday, September 16, 2011 11:21 AM
To: Partti, Tapio (NSN - FI/Espoo)
Cc: nox-dev@noxrepo.org
Subject: Re: [nox-dev] python flow fetcher re
Hi,
I have trouble using the python flow fetcher. I can successfully fetch
flows as long as the request doesn't contain uint32_t types on fields,
i.e. nw_src or nw_dst. No matter what values I use, only the first two
bytes will be non-zero. For example, if I construct the request like
this:
Flow_
Hi,
I'm trying to setup flows so that a 'route' is installed through a
topology of OVSs. Using setup_route() from pyrouting does this for me,
but I'm not sure how to set actions for different OVSs along the route.
In C++ api the setup_route function seems to take in a list of actions
but not in py
011 02:37:47 AM Partti, Tapio (NSN - FI/Espoo)
wrote:
> Hi all.
>
> When giving out a subprocess call (with subprocess.check_call) in any
> event's callback function, nox gives out the following error.
>
> 3|reactor|ERR:Unhandled Error
>
Hi all.
When giving out a subprocess call (with subprocess.check_call) in any
event's callback function, nox gives out the following error.
3|reactor|ERR:Unhandled Error
Traceback (most recent call last):
--- ---
File "./nox/coreapps/pyrt/pyoxidereactor.py", line 85
