RV220W 1.0.6.6 IPv6 Tunnelbroker tunnel is not working

With firmware 1.0.4.17 I have had our IPv6 tunnel working fine for a couple of years but it does not seem to work after upgrading to firmware 1.0.6.6
I have followed the instructions in 43132-Connecting_RV220W_to_an_IPv6_Tunnel_broker.pdf to no avail.
Has anybody been able to run an IPv6 6in4 tunnel with a firmware later than 1.0.4.17 and if yes, how ?
This is also a question to Cisco

I don't recall on which firmware version I set up the tunnel, but anyway I have fallen back to 1.0.4.17 with a factory reset.
It may be important to follow the instructions in https://supportforums.cisco.com/sites/default/files/legacy/2/3/1/43132-Connecting_RV220W_to_an_IPv6_Tunnel_broker.pdf in the proper sequence.
Pay attention to the two entries (different types) in the Advertisement Prefixes section.
In the Tunneling section your tunnelbroker IP-adress will not show up in the IPv6 Tunnel Status Table. I have enabled and entered the Remote End Point IPv4 Address.

Similar Messages

VPN split tunneling does not work with filtering enabled

I restricted our Windows VPN clients to reach only certain IPs and ports using filtering in their group policy. It works but I would like to add split tunneling for client's local Internet access. I temporary disabled filtering, unchecked the 'user default gateway on remote' box in properties of Windows VPN client, configured networks to be tunneled and it works. The moment I configure filters, my split tunneling does not tunnel the networks - they are not listed in Windows 'route print'. I change filtering to inherit or NONE and reconnect VPN and the tunneled networks show up again. I change filtering to a simple testing ACL/ACE and reconnect and they are gone again. Can I have split tunneling and filtering working simultaneously? Any help would be appreciated.

I'm not aware of any method named tokenize and there isn't one listing in
the alphabetic list of methods in the J2SE API. Perhaps you were thinking
of java.util.StringTokenizer, whose API contains this note:
StringTokenizer is a legacy class that is retained for compatibility reasons
although its use is discouraged in new code. It is recommended that anyone
seeking this functionality use the split method of String or the java.util.regex
package instead.

IPv6 OSPFv3 authentication (MD5) not working

I'm configuring two 2800 routers (ADVENTERPRISEK9, 12.4(24)T2) for OSPFv3. The interfaces are Frame-relay multipoint interfaces on both routers. OSPFv3 is fine without authentication. But when I added same MD5 authentication to the two interfaces, OSPFv3 adjacency never came back up. I'm using the exact same command as IOS IPv6 configuration guide.
Here are the configs on the two routers. What could be incorrect? In "show ipv6 ospf interface", secure socket is shown "up".
R1#
interface Serial0/0/0.402 multipoint
ipv6 address FE80:1:1::1 link-local
ipv6 address 2001:1:1::1/64
ipv6 ospf network broadcast
ipv6 ospf 1 area 0
ipv6 ospf authentication ipsec spi 500 md5 1234567890abcdef1234567890abcdef
frame-relay map ipv6 FE80:1:1::2 402 broadcast
ipv6 router ospf 1
router-id 1.1.1.1
R2#
interface Serial0/0/0.204 multipoint
ipv6 address FE80:1:1::2 link-local
ipv6 address 2001:1:1::2/64
ipv6 ospf network broadcast
ipv6 ospf 1 area 0
ipv6 ospf authentication ipsec spi 500 md5 1234567890abcdef1234567890abcdef
frame-relay map ipv6 FE80:1:1::1 204 broadcast
ipv6 router ospf 1
router-id 1.1.1.2
R1#sh ipv6 ospf int s0/0/0.402
Serial0/0/0.402 is up, line protocol is up
Link Local Address FE80:1:1::1, Interface ID 14
Area 0, Process ID 1, Instance ID 0, Router ID 1.1.1.1
Network Type BROADCAST, Cost: 64
MD5 authentication SPI 1000, secure socket UP (errors: 0) Rack61R4#sh ipv6 os int s0/0/0.402

