Browsing 192.168.0.23 returns 192.168.0.11, why?

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Roberto Inzerill » Fri, 20 Jul 2001 05:49:29



Hi all,
 I have a problem with my linux box. I'm trying to browse from the linux box
(with ip = 192.168.11) the Apache server of another linux box (the one with
ip = 192.168.0.23) but I always get as result the pages generated by the
Apache installed in the 192.168.0.11 . What's wrong with my configuration?
Is Netscape Navigator crazy ?!?! It seems that IP packets are routed inside
the 192.168.0.11 itself instead of going out on the local net but ... why ?!
I also don't ping with success from 192.168.0.11 to 192.168.0.23 (host
unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

The TCP/IP configuration seems ok, I don't make use of DNS (I use the IP
addresses instead). There is no firewall in neither the boxes. Where do I
have to look for in my configuration files? Do you have any idea about the
mistake I'm doing?

thanks in advance,
     Roberto

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Andrei Ivan » Fri, 20 Jul 2001 06:14:38



>  I have a problem with my linux box. I'm trying to browse from the linux box
> (with ip = 192.168.11) the Apache server of another linux box (the one with
> ip = 192.168.0.23) but I always get as result the pages generated by the
> Apache installed in the 192.168.0.11 . What's wrong with my configuration?
> Is Netscape Navigator crazy ?!?! It seems that IP packets are routed inside
> the 192.168.0.11 itself instead of going out on the local net but ... why ?!
> I also don't ping with success from 192.168.0.11 to 192.168.0.23 (host
> unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

Show us 'route -n' output.

--
andrei

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Roberto Inzerill » Fri, 20 Jul 2001 09:54:25


Hi Andrei,

Quote:> > ...
> > I also don't ping with success from 192.168.0.11 to 192.168.0.23 (host
> > unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

> Show us 'route -n' output.

Here it is:

On the 192.168.0.23 "route -n" gives:
Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
127.0.0.0     0.0.0.0    255.0.0.0      U      0        0      0    lo

On the 192.168.0.11 "route -n" gives:
Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    lo

Here I see that something looks curious but I'm not great with routing :-(

                Roberto

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Dean Thompso » Fri, 20 Jul 2001 11:36:33


Hi!,

Quote:> Hi all,
> I have a problem with my linux box. I'm trying to browse from the linux box
> (with ip = 192.168.11) the Apache server of another linux box (the one with
> ip = 192.168.0.23) but I always get as result the pages generated by the
> Apache installed in the 192.168.0.11 . What's wrong with my configuration?
> Is Netscape Navigator crazy ?!?! It seems that IP packets are routed inside
> the 192.168.0.11 itself instead of going out on the local net but ... why
> ?! I also don't ping with success from 192.168.0.11 to 192.168.0.23 (host
> unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

> The TCP/IP configuration seems ok, I don't make use of DNS (I use the IP
> addresses instead). There is no firewall in neither the boxes. Where do I
> have to look for in my configuration files? Do you have any idea about the
> mistake I'm doing?

Is it possible to take a look at the output from /sbin/route -n and
/sbin/ifconfig to see how the network card and routes are configured on the
machine ?

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Bob Hau » Fri, 20 Jul 2001 12:44:08


On Thu, 19 Jul 2001 02:54:25 +0200, Roberto Inzerillo


> On the 192.168.0.11 "route -n" gives:
> Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
> 192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
> 192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    lo

This says that the gateway for the 192.168.0.0 network is your loopback
device.  That's surely wrong, and will give the symptom you posted
(talking to yourself when trying to reach another system on that net).
You need to go into your network setup and see where things are being
set wrong.  You probably entered an address for lo thinking you were
entering one for eth0.  This table should look something like:


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.2.1     0.0.0.0         UG    1      0        0 eth0

IOW, lo should have an address of 127.0.0.1 and be on the 127.0.0.0
network.

--
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.haucks.org/

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by David Efflan » Fri, 20 Jul 2001 12:55:06



