On Tue, Feb 08, 2011 at 04:52:05PM +, Tom Evans wrote:
> If you use Listen *:80, and use a hub, your apache instance will not
> start responding to requests on port 80 directed to another computer
> on the same hub. Seriously.
Then why bother to even have a listen if it doesn't make a differen
On Tue, Feb 8, 2011 at 4:41 PM, Mike Brown wrote:
> On Tue, Feb 08, 2011 at 02:00:24PM +, Tom Evans wrote:
>> > Then the ethernet ports on both computers
>> > would "see" IP traffic meant for each other.
>>
>> No.
>
> Ah, but that is indeed what happens. If a hub is used, all packets are plac
On Tue, Feb 08, 2011 at 02:00:24PM +, Tom Evans wrote:
> > Then the ethernet ports on both computers
> > would "see" IP traffic meant for each other.
>
> No.
Ah, but that is indeed what happens. If a hub is used, all packets are placed
onto all of the jacks of the hub, therefore both compute
On Tue, Feb 8, 2011 at 12:36 PM, Mike Brown wrote:
> On Tue, Feb 08, 2011 at 12:29:00PM +, Tom Evans wrote:
>> *:80 means "listen on on all addresses on all interfaces THIS BOX
>> has", not "respond to every IP address in the world". Furthermore, how
>> would the 'request meant for the linux s
> It is possible that the Linux box and the Windblows box could be connected
> to a hub, instead of a switch. Then the ethernet ports on both computers
> would "see" IP traffic meant for each other.
>
> To me it would be safer not to use the wildcard.
This does not impact what data normal socket
On Tue, Feb 08, 2011 at 12:29:00PM +, Tom Evans wrote:
> *:80 means "listen on on all addresses on all interfaces THIS BOX
> has", not "respond to every IP address in the world". Furthermore, how
> would the 'request meant for the linux server' be routed to the
> windows box?
Not every address
On Tue, Feb 8, 2011 at 12:21 PM, Mike Brown wrote:
> On Tue, Feb 08, 2011 at 12:11:26PM +, Tom Evans wrote:
>> Apache doesn't control how packets get routed to your computer, it
>> only controls what it does when they arrive. If you listen on *:80 or
>> 192.168.1.2:80, then anything that can r
On Tue, Feb 08, 2011 at 12:11:26PM +, Tom Evans wrote:
> Apache doesn't control how packets get routed to your computer, it
> only controls what it does when they arrive. If you listen on *:80 or
> 192.168.1.2:80, then anything that can route packets to that
> server/port will communicate with
On Tue, Feb 08, 2011 at 01:02:18PM +0100, Alain Roger wrote:
> i have a host (windows 7) on wihich i have web server with apache/PHP/MySQL.
> for now this computer has IP 192.168.1.2 (for example).
> on the other hand i have a linux (Fedora 14) computer with IP 192.168.1.50
> (for example) which sh
On Tue, Feb 8, 2011 at 12:02 PM, Alain Roger wrote:
> Hi,
>
> i have a host (windows 7) on wihich i have web server with apache/PHP/MySQL.
> for now this computer has IP 192.168.1.2 (for example).
> on the other hand i have a linux (Fedora 14) computer with IP 192.168.1.50
> (for example) which sh
Hi,
i have a host (windows 7) on wihich i have web server with apache/PHP/MySQL.
for now this computer has IP 192.168.1.2 (for example).
on the other hand i have a linux (Fedora 14) computer with IP 192.168.1.50
(for example) which should access to the web server via IP 192.168.1.2.
except Listen
11 matches
Mail list logo
