Shorewall users - May 2005 - Interface Broadcast

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I''ve a problem on the broadcast it is adding some additional route to
the router which caused me some problem...

Below is my /etc/shorewall/interface

swtmng1 eth0.1          202.73.10.127     norfc1918
apmng1  eth0.10         202.73.8.7        norfc1918
dist1   eth0.1000       202.73.11.255     norfc1918,nobogons
idc1    eth2.50         202.73.10.255     norfc1918
net     eth3            203.115.208.143   norfc1918,blacklist,nobogons
dmz     eth4.4000       202.73.10.63      norfc1918
loc     eth5

     dhcp,routeback,blacklist

And This are the netconfig that I have.

eth0.1
202.73.10.65 broadcast 202.73.10.127 netmask 255.255.255.192
eth0.10
202.73.8.1 broadcast 202.73.8.7 netmask 255.255.255.248
eth0.1000
202.73.11.1 broadcast 202.73.11.255 netmask 255.255.255.0
eth2.50
202.73.10.129 broadcast 202.73.10.255 netmask 255.255.255.128
eth3
203.115.208.140 broadcast 203.115.208.143 netmask 255.255.255.248
eth4.4000
202.73.10.1 broadcast 202.73.10.63 netmask 255.255.255.192
eth5
192.168.0.10 broadcast 192.168.0.255 netmask 255.255.255.0

But this is the route that I''ve which is a bit problem for me, Someone
know a solution?
eth0.1
202.73.10.64/26  proto kernel  scope link  src 202.73.10.65
202.73.10.0/24  proto kernel  scope link  src 202.73.10.65 <-- ERROR
eth0.10
202.73.8.0/29  proto kernel  scope link  src 202.73.8.1
eth0.1000
202.73.11.0/24  proto kernel  scope link  src 202.73.11.1
eth4.4000
202.73.10.0/26  proto kernel  scope link  src 202.73.10.1
202.73.10.0/24  proto kernel  scope link  src 202.73.10.1  <-- ERROR
eth5
192.168.0.0/24  proto kernel  scope link  src 192.168.0.10

Anyone have any idea?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFCiEXiV0p9slMZLW4RAkvFAKDAX6OHv8JdAb49T7GBIn8DNWt51gCeJ5m5
VQnKSQ8tVXlzjLuPEOfUF1A=xwVa
-----END PGP SIGNATURE-----

Chan Min Wai wrote:
> I''ve a problem on the broadcast it is adding some additional route
to
> the router which caused me some problem...
I am baffled as to why you are posting this on the Shorewall list --
entries in /etc/shorewall/interfaces _do not generate entries in your
routing table_ so this problem has nothing whatsoever to do with Shorewall.

The routes that you posted are a natural consequence of the way that you
have defined your interfaces and addresses. I suppose that if there is
one that you don''t like, you can always delete it once the
corresponding
interface has been configured.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key