Hi Tahmid,
- osmo-bsc
https://docs.google.com/document/d/1mFRtjnOfecCFZSmAaA22GA_EM28rB59dIjftM_UXmPc/edit?usp=sharing
- osmo-sgsn
https://docs.google.com/document/d/1r3VfTNPlb-9XWU8FWfALh5kRr9502WgrSMuYXkqHrE0/edit?usp=sharing
your pcu can't connect to the sgsn. You tell your pcu to connect to 127.0.0.9:23001 The bsc is configuring the pcu via the bts. (bsc -> bts -> pcu) bsc-config: [...] gprs nsvc 0 remote ip 127.0.0.9 gprs nsvc 0 remote udp port 23001 gprs nsvc 0 local udp port 23002 gprs nsvc 0 nsvci 1800 [...]
But in your sgsn configuration you set the listen ip/port to 127.0.0.20:23000 [...] ns bind udp local listen 127.0.0.20 23000 accept-ipaccess [...]
Please change your bsc configuration to 127.0.0.20 and the remote udp port to 23000
gprs nsvc 0 remote ip 127.0.0.20 gprs nsvc 0 remote udp port 23000
Also your ggsn configuration has: ip dns 0 127.0.0.1
This will tell the phone to ask itself for dns queries. Please replace it with a valid dns server (e.g. 1.1.1.1)
Best, lynxis
On Sat, 20 May 2023 at 16:42, Alexander 'lynxis' Couzens lynxis@fe80.eu wrote:
Hi Ahnaf,
the structure of osmocom have changed since the manual has been written. The manual is written for the long outdated osmo-nitb (a combined BSC,MSC).
I have noticed that the wiki page for OpenBSC GPRS at https://osmocom.org/projects/cellular-infrastructure/wiki/OpenBSC_GPRS
has
not been updated for four years, and since then, there have been significant updates to the software. As a result, the information on the GPRS/EDGE Setup page may be outdated, and I am struggling to configure
GPRS
on my system.
I have attached my configuration files below for your review.
I would recommend to take a look into the https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In... But you already have configuration files for bsc, msc, sgsn, ggsn.
I would also recommend you to add an IP for every core network component and ran. Because it helps debugging to have the IPs seperate. For a local network (everything runs on the same host) I would do:
- 127.0.0.10 bts + pcu
- 127.0.0.11 bsc + bsc-mgw (yes running mgw twice)j
- 127.0.0.12 msc + osmo-sip-connector + msc-mgw
- 127.0.0.13 sgsn
- 127.0.0.14 ggsn
- 127.0.0.15 sip-server (e.g. asterix, ...)
- 127.0.0.16 hlr
You will need to change vty and ctrl interface ips as well.
Back to your current network. Are you running osmo-stp? osmo-stp is required for the new network.
Ok. but what is not working? Please add more information!
- Can your MS/UE connect to the network?
- CS: location update works?
- PS: routing area update works?
- Does your phones gets an IP? (PDP Context)
- Does `tcpdump -i tun4 -vn` shows any traffic?
Do you have a pcap trace? (Best to upload it to a website and only send the link on this mailinglist)
Your tun.network file looks wrong. The device should be named tun4 and the IP range is also wrong. Personally I wouldn't use systemd-networkd for this. At least I would expect routing issues. Also I wonder why there isn't a tun4 device.
Even if there is a tun4 device, you might missing the routing and depending on your setup, NAT/masquerading. I think you would need to run `ip route add 172.16.222.0/24 dev tun4` and `iptables -t nat -A POSTROUTING -j MASQUERADE -s 172.16.222.0/24 -o wlp1s0`
Best, lynxis