Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jun 2012 16:35:52 +0300
From:      "UNIX developer @ Google.com" <developerunix@gmail.com>
To:        Mark Felder <feld@feld.me>
Cc:        freebsd-questions@freebsd.org
Subject:   Problem with routing in VmWare VMS
Message-ID:  <853166013.20120622163552@gmail.com>
In-Reply-To: <op.wga3u1vd34t2sn@tech304>
References:  <1842148286.20120621235936@gmail.com> <op.wf9wkzvm34t2sn@tech304> <1274191465.20120622161043@gmail.com> <op.wga3u1vd34t2sn@tech304>

next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Mark!
All work!


-------------
=D0=92=D1=8B =D0=BF=D0=B8=D1=81=D0=B0=D0=BB=D0=B8 22 =D0=B8=D1=8E=D0=BD=D1=
=8F 2012 =D0=B3., 16:31:39:

> On Fri, 22 Jun 2012 08:10:43 -0500, UNIX developer @ Google.com =20
> <developerunix@gmail.com> wrote:

>> now after reboot the problem still the same.
>> ping -S 192.168.2.1 192.168.1.1
>> PING 192.168.1.1 (192.168.1.1) from 192.168.2.1: 56 data bytes
>> ^C
>> --- 192.168.1.1 ping statistics ---
>> 8 packets transmitted, 0 packets received, 100.0% packet loss

> 192.168.1.1 does not know how to find 192.168.2.1, so it can't respond to
> the ping. I bet it only has a default route to the internet. If you add a
> static route on 192.168.1.1 telling it that it can find 192.168.2.0/24 at
> 192.168.1.10 it will probably work.


> On 192.168.1.1:

> route add -net 192.168.2.0/24 192.168.1.10

> Now the pings will work.


--=20
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
 UNIX                          mailto:developerunix@gmail.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?853166013.20120622163552>