-------- Original Message --------
Subject: RE: [Shorewall-users] Issue with IP Aliasing
Date: Tue, 13 Apr 2004 12:41:52 -0600
From: Daniel Watrous <daniel.watrous@maintainfit.com>
To: ''Tom Eastep'' <teastep@shorewall.net>
Thank you. This solved the problem.
Daniel Watrous
801-363-6747
-----Original Message-----
From: Tom Eastep [mailto:teastep@shorewall.net]
Sent: Tuesday, April 13, 2004 12:30 PM
To: Mailing List for Shorewall Users; daniel.watrous@maintainfit.com
Subject: Re: [Shorewall-users] Issue with IP Aliasing
Tom Eastep wrote:> Daniel Watrous wrote:
>
>>
>> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
>> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
100
>> link/ether 00:0c:f1:87:6d:42 brd ff:ff:ff:ff:ff:ff
>> inet 10.0.0.1/24 brd 10.0.0.255 scope global eth0
>> 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
100
>> link/ether 00:90:27:1a:c3:21 brd ff:ff:ff:ff:ff:ff
>> inet 166.70.187.66/29 brd 166.70.187.71 scope global eth1
>> inet 166.70.187.68/16 brd 166.70.255.255 scope global eth1:0
>> inet 166.70.187.69/16 brd 166.70.255.255 scope global secondary
>> eth1:1
>> inet 166.70.187.70/16 brd 166.70.255.255 scope global secondary
>> eth1:2
>
>
> The subnetting on your aliases is wrong (/16 vs /29).
>
While I don''t guarantee that fixing that will solve your problem, it is
definitely wrong and can cause problems accessing certain addresses.
Hopefully the following hint will be helpful:
gateway:~# shorewall ipcalc 166.70.187.66/29
CIDR=166.70.187.66/29
NETMASK=255.255.255.248
NETWORK=166.70.187.64
BROADCAST=166.70.187.71
gateway:~#
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net