> Hi Andrei,
>> > ...
>> > I also don't ping with success from 192.168.0.11 to 192.168.0.23 (host
>> > unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

>> Show us 'route -n' output.

> Here it is:

> On the 192.168.0.23 "route -n" gives:
> Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
> 192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
> 127.0.0.0     0.0.0.0    255.0.0.0      U      0        0      0    lo

> On the 192.168.0.11 "route -n" gives:
> Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
> 192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
> 192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    lo

Something is drastically wrong here.  the lo interface should be 127.0.0.1
with a 127.0.0.0 net route (like on 192.168.0.23).  How did that bogus lo
route get there?  What does ifconfig show for lo?  Did you tamper with or
remove the 127.0.0.1 localhost line in your /etc/hosts?

This apparently tells your 192.168.0.11 box to loop everything for the
192.168.0.0 net back to yourself.

--
David Efflandt  (Reply-To is valid)  http://www.de-srv.com/
http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by M. Buchenried » Fri, 20 Jul 2001 15:58:58



>On the 192.168.0.11 "route -n" gives:
>Destination   Gateway    Genmask        Flags  Metric   Ref    Use  Iface
>192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    eth0
>192.168.0.0   0.0.0.0    255.255.255.0  U      0        0      0    lo

^^^^^^^^^^^                                                        ^^^^^

[...]

This line is completely bogus. Delete it and add a route to your
loopback interface with the correct values. Presently, all packets
sent to the 192.168.0.0 network are routed to your loopback interface.

Michael

--

          Lumber Cartel Unit #456 (TINLC) & Official Netscum
    Note: If you want me to send you email, don't munge your address.

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Villy Kru » Fri, 20 Jul 2001 21:52:30


On Thu, 19 Jul 2001 03:44:08 GMT,


>Kernel IP routing table
>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
>127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
>0.0.0.0         192.168.2.1     0.0.0.0         UG    1      0        0 eth0

What is your reason for adding this route going via 192.168.2.1?
Unless there realy is a router at that IP address and unless that router
realy functionas as the catch-all default route to the rest of the world
you shouldn't have the default route specified that way.  This route
may also prevent a ppp connection to the internet from working properly
as it will be that ppp link that needs the default route rather than
the possibly non-existing router at 192.168.2.1.

Villy

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Bob Hau » Sat, 21 Jul 2001 11:44:21


On 19 Jul 2001 12:52:30 GMT, Villy Kruse


> On Thu, 19 Jul 2001 03:44:08 GMT,


> >Kernel IP routing table
> >Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> >192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
> >127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> >0.0.0.0         192.168.2.1     0.0.0.0         UG    1      0        0 eth0

> What is your reason for adding this route going via 192.168.2.1?

Because it is my Internet gateway.  I have a wireless LAN that's behind
a masquerading firewall.

Quote:> Unless there realy is a router at that IP address and unless that router
> realy functionas as the catch-all default route to the rest of the world

There is and it does.

--
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.haucks.org/

 
 
 

Browsing 192.168.0.23 returns 192.168.0.11, why?

Post by Roberto Inzerill » Sun, 22 Jul 2001 02:56:45


Many thanks to all,
 your suggestions where precious and really halpfull.