I have had the same problem. The reason is a bug in Cisco IOS CSCtc72699.
Workaround:
The setting of "no crypto engine onboard 0" is added, and the
command of "clear crypto sa" is executed.
Before:
r1(config-if)#do sh crypto ipsec sa
interface: Serial0/0/1
    Crypto map tag: (none), local addr FE80::219:E8FF:FEE0:3640
   IPsecv6 policy name: OSPFv3-2001-256
   IPsecv6-created ACL name: Serial0/0/1-ipsecv6-ACL
   protected vrf: (none)
   local ident (addr/mask/prot/port): (FE80::/10/89/0)
   remote ident (addr/mask/prot/port): (::/0/89/0)
   current_peer :: port 500
     PERMIT, flags={origin_is_acl,}
   #pkts encaps: 416, #pkts encrypt: 416, #pkts digest: 416
    #pkts decaps: 0, #pkts decrypt: 0, #pkts verify: 0
    #pkts compressed: 0, #pkts decompressed: 0
    #pkts not compressed: 0, #pkts compr. failed: 0
    #pkts not decompressed: 0, #pkts decompress failed: 0
    #send errors 0, #recv errors 0
     local crypto endpt.: FE80::219:E8FF:FEE0:3640,
     remote crypto endpt.: ::
     path mtu 1500, ip mtu 1500, ip mtu idb Serial0/0/1
     current outbound spi: 0x100(256)
     inbound esp sas:
     inbound ah sas:
      spi: 0x100(256)
        transform: ah-md5-hmac ,
        in use settings ={Transport, }
        conn id: 2005, flow_id: NETGX:5, crypto map: (none)
        no sa timing
        replay detection support: N
        Status: ACTIVE
     inbound pcp sas:
     outbound esp sas:
     outbound ah sas:
      spi: 0x100(256)
        transform: ah-md5-hmac ,
        in use settings ={Transport, }
        conn id: 2006, flow_id: NETGX:6, crypto map: (none)
        no sa timing
        replay detection support: N
        Status: ACTIVE
     outbound pcp sas:
After:
r1#sh crypto ipsec sa
interface: Serial0/0/1
    Crypto map tag: (none), local addr FE80::219:E8FF:FEE0:3640
   IPsecv6 policy name: OSPFv3-2001-256
   IPsecv6-created ACL name: Serial0/0/1-ipsecv6-ACL
   protected vrf: (none)
   local ident (addr/mask/prot/port): (FE80::/10/89/0)
   remote ident (addr/mask/prot/port): (::/0/89/0)
   current_peer :: port 500
     PERMIT, flags={origin_is_acl,}
    #pkts encaps: 56, #pkts encrypt: 56, #pkts digest: 56
    #pkts decaps: 55, #pkts decrypt: 55, #pkts verify: 55
    #pkts compressed: 0, #pkts decompressed: 0
    #pkts not compressed: 0, #pkts compr. failed: 0
    #pkts not decompressed: 0, #pkts decompress failed: 0
    #send errors 0, #recv errors 0
     local crypto endpt.: FE80::219:E8FF:FEE0:3640,
     remote crypto endpt.: ::
     path mtu 1500, ip mtu 1500, ip mtu idb Serial0/0/1
     current outbound spi: 0x100(256)
     inbound esp sas:
     inbound ah sas:
      spi: 0x100(256)
        transform: ah-md5-hmac ,
        in use settings ={Transport, }
        conn id: 1, flow_id: SW:1, crypto map: (none)
        no sa timing
        replay detection support: N
        Status: ACTIVE
     inbound pcp sas:
     outbound esp sas:
     outbound ah sas:
      spi: 0x100(256)
        transform: ah-md5-hmac ,
        in use settings ={Transport, }
        conn id: 2, flow_id: SW:2, crypto map: (none)
        no sa timing
        replay detection support: N
        Status: ACTIVE
     outbound pcp sas:

Microsoft teredo tunneling adapter not working

i have been facing this problem from about 3 days and I am not able to connect my phone through cable to my laptop neither i am able to use bluetooth...so I checked for the prblm and its this teredo adapter not working which is related to the devices i think....I
have followed every measure I could given by microsoft...I have tried uninstalling the teredo adapter but i couldn't...actually I clicked on the option dat was der as uninstall but it didn't....
after uninstalling only we had to restart the computer but since the uninstallation was not successfull so it didn;t helped me..
plz tell me some solution for this prblm!!!

