On Thu, 5 Jun 2003, shrek-m@xxxxxx wrote: > ___cliff rayman___ schrieb: > > > what program are you trying to connect "out" from? > > > > Ajay Sharma wrote: > > > >> eth0 -> 192.168.1.10 (www.sitea.com) > >> eth0:3 -> 192.168.1.13 (www.sited.com) > >> > >> I'm wondering why the traffic is going out as 192.168.1.13 when it > >> should be using eth0 and 192.168.1.10?? For a while we were pulling > >> our > > > > for my little brain the mysql-client is going *in* via .1.13 not out well, it's "out" on the colocated server and "in" the local sql server. The problem is that the sql server is seeing the connection coming in from the alias address 192.168.1.13 (sited.com) when it should be seeing the connection as the real address 192.168.1.10 (sitea.com). > $ man mysqld > --bind-address=IP > IP address to bind to. The server isn't the issue as it binds to it's own address just fine. It's the client that is being seen as the ip alias (.13) instead of the real address (.10). The temporary fix is just to add entries in the mysql tables for user@xxxxxxxxxxxx and it's working now. But what happens when I add in another alias? Will I have to rework all the tables again and add in user@xxxxxxxxxxxx?? That's just not cool as all this worked fine pre-redhat 9. And this isn't a specific mysql problem either. If I ssh from the colocated server to the local sql box, it looks like I'm coming from the alias (.13) instead of the real address (.10). I verified this with 'netstat -nap'. I appreciate your suggestions! Thanks, Ajay -------------------------------------------------------------------- Satyajot (Ajay) Sharma ssharma@xxxxxxx --------------------------------------------------------------------
