osmo_sock_get_name() order

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/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Wed Jun 21 18:54:40 UTC 2017


In terms of left/right: I think there is no obvious or correct way.

My original idea was that a system administrator would inherently know
which of the two sides is the local side of the socket, based on his
configuration.

Based on the fd it's unfortunately not possible to have an explicit
"CLIENT -> SERVER" kind of notation replacing the bi-directional arrow
that we currently print.  This would require that we keep a lot more
state and nothing that can be derived from the fd alone :/

On Wed, Jun 21, 2017 at 05:17:18AM +0200, Neels Hofmeyr wrote:
> On Wed, Jun 21, 2017 at 12:58:59AM +0200, Max wrote:
> > R:127.0.0.1:2905<->L:127.0.0.1:60661
> 
> +1, I'd even favor writing out 'remote:' and 'local:'.

L/R I can still live with, but please don't make it even longer.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list