Re: [nox-dev] adding rule with multiple actions

2011-05-06 Thread Vishal
Hello Murphy, I changed max_len to 128 for the action -> send to openflow.OFPP_CONTROLLER and tried again. what i observe is : The switch sends a Port Status Message (ofp_port_status) with OFPPR_MODIFY with reason field set as "Some attribute of the port has changed". The Physical Port Header

Re: [nox-dev] host deathentication

2011-05-06 Thread kk yap
ARP is a great idea. Someone should give it a try, though I know some routers sometimes do funny things with ARP for their own devices, but that would not be too big an issue I guess. Regards KK On 6 May 2011 03:59, Murphy McCauley wrote: > I don't consider this a big issue, but what about ARP

Re: [nox-dev] matching fields

2011-05-06 Thread Murphy McCauley
Indeed, that's a problem. routing assumes it's installing exact matches. It seems like one way to do this would just be to install a new rule for every destination MAC you came up against, even though the destination MAC wouldn't actually be used for determining the path. So you'd still do exa

Re: [nox-dev] host deathentication

2011-05-06 Thread Murphy McCauley
I don't consider this a big issue, but what about ARPing at it? I bet even machines that are set to not respond to ICMP echo will still usually answer an ARP. Moreover, if they respond once, I'd think it's probably safe to assume they will continue to do so. So if something never responds to

Re: [nox-dev] matching fields

2011-05-06 Thread karim torkmen
Hi Murphy, thanks a lot for your answeer. The small problem is that I am using python and the setup_route ("self.routing.setup_route(flow,route, inport, outport,FLOW_TIMEOUT, [], False")) method of pyrouting which takes as an entry a flow not an "attrs". My aim is to make the switch just decid