5 Commits

Author	SHA1	Message	Date
Bob Lantz	4b51d5c32e	Various minor fixes and improvements ... - enable parameters for onos cli commands (e.g. onos:apps -a) - don't depend on onos1's name - reduce dependencies on unnecessary variables - enable running if karaf isn't installed elsewhere - make NAT an option Change-Id: I3e8abd51aa8d3f5c7afab1c6b86e50707de20ef6	2016-05-31 22:26:58 +00:00
Bob Lantz	1451d7241b	Run onos as ONOS_USER rather than root (!) ... Change-Id: Ibe87b89a71d12665eb932b40a843c691c4cfa584	2016-05-17 14:44:14 -07:00
Bob Lantz	bb37d87ac7	Add port forwarding using iptables ... By default, we now forward the following ports from port on eth0 to port+N on onosN: 8101 (KarafPort) 8181 (GUIPort) (also REST) 6643 (OpenFlowPort) Note: this will not work if your default interface is called something other than eth0. Also: added null topology so we can use onos.py to control an external/hardware network. Bugs: it seems that iptables isn't cleaned up completely - Mininet's NAT element may be to blame. Change-Id: I2197194100a77ebfddd0d38ad5194ad7569ceba3	2016-05-17 17:14:57 +00:00
Bob Lantz	1125848f95	Fix ipBase option misspelling ... It's arguable that maybe might want to support 'ipbase' as well since it's used in --ipbase and it's easier to type. However, ipBase is the spelling used in Mininet, so we should be consistent. Change-Id: I2f61df0d2d09abf652c5f06ef9c734a55159a7de	2016-05-11 19:09:34 -07:00
Bob Lantz	087b5d93f2	onos.py: ONOS cluster and control network modeling in Mininet ... This is intended to facilitate ONOS development and testing when you require an ONOS cluster and a modeled control network. More information is available in the file comments/module docstring. Change-Id: I8a7338b61bd21eb82ea4e27adbf3cea15be312ee	2016-05-12 22:03:48 +00:00