Hi,
I am afraid that this forum is not a correct forum for this issue. Since this forum is discuss about Windows form development . I suggested you posting this thread to
answer.microsoft.com-Windows OS
Have a nice time!
Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

RV220W 1.0.2.4: 6to4 Tunnel did not initialize after reboot

IPv6 -> Tunneling
The 6to4 tunnel did not initialize after a reboot.
The automatic tunneling had to be disabled and enabled again.
It was used for a 6in4 tunnel to tunnelbroker and the Remote End Point IPv4
Address was enabled and specified.

Why is this bad ?
After a power outage or deliberate power cycling the unit, the IPv6 network is not working.
What does this mean for Cisco? No sale.
I do not replace our current branch office router with this unit yet.
When managing the site remotely it has been invaluable, that the current router has been able to provide access through IPv6 when there was certain problems with IPv4.
The issue has been reproduced.

RV220W DMZ not working and protocol 41 packets not forwarded

After fighting a brand new RV220W for hours I am just about giving up on it.
It does not forward anything the to the DMZ server including the IP protocol 41 packets needed for our IPv6 6in4 tunnel.
Nor does it send protocol 41 packets to the WAN.
TCP and UDP packets are only forwarded to the DMZ server if specifically done by a firewall rule.
CISCO support was not able to solve the problem after half an hour on the phone.
Factory resets and absolutely minimal configuration changes have been tried to no avail.
Firmware is 1.0.1.0.
The hairpinning problem as well as the weird time problem cause by ticking the daylight savings box has been observed as well.
Should I return this thing having learned that CISCO quality is a thing of the past ?
The Netgear WNDR3700 it was supposed to replace, due to the SNMP support found in this router, happily forwards packets at half the price.

Manually creating a firewall rule with protocol 41 in the backup config file and restoring it makes no difference.
(A new checksum for the configuration file may be generated by md5sum when the checksum line has been deleted)
Default should be to route all IP packets regardless of protocol number to the DMZ server, when DMZ is enabled. Now the router returns a ICMP port unreachable message to the WAN sender.
Update:
The problem is only present when the dual stack IPv4/IPv6 feature is enabled, so after all it may be a bug and not a design decision. Waiting for Cisco support to verify/advice on this.
BTW it is unbelievable, that the configuration file (plain text) saved by the backup function in the router cannot be read / used by Cisco suppport. They can only handle something which can be displayed in a browser (sic!)
Update 2:
Further testing has shown, that the option of forwarding of protocol 41 packets for 6in4 tunnels in any mode (IPv4 only or IPv4/IPv6) is randomly enabled. Sometimes suddenly working after 30 minutes. At other times not at all even after a reboot. Occasionally it has been working in both modes.
I have provided information about this to CISCO.
Cisco support has recognized this to be a problem of the current software 1.0.1.0 and is issuing a refund of the router.

All the traffic go through IPsec tunnel(site to site ) ,but something seems not working correctly

