[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: virtual interfaces



On Sun, Dec 05, 2004 at 11:07:55PM +1100, Sam Watkins wrote:
> On Sat, Dec 04, 2004 at 11:07:08AM -0500, Antonio Rodriguez wrote:
> > After 
> > 1. adding the needed paragraph to /etc/network/interfaces to reflect
> > the virtual iface with 'anotherIP', 
> > 2. adding the corresponding file in /etc/apache2/sites-available,
> > 3. creating the symlink in /etc/apache2/sites-enabled
> > 4. stopping, starting, reloading again networking and apache2
> > still can't get the added domain to respond. My question is: is there
> > any other step that I am missing, or should I make the assumption that
> > the 'anotherIP' is not pointing to my physical machine?
> 
> Did you type "ifconfig" to check that the IP alias is set up?
> it should show up as eth0:1 or whatever number you gave it.
> 
> can you ping the new IP address from the machine running apache2?
> what about from a different machine?

Here is what happens:
dedicated-deb-17boom:/etc/apache2# ping 'anotherIP'
PING 'anotherIP' ('anotherIP') 56(84) bytes of data.
>From 'mainIP' icmp_seq=1 Destination Host Unreachable
>From 'mainIP' icmp_seq=2 Destination Host Unreachable
>From 'mainIP' icmp_seq=3 Destination Host Unreachable

It seems to be a configuration problem in my side, here is what I
have:

dedicated-deb-17boom:/etc/apache2# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:01:29:94:A2:1B
          inet addr:'mainIP'  Bcast:'mainIPfragment'.255  Mask:255.255.255.0
          inet6 addr: fe80::201:29ff:fe94:a21b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:41030 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6365 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2894637 (2.7 MiB)  TX bytes:1354262 (1.2 MiB)
          Interrupt:177 Base address:0xec00

eth0:0    Link encap:Ethernet  HWaddr 00:01:29:94:A2:1B
          inet addr:'anotherIP'  Bcast:'mainIPfragment'.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:177 Base address:0xec00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1184 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1184 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:318605 (311.1 KiB)  TX bytes:318605 (311.1 KiB)

and also 'cat /etc/network/interfaces' shows

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 'mainIP'
        netmask 255.255.255.0
        network 'mainIPfragment'.0
        broadcast 'mainIPfragment'.255
        gateway 'mainIPfragment'.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 66.180.166.247
        dns-search netsonic.net

# The secondary network interface (virtual 1)
auto eth0:0
iface eth0:0 inet static
        address 'anotherIP'
        netmask 255.255.255.0
        network 'mainIPfragment'.0
        broadcast 'mainIPfragment'.255
        gateway 'mainIPfragment'.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 66.180.166.247
        dns-search netsonic.net


(????) 
Sam, all your help and input is greatly appreciated

earlier, before your post, after reading some of the documentation for
apache2, I had written in ports.conf:

Listen 'mainIP':80
Listen 'anotherIP':80

and as a result:

Starting web server: Apache2(99)Cannot assign requested address: make_sock: could not bind to address 'anotherIP':80
no listening sockets available, shutting down
Unable to open logs

It tells me that if eth0 is already using port 80, eth0:0 is not
going to be able to use it too. May be I should have started aliasing
eth0:1, don't know.


> How are you testing if apache is listening?  try:
> 
>   telnet 1.2.3.4 80
> 
> from the machine that apache2 is running on,
> where 1.2.3.4 is your new ip address.

apache is working perfectly with the 'mainIP', the trouble is with the
second, now I have reverted to only
Listen 80
in ports.conf to maintain the main server running until the problems
is solved.



Reply to: