[maybe less of a nox question and more of an openflow question, but...] The switch opens a raw socket to listen on each interface, so it's effectively a read-only copy like tcpdump uses (exactly like tcpdump), so it doesn't interfere with any other processing that happens. You could imagine the switch doing something more exotic (e.g., hooking into the stack deeper with netfilter -- www.netfilter.org), but I think the common case is to use the switch on interfaces that do not have daemons running on them.
What is the high level goal that you have here? I mean you could always block the response with iptables, but that begs the question of why not just turn the service off in the first place? - Rob . On Sun, Nov 21, 2010 at 10:39 AM, Aaron Rosen <aro...@clemson.edu> wrote: > Hello, > > I have a question about what happens when you are sending packets to a host > that is also running the openflow switch. For example, I'm running openflow > on a pc-engine with the following command. > > ofprotocol unix:/var/run/dp0 tcp:130.127.39.173:6639 --fail=closed & > ofdatapath punix:/var/run/dp0 -i eth0,wlan0 ptcp:6633 & > > This pc-engines ip address is 192.168.2.2. > > So, when this pc-engine receives a packet for 192.168.2.2 (under a special > condition) I want to change this packet and send it out to someone else by > modifiying the ip.dst (etc). Though it seems that when the pc-engine > receives this packet it will go a head and respond and then pass the packet > to openflow (which is running between eth0 + wlan0). Is this what is > expected? > > Thanks, > > Aaron > > > > > -- > Aaron O. Rosen > Masters Student - Network Communication > 306B Fluor Daniel > 843.425.9777 > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
