Hey, On Tue, Feb 13, 2024 at 1:18 PM Garfield Watkins <garfield.watk...@gmail.com> wrote: > > Bearer 0 is the initial default bearer. > > Bearer 1 is the connected bearer > > Output from mmcli -b 1 is: > > --------------------------------- > General | path: /org/freedesktop/ModemManager1/Bearer/1 > | type: default > --------------------------------- > Status | connected: yes > | suspended: no > | multiplexed: no > | interface: enp0s20f0u2 > | ip timeout: 20 > | profile id: 1 > --------------------------------- > Properties | apn: internet > | roaming: allowed > | ip type: ipv4 > --------------------------------- > IPv4 configuration | method: dhcp > | prefix: 0 > --------------------------------- > Statistics | start date: 2024-02-13T12:08:31Z > | attempts: 1 > > Please note ModemManager is not responsible for running the DHCP > client in the net interface, so if your plugin is reporting "dhcp" IP > method in the connected bearer settings (in your get_ip_config_3gpp() > method), then whoever is the network management layer on top of > ModemManager would be the one in charge of running DHCP client. > > I have NetworkManager running. I was under the assumption that it would > automatically run its dhcp client on the interface. It seems to do this when > I manually issue AT+CGACT=1,1. Its only when running under ModemManager that > nothing seems to happen, in fact I have tried to run dhclient enp0s20f0u2 and > only then do i get an ip address. >
Did you connect the modem using NetworkManager (e.g. using nmcli) or did you connect the modem using mmcli? -- Aleksander
