Hi,
with the new NS2 code [1] the vty keep compatible. However the new NS2
code is more flexible and support more use cases except the old vty
doesn't allow it.
I've created an osmocom ticket [2] to experiment and write a draft of
the new VTY commands.
I would be nice if you can give me some feedback here.
Best,
lynxis
[1] NS <> NS2. it's still the same protocol, just a second
implementation of NS.
[2]
https://osmocom.org/issues/4770
new vty example:
1.1. sgsn with udp bind - ipa style
1.2. sgsn with udp bind - with persistent nsvc
1.3. sgsn with sns listen on all interfaces
1.4. sgsn with sns listen on specific interface
1.5. sgsn with fr
2.1. TODO: pcu with binds to use when receiving info ind
2.2. TODO: pcu with static configuration
<pre>
;; 1.1. sgsn with udp bind - dynamic with ipa style
ns
bind udp some
listen 192.168.0.2 23000
allow-block-reset-nsvci
</pre>
<pre>
;; 1.2. sgsn with udp bind - no dynamic connection - only vty
configured NSE (persistent)
ns
bind udp some
listen 192.168.0.2 23000
nsei 1001
nsvc udp some 10.0.1.2 23000
</pre>
<pre>
;; 1.2. sgsn with udp bind - no dynamic connection - only vty
configured NSE (persistent)
ns
bind udp some
listen 192.168.0.2 23000
bind udp other
listen 192.168.1.2 23000
nsei 1001
;; will use all bindings
nsvc udp * 10.0.1.2 23000
nsei 1002
nsvc udp other 10.0.1.3 23000
nsvc udp some 10.0.1.3 23000
</pre>
<pre>
;; 1.3. sgsn with sns listen on all interfaces
ns
bind udp some
listen 192.168.0.2 23000
allow-sns group all
bind udp other
listen 192.168.1.2 23000
allow-sns group all
</pre>
<pre>
;; 1.4. sgsn with sns listen on specific interface
ns
bind udp some
listen 192.168.0.2 23000
allow-sns group alice
bind udp other
listen 192.168.1.2 23000
allow-sns group bob
</pre>
<pre>
;; 1.5. sgsn with fr
fr
link hdlc1
link hdlc2
ns
nsei 1002
nsvc fr hdlc1 dlci 10
nsvc fr hdlc2 dlci 10
</pre>
--
Alexander Couzens
mail: lynxis(a)fe80.eu
jabber: lynxis(a)fe80.eu
gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604