Westell 9100EM VPN Issue

I have a work laptop that utilizes a Cisco VPN in order to communicate to the work server. I connect wirelessly thru my home network via the Westell 9100EM. This has worked flawlessly for 3-4 years.
Less than a week ago, it stopped working. I could access server based drives via a hard IP address but not the normal way. Likewise, OUTLOOK no longer would access the email server.
Three observations:
1. I went to a Starbucks and attempted to use the VPN. This was successful (wireless).
2. At home, I then tried a wired connection to the Westell router and it also successfully connected via the VPN.
3. Normal wireless connectivity (no VPN) via the Westell functions correctly.
The VPN connection fails only at home and when using wireless connectivity - this failure only manifested itself about a week ago after 3-4 years of successful operation. I have also performed a hard reset of the router to no avail.
Any insight into this issue and resolution would be appreciated.

Well, I just got the replacement Westell router (a Rev. B - mine was a Rev. A) and set it up to try it out.
**bleep** if it didn't fail in the same way! I guess it's not a router issue after all. I am completely stumped as to why the VPN fails wirelessly only at my home. More ideas and comments are welcome.
BTW, I think I will keep my old router and return the new one. My old router is "burned in" and has more options than the new one in some areas. Also, Verizon gave me a contact number for Westell tech support - I'll be calling them next week.
Harvey

Similar Messages

Westell 9100EM - DNS issue.

Some time ago DNS started to work unstable.
I've read similar cases around, but none of them looks similar to mine...
DNS stop functioning all the time for several seconds...
E.g.. If I constantly do the nslookup than at least once a minute I'm getting behavior showed below.
At the same time, Google DNS responds with no issues.
I managed to configure most of my numerous devices to use Google DNS, but I do not like such approach.
Router firmware update did not help.
In router logs there is a line:
Apr 19 22:31:23 2011 System Log Message daemon.warn DNS: unknown PTR name format
I could not find correlation between this line and issue, but I did not look deep enough, though.
Any ideas?
Thank you.
DK
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
DNS request timed out.
   timeout was 2 seconds.
DNS request timed out.
   timeout was 2 seconds.
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.homeAddress: 192.168.1.1
DNS request timed out.   timeout was 2 seconds.
DNS request timed out.   timeout was 2 seconds.
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245