Hi, all,
I have seen a good post in google.com about how to make all the client's traffic though IPsec tunnel then out to the Internet from the Main site,now I attach this configuration and application for discussion, and what the problem is that I am still confused with the configuration on Main site , I hope anyone who can tell me more detail and how to accomplish it. Any answer will be appreciated , thank you !
Quote :
Question ? :
Mine is a very simple configuration. I have 2 sites linked via an IPsec tunnel. Dallas is my Main HQ R1 and Austin R2 is my remote office. I want all traffic from Austin to route thru the tunnel up to Dallas, then out to the Internet.
Dallas (Main) Lan Net is: 10.10.200.0/24
Austin (Remote) LAN Net is: 10.20.2.0/24
The Dallas (Main) site has a VPN config of:
Local Net: 0.0.0.0/0
Remote Net: 10.20.2.0/24
The Austin (Remote) site has a VPN config of:
10.20.2.0/24
Remote Net: 0.0.0.0/0
The tunnel gets established just fine. From the Austin LAN clients, I can ping the router at the main site (10.10.200.1). This is how I know the tunnel is created, but I cannot ping anything beyond the router from the Austin LAN, e.g. 8.8.8.8.
I'm sure it's something simple I failed to configure. Anyone have any pointers or hints?
Answer:
Thanks to Jimp from the other thread, I was able to see why it was not working. To fix, I had to change the Outbound NAT on the main side to Manual. Then I created a new Outbound NAT rule that included the subnet from the Austin network (10.20.2.0). Basically, I just created a copy of the default rule and changed the Source network.
Once I made this change, Voila! Traffic from the remote side started heading out to the Internet. Now all traffic flows thru the Main site. It makes perfect sense why I needed to make this change, it just took a slap in the head from Jimp to point me in the right direction.
My question ?
The answer said "To fix, I had to change the Outbound NAT on the main side to Manual. Then I created a new Outbound NAT rule that included the subnet from the Austin network (10.20.2.0). Basically, I just created a copy of the default rule and changed the Source network." what this mean and
how to do it , could anybody give me the specific configuration ? thanks a lot.

Thank you for Jouni's reply, following is the configuration on Cisco 2800 router ,no firewall enable, :
crypto isakmp policy 100
encr aes 256
authentication pre-share
group 2
crypto isakmp key x.x.x address 0.0.0.0 0.0.0.0
crypto isakmp keepalive 60
crypto ipsec transform-set IPsectrans esp-3des esp-md5-hmac
crypto dynamic-map IPsecdyn 100
set transform-set IPsectrans
match address 102
crypto map IPsecmap 100 ipsec-isakmp dynamic IPsecdyn
interface Loopback1
ip address 10.10.200.1 255.255.255.0
interface FastEthernet0/0
ip address 113.113.1.1 255.255.255.128
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
crypto map IPsecmap
interface FastEthernet0/1
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
ip route 0.0.0.0 0.0.0.0 113.113.1.2
ip http server
no ip http secure-server
ip nat inside source list 100 interface FastEthernet0/0 overload
access-list 100 permit ip 192.168.1.0 0.0.0.255 any
access-list 102 permit ip any 10.20.2.0 0.0.0.255

Phase 2 tunnel is not going up between PIX 525 and Watchguard

