Yeah. The last couple commits on destiny actually partially and sort of
haphazardly confronted this. Just pushed what is hopefully a more complete
patch.
-- Murphy
On Aug 26, 2011, at 4:45 PM, Edward Balas wrote:
> Hey all,
>
> Does anyone know if the NOX python API has been tested on 64 bi
We routinely run Nox (including Python) on 64 bit systems. However,
that doesn't mean we're exercising the same code paths ...
Hey all,
Does anyone know if the NOX python API has been tested on 64 bit systems?
What I have run into looks like the 32 bit value is being stored in the high
orde
Hey all,
Does anyone know if the NOX python API has been tested on 64 bit systems?
What I have run into looks like the 32 bit value is being stored in the high
order 32 bits
of a 64bit int type. Ex. 0x7FFF for a port's curr value returned in a
datapath_join
event. A type call in pyth
Well, I think at least part of the reason that it keeps trying to look things
up is because you keep not answering. I think if you answered, it'd stop
asking so much. So... hopefully the answer is yes.
-- Murphy
On Aug 26, 2011, at 6:08 AM, IBRAHIM MENEM wrote:
> Hi Murphy,
>
> firstly,Than
Hi Murphy,
firstly,Thanks for your great help :D
Actually, I'm now hard codding the addresses and for the moment I'll
use a file to make nox my dns server. I'll try to solve the reverse
lookups problem as you suggested, however ping is not what i want to do,
so if connectivity is achieved "ping -n
How does your DNS component in NOX work? Does it just query some other server?
Or have you entered your own list of addresses?
I think what you are seeing is because ping *does* try to resolve a name for
every ping. Specifically, I think something like the following is happening:
ping does a
Sorry!! I didn't see the -n :o
yes, with ping -n it works perfectly, the only problem is the DNS request for
every ping.
Ibrahim,
From: ibrahim.me...@alumnos.upm.es
To: jam...@nau.edu
CC: nox-dev@noxrepo.org
Subject: RE: [nox-dev] Adding DNS functionality to nox
Date: Fri, 26 Aug 2011 14:02
Just to verify:
That's even with ping -n ?
-- Murphy
On Aug 26, 2011, at 5:02 AM, ibrahim mun wrote:
> It takes about 45 sec to respond, and it sends dns request for every ping!
> however, nslookup responds in 0 sec. Also, no more unknown host messages.
>
> Ibrahim,
>
> Subject: Re: [nox-dev
It takes about 45 sec to respond, and it sends dns request for every ping!
however, nslookup responds in 0 sec. Also, no more unknown host messages.
Ibrahim,
Subject: Re: [nox-dev] Adding DNS functionality to nox
From: jam...@nau.edu
Date: Fri, 26 Aug 2011 04:24:53 -0700
CC: nox-dev@noxrepo.org
What's the behavior with "ping -n " ?
-- Murphy
On Aug 26, 2011, at 4:05 AM, ibrahim mun wrote:
> Hi Murphy, Christian, All,
>
> The problem is partially solved. I've added the following code to
> pyswitch.packet_in_callback
>
> # drop packets to dns 10.0.0.2
> iph=packet.find("ipv4")
Hi Murphy, Christian, All,
The problem is partially solved. I've added the following code to
pyswitch.packet_in_callback
# drop packets to dns 10.0.0.2
iph=packet.find("ipv4")
udph=packet.find("udp")
if iph!= None and udph!= None:
if iph.dstip==ipstr_to_int("10.0.0.2") a
11 matches
Mail list logo
