IP alias Networking Errors.
malcolm.kay at internode.on.net
Sat May 24 19:30:59 PDT 2003
On Sun, 25 May 2003 11:51, Andy Farkas wrote:
> On Sat, 24 May 2003, Grant Peel wrote:
> > fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
> > inet 18.104.22.168 netmask 0xfffffff0 broadcast 22.214.171.124
> > inet 126.96.36.199 netmask 0xffffffff broadcast 188.8.131.52
> > inet 184.108.40.206 netmask 0xffffffff broadcast 220.127.116.11
> > inet 18.104.22.168 netmask 0xffffffff broadcast 22.214.171.124
> > inet 126.96.36.199 netmask 0xffffffff broadcast 188.8.131.52
> > inet 184.108.40.206 netmask 0xffffffff broadcast 220.127.116.11
> > inet 18.104.22.168 netmask 0xffffffff broadcast 22.214.171.124
> > inet 126.96.36.199 netmask 0xffffffff broadcast 188.8.131.52
> > ether 00:06:5b:ee:40:32
> > media: Ethernet autoselect (100baseTX <full-duplex>)
> > status: active
> > When the next group of IP were assigned to me, and I set them as aliases
> > on this machine, thats when I started getting the errors.
> When you add aliases for a different subnet, the netmask should be the
> proper one for the subnet ie. netmask 0xfffffff0.
From the man pages (ifconfig(8)):
alias Establish an additional network address for this interface. This
is sometimes useful when changing network numbers, and one wishes
to accept packets addressed to the old interface. If the address
is on the same subnet as the first network address for this
interface, a non-conflicting netmask must be given. Usually
0xffffffff is most appropriate.
More information about the freebsd-questions