Hi There,
 
        Yes, when I did the multi homed IP patches for ASSP, it happened from time to time that connections failed awfully, after some debugging I found that the incomming address was that one, 0.0.0.0 that was REALLY weird.. so instead of trying to figure out where I was supposed to connect, I sent the connection to 127.0.0.1
 
        Now... WHY this happens is an excellent question, because obviously 0.0.0.0 is the wildcard IP address for listening, but once a connection is received, the inbound IP is supposed to be the REAL IP that received the connection.
 
        I think it is caused by the socket itself, not by any ASSP code.
 
        Who knows...
 
Regards!
Javier Albinarrate
 
       
----- Original Message -----
Sent: Thursday, August 17, 2006 8:44 PM
Subject: Re: [Assp-user] something really odd

[EMAIL PROTECTED] wrote:
On 16 Aug 2006 at 21:35, Evans Martin wrote:

  
Anyone know what this means?
    

Not really  
 
  
Aug-16-06 21:34:46 Something really odd is going on with this incomming
connection at 0.0.0.0:25
    

If what ASSP believes is your local IP (as a variable) becomes 0.0.0.0, it spits out that log message and then that local IP variable is changed to 127.0.0.1.

This appears to happen during the course of IP connection limiting.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to