On Tue, 19 Jan 2016 00:31:51 +0100 Aleksander Morgado <aleksan...@aleksander.es> wrote:
> On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn > <gwashb...@eagleeyenetworks.com> wrote: > > "curl -v --interface wwan0 http://www.google.com" > > You're binding the request to the wwan interface, which I assume it's > because it isn't the default route. > > Try to disable the reverse path filtering, something like: > # for i in /proc/sys/net/ipv4/conf/*/rp_filter ; do echo 0 > $i; done Amazing! That resolved that particular issue. Now I'm wondering why when I do "route del default gw 100.95.66.90 dev wwan0", where 100.95.66.90 is the IP for the NM created default route, the curl command fails with a connection timeout. And if I then remove the default gateway so that the routes are back to the way NM configured them, curl still doesn't work. Am I not allowed to mess with any routes for the wwan0 interface? # ip route default via 172.30.0.1 dev eth1 proto static metric 100 default via 192.168.0.1 dev wlan0 proto static metric 600 default via 100.95.66.90 dev wwan0 proto static metric 700 100.95.66.88/30 dev wwan0 proto kernel scope link src 100.95.66.89 metric 700 172.30.0.0/20 dev eth1 proto kernel scope link src 172.30.9.123 172.30.0.0/20 dev eth1 proto kernel scope link src 172.30.9.123 metric 100 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.149 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.149 metric 600 Also, unexpectedly (to me), ssh using -b <wwan IP> fails with a connection timeout. However, ssh without the -b does work when I have wwan0 as the default route, as setup by NM. Glenn -- Eagle Eye Networks - Cloud based video surveillance _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel