On 07/03/2015 03:41 PM, Daniel Wagner wrote: > On 07/03/2015 03:18 PM, Gianfranco Casanova wrote: >> ———————————————————————————— >> root@ale:/var/log# ip rule show >> 0: from all lookup local >> 32764: from all fwmark 0x101 lookup 257 >> 32765: from all fwmark 0x100 lookup 256 >> 32766: from all lookup main >> 32767: from all lookup default >> ———————————————————————————— >> >> ———————————————————————————— >> root@ale:/var/log# ip route show table 0x101 >> ———————————————————————————— > > So this is wrong. We should have a default routing entry for the wifi > policy routing table. Without a match, the main/default routing table > will be used. > > For testing just add the missing route entry to table 0x101, e.g. > > # ip route add default via 172.20.10.1 dev wlan0 table 0x101
I'll tested this setup. On my system the policy tables have the correct entries: # ip rule 0: from all lookup local 32764: from all fwmark 0x101 lookup 257 32765: from all fwmark 0x100 lookup 256 32766: from all lookup main 32767: from all lookup default # ip route show table 256 default via 192.168.0.254 dev eth0 # ip route show table 257 default via 10.0.201.254 dev wlan0 Maybe the kernel rejects for some reason to install the route for your table 0x101. I would expect that the kernel would tell us with some error code if things wont work, but it looks like it silently ignores it. cheers, daniel _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
