|
Posted by Andrew Engels Rump (formerly L on July 25, 2008, 4:45 pm
If you were Registered and logged in, you could reply and use other advanced thread options
This is the famous: "I only pressed *that* button! *Not* *that* button".
I've searched high and low including browsing through the last 8000+
posts in this group but haven't found anything which gave me a clue of
what causes my vpn to stop working. :-( I know I should provide the
configuration (and I will this Monday) but I hope somebody may provide me
with a clue of what events triggered my vpn to stop working.
The employee before me configured the following internet set up:
(internet) 192.168.1.1 -> 192.168.1.2 (ASA 5510) 172.18.1.x -> (network)
The internet router is a standard (Danish) internet router which performs
PAT, DHCP, ... The ASA 5510 is set up to "the same way", i.e., it also
performs PAT, DHCP, ..., i.e., the functionality of the ISP router is
ignored! And the provider claims that we haven't ever asked them to set
their router in bridge-mode, i.e., passing the tcp/ip directly to our
Cisco box.
Then one day some yerk dug a hole without consulting the maps and lo &
behold he cut a fiber and we (and the rest of the people on an island)
went offline! Fortunately we have a WiMax (wireless) so I set out to use
that instead and after changing the following settings through the GUI:
1. the static ip-address & netmask of the ASA to match the WiMax
2. the default route to match the WiMax (deleted and created a new one)
3. the DNS entries in the DHCP settings
everything(*) worked like a charm and we got back to work!
*) The vpn from the outside didn't work of course because our ip-address
changed because we changed provider but that should work again when we
restored the original connection - yeah right!
The next day the original line was back up and I (as far as I know)
restored the values in the ASA - but it didn't work and I fiddled - don't
*do* that - with all the settings and finally consulted the documentation
and suddenly after 15 minutes the packets started flowing through!?!
What happened? Well I don't know but everything seemed to work - except
the vpn! :-(
When I look into the log it complains about "deny ip spoof from
192.168.1.2" (or was it 192.168.1.1) every time I try to connect through
vpn.
What has been changed/removed without my knowledge when I
changed/removed/created the values to connect the WiMax and later to
restore the original connection?
Andrew Engels Rump
--
Software Engineer
E-mail: mailto:newandrew@rump.dk
WWW: http://www.rump.dk/homepage/andrew/
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map