Holger Hans Peter Freyther
c16cf27bd5
nat: Add config option to filter/handle certain imsi'es.
2010-06-15 20:24:13 +08:00
Holger Hans Peter Freyther
bcfebb2c1d
[nat] Add show statistics to the nat
2010-06-15 20:24:13 +08:00
Holger Hans Peter Freyther
57f874ad8d
[nat] Change the command strings
...
Put the Target/Object first... Apparently this is more what people
that know IOS expect to do.
2010-06-15 20:24:13 +08:00
Holger Hans Peter Freyther
870663af20
nat: Print the IP address of the connected BSCs
2010-06-15 20:24:13 +08:00
Holger Hans Peter Freyther
47dd4944ae
nat: Store the config in the connection instead of the lac
...
This allows that we can print the Nr. next to the lac
and it allows us to change the lac at runtime without
reconnecting the BSC.
2010-06-15 20:24:12 +08:00
Holger Hans Peter Freyther
5f291d5077
nat: Add logging commands for the nat as well.
2010-06-15 20:24:12 +08:00
Holger Hans Peter Freyther
560af50422
nat: Print the SCCP ref's as hex numbers
...
This allows to more easily compare the numbers with traces
seen in wireshark.
2010-06-15 20:24:11 +08:00
Holger Hans Peter Freyther
32d343644d
nat: Print the MSC multiplex as well
2010-06-15 20:24:11 +08:00
Holger Hans Peter Freyther
f7d3335817
nat: Add MGCP code and parsing to the nat code..
...
For the nat we will have NAT and MGCP in the same process
and this commit starts with that. We are linking in the MGCP
code and one can embed MGCP config snippets...
2010-06-15 20:24:09 +08:00
Holger Hans Peter Freyther
39ee87783f
nat: Verify that the configured LACs are unique across the nat
2010-06-15 20:24:09 +08:00
Holger Hans Peter Freyther
ed07a3fc1c
nat: Start using a write_queue for the BSC connection
...
We are still writing to the BSC directly and don't make real
use of this feature right now but we will need to do it.
2010-06-15 20:24:07 +08:00
Holger Hans Peter Freyther
6c45f2e325
nat: Redo a merge with master that happend at this time.
2010-06-15 20:24:07 +08:00
Holger Hans Peter Freyther
9a85ef3266
[nat] Add VTY support to the BSC nat application
...
* Create struct bsc_nat and move the various lists into this structure
* Create the VTY code
* Call the VTY init and parsing code
* Create functions to create the types..
* Add some stuff into the bsc_connection to be used for the NAT with
proper config files. E.g. to close the connection if the BSC does not
respond to a given command.
2010-06-15 20:24:06 +08:00