>Number:         1540
>Category:       general
>Synopsis:       Apache stops to respond on virtual interfaces
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Dec 10 04:10:00 PST 1997
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.2.4
>Environment:
SunOS atlas 5.6 Generic sun4u sparc SUNW,Ultra-1
>Description:
Solaris 2.6 seems to have a bug in ifconfig so that one must do an extra
ifconfig le0:0 x.x.x.x (machines REAL IP) after you have set the virtual 
interfaces.
This is because it seems like solaris 2.6 assumes that the last ifconfig 
command made is 
setting the machines real IP, which is not the case.

Example, i now only have 1 virtual interface, ifconfig shows:
le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
        inet 194.18.134.14 netmask ffffff00 broadcast 194.18.134.255
        ether 8:0:20:82:bd:d 
le0:1: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 194.18.134.220 netmask ffffff00 broadcast 194.18.134.255

this is how the machine looks after a reboot. And this makes the server to 
think that
its real IP is 194.18.134.220 (which causes IP-checkers looking for 
194.18.134.14 to refuse our connections).

So what i discovered is that if i do ifconfig le0:0 194.18.134.14 up , the 
machine
appears on it's real IP again. But after aprx. 5mins the webserver stop to 
respond
to the virtual interfaces IP (194.18.134.220).  I can still ping all IP's 
fully, and telnet 
to port 80 and the webserver responds.. but it will not load the pages that
are supposed to show on 194.18.134.220, but on 194.18.134.14 the server still 
responds as it should..
>How-To-Repeat:
the following are the only modifications on any services on our machine,
ndd -set /dev/ip ip_enable_group_ifs 0
ndd -set /dev/ip ip_forwarding 1

so to reproduce the problem, do:
ifconfig le0:1 x.x.x.x up
ifconfig le0:0 x.x.x.x (machines REAL IP)
and of course configure up a webserver to respond to both adresses. wait 3-10 
mins
and you should se that webpages under le0:1 will not load.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]



Reply via email to