On Thu, Dec 10, 2015 at 09:02:49PM +0100, Holger Freyther wrote:
On 30 Nov 2015, at 12:47, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
Good Evening Neels,
Added awareness of it (in my head), added gtphub (in osmoappdesc.py) and merged to master.
we need to revert or extend the gtphub vty to make it work on our CI platform. You can not bind to 127.0.0.1 and 127.0.0.2 on the CI infrastructure so the default config can't be execute. We could add VTY commands to specify the ports to be used and multiplex it then.
There is no "default" config, but gtphub requires a config file...
VTY for port numbers already exists: there is a short version using standard ports and a longer one where you can issue ports.
short:
gtphub bind-to-sgsns 127.0.0.1 bind-to-ggsns 127.0.0.2
long, with ports:
bind-to-sgsns ctrl 127.0.0.1 12123 user 127.0.0.1 12152 bind-to-ggsns crtl 127.0.0.1 22123 user 127.0.0.1 22152
The other issue is the position of the gtphub. At the bottom we have this:
vty_command = ["./src/osmo-nitb/osmo-nitb", "-c", "doc/examples/osmo-nitb/nanobts/openbsc.cfg"]
vty_app = apps[-1]
So we run the nitb but try to connect to port 4253 which of course fails and explains why the OpenBSC build failed the last couple of times. :)
Those python structures are a bit sneaky ... they seem so simple, but they'll bite your ankles ;)
vty_app looks weird. is vty_app only used for osmo-nitb? IMHO it could make sense to clarify the python, but for the time being we could simply fix with
vty_app = apps[-2]
??
~Neels