Hi Folks,
Can you please help me in knowing where is the problem liying, currently I am trying to establish a VPN tunnel between PIX firewall and Watchguard , all the parameters of both devices are the same though Phase two tunnel is not coming up.
here is the debug :
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:500 dpt:500
OAK_MM exchange
ISAKMP (0): processing KE payload. message ID = 0
ISAKMP (0): processing NONCE payload. message ID = 0
ISAKMP (0:0): Detected NAT-D payload
ISAKMP (0:0): NAT does not match MINE hash
hash received: b3 8f bb 0 93 3b 65 e8 35 6f 54 6 c4 6f 59 cc
my nat hash : dd 70 9 ac 35 58 40 da 3b 5b fc 1b 4c 87 d2 11
ISAKMP (0:0): Detected NAT-D payload
ISAKMP (0:0): NAT does not match HIS hash
hash received: ba 72 c5 e 5b fb 88 f0 1e f7 8a ba c9 c6 c1 cc
his nat hash : c 4c 89 a5 66 c1 dd 80 76 48 3f a5 b0 f0 56 ed
ISAKMP (0:0): constructed HIS NAT-D
ISAKMP (0:0): constructed MINE NAT-D
return status is IKMP_NO_ERROR
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:4500 dpt:4500
OAK_MM exchange
ISAKMP (0): processing ID payload. message ID = 0
ISAKMP (0): processing HASH payload. message ID = 0
ISAKMP (0): SA has been authenticated
ISAKMP: Created a peer struct for 212.37.17.43, peer port 37905
ISAKMP: Locking UDP_ENC struct 0x3cbb634 from crypto_ikmp_udp_enc_ike_init, count 1
ISAKMP (0): ID payload
next-payload : 8
type : 2
protocol : 17
port : 0
length : 23
ISAKMP (0): Total payload length: 27
return status is IKMP_NO_ERROR
ISAKMP (0): sending INITIAL_CONTACT notify
ISAKMP (0): sending NOTIFY message 24578 protocol 1
VPN Peer: ISAKMP: Added new peer: ip:212.37.17.43/4500 Total VPN Peers:16
VPN Peer: ISAKMP: Peer ip:212.37.17.43/4500 Ref cnt incremented to:1 Total VPN Peers:16
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:4500 dpt:4500
ISAKMP (0): processing NOTIFY payload 24578 protocol 1
spi 0, message ID = 3168983470
ISAKMP (0): processing notify INITIAL_CONTACT
return status is IKMP_NO_ERR_NO_TRANS
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:4500 dpt:4500
OAK_QM exchange
oakley_process_quick_mode:
OAK_QM_IDLE
ISAKMP (0): processing SA payload. message ID = 484086886
ISAKMP : Checking IPSec proposal 1
ISAKMP: transform 1, ESP_3DES
ISAKMP: attributes in transform:
ISAKMP: SA life type in seconds
ISAKMP: SA life duration (basic) of 28800
ISAKMP: SA life type in kilobytes
ISAKMP: SA life duration (basic) of 32000
ISAKMP: encaps is 61433
ISAKMP: authenticator is HMAC-MD5
ISAKMP (0): atts not acceptable. Next payload is 0
ISAKMP (0): SA not acceptable!
ISAKMP (0): sending NOTIFY message 14 protocol 0
return status is IKMP_ERR_NO_RETRANS
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:4500 dpt:4500
ISAKMP: phase 2 packet is a duplicate of a previous packet
ISAKMP: resending last response
ISAKMP (0:0): sending NAT-T vendor ID - rev 2 & 3
crypto_isakmp_process_block:src:212.37.17.43, dest:212.118.128.233 spt:4500 dpt:4500
ISAKMP: phase 2 packet is a duplicate of a previous packet
ISAKMP: resending last response
crypto_isakmp_process_block:src:213.210.211.82, dest:212.118.128.233 spt:500 dpt:500
ISAKMP (0): processing NOTIFY payload 36136 protocol 1
spi 0, message ID = 287560609
ISAMKP (0): received DPD_R_U_THERE from peer 213.210.211.82
ISAKMP (0): sending NOTIFY message 36137 protocol 1
return status is IKMP_NO_ERR_NO_TRANSdebug
ISAKMP (0): retransmitting phase 1 (0)...
Thanks,
Ismail

