On 1/21/2011 9:25 PM, DuWayne Odom wrote:
Better late than never... :-)
That change fixed the problem. Thanks for your response! I was almost on
the edge of giving up on pfsense.
As a side note: Shrewsoft has been a huge life saver for me as an IT
support person. It has allowed my co-workers
On 1/4/2011 12:55 AM, DuWayne Odom wrote:
There must be something tiny that is being missed. h
Obviously a late reply, but if you are using Shrew Soft version 2.1.7 or
later you will need to set the policy generation mode to unique under
the policy tab.
-Matthew
On Tue, Jan 4, 2011 at 12:56 AM, DuWayne Odom d.w.o...@gmail.com wrote:
I am attempting to use Shrewsoft VPN Client to connect to a Cisco VPN
Concentrator at work. I had no issue connecting while using m0n0wall, but
now that I have switched to pfSense I have been unable to get it to work
I just removed that line again and still the same issue. :-(
On Tue, Jan 4, 2011 at 12:59 AM, Chris Buechler cbuech...@gmail.com wrote:
On Tue, Jan 4, 2011 at 12:56 AM, DuWayne Odom d.w.o...@gmail.com wrote:
I am attempting to use Shrewsoft VPN Client to connect to a Cisco VPN
Concentrator
On Tue, Jan 4, 2011 at 12:59 AM, Chris Buechler cbuech...@gmail.com
wrote:
On Tue, Jan 4, 2011 at 12:56 AM, DuWayne Odom d.w.o...@gmail.com
wrote:
I am attempting to use Shrewsoft VPN Client to connect to a Cisco VPN
Concentrator at work. I had no issue connecting while using m0n0wall,
Yes I allow all as seen below...
IDProtoSourcePortDestinationPortGatewayQueueScheduleDescriptionhttp://192.168.1.1:666/firewall_rules_edit.php?if=lanafter=-1
***LAN Address22
666**Anti-Lockout Rule
On Tue, Jan 4, 2011 at 1:08 AM, e...@tm-k.com wrote:
On Tue, Jan 4, 2011 at 12:59 AM, Chris Buechler cbuech...@gmail.com
wrote:
On Tue, Jan 4, 2011 at 12:56 AM, DuWayne Odom d.w.o...@gmail.com
wrote:
I am attempting to use Shrewsoft VPN Client to connect to a Cisco
VPN
I dont know if this helps... I just captured this data.
01:16:52.081340 AF IPv4 (2), length 1166: (tos 0x0, ttl 63, id 11796, offset
0, flags [none], proto UDP (17), length 1162)
67.33.160.231.500 63.148.132.32.500: [udp sum ok] isakmp 1.0 msgid
cookie -: phase 1 I agg:
(sa: doi=ipsec
I dont know if this helps... I just captured this data.
It looks like NAT is ok but I do not think phase2 ends up ok. Are you
alone who tries to use this ipsec tunnel from behind pfSense? Are both
devices configured to use NAT-T (it seems they do but anyway)?
