RE: Interface aliases


Subject: RE: Interface aliases
From: Mike Barsalou (mbarsalou@aidea.org)
Date: Fri Jun 14 2002 - 08:52:18 AKDT


The route is there already but the gateway is 0.0.0.0 could that be causing
the weirdness?

Another thing that seems odd is that when I telnet from 192.168.4.115 to
192.168.4.11 through the 192.168.4.1 interface...packets at 192.168.4.11
show that they sourced at the 192.168.4.1 interface not the 192.168.4.115
like I would expect.

Any ideas on that?

-----Original Message-----
From: Anthony Valentine [mailto:amv@akvalentine.com]
Sent: Thursday, June 13, 2002 7:03 PM
To: Mike Barsalou
Cc: 'aklug@aklug.org'
Subject: Re: Interface aliases

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 : Fri Jun 14 2002 - 08:52:54 AKDT