RE: Problems with providers

Derek Murawsky
Tue, 26 Jul 2005 23:22:06 -0000

I forgot one file, I am running some NAT:
#EXTERNAL       INTERFACE       INTERNAL       ALL INTERFACES   LOCAL
63.211.45.142   eth3            192.168.1.245  No               No
63.211.45.133   eth3            192.168.1.246  No               No

-----Original Message-----
From: Derek Murawsky
Sent: Tuesday, July 26, 2005 7:13 PM
To: ''Mailing List for Shorewall Users''
Subject: Problems with providers

Hello all,
	I''m having a problem using multiple providers and shorewall on
an ubuntu linux box. (Debian clone)
My interfaces file does not have any routes assigned in it

I read the shorewall and routing docs and set up my providers file as:
#NAME   NUMBER  MARK    DUPLICATE       INTERFACE       GATEWAY
OPTIONS
cogent 2       2       main            eth1            66.28.28.79
track,balance=1
birns  3       3       main            eth3            63.211.45.129
track,balance=2

MASQ file is set up:
#INTERFACE              SUBNET          ADDRESS         PROTO   PORT(S)
IPSEC
eth3                    eth5            63.211.45.130
eth1                    eth5            66.28.28.78

I don''t think rules are important here, and I haven''t set up
anything
else fancy except openvpn
Tunnels file:
# TYPE                  ZONE    GATEWAY         GATEWAY
#                                               ZONE
openvpn                 net     4.79.128.50

Shorewall check completes successfully.
A shorewall restart, however exits unsuccessfully

Processing /etc/shorewall/providers...
RTNETLINK answers: File exists

Shorewall debug restart shows a lot of stuff, but I believe this is
pertinent:
+ run_ip route show table main
+ ip route show table main
+ read net route
+ case $net in
+ ensure_and_save_command ip route add table 2 10.1.0.1 dev tun0 proto
kernel scope link src 10.1.0.2
+ eval ip route add table 2 10.1.0.1 dev tun0 proto kernel scope link
src 10.1.0.2
++ ip route add table 2 10.1.0.1 dev tun0 proto kernel scope link src
10.1.0.2
+ echo ip route add table 2 10.1.0.1 dev tun0 proto kernel scope link
src 10.1.0.2
+ read net route
+ case $net in
+ ensure_and_save_command ip route add table 2 66.28.28.76/30 dev eth1
proto kernel scope link src 66.28.28.78
+ eval ip route add table 2 66.28.28.76/30 dev eth1 proto kernel scope
link src 66.28.28.78
++ ip route add table 2 66.28.28.76/30 dev eth1 proto kernel scope link
src 66.28.28.78
+ echo ip route add table 2 66.28.28.76/30 dev eth1 proto kernel scope
link src 66.28.28.78
+ read net route
+ case $net in
+ ensure_and_save_command ip route add table 2 63.211.45.128/28 dev eth2
proto kernel scope link src 63.211.45.132
+ eval ip route add table 2 63.211.45.128/28 dev eth2 proto kernel scope
link src 63.211.45.132
++ ip route add table 2 63.211.45.128/28 dev eth2 proto kernel scope
link src 63.211.45.132
+ echo ip route add table 2 63.211.45.128/28 dev eth2 proto kernel scope
link src 63.211.45.132
+ read net route
+ case $net in
+ ensure_and_save_command ip route add table 2 63.211.45.128/28 dev eth3
proto kernel scope link src 63.211.45.130
+ eval ip route add table 2 63.211.45.128/28 dev eth3 proto kernel scope
link src 63.211.45.130
++ ip route add table 2 63.211.45.128/28 dev eth3 proto kernel scope
link src 63.211.45.130
RTNETLINK answers: File exists

Any ideas on what''s going on?  Thanks in advance for any help.
-Derek


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click