(I'm topicstarter here)...
Funny thing, I contacted Verizon customer support recently and encountered very intellegent and responsive person who read all the details (I used the live chat option) and suggested to replace router for free with the new one - not Westel, something starts with letter A.
I was little bit disappointed that new router had only 100Mb switch and no 5GHz band support... But at least it supports the wifi-N...
Anyway, I do not need all these bells and whisles cause I'm using NetGear router for wifi + Cisco home switch for wired network.
Sorry, I deviated from the main issue course.
I do not have any update on the DNS issue cause all my devices still configured to use Google DNS servers.
However, I expect that quite soon I will get Logitech Revue and will have update on this issue.

Fios Westell Model 9100EM firmware issue

So i'm a born again Fios Internet owner, since I move from an area where I had Fios to an area that didn't and now move again to an area that has it.
I was given a cd about my router, and saw information about updating the firmware. I log into the router control panel where it asked about the URL to the firmware. I did not know, so I Google the model and firmware, and I was brought to this POST...
So I looked up the fireware for my router and they provided a firmware of 1.02.00.04, but the firmware on my router currently is 1.03.00.08. Of course it wouldn't allow me to install the downgrade, but why isn't the 1.03.00.08 not on there?
Fios Router Firmware Download Site

It's actually a good thing 1.03.00.08 isn't on there.
It breaks routers, as you can see from the post I made a couple days ago: http://forums.verizon.com/t5/FiOS-Internet/Where-have-all-my-router-s-features-gone-Westell-9100EM/t...
But, if you're really interested, here's the URL for the firmware: http://download.verizon.net/webdownload/firmware/upgrades/westell_router_9100em/A90-9100EM15-10-1.03...
Also, if you read through my post, downgrading is possible, but it takes more work than the average user may be willing to do (and even still, Verizon forces new updates on your router, even if you don't agree to them).

Wireless IP Camera Won't Connect To Westell 9100EM Router

I'm trying to connection an IP camera, on Fios, to my Verizon Westell 9100EM router.
Connecting the camera via a wired connection works fine. Port forwarding is automatically configured when turning the camera on, at TCP ANY 554, and the IP camera is viewable on the web. No worries.
However, when unplugging the cord, the router never recogizes the camera. Not after resetting, powering off/on, etc. Both the WEP and SSID are set correctly on the camera. All other wireless devices (laptops, Xbox 360, iPhone, etc.) work fine on the router.
Naturally, the camera people blame Verizon and Verizon blames the camera people.
Does anyone have any ideas?
Thanks!

What are the details on the camera (Make, model, etc) ?
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it.
If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Westell 9100em crashes periodically

I have had a Westell 9100em for about a year - (model no A90-9100EM15-10, firmware version 1.02.00.04),
Every so often, the router crashes and loses all configuration information. In addition, all log entries are wiped out except for a number of entries that read December 31, 2002. This usually happens when I am away and most dependent on having access to my network.
UPNP is disabled. I am using WPA/WPA2 security on the wireless. I have static mac addresses that are working fine when the router is up and my connection is coax.
More recently I have discovered that one thing that can cause it to crash is trying to access the wireless from a MAC laptop. Even if a machine is not authorized to access the wireless, I don't think it should be crashing the router,
Verizon replaced the router a couple months into this and it seemed to go away for awhile, but maybe I was just lucky and no MAC users were trying to access my wireless. It seems like a firmware issue and I see similar symptoms reported but only the one solution - turning off UPNP - which didn't help in my case. As near as I can tell, the firmware version I have is the latest. Any ideas anyone?
Thanks in advance!

This is a problem with verizons equipment i have the same issues. I recently was contacted by someone at verizon who is contacting the distributors of these routers. Hopefully they get the problems fixed.

Flaky VOIP with Westell 9100em

After adding FiOS TV last week my voip started flaking out, working sometimes, then not. I've moved my voip box to the DMZ of the router without any change of behavior. I can receive calls, but as soon as I do I cannot dial out for a while.
After chatting with my voip provider they said the Westell 9100em is the problem and SPI is getting in the way. I tend to agree with that diagnosis but do not know how to fix it. I don't know a lot about SPI, but it's frustrating the the DMZ isn't really wide open to the world.
I tried some Advanced Filtering rules to disable SPI without luck.
Any suggestions greatly appreciated. I really like my voip provider but I'm unwilling to put their box in front of the Westell router.

You did setup a static IP that is outside of the DHCP range of the router:
portforward.com -> forum -› Knowledge Base -› How to choose a Static IP address
http://forum.portforward.com/YaBB.cgi?num=1116577357
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Westell 9100em: Ports not forwarding

I moved into a new apartment recently with Fios and a Westell A90 9100EM15-10 and I haven't figured out how to port forward with it yet. I need these ports forwarded:
7777(TCP/UDP)
28900 (TCP)
27900 (UDP)
28910 (TCP)
I followed the instructions an admin posted in this thread: http://forums.verizon.com/t5/FiOS-Internet/port-forward-on-new-Westell-9100em/m-p/3021
However, when I test the ports (for instance, port 7777 http://www.utorrent.com/testport?port=7777 here,) it never says any of them are open. I have followed the directions step by step. On the port forwarding menu, it lists my entry for these ports as active for the local host and address 192.168.1.35, the static IP I have assigned to my computer. The protocols read as follows:
TCP Any -> 7777
        UDP Any -> 7777
        TCP Any -> 28900
        UDP Any -> 27900
        TCP Any -> 28910
I have experience with port forwarding in the past with a Linksys router, but it apparently simply is not working out for me with this Westell. Any assistance is appreciated...

Do yours actually open? I know Borderlands has serious connectivity issues right now. My issue is that it doesn't seem like these ports are ever actually open for me. I don't see why every port check site I used should return "closed" if they're actually open.

Remote access Vpn issue

Dear All,
I have configured remote access vpn without using split tunnel.Everything is working fine.I can access all the inside network which is allowed in acl.
I am facing strange issue now. I have created a pool for remote access vpn with a range 192.168.5.8/29.I can access my internal subnets 10.10.0.0/16.
I have below acess-list for acl-in.
access-list acl-in extended permit ip object-group vpnclients 192.168.5.8 255.255.255.248
object-group network vpnclients
network-object host 10.110.100.26
network-object host 10.106.100.15
network-object host 10.10.10.6
network-object host 10.10.20.82
network-object host 10.110.100.48
network-object host 10.10.20.53
network-object host 10.10.20.54
network-object host 10.60.100.1
network-object host 10.10.10.75
network-object host 10.10.20.100
network-object host 10.10.130.136
network-object host 10.106.100.16
network-object host 10.106.100.9
network-object host 10.170.100.1
network-object host 10.170.100.2
network-object host 10.170.100.21
network-object host 10.101.100.20
network-object host 10.170.100.25
So whichever IPs i have called in vpnclient group is able to access via RA vpn.Issue is when i try to access internal network of 192.168.198.0/24, i am able to access it without adding in vpnclient group. Even for 192.168.197.0/24,192.168.197.0/24 the same. But for 10.10.0.0/16 we can access only after adding in vpnclient group. Any one has face this issue before. Is this because of same network i mean 192.168.0.0 something like that.There is no other staement in acl-in for 192.168.0.0
Regards
-Danesh Ahammad

Hi,
If i read correctly you made the RA vpn "without" split tunnel, correct? if that is the case, all of the traffic will traverse the vpn connection (tunnel all) , the access-list "acl-in" is of no use to it.
try converting it to use split tunnel, i am sure that way you can not access resources that are not mentioned in the list.
~Harry

Any ideas how to better troubleshoot VPN issue?

Hi,
I've recently upgraded my WLAN router to a brand new AVM FRITZ!Box WLAN 7390, in part for its VPN capabilities.
So far, I've been unable to create a working connection.
AVM's VPN is based on Cisco IPSec, and they provide a step-by-step procedure on how configure a Mac-based VPN connection (http://www.avm.de/de/Service/Service-Portale/Service-Portal/VPN_Interoperabilita et/16206.php - unfortunately only available in German, sorry). Following it, I still can't get it to work. Contacting their support I got first the same procedure and after pointing out I already followed it a "we don't support other vendors".
Funny enough, I got a second VPN connection to my work's VPN server just fine, though admittedly there we have a true Cisco box.
My initial setup was based on a 192.x.x.x net on my AVM, I could establish a VPN connection but coudn't ping/ssh/http/you-name-the-protocol in either direction. Our companies net is a 10.x.x.x net so, and as I have also VMware fusion running on my Mac with DHCP enabled on a different 192.x.x.x net plus a third 192.x.x.x net from my Wifi access I decided to reconfigure my AVM net to a 172.x.x.x net and stop VMware services for the tests (ie simplify as much as I could to help troubleshoot).
Alas, instead of being able to establish a non-working VPN connection, now I ain't able to get the tunnel up. IKE Phase 1 completes but Phase 2 doesn't.
Here's the relevant section from kernel.log:
Dec 30 11:47:57 jupiter configd[16]: IPSec connecting to server <myservernameismybusiness>.dyndns.info
Dec 30 11:47:57 jupiter configd[16]: SCNC: start, triggered by SystemUIServer, type IPSec, status 0
Dec 30 11:47:57 jupiter configd[16]: IPSec Phase1 starting.
Dec 30 11:47:57 jupiter racoon[1910]: IPSec connecting to server 77.x.x.x
Dec 30 11:47:57 jupiter racoon[1910]: Connecting.
Dec 30 11:47:57 jupiter racoon[1910]: IPSec Phase1 started (Initiated by me).
Dec 30 11:47:57 jupiter racoon[1910]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1).
Dec 30 11:47:58 jupiter racoon[1910]: IKEv1 Phase1 AUTH: success. (Initiator, Aggressive-Mode Message 2).
Dec 30 11:47:58 jupiter racoon[1910]: IKE Packet: receive success. (Initiator, Aggressive-Mode message 2).
Dec 30 11:47:58 jupiter racoon[1910]: IKEv1 Phase1 Initiator: success. (Initiator, Aggressive-Mode).
Dec 30 11:47:58 jupiter racoon[1910]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 3).
Dec 30 11:47:58 jupiter racoon[1910]: IKE Packet: transmit success. (Information message).
Dec 30 11:47:58 jupiter racoon[1910]: IKEv1 Information-Notice: transmit success. (ISAKMP-SA).
Dec 30 11:47:58 jupiter racoon[1910]: IPSec Phase1 established (Initiated by me).
Dec 30 11:47:58 jupiter racoon[1910]: IPSec Extended Authentication requested.
Dec 30 11:47:58 jupiter configd[16]: IPSec requesting Extended Authentication.
Dec 30 11:48:01 jupiter configd[16]: IPSec sending Extended Authentication.
Dec 30 11:48:01 jupiter racoon[1910]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 11:48:01 jupiter racoon[1910]: IPSec Extended Authentication sent.
Dec 30 11:48:02 jupiter racoon[1910]: IKEv1 XAUTH: success. (XAUTH Status is OK).
Dec 30 11:48:02 jupiter racoon[1910]: IPSec Extended Authentication Passed.
Dec 30 11:48:02 jupiter racoon[1910]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 11:48:02 jupiter racoon[1910]: IKEv1 Config: retransmited. (Mode-Config retransmit).
Dec 30 11:48:02 jupiter racoon[1910]: IPSec Network Configuration requested.
Dec 30 11:48:03 jupiter racoon[1910]: IPSec Network Configuration established.
Dec 30 11:48:03 jupiter racoon[1910]: IKE Packet: receive success. (MODE-Config).
Dec 30 11:48:03 jupiter configd[16]: IPSec Network Configuration started.
Dec 30 11:48:03 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-ADDRESS = 172.77.7.14.
Dec 30 11:48:03 jupiter configd[16]: IPSec Network Configuration: SAVE-PASSWORD = 1.
Dec 30 11:48:03 jupiter configd[16]: IPSec Network Configuration: DEFAULT-ROUTE = local-address 172.77.7.14/32.
Dec 30 11:48:03 jupiter configd[16]: host_gateway: write routing socket failed, command 2, No such process
Dec 30 11:48:03 jupiter configd[16]: IPSec Phase2 starting.
Dec 30 11:48:03 jupiter configd[16]: IPSec Network Configuration established.
Dec 30 11:48:03 jupiter configd[16]: IPSec Phase1 established.
Dec 30 11:48:03 jupiter configd[16]: event_callback: Address added. previous interface setting (name: en1, address: 192.168.43.242), current interface setting (name: utun0, family: 1001, address: 172.77.7.14, subnet: 255.255.255.255, destination: 172.77.7.14).
Dec 30 11:48:03 jupiter racoon[1910]: IPSec Phase2 started (Initiated by me).
Dec 30 11:48:03 jupiter racoon[1910]: IKE Packet: transmit success. (Initiator, Quick-Mode message 1).
Dec 30 11:48:03 jupiter configd[16]: network configuration changed.
Dec 30 11:48:03 jupiter configd[16]: IPSec port-mapping update for en1 ignored: VPN is the Primary interface. Public Address: ac4d070e, Protocol: None, Private Port: 0, Public Port: 0
Dec 30 11:48:03 jupiter configd[16]:
Dec 30 11:48:03 jupiter configd[16]: setting hostname to "jupiter.local"
Dec 30 11:48:03 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:06 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:07 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:09 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:09 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:12 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:13 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:15 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:15 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:18 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:18 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:21 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:21 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:24 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:25 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:27 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:27 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:30 jupiter racoon[1910]: IKE Packet: transmit success. (Phase2 Retransmit).
Dec 30 11:48:30 jupiter racoon[1910]: IKE Packet: receive success. (Information message).
Dec 30 11:48:33 jupiter configd[16]: IPSec disconnecting from server 77.x.x.x
Dec 30 11:48:33 jupiter racoon[1910]: IPSec disconnecting from server 77.x.x.x
Dec 30 11:48:33 jupiter racoon[1910]: IKE Packet: transmit success. (Information message).
Dec 30 11:48:33 jupiter racoon[1910]: IKEv1 Information-Notice: transmit success. (Delete ISAKMP-SA).
Dec 30 11:48:33 jupiter configd[16]: SCNC Controller: service_ending_verify_primaryservice, waiting for PrimaryService. status = 1
Dec 30 11:48:33 jupiter configd[16]:
Dec 30 11:48:33 jupiter configd[16]: network configuration changed.
Dec 30 11:48:33 jupiter configd[16]: SCNC Controller: ipv4_state_changed, done waiting for ServiceID.
Dec 30 11:48:33 jupiter configd[16]:
Dec 30 11:48:33 jupiter configd[16]: setting hostname to "jupiter"
When connecting to my work-place it looks like:
Dec 30 12:33:14 jupiter configd[16]: IPSec connecting to server <mycompanyismybusiness>.ch
Dec 30 12:33:14 jupiter configd[16]: SCNC: start, triggered by SystemUIServer, type IPSec, status 0
Dec 30 12:33:14 jupiter configd[16]: IPSec Phase1 starting.
Dec 30 12:33:14 jupiter racoon[1976]: IPSec connecting to server 62.x.x.x
Dec 30 12:33:14 jupiter racoon[1976]: Connecting.
Dec 30 12:33:14 jupiter racoon[1976]: IPSec Phase1 started (Initiated by me).
Dec 30 12:33:14 jupiter racoon[1976]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1).
Dec 30 12:33:14 jupiter racoon[1976]: IKEv1 Phase1 AUTH: success. (Initiator, Aggressive-Mode Message 2).
Dec 30 12:33:14 jupiter racoon[1976]: IKE Packet: receive success. (Initiator, Aggressive-Mode message 2).
Dec 30 12:33:14 jupiter racoon[1976]: IKEv1 Phase1 Initiator: success. (Initiator, Aggressive-Mode).
Dec 30 12:33:14 jupiter racoon[1976]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 3).
Dec 30 12:33:14 jupiter racoon[1976]: IPSec Phase1 established (Initiated by me).
Dec 30 12:33:15 jupiter racoon[1976]: IPSec Extended Authentication requested.
Dec 30 12:33:15 jupiter configd[16]: IPSec requesting Extended Authentication.
Dec 30 12:33:21 jupiter configd[16]: IPSec sending Extended Authentication.
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Extended Authentication sent.
Dec 30 12:33:21 jupiter racoon[1976]: IKEv1 XAUTH: success. (XAUTH Status is OK).
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Extended Authentication Passed.
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 12:33:21 jupiter racoon[1976]: IKEv1 Config: retransmited. (Mode-Config retransmit).
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Network Configuration requested.
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Network Configuration established.
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: receive success. (MODE-Config).
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration started.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-ADDRESS = 10.100.1.18.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-MASK = 255.255.255.0.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: SAVE-PASSWORD = 1.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-DNS = 10.100.1.129.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: SPLIT-INCLUDE.
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration: DEF-DOMAIN = iw.local.
Dec 30 12:33:21 jupiter configd[16]: host_gateway: write routing socket failed, command 2, No such process
Dec 30 12:33:21 jupiter configd[16]: installed route: (address 10.100.1.0, gateway 10.100.1.18)
Dec 30 12:33:21 jupiter configd[16]: IPSec Phase2 starting.
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Phase2 started (Initiated by me).
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: transmit success. (Initiator, Quick-Mode message 1).
Dec 30 12:33:21 jupiter configd[16]: IPSec Network Configuration established.
Dec 30 12:33:21 jupiter configd[16]: IPSec Phase1 established.
Dec 30 12:33:21 jupiter configd[16]: event_callback: Address added. previous interface setting (name: en1, address: 192.168.43.242), current interface setting (name: utun0, family: 1001, address: 10.100.1.18, subnet: 255.255.255.0, destination: 10.100.1.18).
Dec 30 12:33:21 jupiter configd[16]: network configuration changed.
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: receive success. (Initiator, Quick-Mode message 2).
Dec 30 12:33:21 jupiter racoon[1976]: IKE Packet: transmit success. (Initiator, Quick-Mode message 3).
Dec 30 12:33:21 jupiter racoon[1976]: IKEv1 Phase2 Initiator: success. (Initiator, Quick-Mode).
Dec 30 12:33:21 jupiter racoon[1976]: IPSec Phase2 established (Initiated by me).
Dec 30 12:33:21 jupiter configd[16]: IPSec Phase2 established.
An earlies test in a Starbucks around here had the same result, during looking at the netstat -nr output I found I got onto a 10.x.x.x net on the Wifi and still could connect to the (different) 10.x.x.x net at work.
My TCP/IP Networking course was around 2000, but the default route seen in the non-working log section looks like bullsh*t to me anyhow: DEFAULT-ROUTE = local-address 172.77.7.14/32
On the other hand, the Phase 2 message seem to indicate a different mode for Phase 2 between the working and the non-working one.
This is from the exported config of my AVM box:
**** CFGFILE:vpn.cfg
* /var/flash/vpn.cfg
* Wed Dec 28 16:01:09 2011
vpncfg {
        connections {
                enabled = yes;
                conn_type = conntype_user;
                name = "[email protected]";
                always_renew = no;
                reject_not_encrypted = no;
                dont_filter_netbios = yes;
                localip = 0.0.0.0;
                local_virtualip = 0.0.0.0;
                remoteip = 0.0.0.0;
                remote_virtualip = 172.77.7.14;
                remoteid {
                        key_id = "<mykeyismybusiness>";
                mode = phase1_mode_aggressive;
                phase1ss = "all/all/all";
                keytype = connkeytype_pre_shared;
                key = "<mykeyismybusiness>";
                cert_do_server_auth = no;
                use_nat_t = no;
                use_xauth = yes;
                xauth {
                        valid = yes;
                        username = "<myuserismybusiness>";
                        passwd = "<mypasswordismybusiness>";
                use_cfgmode = no;
                phase2localid {
                        ipnet {
                                ipaddr = 0.0.0.0;
                                mask = 0.0.0.0;
                phase2remoteid {
                        ipaddr = 172.22.7.14;
                phase2ss = "esp-all-all/ah-none/comp-all/no-pfs";
                accesslist =
                             "permit ip 172.22.7.0 255.255.255.240 172.22.7.14 255.255.255.255";
        ike_forward_rules = "udp 0.0.0.0:500 0.0.0.0:500",
                            "udp 0.0.0.0:4500 0.0.0.0:4500";
// EOF
**** END OF FILE ****
I also noticed an extra "IPSec port-mapping update for en1 ignored" message in the non-working log section, but I'm not sure a) how significant that might be, and b) how to find out what the ignored update might have been to decide whether not ignoring it would help.
A quick test with the AnyConnect Client from Cisco didn't help either, apparently it establishes an https connection first as I got a window which certificate details from my QNAP behind the AVM Box (I got a port forward for https to it)
So I'm looking for any ideas how to better troubleshoot this VPN issue...
Many thanks in advance!
BR,
Alex

Ok, found a small typo in my config (had at one point a 172.77.7.14 instead of the 172.22.7.14), no I can also connect from the 172.x.x.x net but still no ping etc. The relevant section of the log looks now like this:
Dec 30 16:44:27 jupiter configd[16]: IPSec connecting to server <myservernameismybusiness>.dyndns.info
Dec 30 16:44:27 jupiter configd[16]: SCNC: start, triggered by SystemUIServer, type IPSec, status 0
Dec 30 16:44:28 jupiter configd[16]: IPSec Phase1 starting.
Dec 30 16:44:28 jupiter racoon[2183]: IPSec connecting to server 77.x.x.x
Dec 30 16:44:28 jupiter racoon[2183]: Connecting.
Dec 30 16:44:28 jupiter racoon[2183]: IPSec Phase1 started (Initiated by me).
Dec 30 16:44:28 jupiter racoon[2183]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1).
Dec 30 16:44:28 jupiter racoon[2183]: IKEv1 Phase1 AUTH: success. (Initiator, Aggressive-Mode Message 2).
Dec 30 16:44:28 jupiter racoon[2183]: IKE Packet: receive success. (Initiator, Aggressive-Mode message 2).
Dec 30 16:44:28 jupiter racoon[2183]: IKEv1 Phase1 Initiator: success. (Initiator, Aggressive-Mode).
Dec 30 16:44:28 jupiter racoon[2183]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 3).
Dec 30 16:44:28 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:44:28 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (ISAKMP-SA).
Dec 30 16:44:28 jupiter racoon[2183]: IPSec Phase1 established (Initiated by me).
Dec 30 16:44:28 jupiter racoon[2183]: IPSec Extended Authentication requested.
Dec 30 16:44:28 jupiter configd[16]: IPSec requesting Extended Authentication.
Dec 30 16:44:31 jupiter configd[16]: IPSec sending Extended Authentication.
Dec 30 16:44:31 jupiter racoon[2183]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 16:44:31 jupiter racoon[2183]: IPSec Extended Authentication sent.
Dec 30 16:44:32 jupiter racoon[2183]: IKEv1 XAUTH: success. (XAUTH Status is OK).
Dec 30 16:44:32 jupiter racoon[2183]: IPSec Extended Authentication Passed.
Dec 30 16:44:32 jupiter racoon[2183]: IKE Packet: transmit success. (Mode-Config message).
Dec 30 16:44:32 jupiter racoon[2183]: IKEv1 Config: retransmited. (Mode-Config retransmit).
Dec 30 16:44:32 jupiter racoon[2183]: IPSec Network Configuration requested.
Dec 30 16:44:33 jupiter racoon[2183]: IPSec Network Configuration established.
Dec 30 16:44:33 jupiter racoon[2183]: IKE Packet: receive success. (MODE-Config).
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration started.
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-ADDRESS = 172.22.7.14.
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration: SAVE-PASSWORD = 1.
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration: INTERNAL-IP4-DNS = 172.22.7.1.
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration: DEFAULT-ROUTE = local-address 172.22.7.14/32.
Dec 30 16:44:33 jupiter configd[16]: host_gateway: write routing socket failed, command 2, No such process
Dec 30 16:44:33 jupiter configd[16]: IPSec Phase2 starting.
Dec 30 16:44:33 jupiter racoon[2183]: IPSec Phase2 started (Initiated by me).
Dec 30 16:44:33 jupiter racoon[2183]: IKE Packet: transmit success. (Initiator, Quick-Mode message 1).
Dec 30 16:44:33 jupiter configd[16]: IPSec Network Configuration established.
Dec 30 16:44:33 jupiter configd[16]: IPSec Phase1 established.
Dec 30 16:44:33 jupiter configd[16]: event_callback: Address added. previous interface setting (name: en1, address: 192.168.43.242), current interface setting (name: utun0, family: 1001, address: 172.22.7.14, subnet: 255.255.255.255, destination: 172.22.7.14).
Dec 30 16:44:33 jupiter configd[16]: network configuration changed.
Dec 30 16:44:33 jupiter racoon[2183]: IKE Packet: receive success. (Initiator, Quick-Mode message 2).
Dec 30 16:44:33 jupiter racoon[2183]: IKE Packet: transmit success. (Initiator, Quick-Mode message 3).
Dec 30 16:44:33 jupiter racoon[2183]: IKEv1 Phase2 Initiator: success. (Initiator, Quick-Mode).
Dec 30 16:44:33 jupiter racoon[2183]: IPSec Phase2 established (Initiated by me).
Dec 30 16:44:33 jupiter configd[16]: IPSec Phase2 established.
Dec 30 16:44:43 jupiter racoon[2183]: IKE Packet: receive failed. (MODE-Config).
Dec 30 16:44:48 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:44:48 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:44:48 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:44:48 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:44:48 jupiter racoon[2183]: IKE Packet: receive success. (Information message).
Dec 30 16:45:03 jupiter configd[16]: setting hostname to "jupiter.local"
followed by lots of:
Dec 30 16:45:03 jupiter racoon[2183]: IKE Packet: receive failed. (MODE-Config).
Dec 30 16:45:08 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:45:08 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:45:08 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:45:08 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:45:08 jupiter racoon[2183]: IKE Packet: receive success. (Information message).
Dec 30 16:45:28 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:45:28 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:45:28 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:45:29 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:45:29 jupiter racoon[2183]: IKE Packet: receive success. (Information message).
Dec 30 16:45:49 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:45:49 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:45:49 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:45:50 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:45:50 jupiter racoon[2183]: IKE Packet: receive success. (Information message).
Dec 30 16:46:10 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:46:10 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:46:10 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:46:10 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:46:10 jupiter racoon[2183]: IKE Packet: receive success. (Information message).
Dec 30 16:46:30 jupiter racoon[2183]: IKE Packet: transmit success. (Information message).
Dec 30 16:46:30 jupiter racoon[2183]: IKEv1 Information-Notice: transmit success. (R-U-THERE?).
Dec 30 16:46:30 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: request transmitted. (Initiator DPD Request).
Dec 30 16:46:30 jupiter racoon[2183]: IKEv1 Dead-Peer-Detection: response received. (Initiator DPD Response).
Dec 30 16:46:30 jupiter racoon[2183]: IKE Packet: receive success. (Information message).

SAPGUI Java 7.20 Rev 6 download and VPN issue

Dear SAP friends please help.
We are trying to connect to SAP via a Mac running Lion and a VPN with SAPGUI for Java Rev 5. We get the logon successfully but never get further than the licence message. We have updated to the latest Java and also tried it in 32 bitz mode. We are unable to download the latest Rev 6 (due to my user authorisation) but we still think this is a VPN issue. Can you please help? I enclose the trace which shows the point at which is stops.
Many thanks
Andrew
16.11. 17:36:05.118 CALL:     <CONTROL SHELLID="101">
16.11. 17:36:05.118 CALL:       <PROPERTY VALUE="0" NAME="120"/>
16.11. 17:36:05.118 CALL:       <PROPERTY VALUE="0" NAME="300"/>
16.11. 17:36:05.118 CALL:     </CONTROL>
16.11. 17:36:05.118 CALL:   </CONTROLS>
16.11. 17:36:05.118 CALL:   <COPY id="copy">
16.11. 17:36:05.118 CALL:     <GUI id="gui">
16.11. 17:36:05.118 CALL:       <METRICS id="metrics" X3="1440" X2="7" X1="7" X0="283" Y3="900" Y2="20" Y1="12" Y0="283"/>
16.11. 17:36:05.118 CALL:     </GUI>
16.11. 17:36:05.118 CALL:   </COPY>
16.11. 17:36:05.118 CALL: </DATAMANAGER>
16.11. 17:36:05.119 CALL: Call 1042: #3#.setMoreDataIndicator(true);
16.11. 17:36:05.122 CON: GuiNiNetConnection: sending DIAG data to writer thread for modus 0
ERROR #############################
16.11. 17:37:10.018 ERROR: GuiNiReaderThread: read failed: Error: connection to partner '172.23.200.109:3200' broken
16.11. 17:37:10.018 ERROR:
16.11. 17:37:10.018 ERROR: Wed Nov 16 17:37:10 2011
16.11. 17:37:10.018 ERROR: Release 720
16.11. 17:37:10.018 ERROR: Component NI (network interface), version 40
16.11. 17:37:10.018 ERROR: rc = -6, module nixxi.cpp, line 5087
16.11. 17:37:10.018 ERROR: Detail NiIRead: P=172.23.200.109:3200; L=10.64.10.112:53387
16.11. 17:37:10.018 ERROR: System Call recv
16.11. 17:37:10.018 ERROR: Error No 60
16.11. 17:37:10.018 ERROR: 'Operation timed out'
ERROR #############################
16.11. 17:37:10.018 CON: -
16.11. 17:37:10.018 CON: GuiNiNetConnection: sending DIAG data to connection for modus -1
ERROR #############################
16.11. 17:37:10.234 ERROR: GuiConnection: Connection closed
16.11. 17:37:10.234 ERROR: Error: connection to partner '172.23.200.109:3200' broken
16.11. 17:37:10.234 ERROR:
16.11. 17:37:10.234 ERROR: Wed Nov 16 17:37:10 2011
16.11. 17:37:10.234 ERROR: Release 720
16.11. 17:37:10.234 ERROR: Component NI (network interface), version 40
16.11. 17:37:10.234 ERROR: rc = -6, module nixxi.cpp, line 5087
16.11. 17:37:10.234 ERROR: Detail NiIRead: P=172.23.200.109:3200; L=10.64.10.112:53387
16.11. 17:37:10.234 ERROR: System Call recv
16.11. 17:37:10.234 ERROR: Error No 60
16.11. 17:37:10.234 ERROR: 'Operation timed out'
ERROR #############################
ERROR #############################

Hello Andrew,
some version of the VPN client on Lion seems to have a known issue according to SAP internal discussions.
I found someone telling, that with F5 SSL VPN Plugin 7000.2011.0907.01, it is working again.
It seems to be available from https://connectfp.sap.com.
For uninstalling old F5 version, see http://support.f5.com/kb/en-us/solutions/public/3000/800/sol3826.html
(many "seems", because I am still on Snow Leopard and can not talk about this issue from my own experience)
Regarding user authorization for downloading software in Service MarketPlace, please refer to [note 1037574|https://service.sap.com/sap/support/notes/1037574].
Best regards
Rolf-Martin

Westell 9100EM and Linsys WRT54G together

In my house, the Westell 9100EM router is in the Far Northeast corner of the home where my (rather old) home computer is located... Our bedrooms are located on the exact opposite corner of the home, in the SW area. Wireless service is quite poor in that area.
I have an existing Linksys WRT-54G router that worked very well when I had SBC DSL at an older house in another area. What I'm thinking is to put the WRT-54G in the middle of the house or in the back bedroom to provide wireless to that corner.
I see a lot of information on the boards and so forth about the Actiontec router and doing this but very little on the 9100EM router. Can anyone point me in a direction that gives more thorough directions for this? Has someone made this work?
Thanks in Advance for the help!
CJ
Lewisville, Texas

CJRadioman wrote:
In my house, the Westell 9100EM router is in the Far Northeast corner of the home where my (rather old) home computer is located... Our bedrooms are located on the exact opposite corner of the home, in the SW area. Wireless service is quite poor in that area.
I have an existing Linksys WRT-54G router that worked very well when I had SBC DSL at an older house in another area. What I'm thinking is to put the WRT-54G in the middle of the house or in the back bedroom to provide wireless to that corner.
I see a lot of information on the boards and so forth about the Actiontec router and doing this but very little on the 9100EM router. Can anyone point me in a direction that gives more thorough directions for this? Has someone made this work?
Thanks in Advance for the help!
CJ
Lewisville, Texas
Only if you have an ethernet port where you want to put it. If you do connect to it locally hard wired and change the subnet to 192.168.2 and set the wanport to a fixed address on the 192.168.1 subnet e.g. 192.168.1.254 Then connect the wan port of the linksys to a lan port of the 9100em via the in house wiring. the linksys by default cannot connect by wirelss to the 9100em.
If you have no inhouse wiring and are somewhat technically savvy and your wrt54g is a newer rev you can hack the firmware to change it to a wireless forwarder - see tomato. Google it on the net. Be warned that if you mess it up you have a very light boat anchor.

Westell 9100EM - Port Forwarding

So, I'm a newbie when it comes to port forwading, and I have tried all the tricks I can find on the internet.
I need to open some ports on my Westell 9100EM and I can't seem to find out how to get a step by step guide. I don't want to mess anything up, so I want to be save about not just trying things out.
This is what I need:
- Allow port 6112 TCP out and allow established sessions in
- Allow port 6112 TCP in
- Allow port 6113-6119 TCP out and in
It seems somewhat straightforward, but perhaps i'm missing something. If anyone can get back to me with some step by step ideas, you'd be my hero forever!
Thanks again for helping another noob.

tsauter wrote:
viafax999 wrote:
For example it should show up like this
My New service TCP Any -> 6112-6119
I remember seeing somewhere that people had trouble forwarding groups of ports and had to make a rule for each port.
Something to keep in mind.
Works ok for my FTP server on non standard ports on a 9100EM, I just changed the port numbers on the example.

Trouble replacing Westell 9100EM router w/ Asus RT-AC68U

I got a new router (ASUS RT-A68U) and want to replace the Westell 9100EM that came installed w/ my FiOS package.
I have the new router connected, and it can get to the internet just fine. It's gui says it's connected to the internet, and I can use it's onboard diagnostics to ping google.com, do a tracert, etc. However, none of the devices I connect to the new router can get an IP address. My WIRED connection from the PC to the router is unable to get an IP, even after ipconfig /release and /renew (Windows 7, from command line). My mobile phone can connect wirelessly to the new router, but is also unable to get an IP address.
Are there some settings I need to manage in order to have it automatically assign IPs to connected devices? I've set the new router to use google's DNS servers (8.8.8.8 and 8.8.8.4). Do I need to use verizon's servers first? Is there a change to the subnet mask or anything else that I'm missing?
Thanks to anyone who can offer some advice
-Adam

ajhartman wrote:
I got a new router (ASUS RT-A68U) and want to replace the Westell 9100EM that came installed w/ my FiOS package.
I have the new router connected, and it can get to the internet just fine. It's gui says it's connected to the internet, and I can use it's onboard diagnostics to ping google.com, do a tracert, etc. However, none of the devices I connect to the new router can get an IP address. My WIRED connection from the PC to the router is unable to get an IP, even after ipconfig /release and /renew (Windows 7, from command line). My mobile phone can connect wirelessly to the new router, but is also unable to get an IP address.
Are there some settings I need to manage in order to have it automatically assign IPs to connected devices? I've set the new router to use google's DNS servers (8.8.8.8 and 8.8.8.4). Do I need to use verizon's servers first? Is there a change to the subnet mask or anything else that I'm missing?
Thanks to anyone who can offer some advice
-Adam
Reset the router to factory defaults by pressing the reset button,
By default the router is set up as 192.168.1.1 so enter that address in a browser and connect
The default login is uerid admin and password admin
you should be able to use Quick Internet Setup QIS
Your fios account will give you an automatic dhcp address and no userid and password is required for that
at this point your router should be connected to the internet.
Using the main manu select lan and make sure the dhcp server is turned on (it's the radio button toggle at the top), should be by default and it should be handing out addresses on the 192.168.1 subnet.
On your machine run cmd and type in ipconfig /all - certify that you have an ip address of 192.168.1.x
If you've set the router dns to the google dns servers after the router reset then ipconfig should also show you that your dns servers are what you entered on the router if so
All is OK an you should be up and running
You'll probably want to change the default wireless settings, how to do that is inb the user manual.
There is no need to reference the Verizon dns servers

Computer not being registered in DNS on Westell 9100EM

I have a Westell 9100EM in my office where some systems register in the DNS and some not. All the systems are in the connections page. All Three PCs are Windows XP, 2 have no problem, just one. I have tired ipconfig /release, ipconfig /renew and ipconfig /registerdns in that order, checking the Westell DNS each time, no change. The two printers register no problem, my D-Link NAS registers. I just need to get this last PC to register. I have compared TCPIP properties, all 3 XP systems are the same. Any ideas?

This came from another thread, but worked for me. Problem is with newest iTunes 4.62 and Windows 8.1. Unistall iTunes, as well as its helper programs (Apple Application Support, Apple Mobile Divice Support, and Apple Software Update). Reboot, and reinstall iTunes. It will reinstall all the other ones and you should be able to connect your nano. Good luck.

Airport Extreme 802.11n New Firmware Release (VPN ISSUE)

The info accompanying the release of today's firmware upgrade makes no mention of a fix to the VPN problems. Does anyone know if the new firmware had any effect on the problem?
Mac Pro Mac OS X (10.4.9) 4 GB Ram

Our VPN is now working (checkpoint)
For me the firmware update initially seemed to fix the VPN issue, but after closer inspection there still seems to be something wrong with it. (We are using CheckPoint.) My Wintel-box that has been provided by my employee is still having issues with connecting to our exchange server and the network drives do not seem to be working all that realiable. Probably a configuration issue, but do you have any ideas on where to start looking for a solution?
br,
-Joose

Westell 9100EM VPN Issue

Similar Messages

Maybe you are looking for