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/.
Martin Hauke mardnh at gmx.deMychaela Falconia wrote: > The first tested implementation is Huawei E303, a 3G data modem in the > USB stick form factor; it is Qualcomm-based to the best of my knowledge. > Here is the ifconfig output: > > ppp0 Link encap:Point-to-Point Protocol > inet addr:21.227.117.124 P-t-P:10.64.64.64 Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:33967 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29454 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:28077904 (26.7 Mb) TX bytes:2831375 (2.7 Mb) > > The other tested implementation is my own FreeCalypso, or more > specifically an FCDEV3B modem board running FreeCalypso Magnetite > hybrid firmware, build date 2018-07-30T20:24:34Z. It is also using a > different SIM, although on the same billing account with T-Mobile and > with the same service configuration - I am too lazy to move the same > SIM back and forth between the USB stick modem and my own board. Here > is the ifconfig output: > > ppp0 Link encap:Point-to-Point Protocol > inet addr:22.255.27.2 P-t-P:10.64.64.64 Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:285 errors:0 dropped:0 overruns:0 frame:0 > TX packets:341 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:79139 (77.2 Kb) TX bytes:35368 (34.5 Kb) > > The dynamically assigned IP address is different because I had to shut > down pppd with one modem and start a new session with the other modem, > but notice that the P-t-P address is the same fixed 10.64.64.64. In this case the P-t-P IP address 10.64.64.64 is probably coming from the pppd on your linux machine. If the remote P-t-P IP address cannot be determined via IPCP pppd is using fallback IP addresses. The IP address pppd then uses is 0x0a404040 + a interface unit id. The interface unit id is "0" for ppp0, "1" for ppp1, ... The resulting (fake) fallback P-t-P remote IP addresses are ppp0 -> 10.64.64.64 ppp1 -> 10.64.64.65 For more details see: https://github.com/paulusmack/ppp/blob/5c765a67fd25f9d84e71ed61ace37c8c97f6be15/pppd/ipcp.c#L1752 This ppp implementation aka "Paul's PPP Package" from https://ppp.samba.org/ is used by more or less all linux distributions these days. best regards, Martin