Hi Kanishka,
The Phase 2 Parameters are the same also PFS is disabled !
There are some curious things in the debug msg, could you please throw some light on them
ISAKMP (0): Checking ISAKMP transform 1 against priority 1 policy
ISAKMP: encryption 3DES-CBC
ISAKMP: hash MD5
ISAKMP: auth pre-share
ISAKMP: life type in seconds
ISAKMP: life duration (VPI) of 0x0 0x1 0x51 0x80
ISAKMP: default group 1
ISAKMP (0): atts are acceptable. Next payload is 0
ISAKMP (0): processing vendor id payload
ISAKMP (0:0): vendor ID is NAT-T
ISAKMP (0): processing vendor id payload
what does the vendor ID is NAT-T above mean ? Is it say that both sides are using Nat traversal.
Also in ecryption its says encryption 3DES-CBC
i am not sure if this CBC is the culprit. Because thats what watchgaurd uses only it does not have an option for only 3DES.
strange enought that Phase 1 is getting up, I am also questioning myself about the following message appearing in Phase 1:
ISAKMP (0:0): Detected NAT-D payload
ISAKMP (0:0): NAT does not match MINE hash
hash received: b3 8f bb 0 93 3b 65 e8 35 6f 54 6 c4 6f 59 cc
my nat hash : dd 70 9 ac 35 58 40 da 3b 5b fc 1b 4c 87 d2 11
ISAKMP (0:0): Detected NAT-D payload
ISAKMP (0:0): NAT does not match HIS hash
hash received: ba 72 c5 e 5b fb 88 f0 1e f7 8a ba c9 c6 c1 cc
his nat hash : c 4c 89 a5 66 c1 dd 80 76 48 3f a5 b0 f0 56 ed
ISAKMP (0:0): constructed HIS NAT-D
ISAKMP (0:0): constructed MINE NAT-D
return status is IKMP_NO_ERROR
how come Phase 1 is coming up though the PIX is claiming that his HASH is not the same as HIS HASH :(
the log messages on WATCH GUARD states that there is no proposal chosen!
why both firewalls are not friends?
I appreciate any input

How to find out whether ipv6 is installed or not

Hello.
I need to determine (in Java 1.5) whether ipv6 is installed on a system (Windows) or not. Any ideas how could I do that? Is it possible at all?
Thanks in advance.

Yes, right.
I have a client/server application and there is a "properties" files where user can specify many options including connection related. And there is an editor that allows to change that "properties" file thru GUI (and there may be no connection with the server at this point). Currently, speaking of connection related options, user is represented with 2 options (ipv4 and ipv6) from which he/she can choose no matter whether ipv6 is installed or not. I need to disable (or remove) ipv6 option if there is no ipv6 installed on a system.
Using server-socket-approch will, probably, do, but may be there is some other way to do this?
And thanks a lot for your answer.
Edited by: serge.kv on Jan 28, 2010 7:51 AM

Microsoft Teredo tunneling adapter #2 is not working

Hi, i'm having problems with "microsoft teredo tunneling adapter #2". I've tried to fix it, but it keeps on saying that it's not working.When i set the tcpip6/parameters value to 0 it only fixed the teredo tunneling adapter but the teredo tunneling
adapter #2 is still not working. any ideas?

Sten
This is a known problem if Zone alarm is installed. If you have it installed remove it at least to check
To turn off Teredo tunneling interface 6to4 open an elevated command prompt and type
netsh interface terredo set state disabled.
To Re-install it
Click on Start.
Type Device Manager in search box and open it.
Click the Action tab at the top and click add legacy hardware
then click next and next again it will then scan and find nothing click next on the screen after that.
Wait a minute and you will see a list of hardware appear, scroll down and choose network adapters then click next, then from the left column choose Microsoft then in the right hand column scroll down and choose Microsoft Teredo Tunneling Adapter, then click
next and this will install it.
To check just make sure it is set to show hidden devices, right click on device manager on the right and click view then show hidden devices.
Wanikiya and Dyami--Team Zigzag

Tunneling result not OK,

Hi,
What can you tell me about the following exception that I get
trying to call a bean on Weblogic 6.1. My program tries to take the connection
for several minutes and then java console shows the exception below.
The problem doesn't occur when I take the connection from the
same network where Weblogic is located.
Can this problem be fixed with service packs?
Could oracle8 have something to do with the problem?
I don't know whether this helps anything, but it seems to me like the problem
would have popped up by itself in the last times. With 'by itself' I mean that
I haven't commited any changes what so ever to weblogic configuration, but still
it has stopped working.
The exception:
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id:
'15'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at
weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
at weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy10.calculator(Unknown Source)
at com.util.Loader$2.run(Loader.java:811)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id: '15']
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy10.calculator(Unknown Source)
at com.util.Loader$2.run(Loader.java:811)
DEBUG util.Loader run:818 - ...model loading from the db in a thread
done in 297828 ms!
<16.7.2002 21:56:56 EEST> <Error> <HTTPClientJVMConnection> <
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id:
'15'
at
weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:406)
at
weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConnection.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
-Ohto

Installing sp3(WLS 6.1) should get rid of this for you.
"Ohto Rainio" <[email protected]> wrote:
>
Hi,
What can you tell me about the following exception that I get
trying to call a bean on Weblogic 6.1. My program tries to take the connection
for several minutes and then java console shows the exception below.
The problem doesn't occur when I take the connection from the
same network where Weblogic is located.
Can this problem be fixed with service packs?
Could oracle8 have something to do with the problem?
I don't know whether this helps anything, but it seems to me like the
problem
would have popped up by itself in the last times. With 'by itself' I
mean that
I haven't commited any changes what so ever to weblogic configuration,
but still
it has stopped working.
The exception:
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id:
'15'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at
weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
at weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy10.calculator(Unknown Source)
at com.util.Loader$2.run(Loader.java:811)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id: '15']
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy10.calculator(Unknown Source)
at com.util.Loader$2.run(Loader.java:811)
DEBUG util.Loader run:818 - ...model loading from the db in a thread
done in 297828 ms!
<16.7.2002 21:56:56 EEST> <Error> <HTTPClientJVMConnection> <
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id:
'15'
at
weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:406)
at
weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConnection.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
-Ohto

