Like a few here, my WWAN modem doesn’t get an ip because it only supports RawIP mode. Because I got this for loadbalancing, it took a bit to figure out. RawIP generally uses interface routing, so I did this first off.
# show protocols static route 0.0.0.0/0
dhcp-interface eth0
interface wwan0 {
distance 215
}
Which sorted out actual routes and getting around the loadbalancing issues. Don’t ask me how it works, it just does… haha.
Actual IP though on the interface? I toyed with installing networkmanager, but as mentioned above, that breaks loadbalancing which I wanted. So I did this instead.
#!/bin/bash
# Check status of the interface
wwanip=$(ip -f inet addr show wwan0 | sed -En -e 's/.*inet ([0-9.]+).*/\1/p')
wipmask=$(ip -f inet addr show wwan0 | awk '/inet / {print $2}')
bearer=$(mmcli -m 0 --output-keyvalue | grep modem.generic.bearers.value |awk '{print $3}' |cut -d "/" -f6)
bearerip=$(mmcli -b $bearer --output-keyvalue |grep bearer.ipv4-config.address | awk '{print $3}')
bearermask=$(mmcli -b $bearer --output-keyvalue |grep bearer.ipv4-config.prefix | awk '{print $3}')
if [ "$wwanip" != "$bearerip" ]
then
echo "Data is different"
/usr/sbin/ip addr del $wipmask dev wwan0
/usr/sbin/ip addr add $bearerip/$bearermask dev wwan0
else
echo "Data are equal"
fi
Set that to run via cron every 5 minutes. What I’ve found, at least with mine, is that once I start pushing a ping through the loadbalancer, it holds the bearer ip for days on end. So all working. It’s hacky, and ugly, but it works at least until we get scripts that read mmcli and implement the IP
