So I just completely disabled IPv6 from the machine removed -Djava.net.preferIPv4Stack=true
Then started fv and it seems to die right away. It seems like it cannot run with IPv4 . arosen@expedient:~$ flowvisor /usr/local/etc/flowvisor/config.xml Starting FlowVisor Running with FV_JVM_ARGS=-server -Xms100M -Xmx1000M -XX:OnError=flowvisor-crash-logger --- 'flowvisor!logging' not set in config; defaulting to loglevel 'NOTE' --- Setting logging level to DEBUG respawning too fast -- DYING On Fri, Jul 15, 2011 at 1:37 PM, Aaron Rosen <[email protected]> wrote: > Hi Nick, > > It seems like it can't run with that: > > > arosen@expedient:~$ netstat -a | grep 6633 > arosen@expedient:~$ flowvisor /usr/local/etc/flowvisor/config.xml > Starting FlowVisor > Running with FV_JVM_ARGS=-server -Xms100M -Xmx1000M > -XX:OnError=flowvisor-crash-logger -Djava.net.preferIPv4Stack=true > --- 'flowvisor!logging' not set in config; defaulting to loglevel 'NOTE' > --- Setting logging level to DEBUG > respawning too fast -- DYING > > > > On Fri, Jul 15, 2011 at 1:19 PM, Nicholas Bastin <[email protected]> wrote: >> On Fri, Jul 15, 2011 at 12:21, Aaron Rosen <[email protected]> wrote: >>> Though all the switches are on this same LAN so ipv6 here should be >>> working between the too. >> >> Except I bet the HPs don't speak v6.. :-) >> >>> Is there an easy way to tell flowvisor not to use v6? Or should I >>> disable it in the OS? >> >> If you modify the script that runs flowvisor (for me, it's >> /usr/local/sbin/flowvisor), you can add: >> >> -Djava.net.preferIPv4Stack=true >> >> to the command line that launches the JVM. >> >> I'm taking a shot in the dark here, but it might be worth a try. >> >> -- >> Nick >> > > > > -- > Aaron O. Rosen > Masters Student - Network Communication > 306B Fluor Daniel > -- Aaron O. Rosen Masters Student - Network Communication 306B Fluor Daniel _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