I made the corrections needed by modifyng the
/etc/sysconfig/network-script/ifcfg-eth0 and
/etc/sysconfig/network-script/ifcfg-lo (I prefer to correct the right
initialization scripts after some studying instead of just using a GUId
program (like netcfg or linuxconf); I think that often the mistake lays on
them); then I run "/etc/rc.d/init/network restart" but nothing happened. The
problem was still there althought I had the following results  :-(
------------------------------------------
route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
------------------------------------------
ifconfig

eth0      Link encap:Ethernet  HWaddr 00:00:E8:9E:12:6B
          inet addr:192.168.0.11  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0x9400

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:184 errors:0 dropped:0 overruns:0 frame:0
          TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
------------------------------------------

After some more test I was frustrated again. I shut down the system and
restarted it after a while. Halleluia!!! Everything is now perfect. The
problem is solved. It seems that it runs everything as it should now. I
don't know what was wrong. I didn't changed again the network-scripts. Maybe
running "/etc/rc.d/init/network restart" is not enough and some other
configuration had to be reread and initialized with some other program.
B.t.w. now I'm happy and I thank you all because you all showed me the right
direction (i.e. correcting the routing and the absence of the lo interface).

What I wish to know now is just why "/etc/rc.d/init/network restart" was not
enough. I was sure that this is the script that runs everything relating the
network (peripherals initialization, etc...). What else runs at boot time
that interferes with the use of the network? Any idea? Please let me know. I
like evolving after having solved some problems.

  bye,
        Roberto



Quote:

> Hi!,

> > Hi all,
> > I have a problem with my linux box. I'm trying to browse from the linux
box
> > (with ip = 192.168.11) the Apache server of another linux box (the one
with
> > ip = 192.168.0.23) but I always get as result the pages generated by the
> > Apache installed in the 192.168.0.11 . What's wrong with my
configuration?
> > Is Netscape Navigator crazy ?!?! It seems that IP packets are routed
inside
> > the 192.168.0.11 itself instead of going out on the local net but ...
why
> > ?! I also don't ping with success from 192.168.0.11 to 192.168.0.23
(host
> > unreachable) but I ping perfectly from 192.168.0.23 to 192.168.0.11.

> > The TCP/IP configuration seems ok, I don't make use of DNS (I use the IP
> > addresses instead). There is no firewall in neither the boxes. Where do
I
> > have to look for in my configuration files? Do you have any idea about
the
> > mistake I'm doing?

> Is it possible to take a look at the output from /sbin/route -n and
> /sbin/ifconfig to see how the network card and routes are configured on
the
> machine ?

> See ya

> Dean Thompson

> --

+____________________________+____________________________________________+

|
> | Bach. Computing (Hons)     | ICQ     - 45191180
|
> | PhD Student                | Office  - <Off-Campus>
|
> | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)
|
> | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077
|
> | Melbourne, Australia       |
|

+----------------------------+--------------------------------------------+
 
 
 

1. From:192.168.0.101 TO:192.168.0.xxx VIA:192.168.2.1 ?

Hi,

My home network is configured as follows:  an iMac G3 gets the
Internet connection from dial-up (!) and shares it through its en0
interface on 192.168.2.1 (a static, pre-defined setting on MacOS X
10.4 for sharing an Internet connection).  en0 also has an IP of:
192.168.0.101 as shown below:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::20a:27ff:feab:3692%en0 prefixlen 64 scopeid 0x4
        inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255
        inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
        ether 00:0a:27:ab:36:92
        media: autoselect (100baseTX <full-duplex>) status: active
        supported media: 10baseT/UTP 10baseT/UTP <full-duplex>
100baseTX 100baseTX <full-duplex> autoselect autosel

From en0, a crossover cable goes into a DLink DI-624 router on its WAN
connector.  DI-624 (192.168.0.1) then gives dynamic IPs from
192.168.0.2- 192.168.0.255.  Computers are all able to share their
resources and to go on the Internet.

The problem is that the iMac G3 cannot communicate with the other
machines on 192.168.0.x and I'd like to know if there is a way around
it?

Thanks.

2. Solaris SA Interview Question

3. Using 192.168.0 versus 192.168.1

4. error document with php

5. 192.168.0.0 vs. 192.168.1.0

6. Keyboard help

7. Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?

8. Unix's password encryption code

9. NAT Interface 192.168.1.x External 192.168.1.x Possible?

10. Routing Linux 192.168.10.x network to Dlink router on 192.168.1.x network

11. 192.168.0.* vs 192.168.1.*

12. Connection attempt to TCP 192.168.0.13:3128 from 192.168.0.12:2050

13. ynn - yet another newbie - ifconfig eth0 192.168.0.2 returns no such device - unknown interface???