Re: Interface aliases


Subject: Re: Interface aliases
From: Anthony Valentine (amv@akvalentine.com)
Date: Thu Jun 13 2002 - 19:03:18 AKDT


Sounds to me like a routing issue. What does '/sbin/route -n' show?

You probably just need to add a route. Try something like this:
route add -net 192.168.4.0 netmask 255.255.255.0 gw 192.168.4.1 dev ethX

Where ethX is the interface name you wish to use.

Then make sure that your default route is set to something other that
the 192.168.4.1 interface.

Hope this helps a little.

Anthony

On Thu, 2002-06-13 at 14:26, Mike Barsalou wrote:
>
> I have an interface 192.168.3.1 and recently I added an alias 192.168.4.1
>
> On this machine is a web server that talks with a MySQL server to get data.
> When I added the alias interface, it started to talk with the MySQL server
> over the new interface....do I use the BindAddress directive?
>
> Also, I only want certain traffic to go over that 192.168.4.1 interface...I
> only want the computer to send traffic destined for 192.168.4 network on
> that interface, however it sends all kinds of traffic over it. How do I
> control that?
>
> Thanks.
>
> Mike
>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.



This archive was generated by hypermail 2a23 : Thu Jun 13 2002 - 19:04:07 AKDT