While I''m still at a loss, it is working again. Here''s what I
did. There
was a cross over cable in eth2 because out of frustration I stuck that in
(it is currently not in service but will be shortly) to see if that would
make a difference. It didn''t and I had left it in there. I went to put
it
the old firewall, after that, it all came back working like it should.
There is probably a simple explanation but I''m too tired to think about
it.
I''m not overly concerned either.
Thanks if anyone started applying brain power to this and sorry for the
inconvenience.
Ben
>From: "Benji Booble" <oneoutof100@hotmail.com>
>Reply-To: shorewall-users@lists.sourceforge.net
>To: shorewall-users@shorewall.net
>Subject: [Shorewall-users] interface mulitple ip address routing problem?
>Date: Mon, 01 Aug 2005 12:59:43 +0000
>
>Hi all,
>
>I think this problem in to do with routing but I am at a loss.
>
>mandriva 2005
>shorewall-2.4.0-1-mdk
>
>I have 3 interfaces, eth0, eth1, and eth2. Eth0 has 3 vlans and are
>configured with private ip address ranges. These work fine. Eth1 is the
>public interface. It has 4 ip addresses attached to it. The main ip
>address works fine but the other 3 are not responding.
>
>ip addr show :
>eth1: <BROADCAST,MULTICAST,UP> mtu 1487 qdisc pfifo_fast qlen 1000
> link/ether 00:0e:2e:07:7b:75 brd ff:ff:ff:ff:ff:ff
> inet 150.101.158.82/29 brd 150.101.158.87 scope global eth1
> inet 150.101.158.83/29 brd 150.101.158.87 scope global secondary eth1
> inet 150.101.158.84/29 brd 150.101.158.87 scope global secondary eth1
> inet 150.101.158.86/29 brd 150.101.158.87 scope global secondary eth1
>
>ip route show :
>172.16.1.0/30 dev eth2 proto kernel scope link src 172.16.1.2
>150.101.158.80/29 dev eth1 proto kernel scope link src 150.101.158.82
>172.16.0.0/25 dev vlan4 proto kernel scope link src 172.16.0.2
>192.168.1.0/24 dev vlan3 proto kernel scope link src 192.168.1.254
>192.168.0.0/24 dev vlan2 proto kernel scope link src 192.168.0.254
>default via 150.101.158.81 dev eth1
>
>ping 150.101.158.82 -I 150.101.158.83 returns echos
>ping 150.101.158.81 -I 150.101.158.83 returns nothing
>
>ethereal shows this for eth1: (greping for 150.101.158.83)
>
>150.101.158.83 -> 150.101.158.81 ICMP Echo (ping) request
>150.101.225.34 -> 150.101.158.83 ICMP Redirect (Redirect for host)
>150.101.225.34 -> 150.101.158.83 ICMP Redirect (Redirect for host)
>
>external addresses cannot see 150.101.158.83 and can''t see it in
shorewall
>logs.
>
>This setup was working previously. This is after a hard disk crash and
>this is the rebuilt machine (with copies of shorewall config from backup).
>
>Any hints,
>
>Ben
>
>_________________________________________________________________
>Express yourself instantly with MSN Messenger! Download today it''s
FREE!
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>
>-------------------------------------------------------
>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_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Shorewall-users mailing list
>Shorewall-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/shorewall-users
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it''s
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------------------------------------------------
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_id=7477&alloc_id=16492&op=click