Change the default gnmi port

google · Oct 31, 2018 · 27a6076 · 27a6076
1 parent 061f94b
commit 27a6076
Show file tree

Hide file tree

Showing 5 changed files with 10 additions and 10 deletions.
diff --git a/agent/agent.go b/agent/agent.go
@@ -41,7 +41,7 @@ import (
 var (
 	ethINTFName    = flag.String("eth_intf_name", "eth0", "The management network interface on this device.")
 	wlanINTFName   = flag.String("wlan_intf_name", "wlan0", "The WLAN interface on this device for AP radio.")
-	gnmiPort       = flag.Int("gnmi_port", 8080, "The port GNMI server listening on.")
+	gnmiPort       = flag.Int("gnmi_port", 10162, "The port GNMI server listening on.")
 	controllerAddr = flag.String("controller_address", "", "The WiFi Controller of this device.")
 
 	cmdRunner = syscmd.Runner()

diff --git a/demo/samples/gnmi_set.sh b/demo/samples/gnmi_set.sh
@@ -6,5 +6,5 @@ sudo env PATH=$PATH ip netns exec lk22 gnmi_set \
 -cert=../cert/client/client.crt \
 -key=../cert/client/client.key \
 -target_name=www.example.com \
--target_addr=192.168.11.8:8080 \
+-target_addr=192.168.11.8:10162 \
 -replace=/:@../ap_config_1r.json
diff --git a/emulator/README.md b/emulator/README.md
@@ -91,7 +91,7 @@ target-eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         TX packets 6  bytes 508 (508.0 B)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 ```
-"target-eth0" is the management interface of the emulated AP, where gNMI target listens on (default port 8080).
+"target-eth0" is the management interface of the emulated AP, where gNMI target listens on (default port 10162).
 
 The link022 agent process runs inside "target" node:
 ```
@@ -119,7 +119,7 @@ mininet> xterm ctrlr
 -cert ../demo/cert/client/client.crt \
 -key ../demo/cert/client/client.key \
 -target_name www.example.com \
--target_addr 10.0.0.1:8080 \
+-target_addr 10.0.0.1:10162 \
 -replace=/:@../tests/ap_config.json
 ```
 
@@ -131,7 +131,7 @@ mininet> xterm ctrlr
 -cert ../demo/cert/client/client.crt \
 -key ../demo/cert/client/client.key \
 -target_name www.example.com \
--target_addr 10.0.0.1:8080 \
+-target_addr 10.0.0.1:10162 \
 -xpath "/access-points/access-point[hostname=link022-pi-ap]/radios/radio[id=1]/config/channel"
 ```
 

diff --git a/testkit/README.md b/testkit/README.md
@@ -46,7 +46,7 @@ Here is one example:
 -cert ../demo/cert/client/client.crt \
 -key ../demo/cert/client/client.key \
 -target_name www.example.com \
--target_addr 127.0.0.1:8080 \
+-target_addr 127.0.0.1:10162 \
 -test_file=testdata/simple_test.json
 
 insecure mode on:
@@ -74,7 +74,7 @@ Note, return here after you've completed Step 4 (verify the setup), but before S
 
 An emulated Link022 AP should run inside mininet node "target".
 * management interface IP: 10.0.0.1
-* gNMI port: 8080
+* gNMI port: 10162
 
 Note: The default log file location:
 * link022 AP: "/tmp/link022_agent.INFO"
@@ -90,7 +90,7 @@ mininet> ctrlr {path to testkit binary} -logtostderr \
 -cert ../demo/cert/client/client.crt \
 -key ../demo/cert/client/client.key \
 -target_name www.example.com \
--target_addr 10.0.0.1:8080 \
+-target_addr 10.0.0.1:10162 \
 -test_file=../testkit/testdata/simple_test.json
 ```
 

diff --git a/tests/README.md b/tests/README.md
@@ -26,7 +26,7 @@ sudo python integration.py \
   --cert ${LINK022}/demo/cert/client/client.crt \
   --key ${LINK022}/demo/cert/client/client.key \
   --target_name www.example.com \
-  --target_addr 10.0.0.1:8080 \
+  --target_addr 10.0.0.1:10162 \
   --json_conf ${LINK022}/demo/ap_config.json
 
 ```
@@ -39,7 +39,7 @@ sudo python integration.py \
   --cert ${LINK022}/demo/cert/client/client.crt \
   --key ${LINK022}/demo/cert/client/client.key \
   --target_name www.example.com \
-  --target_addr 10.0.0.1:8080 \
+  --target_addr 10.0.0.1:10162 \
   --json_conf ${LINK022}/demo/ap_config.json
 
 ```