sgsnemu: why --listen and --remote in one network?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.

Viktor Tsymbalyuk viktor.tsymbalyuk at gmail.com
Fri Jan 19 11:07:05 UTC 2018


Hello Harald,

On 2018-01-18 18:37, Harald Welte wrote:
> Hi Viktor,
>
> On Thu, Jan 18, 2018 at 10:59:20AM +0200, Viktor Tsymbalyuk wrote:
>> Hello,
>> I'm querying  why sgsnemu shoul work in a same network with ggsn?
>> What the reason for such limitation?
> can you please be more specific, what you are referrinng to?  If you
> think some statement or documentation is incorrect, please quote and/or
> point exactly to what you are referring. There's code comments, readme files
> in the source repository, wiki, manuals, ...
>
Sorry, it's was my fault. Let's close thread.
I were confused by sting "Use the same LAN switch as the one your SGSN 
is connected to." from http://git.osmocom.org/osmo-ggsn/about/
If you interesting my mind, it's better to remove this string.
and delete "--dns 10.20.38.51" from
"sgsnemu --listen 10.0.0.50 --remote 10.0.0.40 --dns 10.20.38.51 
--timelimit 10 --contexts 0" in point 4. DNS not needed in echo mechanism.




More information about the osmocom-net-gprs mailing list