no, here we have "double (double quotes)"

It seems related to this Android 6.X 7.X bug
https://code.google.com/p/android/issues/detail?id=194269
https://code.google.com/p/android/issues/detail?id=196939

This bug is also present in the last night build

1.1.7

In T142#2451, @whiskeyalpharomeo wrote:

Opinion: Yes, 1.1.8.

In T128#2209, @UnicronNL wrote:

As it is now it can not break the config, that is why "wontfix".
If we block it then configs that have non existent interfaces in them (due to breakage or removed and forgot to remove from dns forwarding) will fail at boot.

In T128#2194, @dmbaturin wrote:

As @UnicronNL says, lines about nonexistent interfaces have no effect on dnsmasq functionality.

But what's worse, is that making it a commit fail will break the configs of those people who carelessly left a nonexistent interface in their DNS forwarding config, it will fail to load at boot time after upgrade.

As much as I hate generating configs that make no sense, leaving those people with potentially inaccessible systems after they upgrade (DNS loads before SSH AFAIR) is not an acceptable cost of somewhat tidier generated configs.

[ policy route PPPOE_CLAMPING ]
iptables: Invalid argument. Run `dmesg' for more information.
Use of uninitialized value $rule_strs[1] in join or string at /opt/vyatta/sbin/vyatta-firewall.pl line 734.
Use of uninitialized value $rule_strs[2] in join or string at /opt/vyatta/sbin/vyatta-firewall.pl line 734.
Use of uninitialized value $rule_strs[3] in join or string at /opt/vyatta/sbin/vyatta-firewall.pl line 734.
Use of uninitialized value $rule_strs[4] in join or string at /opt/vyatta/sbin/vyatta-firewall.pl line 734.
Use of uninitialized value $rule_strs[5] in join or string at /opt/vyatta/sbin/vyatta-firewall.pl line 734.
iptables error: No such file or directory - -m comment --comment "PPPOE_CLAMPING-10" -p tcp -m tcp --tcp-flags SYN SYN -m iprange ! --dst-range 192.168.20.0-192.168.30.255 -j TCPMSS --clamp-mss-to-pmtu at /opt/vyatta/sbin/vyatta-firewall.pl line 734.