<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Just ping to pfsense server but Unable to Ping my Remote Netowork]]></title><description><![CDATA[<p dir="auto">my Scenario is i am coming from<br />
My remote Network where Pfsense server is running Ip Sceme is 192.168.1.0/24<br />
Pfsense Ip addres is 192.168.1.20<br />
Clients pool is 192.168.2.0/24<br />
Local Network 192.168.1.0/24</p>
<p dir="auto">but when i connect to it it is connected and just ping the 192.168.1.20 the Pfsense and after enable http in firewall i can able to open http://192.168.120 but unable to ping any other ip addrss inside that network.</p>
<p dir="auto">VPN Pfsense -openVPN-Custom<br />
push "route 192.168.1.0 255.255.255.0 ";</p>
<p dir="auto">but still unable to connect . i have these logs.</p>
<p dir="auto">Fri Jan 15 16:00:00 2010 us=217996 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,route 192.168.1.0 255.255.255.0,route 192.168.2.1,ping 10,ping-restart 60,ifconfig 192.168.2.6 192.168.2.5'<br />
Fri Jan 15 16:00:00 2010 us=218240 OPTIONS IMPORT: timers and/or timeouts modified<br />
Fri Jan 15 16:00:00 2010 us=218268 OPTIONS IMPORT: –ifconfig/up options modified<br />
Fri Jan 15 16:00:00 2010 us=218289 OPTIONS IMPORT: route options modified<br />
Fri Jan 15 16:00:00 2010 us=281735 TAP-WIN32 device [Local Area Connection 2] opened: \.\Global{5E5D0904-D3C3-4DF7-96B1-967880569A19}.tap<br />
Fri Jan 15 16:00:00 2010 us=288660 TAP-Win32 Driver Version 8.4<br />
Fri Jan 15 16:00:00 2010 us=294556 TAP-Win32 MTU=1500<br />
Fri Jan 15 16:00:00 2010 us=298594 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.2.6/255.255.255.252 on interface {5E5D0904-D3C3-4DF7-96B1-967880569A19} [DHCP-serv: 192.168.2.5, lease-time: 31536000]<br />
Fri Jan 15 16:00:00 2010 us=328183 Successful ARP Flush on interface [131076] {5E5D0904-D3C3-4DF7-96B1-967880569A19}<br />
Fri Jan 15 16:00:00 2010 us=491360 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:00 2010 us=491426 Route: Waiting for TUN/TAP interface to come up…<br />
Fri Jan 15 16:00:01 2010 us=599132 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:01 2010 us=599205 Route: Waiting for TUN/TAP interface to come up...<br />
Fri Jan 15 16:00:02 2010 us=693005 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:02 2010 us=693081 Route: Waiting for TUN/TAP interface to come up...<br />
Fri Jan 15 16:00:03 2010 us=786844 TEST ROUTES: 3/3 succeeded len=3 ret=1 a=0 u/d=up<br />
Fri Jan 15 16:00:03 2010 us=786925 route ADD 192.168.1.0 MASK 255.255.255.0 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=806350 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=806427 route ADD 192.168.1.0 MASK 255.255.255.0 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=824514 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=824585 route ADD 192.168.2.1 MASK 255.255.255.255 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=838830 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=838902 Initialization Sequence Completed<br />
now when i dial from remote network i get the ip address<br />
Fri Jan 15 16:00:00 2010 us=217996 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,route 192.168.1.0 255.255.255.0,route 192.168.2.1,ping 10,ping-restart 60,ifconfig 192.168.2.6 192.168.2.5'<br />
Fri Jan 15 16:00:00 2010 us=218240 OPTIONS IMPORT: timers and/or timeouts modified<br />
Fri Jan 15 16:00:00 2010 us=218268 OPTIONS IMPORT: --ifconfig/up options modified<br />
Fri Jan 15 16:00:00 2010 us=218289 OPTIONS IMPORT: route options modified<br />
Fri Jan 15 16:00:00 2010 us=281735 TAP-WIN32 device [Local Area Connection 2] opened: \.\Global{5E5D0904-D3C3-4DF7-96B1-967880569A19}.tap<br />
Fri Jan 15 16:00:00 2010 us=288660 TAP-Win32 Driver Version 8.4<br />
Fri Jan 15 16:00:00 2010 us=294556 TAP-Win32 MTU=1500<br />
Fri Jan 15 16:00:00 2010 us=298594 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.2.6/255.255.255.252 on interface {5E5D0904-D3C3-4DF7-96B1-967880569A19} [DHCP-serv: 192.168.2.5, lease-time: 31536000]<br />
Fri Jan 15 16:00:00 2010 us=328183 Successful ARP Flush on interface [131076] {5E5D0904-D3C3-4DF7-96B1-967880569A19}<br />
Fri Jan 15 16:00:00 2010 us=491360 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:00 2010 us=491426 Route: Waiting for TUN/TAP interface to come up…<br />
Fri Jan 15 16:00:01 2010 us=599132 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:01 2010 us=599205 Route: Waiting for TUN/TAP interface to come up...<br />
Fri Jan 15 16:00:02 2010 us=693005 TEST ROUTES: 0/0 succeeded len=3 ret=0 a=0 u/d=down<br />
Fri Jan 15 16:00:02 2010 us=693081 Route: Waiting for TUN/TAP interface to come up...<br />
Fri Jan 15 16:00:03 2010 us=786844 TEST ROUTES: 3/3 succeeded len=3 ret=1 a=0 u/d=up<br />
Fri Jan 15 16:00:03 2010 us=786925 route ADD 192.168.1.0 MASK 255.255.255.0 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=806350 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=806427 route ADD 192.168.1.0 MASK 255.255.255.0 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=824514 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=824585 route ADD 192.168.2.1 MASK 255.255.255.255 192.168.2.5<br />
Fri Jan 15 16:00:03 2010 us=838830 Route addition via IPAPI succeeded<br />
Fri Jan 15 16:00:03 2010 us=838902 Initialization Sequence Completed</p>
]]></description><link>https://forum.netgate.com/topic/20701/just-ping-to-pfsense-server-but-unable-to-ping-my-remote-netowork</link><generator>RSS for Node</generator><lastBuildDate>Sat, 16 May 2026 02:00:41 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/20701.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 15 Jan 2010 12:24:08 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Just ping to pfsense server but Unable to Ping my Remote Netowork on Mon, 25 Jan 2010 08:00:39 GMT]]></title><description><![CDATA[<p dir="auto">My problem is solved.<br />
Set pfsense_Pc as a  Gateway to all office computer whom you want to connect from remote pc(road warier )</p>
]]></description><link>https://forum.netgate.com/post/220694</link><guid isPermaLink="true">https://forum.netgate.com/post/220694</guid><dc:creator><![CDATA[farrukhndm]]></dc:creator><pubDate>Mon, 25 Jan 2010 08:00:39 GMT</pubDate></item><item><title><![CDATA[Reply to Just ping to pfsense server but Unable to Ping my Remote Netowork on Mon, 18 Jan 2010 09:53:09 GMT]]></title><description><![CDATA[<p dir="auto">i have same problem and can do the same, ping the firewall.</p>
<p dir="auto">Have you been able to figure it out or GruensFroeschli what subnet are you thinking there is missing ?</p>
]]></description><link>https://forum.netgate.com/post/219880</link><guid isPermaLink="true">https://forum.netgate.com/post/219880</guid><dc:creator><![CDATA[Glennbones]]></dc:creator><pubDate>Mon, 18 Jan 2010 09:53:09 GMT</pubDate></item><item><title><![CDATA[Reply to Just ping to pfsense server but Unable to Ping my Remote Netowork on Fri, 15 Jan 2010 12:29:22 GMT]]></title><description><![CDATA[<p dir="auto">Can you please add a diagram?<br />
I don't get where, what IP range is out of your description.<br />
(You're missing at least one subnet if this is a site to site connection)</p>
]]></description><link>https://forum.netgate.com/post/219635</link><guid isPermaLink="true">https://forum.netgate.com/post/219635</guid><dc:creator><![CDATA[GruensFroeschli]]></dc:creator><pubDate>Fri, 15 Jan 2010 12:29:22 GMT</pubDate></item></channel></rss>