"Tunneling result not OK" error

With Weblogic 6.1SP1 on Windows 2000, I see the following error once in a
while.
At the client, I get the following:
-----------client-side error stack begin-------------
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id:
'18'
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id:
'18'
at
weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPCli
entJVMConnection.java:406)
at
weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConne
ction.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------client-side error stack end-----------------
Meanwhile, at the server, the wl-domain.log has the following stack trace:
----------server-side error stack begin-----------
####<Nov 11, 2001 7:11:20 PM CST> <Error> <ConnectionManager> <[Hostname]>
<[Managed Server Name]>
<ExecuteThread: '14' for queue: 'default'> <> <> <000000> <>
java.rmi.UnmarshalException: Incoming message header or abbreviation
processing failed ; nested exception is:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
Start server side stack trace:
java.rmi.UnmarshalException: Incoming message header or abbreviation
processing failed ; nested exception is:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
at
weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.j
ava:182)
at
weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.j
ava:154)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:582)
at
weblogic.rjvm.http.HTTPServerJVMConnection.dispatch(HTTPServerJVMConnection.
java:359)
at weblogic.rjvm.http.TunnelSendServlet.service(TunnelSendServlet.java:25)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.Kernel.execute(Kernel.java:229)
at
weblogic.servlet.internal.WebAppServletContext.dispatch(WebAppServletContext
.java:2352)
at
weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:
521)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------server-side error stack end-----------
This is not easy to reproduce - I've only seen it about once a day during
extended
performance stress tests, which complete most of the time successfully.
Any idea what these errors mean? Is there some tuning I can do to make them
stop?
I've already tried setting the ThreadCount to 10 and the
PercentSocketsReaders to 60
on the client command line, based on advice we got from BEA, but I've seen
this
particular problem whether I set those parameters or not. I had not seen
this problem
before switching to Weblogic 6.1 from 6.0.
--Rajiv

I have the same problem. Any hint? Is it a bug? There is some fix?
Angelo
"Michael Gogins" <[email protected]> wrote:
>
We have had a similar problem with tunneling JMS publish/subscribe through
HTTP
and HTTPS to get through firewalls. The JMS connection drops, and cannot
properly
be recovered.
Can anybody tell me if they have also had this problem with tunneling
other protocols
such as RMI or EJB?
In other words, does anybody know what layer of the protocol stack causes
this
problem?
Also, needless to say, does anyone have a workaround or solution?
"Rajiv Jauhari" <[email protected]> wrote:
With Weblogic 6.1SP1 on Windows 2000, I see the following error once
in a
while.
At the client, I get the following:
-----------client-side error stack begin-------------
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.net.ProtocolException: Tunneling result not OK, result:
'DEAD',
id:
'18'
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD',
id:
'18'
at
weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPCli
entJVMConnection.java:406)
at
weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConne
ction.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------client-side error stack end-----------------
Meanwhile, at the server, the wl-domain.log has the following stacktrace:
----------server-side error stack begin-----------
####<Nov 11, 2001 7:11:20 PM CST> <Error> <ConnectionManager> <[Hostname]>
<[Managed Server Name]>
<ExecuteThread: '14' for queue: 'default'> <> <> <000000> <>
java.rmi.UnmarshalException: Incoming message header or abbreviation
processing failed ; nested exception is:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
Start server side stack trace:
java.rmi.UnmarshalException: Incoming message header or abbreviation
processing failed ; nested exception is:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
at
weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.j
ava:182)
at
weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.j
ava:154)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:582)
at
weblogic.rjvm.http.HTTPServerJVMConnection.dispatch(HTTPServerJVMConnection.
java:359)
at weblogic.rjvm.http.TunnelSendServlet.service(TunnelSendServlet.java:25)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.Kernel.execute(Kernel.java:229)
at
weblogic.servlet.internal.WebAppServletContext.dispatch(WebAppServletContext
..java:2352)
at
weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:
521)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------server-side error stack end-----------
This is not easy to reproduce - I've only seen it about once a day during
extended
performance stress tests, which complete most of the time successfully.
Any idea what these errors mean? Is there some tuning I can do to make
them
stop?
I've already tried setting the ThreadCount to 10 and the
PercentSocketsReaders to 60
on the client command line, based on advice we got from BEA, but I've
seen
this
particular problem whether I set those parameters or not. I had notseen
this problem
before switching to Weblogic 6.1 from 6.0.
--Rajiv

