daveb93 wrote:
> My bacula server is multi-homed.
> I am needing port 9102 to answer on all of the IP addresses on the server in
> order to service all of the subnets attached to the machine
>
> I looked at taking care of this on the network routing level but it just
> would not be practical
>
On Wed, Jul 14, 2010 at 9:52 PM, James Harper wrote:
> >
> > My bacula server is multi-homed.
> > I am needing port 9102 to answer on all of the IP addresses on the
> server in
> > order to service all of the subnets attached to the machine
> >
> > I looked at taking care of this on the network r
>My bacula server is multi-homed.
>I am needing port 9102 to answer on all of the IP addresses on the server in
>order to service all of the subnets attached to the machine
>
>I looked at taking care of this on the network routing level but it just would
>not be practical
What's funny is the c
>sorry 9103
As far as SD's go, my experience is that they "do not" bind to a specific
address
unless told to, but then again, the case I refer to had two interfaces on the
same subnet. SDAddresses should still accomplish what you need...
--
>
> My bacula server is multi-homed.
> I am needing port 9102 to answer on all of the IP addresses on the
server in
> order to service all of the subnets attached to the machine
>
> I looked at taking care of this on the network routing level but it
just would
> not be practical
>
> Any help wou
sorry 9103
+--
|This was sent by daveb93_2...@yahoo.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
My bacula server is multi-homed.
I am needing port 9102 to answer on all of the IP addresses on the server in
order to service all of the subnets attached to the machine
I looked at taking care of this on the network routing level but it just would
not be practical
Any help would be greatly
