Problem with routing in VmWare VMS

Ok, I understud!
I remove from rc.conf this rows:
static_routes="clnet"
route_clnet="-net 192.168.2.0/24 192.168.1.10"

new rc.conf:
ifconfig_em0=" inet 192.168.1.10 netmask 255.255.255.0"
ifconfig_em1=" inet 192.168.2.1 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
gateway_enable="YES"


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


netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGS 0 38 em0
127.0.0.1 link#4 UH 0 0 lo0
192.168.1.0/24 link#1 U 0 1153 em0
192.168.1.10 link#1 UHS 0 6 lo0
192.168.2.0/24 link#2 U 0 0 em1
192.168.2.1 link#2 UHS 0 6 lo0

Where more can be trouble?


-------------
Вы писали 22 июня 2012 г., 0:56:49:

On Thu, 21 Jun 2012 15:59:36 -0500, UNIX developer @ Google.com
<developerunix@xxxxxxxxx> wrote:

/etc/rc.conf
ifconfig_em0=" inet 192.168.1.10 netmask 255.255.255.0"
ifconfig_em1=" inet 192.168.2.1 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
gateway_enable="YES"
static_routes="clnet"
route_clnet="-net 192.168.2.0/24 192.168.1.10"

You simply CANNOT do this. Traffic for 192.168.2.0/24 is bound to em1 and
cannot be changed. You setup a static route that basically says "to find
192.168.2.0/24, don't use em1 but instead ask 192.168.1.10 how to find it"?

This makes no sense at all.


--
С уважением,
UNIX mailto:developerunix@xxxxxxxxx

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: RELENG_6_3 ping and DUP packets
    ... RELENG_6_3 ping and DUP packets ... While rebooting to try disabling MSI, I noticed that the machine was still pingable during the reboot, while the thing was still doing its POST routines -- which of course made me do a few double-takes, given that the FreeBSD kernel wasn't even running:) Weirder is that the responses all had the bogus 255 TTL that the dupes had when the system was up. ... So ping replies were coming from both the management CPU and the main CPU when the system was up, and just the management CPU when the system was down. ...
    (freebsd-stable)
  • Netgear MA401 stopped working
    ... the host, seem to be sending packets, but never receive anything back. ... PING 192.168.112.1: 56 data bytes ... I, on the other hand, suspect a hardware problem with the card. ... pci_cfgintr: 0:2 INTA BIOS irq 11 ...
    (freebsd-net)
  • Re: netcat delays between pages over wan
    ... >8000 printers. ... All that is going to show you is that ping in the default mode has ... >servers and Lantronix servers were rebooted. ... By default ping sends 56 byte packets 1 second apart. ...
    (comp.unix.sco.misc)
  • ubr924 modem does not want to talk through its ethernet0 port
    ... hostname burpmaster ... interface cable-modem0 ... input packets with dribble condition detected ... burpmaster#ping 10.0.0.13 <-- Ping my unix box, which I am using to connect to the ubr924 modem's console port. ...
    (comp.dcom.sys.cisco)
  • Failing to use Linux PC as router
    ... I can ping from one computer to the other and from the ... INTERFACES eth0 (?Firewire? ... iface lo inet loopback ... packets transmitted, 5 packets received, 0% packet loss ...
    (Debian-User)