You can definitely run OVS on pc-engines boxes. I'll be releasing a new
version of the nox box (an image for pc engines alix boards) in the nearish
future that does this.
On Nov 18, 2010 11:27 AM, "Aaron Rosen" wrote:
___
nox-dev mailing list
nox-dev@no
Hmm,
If I replace flow = extract_flow(packet) with
#flow = extract_flow(packet)
flow = {}
flow[core.DL_DST] = packet.dst;
I don't seem to encounter this issue. Any idea why? Sorry if I side tracked
this a little thread. I'm still having the ToS problem when my action is
this,
action
Hi Murphy,
Ok so now I'm just pinging 130.127.39.206 from 130.127.48.212 and it does
seem to set the correct ToS bit value in this case. Though not in the case
before when [openflow.OFPAT_OUTPUT, [0, openflow.OFPP_IN_PORT] is in the
action list.
Also, I just noticed that for some reason my contro
As an experiment, why don't you try setting the ToS bits to 0x10 and see
if that actually comes out like you'd expect it to.
-- Murphy
On Wed, 2010-11-17 at 20:49 -0500, Aaron Rosen wrote:
> Hi Murphy,
>
> So here is the topology: I am pinging 130.127.39.206 (<- connected via
> pc-engine which
Hi Murphy,
So here is the topology: I am pinging 130.127.39.206 (<- connected via
pc-engine which is running the openflow switch )from 130.127.48.212
(Non-Openflow). Then I install the following action for that flow.
actions = [[openflow.OFPAT_SET_NW_TOS, 22],[openflow.OFPAT_SET_DL_DST,
"00:17
Where are you sniffing with Wireshark? On the machine running the switch?
Which interface are you sniffing? It needs to be an interface the packet *goes
out on after having gone through the switch* or you won't see any difference
since the switch hasn't actually gotten a chance to modify it y
So you are seeing that the switch receives the action correctly (that is, with
the ToS modify action and the correct new ToS bits), but the packets aren't
being modified as you expect? Are you sure the packets you want modified are
matching?
-- Murphy
On Nov 16, 2010, at 12:09 PM, Aaron Rosen
Murphy,
Unfortunately this patch does not actually change the ToS bits in the ip
packet. Sorry I should have confirmed that before I told you it worked. I
just checkout a fresh copy of nox destiny and confirmed this with wireshark.
(I assumed it worked before, because of this "68, n_packets=37,
Great. Pushed to destiny.
-- Murphy
On Mon, 2010-11-15 at 20:11 -0500, Aaron Rosen wrote:
> Awesome Murphy that seemed to work :D
>
> cookie=0, duration_sec=31s, duration_nsec=71000s, table_id=0,
> priority=32768, n_packets=32, n_bytes=3136,
> idle_timeout=5,hard_timeout=0,icmp,dl_vlan=0xf
Awesome Murphy that seemed to work :D
cookie=0, duration_sec=31s, duration_nsec=71000s, table_id=0,
priority=32768, n_packets=32, n_bytes=3136,
idle_timeout=5,hard_timeout=0,icmp,dl_vlan=0x,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:02,dl_dst=00:00:00:00:00:04,nw_src=10.0.0.2,nw_dst=10.0.0.4,
Try this patch.
Also, your parameter for OFPAT_SET_NW_TOS ("44") should probably be an
integer (44).
-- Murphy
On Mon, 2010-11-15 at 15:30 -0500, Aaron Rosen wrote:
> Thanks Niky,
>
>
> Does anyone know how I would modify those ToS bits then? Or what all I
> would have to add to make, make_ac
Thanks Niky,
Does anyone know how I would modify those ToS bits then? Or what all I would
have to add to make, make_action_array be able to modify the ToS in the
manor that I'm attempting?
Thanks,
Aaron
On Mon, Nov 15, 2010 at 3:20 PM, Niky Riga wrote:
> I am not 100% but I think the problem
I am not 100% but I think the problem is that the OFPAT_SET_NW_TOS
action is not currently handled by the function that creates the actions
for the python modules.
If you look at the core.py (src/nox/lib/core.py) there is a function
make_action_array() that creates the actions string that is sen
Hello,
I'm trying to change the ToS bits in IP packets but nox is telling me
invalid action type 8.
Here is the blurb of code that I'm trying:
attrs = extract_flow(packet)
outport = self.data[dpid, mac_to_str(packet.dst)]
actions = [[openflow.OFPAT_SET_NW_TOS, "44"], [ openflow.OFPAT_OUTPUT, [0
14 matches
Mail list logo