How do split tunnelling in VPNs work?

How do split tunnelling in VPNs work?

The most visible issue is where the client's default gateway goes. In a full tunnel, it moves to the far side of the tunnel. In the split tunnel, it stays local. The security risk of split tunneling is that the client is providing a bridging path for outside malicious traffic to leak across the tunnel, with no influence from the far end's firewall and IDS. The performance risk of full tunnels is that 3rd party outside traffic not terminating at the organization on the far side still has to take the tunnel, which can add latency, limit throughput, or increase packet loss. The best designs require balancing the network layout, uplink sizing, and security posture in concert.
-- Jim Leinweber, WI State Lab of Hygiene

IPv6 does not work (MacMini late 2014)

Hello,
recently I bought an new MacMini late 2014 to use this machine as an OpenDirectory server to service request from our file servers and other boxes. Therefore this computer is configured with static ip addresses (v4, v6) within a separate server vlan. Nothing special, other machines (FreeBSD, OSX 10.9) within this segment are working well. The native en0 interface has the two server-lan addresses (v4, v6), an additional vlan interface of en0 is differently configured (v4; v6 only link local. All other initially active network interfaces are deactivated (thunderbold-bridge, bluetooth, WiFi etc.), because they are of no use.
Because of the machine's job as a server, I deactivated all temporary ipv6 address games (sysctl).
This standard configuration simply does not work as intended:
IPv4: communications to servers in the same lan segment are possible, the firewall is reachable, outside connections can be established.
IPv6: HORROR!
Different reactions between "no route to host" (hey, read your kernel tables and use the routes!) and timeouts (it read the kernel routing table, but failed with nd). The ping (ping6) targets are in this first step of testing machines within the same lan segment. Ping-ing of non-local, existing link local addresses is not possible. The MacMini sees itself but nothing more.
All firewalls (via GUI) are turned off, the computer is rebooted again and again. I checked sysctl for mess with packet filters and found an entry for an activation of an ipv6 fw (firewall?!), which I deactivated -- without success.
Software: 10.10 (delivery) plus update to 10.10.1; Apps: OSX Server.
Has anyone ideas what to check further (beside of using a network sniffer)?
Wolfgang

I have a mid-2010 Macmini running 10.10.3 with similar IPv6 symptoms. Not picking up a global address from RA, can't ping6 other link-local addresses, IPv4 working fine. Driving me crazy!

IPv6 - how to make it work and what advantages brings it ?

There is a discussion going on in arch discussion board about modularizing IPv6. I voted for it, but did some checking on this page
http://www.ripe.net/rs/ipv6/stats/ripencc.html .
Among the entries i found Xs4all (my own ISP) and surfnet / heanet , the 2 arch mirrors i use most of the time.
This has gotten me interested.
Can anyone point in the right direction to start using IPv6 and what benefits it could give me ?

Hello pepson93! The Samsung Fascinate is a CDMA only device, which makes it great for use in areas were CDMA signal is available. Unfortunately, the country of Poland does not have CDMA service providers so the Fascinate will not work there. I recommend seeking options for equipment with your local carriers. Best of luck!
Dion M.
VZW Support
Follow us on Twitter www.twitter.com/vzwsupport

RV220W 1.0.6.6 IPv6 Tunnelbroker tunnel is not working

Similar Messages

Maybe you are looking for