> Is that code missing?
No, it's there
...
# Update the routing table database
#
if [ -w /etc/iproute2/rt_tables ]; then
cat > /etc/iproute2/rt_tables <<EOF
#
# reserved values
#
255 local
254 main
253 default
0 unspec
#
# local
#
1 Prov1
2 Prov2
EOF
...
> If not, then is /etc/iproute2/rt_tables writable?
ls -al /etc/iproute2/rt_tables
-r--r--r-- 1 root root 87 Aug 10 09:06 /etc/iproute2/rt_tables
That's a problem. Fixing,
chmod 0644 /etc/iproute2/rt_tables
Recompile & push SW,
shorewall show routing
now correctly returns
Routing Rules
0: from all lookup local
10000: from all fwmark 0x100/0xff00 lookup Prov1
10001: from all fwmark 0x200/0xff00 lookup Prov2
20000: from xx.xx.xx.xx lookup Prov1
20000: from yy.yy.yy.yy lookup Prov2
32766: from all lookup main
32767: from all lookup default
Table default:
...
Table local:
...
Table main:
...
Table Prov1:
...
Table Prov2:
...
(1) no idea why the rt_tables perm's changed; exploring recent @distro updates.
(2) afaict, there's no logged complaint about the incorrect/unwritable perm on
exec of
sh shorewall reload -s ${TARGET}
Is it logged somewhere, and I"ve missed? if not, should there, perhaps, be a
perms check coded?
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users