Hi all,
I just noticed that osmo-bts commit
6d117891c93da969e0ff8b293bef97c699490f2b is the last version that can be
brought up by the openBSC aka osmo-nitb.
Which makes me wonder now, should the openbsc / osmocom-nitb package
continue to be published to repositories?
Hi All,
I have scanned 3GPP documents for info on the GGSN IP network facing
side, IIUC how the GGSN responds there is "out of scope" - I'm
specifically wondering about sending ICMP host unreachable messages in
response to packets for IPs that are not currently active in the pool.
Sometimes it would happen where I was pinging an IP assigned to an MS
while looking at other things in the SGSN and PCU but in the meantime
the MS would cycle the PDP context and have a new IP.
For this and maybe other reasons I wrote a proof of concept, probably
not great code, but working, patch to have the GGSN send ICMP host
unreachable.
Do you think this is a desirable feature?
If so I would try to clean it up and submit to code review.
Also if in agreement, would it be worth making it switchable via a vty
param? I am thinking of where one might not want the IP space to be
probable, although I would assume that kind of thing is best left to the
local firewall implementation.
Patch here: http://git.osmocom.org/osmo-ggsn/?h=keith%2Ficmp
Thanks.
K.
Hi Andreas,
I pulled the new master, rebuilt my setup from source in a clean state and
it works as it should.
One more question though: is it possible to use the MNCC socket to connect
the NMT-450 network to 2G (via Osmo-BSC), or to SIP via LCR?
Thanks again!
Regards,
Csaba
