mailing list said:
>
> Hmmm, I'm confused
>
>> If you want to have your aliases attached to the tl0
>> interface, you need to use addresses in that range. So,
>> something like:
>>
>> ifconfig_tl0_alias3="inet XXX.82.15.210 netmask 0x"
>
> That's what I have, and I'm getting those funny a
Hmmm, I'm confused
> If you want to have your aliases attached to the tl0
> interface, you need to use addresses in that range. So,
> something like:
>
> ifconfig_tl0_alias3="inet XXX.82.15.210 netmask 0x"
That's what I have, and I'm getting those funny arplookup error
messages.
> T
mailing list\ said:
>
> Hi Michael,
>
> My network topology skills are limited... does this mean the following:
>
> - my default gateway is on a 255.255.255.240 subnet
> - so is my devices real address
> - there is another device listed there (de0), no problems (internal)
>
> So, if I change the a
M
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: arplookup messages? now what have I done?
>
>
>
> mailing list said:
> >
> > I recently added some aliases to my ipconfig and now I'm
> getting these
> > system messages? Should I be c
mailing list said:
>
> I recently added some aliases to my ipconfig and now I'm getting these
> system messages? Should I be concerned? (FreeBSD 4.6)
>
>
> ifconfig_de0="inet XXX.168.0.219 netmask 255.255.255.0"
> ifconfig_tl0="inet XXX.82.15.219 netmask 255.255.255.240"
> ifconfig_tl0_alias3=
