Thanks to anyone who had a think about this one.
It appears the cause is a bit simpler than thought. Quite simply, the
hosting centre have apparantly allocated the IP addresses to someone else
so whilst there is something responding, it isn't actually the right
machine.
Numpties. :)
Regards,
Colin.
On Sat, 17 Mar 2007, Colin Waring wrote:
> Basically, .a and .d respond to pings and pass all traffic
> .b and .c respond to pings but don't appear to pass any other traffic.
>
> IPF is compiled but I've completely turned it off for testing
If you run one tcpdump on lo0 and another on em0 an
I'm sure I wrote out some more info than that but apparently not. I must
be getting confused as I did a description somewhere else, sorry!
Basically, .a and .d respond to pings and pass all traffic
.b and .c respond to pings but don't appear to pass any other traffic.
IPF is compiled but I've com
Somewhere around Sat, Mar 17, 2007 at 14:10 , the world stopped
and listened as Colin Waring graced us with this profound tidbit
of wisdom that would fulfill the enjoyment of future generations:
> Hi folks,
> Been running into brick walls since last night on this one.
> Situation is that our serv
On Sat, 17 Mar 2007, Colin Waring wrote:
> Hi folks,
> Been running into brick walls since last night on this one.
> Situation is that our server has 6.1-RELEASE on it with four IP addresses.
>
> The section of rc.conf is this:
>
> ifconfig_em0="inet a.a.a.a netmask 255.255.255.0"
> ifcon
Hi folks,
Been running into brick walls since last night on this one.
Situation is that our server has 6.1-RELEASE on it with four IP addresses.
The section of rc.conf is this:
ifconfig_em0="inet a.a.a.a netmask 255.255.255.0"
ifconfig_em0_alias0="inet a.a.a.b netmask 255.255.255.255"
ifconfig_em
