WRVS4400N - eth0: received packet with own address as source address

I am using a WRVS4400N as my primary router for a small office.  I get the following message repeated over and over in my logs.  This seems to happen for 2 or 3 days and then it will go away for about a week and then come back.  Does anyone know what is causing this?  The best I can tell I don't have any IP conflicts on the network and most of the time the network has very little traffic other than 2 or 3 computers surfing the web.
Jan  3 16:48:09  - eth0: received packet with  own address as source address
Jan  3 16:48:09  - eth0: received packet with  own address as source address
Jan  3 16:48:15  - eth0: received packet with  own address as source address
Jan  3 16:48:27  - eth0: received packet with  own address as source address
Jan  3 16:48:51  - eth0: received packet with  own address as source address

any news on this issue?
I am getting more and more messages (20+/day) - hundreds this month.
Now Coming every 10 minutes - HELP
eth0: received packet with own address as source address
Done everything, now waiting for input from Cisco.
Please, anyone as Cisco got any answers?
1:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
12:36 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
2:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
3:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
4:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
5:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
6:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
7:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
8:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]

Similar Messages

  • Proxy receiver channel with HTTP destination or URL address?

    Hi Experts,
         I have a scenario as below:
         (Webservice Client)SOAP --> PI --> PROXY(SAP ECC).
         A webservice client calls PI using SOAP. PI then sends the request to SAP ECC using PROXY.
        I am using AAE. Therefore I have ICO.
        In the receiver PROXY channel I have given:
       ADAPTER TYPE: SOAP
       Transport Protocol: HTTP
       Message Protocol: XI3.0.
       Under connection parameters:
       Addressing Type dropdown as 2 entries HTTP destination and URL address.
       In what cases i should use HTTP destination and URL address respectively?
       Which option is preferred?
       Do they work same or differently? How?   
       When I select HTTP destination where should I create the corresponding RFC destination? In PI ABAP stack using SM59 or PI NWA?
       If this HTTP destination is created in PI ABAP stack using SM59 then what type it should be? H? or G? 
    Thanks
    Gopal

    Hi Gopal,
    In creating XI receiver communication channel, you have 2 options for Addressing Type:
    1. URL Address - no need to create RFC destination. You just have to specify the XI receiver host name, HTTP port, path (/sap/xi/engine?type=receiver), Authentication data (logon details for SAP Client number of the PI system).
    2. HTTP Destination - create RFC destination in SXMB_ADM and specify the RFC destination name in your receiver communication channel.
    For SAP documentation, see this link:
    http://help.sap.com/saphelp_nwpi711/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm?frameset=/en/e1/091640a991c742e10000000a1550b0/frameset.htm&current_toc=/en/43/96cbccb9335b77e10000000a11466f/plain.htm&node_id=5
    Regards,
    Naveen.

  • Zone with own NIC and IP address

    hi all
    i just created zones on my SF4800 and no errors.
    when i boot that zone i get the following errors.
    "could not verify net address=10.xxx.xxx.xxx
    physical=qfe1: No such device or address
    zoneadm: zone ZWAS502 failed to verify"
    how could i solve this ASAP.
    thanks
    peter

    Hi Peter,
    i another thread i found this for you:
    To access the cdrom in a local zone you woul use zonecfg from the Global Zone
    "myzone" being the name of our zone..
    zonecfg -z myzone
    zonecfg:myzone>add fs
    zonecfg:myzone:fs>set dir=/cdrom
    zonecfg:myzone:fs>set special=/cdrom
    zonecfg:myzone:fs>set type=lofs
    zonecfg:myzone:fs>set options=[nodevices]
    zonecfg:myzone:fs>end
    zonecfg:myzone>verify
    zonecfg:myzone>commit
    zonecfg:myzone>exit
    There is more detail on this in http://developers.sun.com/solaris/articles/application_in_zone.html
    Holger

  • How is NTP reply routed when requesting router uses loopback as source address

    The Cisco NTP Best Practices White Paper and DISA STIGs recommend setting the NTP source address to a loopback interface (e.g. "ntp source loopback0").
    But this only seems to work if the requesting (NTP client) router is the default gateway for the NTP server. 
    Specifically, the NTP server will attempt to reply to the requesting router's loopback-based source address (taken from the NTP request packet).  Since that address will always be non-local from the perspective of the NTP server, the NTP server will encapsulate the reply in a Layer 2 frame addressed to its default gateway.  If the gateway was the source of the original NTP request, that should work.  But in most other situations that gateway won't know how to reach a loopback-based address, and will discard the reply.
    I have verified this in tests with routers running both 12.4 and 15.1 releases (and NTP debugging enabled).  When the NTP source is a loopback address, NTP replies never reach the requesting router.  With the default NTP source address (i.e. based on the exit interface) everything works fine.
    Obviously, you could employ workarounds, such as static routes or injecting loopback addresses into your routing protocols.  But that seems uglier than leaving NTP source addresses at their defaults.
    Why is this "best practice" so commonly advocated without mention of some significant caveats regarding routing?  Am I missing something? 
    Thanks,
      Mark

    Michel:
    Thanks for the response.  Actually, I understand what kind of routing workarounds could allow NTP to function in spite of this "best practice."  But I am mystified as to why a Cisco "NTP best practice" paper (http://www.cisco.com/en/US/tech/tk869/tk769/technologies_white_paper09186a0080117070.shtml) and various security policies would call for setting a loopback address as the NTP source when that practice will often cause more problems than it solves.
    The stability of a loopback address is nice when that address is used to uniquely identify the platform for a routing protocol or syslog.  A loopback-based source address can also simplify ACL management, since that address won't change if an interface or link failure forces the router to send traffic from a different interface.  But I keep seeing security configuration guides/policies that call for also using a loopback address as the source for two-way protocols, such as FTP and NTP. That just doesn't make sense to me when you balance the routing implications against the limited security benefits (stable device identification, simplified ACL maintenance, and obfuscation of device addresses).
    I was hoping to learn that some obscure command might allow me to control which NTP exchanges use the loopback-based source address.  For example, the loopback source address would work fine on outgoing NTP broadcasts (and probably in replies from NTP servers).  But I would prefer that NTP client requests use a source address based on the exit interface. That way replies can be routed back to the client without cluttering up routing tables with routes to loopback addresses.
    So far, it looks like I'll need to chalk this up to poor coordination between the network security and network administration communities.
    Thanks again,
      Mark

  • ISR router cannot receive packets addressed to itself?

    Hello, Support Team and All Members,
    I have a C881G router connected to 2 different ISP networks with a failover function configured and running properly. The following is a simple network diagram:
    The main WAN traffic goes through the ISP 1 LTE network and the router, provided by that ISP. The DMS Host on that router points to our C881G router Fa4 WAN interface (192.168.1.10), so the ISP 1 NAT Router is practically transparent to our traffic. Our C881G tracks the DNS server within the ISP 1 network (194.dns.isp.1) and in case of it's inaccessibility the traffic is switched to the backup link, served by the on-board HSPA+ modem (interface Dialer0 of our C881G), connected to the ISP 2 HSPA network. It works fine, but the problem is with the PPTP connections from outside to the C881G router. The PPTP calls work always from the PPTP Client 2 PC (directly connected to the Fa4 subnet), but from PPTP Client 1 PC it works only in the failover mode - when all traffic goes through the ISP 2. The incoming path via ISP 1 does not work. The problem is rather not connected to the PPTP VPN, GRE, authentication or encryption, because just the first TCP 1723 SYN packets are dropped at Fa4 much earlier by the C881G router. The debug ip packet detail shows the following routing decision:
    IP: s=194.xxx.yyy.80 (FastEthernet4), d=192.168.1.10, len 40, input feature
        TCP src=4241, dst=1723, seq=791503628, ack=4111924253, win=0 ACK RST, MCI Check(94), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    FIBipv4-packet-proc: route packet from FastEthernet4 src 194.xxx.yyy.80 dst 192.168.1.10
    FIBfwd-proc: Default:192.168.1.10/32 receive entry
    FIBipv4-packet-proc: packet routing failed
    All other packets addressed from outside networks to the router itself and received via the Fa4 are also dropped in this way. All packets sent to Fa4 from the local subnet 192.168.1.0 are accepted. The routing table shows only standard connected interfaces and 1 static route to the 194.dns.isp.1 via 192.168.1.1, which is also the tracked gateway of last resort.
    Router runs the CEF.
    I cannot locate in the following configuration file any statement preventing the packets addressed to the router itself:
    version 15.3
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    service internal
    hostname C881_xyz
    boot-start-marker
    boot-end-marker
    logging buffered 8192
    no logging console
    no logging monitor
    no aaa new-model
    clock timezone PCTime 1 0
    clock summer-time PCTime date Mar 30 2003 2:00 Oct 26 2003 3:00
    crypto ...
    ... <removed for sanity>
    crypto pki ...
    ip dhcp excluded-address 192.168.70.1 192.168.70.99
    ip dhcp excluded-address 192.168.70.180 192.168.70.254
    ip dhcp excluded-address 192.168.71.1 192.168.71.99
    ip dhcp excluded-address 192.168.71.180 192.168.71.254
    ip dhcp pool ccp-pool
     import all
     network 192.168.70.0 255.255.255.0
     dns-server 8.8.8.8 8.8.4.4
     default-router 192.168.70.1
     lease 0 12
    ip dhcp pool NVR
     import all
     network 192.168.71.0 255.255.255.0
     dns-server 8.8.8.8 8.8.4.4
     default-router 192.168.71.1
     lease 0 12
    ip domain name mydomain.com
    ip name-server 8.8.8.8
    ip name-server 8.8.4.4
    ip inspect WAAS flush-timeout 10
    ip cef
    no ipv6 cef
    multilink bundle-name authenticated
    vpdn enable
    vpdn-group 1
     ! Default PPTP VPDN group
     accept-dialin
      protocol pptp
      virtual-template 1
    chat-script gsm "" "AT!SCACT=1,1" TIMEOUT 60 "OK"
    license udi pid C881G+7-K9 sn ***********
    username admin privilege 15 secret 5 ******************************
    controller Cellular 0
    track 1 ip sla 1 reachability
     delay down 1 up 30
    interface FastEthernet0
     description All VLANs Trunk
     switchport mode trunk
     no ip address
    interface FastEthernet1
     description VLAN 1 - LAN Main
     no ip address
    interface FastEthernet2
     description VLAN 20 - LAN NVR
     switchport access vlan 20
     no ip address
    interface FastEthernet3
     description Traffic Monitoring only
     no ip address
    interface FastEthernet4
     description WAN SP1$ETH-WAN$
     ip address 192.168.1.10 255.255.255.0
     ip nat outside
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface Virtual-Template1
     ip unnumbered FastEthernet4
     peer default ip address pool vpn_pptp_pool
     no keepalive
     ppp encrypt mppe auto
     ppp authentication ms-chap-v2
    interface Cellular0
     ip address negotiated
     ip nat outside
     ip virtual-reassembly in
     encapsulation slip
     dialer in-band
     dialer pool-member 1
     dialer-group 1
     async mode interactive
    interface Vlan1
     description LAN Main
     ip address 192.168.70.1 255.255.255.0
     ip flow ingress
     ip flow egress
     ip nat inside
     ip virtual-reassembly in
    interface Vlan20
     description LAN NVR
     ip address 192.168.71.1 255.255.255.0
     ip flow ingress
     ip flow egress
     ip nat inside
     ip virtual-reassembly in
    interface Dialer0
     ip address negotiated
     ip nat outside
     ip virtual-reassembly in
     encapsulation slip
     dialer pool 1
     dialer idle-timeout 0
     dialer string gsm
     dialer persistent
     dialer-group 1
    ip local policy route-map track-primary-if
    ip local pool vpn_pptp_pool 192.168.70.180 192.168.70.199
    ip forward-protocol nd
    no ip http server
    ip http access-class 1
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip flow-top-talkers
     top 32
     sort-by bytes
     cache-timeout 600000
    ip nat inside source route-map ISP_1 interface FastEthernet4 overload
    ip nat inside source route-map ISP_2 interface Dialer0 overload
    ip route 0.0.0.0 0.0.0.0 192.168.1.1 track 1
    ip route 0.0.0.0 0.0.0.0 Dialer0 253
    ip route 194.dns.isp.1 255.255.255.255 192.168.1.1
    ip sla auto discovery
    ip sla 1
     icmp-echo 194.dns.isp.1 source-interface FastEthernet4
     frequency 10
    ip sla schedule 1 life forever start-time now
    logging trap debugging
    dialer-list 1 protocol ip permit
    route-map track-primary-if permit 1
     match ip address 100
     set interface FastEthernet4
    route-map Static_ISP_2 permit 10
     match interface Dialer0
    route-map Static_ISP_1 permit 10
     match interface FastEthernet4
    route-map ISP_2 permit 10
     match ip address 1
     match interface Dialer0
    route-map ISP_1 permit 10
     match ip address 1
     match interface FastEthernet4
    access-list 1 remark List for outside NATs
    access-list 1 remark CCP_ACL Category=2
    access-list 1 permit 192.168.70.0 0.0.0.255
    access-list 1 permit 192.168.71.0 0.0.0.255
    access-list 100 remark CCP_ACL Category=0
    access-list 100 permit icmp any host 194.dns.isp.1
    access-list 105 remark List for debugging local ICMP tests
    access-list 105 remark CCP_ACL Category=16
    access-list 105 permit icmp any any
    control-plane
    line con 0
     no modem enable
    line aux 0
    line 3
     script dialer gsm
     modem InOut
     no exec
     transport input all
     rxspeed 21600000
     txspeed 5760000
    line vty 0 4
     exec-timeout 0 0
     privilege level 15
     login local
     transport input telnet ssh
    line vty 5 15
     access-class 23 in
     privilege level 15
     login local
     transport input telnet ssh
    ntp update-calendar
    ntp server 195.time.srv.1
    end
    Do you have an idea what can be the reason of that behaviour?
    I really appreciate your suggestions,
    Maciex

    Hello Maciex,
    I am afraid that the debug ip packet detailed has led you to a wrong conclusion. Whatever the "forus FALSE" means, it does not indicate that the router refuses to consider the packet as addressed to itself. I've just concocted a very quick test - two routers connected back to back, one is 10.0.1.1/24, the other is 10.0.1.2/24. I am pinging 10.0.1.2 from 10.0.1.1 and this is what 10.0.1.2 shows me:
    *Aug 4 23:09:38.067: IP: s=10.0.1.1 (Ethernet2/1), d=10.0.1.2, len 100, input feature
    *Aug 4 23:09:38.071: ICMP type=8, code=0, MCI Check(94), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
    *Aug 4 23:09:38.079: FIBipv4-packet-proc: route packet from Ethernet2/1 src 10.0.1.1 dst 10.0.1.2
    *Aug 4 23:09:38.083: FIBfwd-proc: Default:10.0.1.2/32 receive entry
    *Aug 4 23:09:38.083: FIBipv4-packet-proc: packet routing failed
    *Aug 4 23:09:38.087: IP: tableid=0, s=10.0.1.1 (Ethernet2/1), d=10.0.1.2 (Ethernet2/1), routed via RIB
    *Aug 4 23:09:38.091: IP: s=10.0.1.1 (Ethernet2/1), d=10.0.1.2 (Ethernet2/1), len 100, rcvd 3
    *Aug 4 23:09:38.095: ICMP type=8, code=0
    *Aug 4 23:09:38.099: IP: s=10.0.1.1 (Ethernet2/1), d=10.0.1.2, len 100, stop process pak for forus packet
    *Aug 4 23:09:38.103: ICMP type=8, code=0
    *Aug 4 23:09:38.107: FIBipv4-packet-proc: route packet from (local) src 10.0.1.2 dst 10.0.1.1
    *Aug 4 23:09:38.111: FIBfwd-proc: packet routed by adj to Ethernet2/1 10.0.1.1
    *Aug 4 23:09:38.111: FIBipv4-packet-proc: packet routing succeeded
    *Aug 4 23:09:38.115: IP: s=10.0.1.2 (local), d=10.0.1.1 (Ethernet2/1), len 100, sending
    *Aug 4 23:09:38.119: ICMP type=0, code=0
    *Aug 4 23:09:38.127: IP: s=10.0.1.2 (local), d=10.0.1.1 (Ethernet2/1), len 100, sending full packet
    *Aug 4 23:09:38.131: ICMP type=0, code=0
    Note that even here, the router said the same as yours - and yet it did respond successfully to the ping request.
    There is, I am afraid, a more mundane problem. PPTP is generally incompatible with PAT. PPTP uses two data streams: one is the control channel run over TCP port 1723, the other is the actual tunneled traffic - however, that traffic is essentially GRE-encapsulated, put directly into IP packets with no port information (there is no TCP/UDP involved). Without special support on the ISP 1 NAT box, PPTP sessions will not be able to pass through it. You will have to negotiate this with your ISP 1 - ask him to configure its NAT box with PPTP Application Layer Gateway support and allow IP protocol 47 (GRE).
    This would explain why the PPTP Client 2 can always connect to your router - it is because there is no NAT/PAT/FW between the client and the router. It would also explain why Client 1 is able to connect over ISP 2 - because on that path, there is no NAT/PAT/FW box apparently present and there is a direct connectivity to the public IP address of your router.
    Try talking to your ISP 1 about this.
    Best regards,
    Peter

  • Updated my AppleID account info.  Under password security shows an email address to be used to receive email with new password settings.  I need to update that email address, how do I do that?  Thanks!

    Updated my AppleID account info.  Under password security shows an email address to be used to receive email with new password settings.  I need to update that email address, how do I do that?  Thanks!

    Thanks for the help Niel.  I couldn't change the rescue email address (an address that no longer exists and is therefore useless) until I could correctly answer the security questions.  After numerous guesses, finally got them right.  Was then presented with the option to change the rescue email address. Guess the only other option was to have Apple Support make the change or reset my account info.  Have made note of the correct answers so this won't happen again.   Thanks for the fast response!!

  • I have 2 problems with Mail. I cannot address an email to more than one recipient. And I receive some emails more than once.

    I have 2 problems with Mail. I cannot address an email to more than one recipient. And I receive some emails more than once. Can you please help?

    Restart your Mac. See if that makes a difference.

  • PI 7.11 - Sync HTTP receiver adapter with response XML file

    Hi
    We have a File to HTTP scenario in which we need a sync HTTP interface. We send a file to the HTTP address and receive a XML acknowledge. As I read in this forum: sync HTTP interfaces are not possible with the "standard" HTTP adapter. So I found an entry which recommended to use the SOAP adapter instead.
    I configured it:
    - Do Not Use SOAP envelope
    - modules: RequestResponseBeans, CallSapAdapter, ResponseOneWayBean
    If i use this scenario, i get following error in the RWB - Message Display Tool:
    Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.Message.getMessageId() of an object loaded from local variable 'message1'.
    I testet this scenario using CURL and it worked properly. Should this kind of scenario work with the SOAP adapter or do I need to buy/develop an own adapter? Is in NW7.3 possible to configure sync HTTP scenarios?
    Thanks in advance
    Michael

    Hi
    actually i use a simple HTTP receiver CC with the setting "XI Payload in HTTP Body" to send a XML datafile to a webpage (java servlet). This part works fine by now. But, this servlet would also send back a status information to the state of the received datafile, which I like to catch.
    e.g. HTTP response from the servlet (catched using CURL):
    HTTP/1.0 403 Forbidden
    Server: Apache-Coyote/1.1
    X-Powered-By: Servlet 2.4; JBoss-4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)/Tomcat-5.5
    Set-Cookie: JSESSIONID=OALHMomjR9TVgIATi8SrPQ**.ajp13_ls_1; Path=/ls
    Content-Type: text/xml
    Date: Tue, 06 Mar 2012 16:19:56 GMT
    X-Cache: MISS from proxy.xxxx.com
    Via: 1.0 proxy.xxxx.com:xxxx (http_scan/4.0.2.6.19)
    Proxy-Connection: close
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><!DOCTYPE transportordersfromls [ <!ELEMENT transportordersfromls (userid, clntid, msgid, (transportorderfromls+ | error))> <!ATTLIST transportordersfromls vers CDATA #REQUIRED> <!ELEMENT userid (#PCDATA)> <!ELEMENT clntid (#PCDATA)> <!ELEMENT msgid (#PCDATA)> <!ELEMENT transportorderfromls (refid, status)> <!ELEMENT refid (#PCDATA)> <!ELEMENT status (ok | error+)> <!ELEMENT ok EMPTY> <!ELEMENT error EMPTY> <!ATTLIST error reason (XMLError | SystemNotAvailable | ApplicationError | OTHER) #REQUIRED message CDATA #REQUIRED> ]>
    <transportordersfromls vers="1.0">
        <userid/>
        <clntid>XXXXX</clntid>
        <msgid>0</msgid>
        <error reason="OTHER" message="Access denied"/>
    </transportordersfromls>
    Michael

  • DMVPN-Why received packet doesn't use UDP port 4500 but 500?

    Hello everyone
    I got a problem with my DMVPN. Spoke is behind a NAT device. x.x.x.x is an public IP address which hub uses. I don't know why it discovered that the hub is also inside a NAT device. And after it sends a packet using port 4500, the received packet from hub was not using port 4500 but 500. I'm confused now. Any advise would be much appreciated.
    *Sep 10 08:56:02 UTC: ISAKMP:(0): beginning Main Mode exchange
    *Sep 10 08:56:02 UTC: ISAKMP:(0): sending packet to x.x.x.x my_port 500 peer_port 500 (I) MM_NO_STATE
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Sending an IKE IPv4 Packet.
    *Sep 10 08:56:02 UTC: ISAKMP (0): received packet from x.x.x.x dport 500 sport 500 Global (I) MM_NO_STATE
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Old State = IKE_I_MM1  New State = IKE_I_MM2 
    *Sep 10 08:56:02 UTC: ISAKMP:(0): processing SA payload. message ID = 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0): processing vendor id payload
    *Sep 10 08:56:02 UTC: ISAKMP:(0): vendor ID seems Unity/DPD but major 69 mismatch
    *Sep 10 08:56:02 UTC: ISAKMP (0): vendor ID is NAT-T RFC 3947
    *Sep 10 08:56:02 UTC: ISAKMP:(0):found peer pre-shared key matching 
    *Sep 10 08:56:02 UTC: ISAKMP:(0): local preshared key found
    *Sep 10 08:56:02 UTC: ISAKMP : Scanning profiles for xauth ...
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Checking ISAKMP transform 1 against priority 1 policy
    *Sep 10 08:56:02 UTC: ISAKMP:      encryption 3DES-CBC
    *Sep 10 08:56:02 UTC: ISAKMP:      hash MD5
    *Sep 10 08:56:02 UTC: ISAKMP:      default group 1
    *Sep 10 08:56:02 UTC: ISAKMP:      auth pre-share
    *Sep 10 08:56:02 UTC: ISAKMP:      life type in seconds
    *Sep 10 08:56:02 UTC: ISAKMP:      life duration (VPI) of  0x0 0x1 0x51 0x80 
    *Sep 10 08:56:02 UTC: ISAKMP:(0):atts are acceptable. Next payload is 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Acceptable atts:actual life: 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Acceptable atts:life: 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Fill atts in sa vpi_length:4
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Fill atts in sa life_in_seconds:86400
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Returning Actual lifetime: 86400
    *Sep 10 08:56:02 UTC: ISAKMP:(0)::Started lifetime timer: 86400.
    *Sep 10 08:56:02 UTC: ISAKMP:(0): processing vendor id payload
    *Sep 10 08:56:02 UTC: ISAKMP:(0): vendor ID seems Unity/DPD but major 69 mismatch
    *Sep 10 08:56:02 UTC: ISAKMP (0): vendor ID is NAT-T RFC 3947
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Old State = IKE_I_MM2  New State = IKE_I_MM2 
    *Sep 10 08:56:02 UTC: ISAKMP:(0): sending packet to x.x.x.x my_port 500 peer_port 500 (I) MM_SA_SETUP
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Sending an IKE IPv4 Packet.
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Old State = IKE_I_MM2  New State = IKE_I_MM3 
    *Sep 10 08:56:02 UTC: ISAKMP (0): received packet from x.x.x.x dport 500 sport 500 Global (I) MM_SA_SETUP
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
    *Sep 10 08:56:02 UTC: ISAKMP:(0):Old State = IKE_I_MM3  New State = IKE_I_MM4 
    *Sep 10 08:56:02 UTC: ISAKMP:(0): processing KE payload. message ID = 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0): processing NONCE payload. message ID = 0
    *Sep 10 08:56:02 UTC: ISAKMP:(0):found peer pre-shared key matching x.x.x.x
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): processing vendor id payload
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): vendor ID is Unity
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): processing vendor id payload
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): vendor ID is DPD
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): processing vendor id payload
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): speaking to another IOS box!
    *Sep 10 08:56:02 UTC: ISAKMP:received payload type 20
    *Sep 10 08:56:02 UTC: ISAKMP (2746): NAT found, both nodes inside NAT
    *Sep 10 08:56:02 UTC: ISAKMP:received payload type 20
    *Sep 10 08:56:02 UTC: ISAKMP (2746): My hash no match -  this node inside NAT
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Old State = IKE_I_MM4  New State = IKE_I_MM4 
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Send initial contact
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):SA is doing pre-shared key authentication using id type ID_IPV4_ADDR
    *Sep 10 08:56:02 UTC: ISAKMP (2746): ID payload 
    next-payload : 8
    type         : 1 
    address      : 192.168.1.101 
    protocol     : 17 
    port         : 0 
    length       : 12
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Total payload length: 12
    *Sep 10 08:56:02 UTC: ISAKMP:(2746): sending packet to x.x.x.x my_port 4500 peer_port 4500 (I) MM_KEY_EXCH
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Sending an IKE IPv4 Packet.
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
    *Sep 10 08:56:02 UTC: ISAKMP:(2746):Old State = IKE_I_MM4  New State = IKE_I_MM5 
    *Sep 10 08:56:03 UTC: ISAKMP (2746): received packet from x.x.x.x dport 500 sport 500 Global (I) MM_KEY_EXCH
    *Sep 10 08:56:03 UTC: ISAKMP:(2746): phase 1 packet is a duplicate of a previous packet.
    *Sep 10 08:56:03 UTC: ISAKMP:(2746): retransmitting due to retransmit phase 1
    *Sep 10 08:56:04 UTC: ISAKMP:(2746): retransmitting phase 1 MM_KEY_EXCH...
    *Sep 10 08:56:04 UTC: ISAKMP (2746): incrementing error counter on sa, attempt 1 of 5: retransmit phase 1
    *Sep 10 08:56:04 UTC: ISAKMP:(2746): retransmitting phase 1 MM_KEY_EXCH
    *Sep 10 08:56:04 UTC: ISAKMP:(2746): sending packet to x.x.x.x my_port 4500 peer_port 4500 (I) MM_KEY_EXCH
    *Sep 10 08:56:04 UTC: ISAKMP:(2746):Sending an IKE IPv4 Packet.

    This could be because the port 4500 packet that is being sent is not being received by the peer side or it is ignoring that packet. 
    Since the port 500 packet that you are receiving is a duplicate of the previous packet it is definitely not a reply packet for the port 4500 packet. 
    If you can get the debugs from the other end, then you could see if the peer side is receiving the udp port 4500 packets.
    If not that then this could be a UDP port 4500 block with the ISP.

  • Intercepting outgoing packets with DLPI, or other means

    My company is porting a network traffic-monitoring application to Solaris. We would like to use the Solaris "DLPI" interface to receive packets for analysis. However, my understanding is that DLPI will only provide incoming packets addressed to the local machine. In order to receive outgoing packets also, I understand that DLPI requires that the application place the network interface in promiscuous mode, which we are loathe to do for efficiency reasons. Is there a way in Solaris 7 or 8 to use the DLPI interface to receive both incoming packets addressed to the local machine and also outgoing packets from the local machine? If not, is there some other means of accomplishing this short of writing our own device driver? Thank you.

    You are correct, the arp's come down like normal messages in DL_UNITDATA_IND
    You can see them in hmeudreq. If you look into the message, you will see two blocks (the second hanging off mp->b_cont), something like the following. I haven't tried decoding it all, but you can see the arp (0806) in there.
    blk=0 len=28:
    00 00 00 07 00 00 00 08 00 00 00 14 00 00 00 00
    00 00 00 00 ff ff ff ff ff ff 08 06
    blk=1 len=28:
    00 01 08 00 06 04 00 01 00 40 2e 33 ca 82 01 01
    01 01 ff ff ff ff ff ff 01 01 01 02
    which is an arp request for 1.1.1.2 from 1.1.1.1.
    Hope this helps.
    S.

  • Bytes Received/Packet received in CPI report

    Hey guys,
    I am working on a  client session report in Prime infrastructure and dont understand tthis report coloums
    Header 1
    Header 2
    Header 3
    Header 4
    Header 5
    Bytes received
    Bytes send
    Packet received
    Packet send
    Data retries
    18923
    32393
    113
    79
    0
    Can any one tell me what is the difference between Byte and a Packet, on ethernet world one packet is equal to 1500 bytes (MTU). My 2nd question how do they calculate Data retries ? Data retries in bytes or packets ?
    what results can we get from this coloums.
    Thanks

    In most computer systems, a byte is a unit of data that is eight binary digits long. A byte is the unit most computers use to represent a character such as a letter, number, or typographic symbol (for example, "g", "5", or "?"). A byte can also hold a string of bits that need to be used in some larger unit for application purposes (for example, the stream of bits that constitute a visual image for a program that displays images or the string of bits that constitutes the machine code of a computer program).
    Packet switching is a communications paradigm in which packets (units of information carriage) are routed between nodes over data links shared with other traffic. In each network node, packets are queued or buffered, resulting in variable delay. This contrasts with the other principal paradigm, circuit switching, which sets up limited number of constant bit rate and constant delay connections between the nodes for their exclusive use for the duration of the communication. When a unit of data, beginning at the application layer (top layer) is transmitted to lower layers, headers and trailers are appended to it. Once the unit of data reaches the IP layer and source and destination IP addresses are added to it, it then is known as an IP datagram. The unit of data, feeling a little bloated from having all this extra baggage is then sent to the link layer where source and destination MAC addresses are perpended to it. Now it is called a frame - and more accurately an Ethernet frame (if the physical layer is Ethernet). To be precise, the unit of data passed between the IP layer and the network interface card is really a packet of data. Thus, a packet can be an entire IP datagram or perhaps a fragment of an IP datagram.
    In computer networking, the maximum transmission unit (MTU) of a communications protocol of a layer is the size (in bytes) of the largest protocol data unit that the layer can pass onwards. MTU parameters usually appear in association with a communications interface (NIC, serial port, etc.). Standards (Ethernet, for example) can fix the size of an MTU; or systems (such as point-to-point serial links) may decide MTU at connect time.

  • I have an Apple ID with a single  e mail address. I want to set multiple addresses in the same ID. Can I? If so how?

    I have an Apple ID with a single  e mail address. I want to set multiple addresses in the same ID. Can I? If so how?

    Howdy there johnzcarp,
    As I understand it you want to have more than 1 email address under your Apple ID. You can have what are called Alternate Email addresses associated with your Apple ID and this article will help you get those setup:
    Manage your Apple ID primary, rescue, alternate, and notification email addresses
    Alternate email address
    You can add one or more alternate email addresses for use with Apple services such as Game Center, FaceTime, Find My Friends, iMessage, and OS X notifications.
    Go to My Apple ID (appleid.apple.com).
    Select “Manage your Apple ID” and sign in.
    Add an alternate address:
    Select Add Email Address, then enter your alternate address. Apple will send a verification email to that address. Didn't receive the email?
    Follow the instructions in the email to verify the address.
    Edit an alternate address:
    Select Edit next to the address, then enter the new address. Apple will send a verification email to that address. Didn't receive the email?
    Follow the instructions in the email to verify the address.
    Delete an alternate address: Select Delete next to the address.
    Thank you for using Apple Support Communities.
    Take care,
    Sterling

  • I have a problem with mail autofilling info email addresses. Emails sent to me the from looks like this: Holiday in the United States email address . I have no idea what this Holiday in the United States is...How can I fix/change to my name?

    I have an irritating problem with mail autofilling info in email addresses. Emails sent to me the from looks like this: Holiday in the United States <my email address>. I have no idea what this Holiday in the United States is or how it got to be there...How can I fix/change to my name?
    I fixed the To: autofilling incorrectly by deleting my email address from the Previous Recipients List, but is there a way to stop that from coming up on emails that I receive?

    Have you checked your Mac address book? If your email is saved somewhere in your address book with the name "Holidays in the United States" it might be adding the name automatically in Mac Mail.
    Alternatively, try this:
    Delete an Email Address from Auto-Complete in Mac OS X Mail
    To remove an email address from the auto-complete list in Mac OS X Mail:
    Start typing the recipient's address or name in a new message.
    Select the desired address from the auto-complete list as if you'd compose an email to them.
    Click the small down arrow in the recipient.
    Select Remove from Previous Recipients List from the menu.
    You can also search for the unwanted address directly in the previous recipients list:
    Select Window | Previous Recipients from the menu in Mac OS X Mail.
    Highlight the address you want to remove.You can highlight multiple addresses by holding down the Command key.
    Click Remove from List.
    Source: About.com

  • I Tunes will not ley me play purchased songs from a computer that is broken, and from a previous e-mail address. I am at my wits end, as whenevr I try to authorise the computer I am using with my dead e-mail address. Any suggestions please?

    i Tunes will not let me play purchased songs from a computer that is broken, and which has a previous e-mail address. I am at my wits end, as whenever I try to play the songs I receive a message to authorise the computer I am using with my dead e-mail address. I end up in a mess, changing I-Ds, etc. I have paid an IT company to sort  things out, with some success, but still I keep getting thiese messages. Surely iTunes should be less complex than this. I am not brilliant with IT, but not at all stupid. Any suggestions please?

    1. The forum suggestions and feedback section is not the proper section of this forum, as you question/issue is not an idea or feedback about this forum.
    2. Reason : You have installed Desktop Manager using the 'Desktop Redirector' option.
    Step 1: If you're not using Redirector, you should uninstall Desktop Manager and then reinstall it using the BlackBerry Internet Service option.
    Step 2: On your device, go to: Options > Advanced > Service Book, and delete all service books for [Desktop]
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • When i send a text in iMessage the person receiving it gets it from my email address... how do i change that. and in message settings the receiving thing has my email and phone number but my phone number is gray and i can't click on it

    when i send a text in iMessage the person receiving it gets it from my email address... how do i change that. and in message settings the receiving thing has my email and phone number but my phone number is gray and i can't click on it help

    Hello Todd:
    I had this very same problem when trying to activate iMessage and Facetime on my iPad. When I signed into my account, I actually wasn't even presented with the option of a phone number - notwithstanding the fact that I was contacting others (and being reached by others) by my phone number on my iPhone. Having both the iPad and the iPhone on, I kept trying to turn off and on both iMessage and Facebook in Settings on both my iPad and iPhone, hoping that that they would eventually sync. But this proposed solution by others was unsuccessful for me.
    Then, I found out what the problem was: When my iPhone was activated, it automatically registered my phone number for contact purposes. I was using iMessage on my iPhone for quite some time without actually being signed into my Apple ID account. When another device - such as an iPad or iPod - is being used for iMessage or Facebook, you are prompted to sign into your Apple account, using your username and password. These two devices will not register your phone number as an option for contact unless your iPhone is signed into your Apple account as well. In other words: your phone number will not be synced.
    Go into your "Settings" on your iPhone and click on "Messages". Scroll down and click on "Send & Receive" (which should be followed by your phone number). On the next page, you will be able to determine whether or not your iPhone is using the Apple ID for messaging purposes. (Note: This information applies for Facetime as well.) If it is using your Apple ID for messaging, than at the top, you will see "Apple ID: <your particular e-mail account>" in Blue text. However, if you are not using your Apple ID for messaging, than you will see the words: "Use your Apple ID for message". Even though below this you will see your phone number checked as the contact source, you will want to click the tab that says, "Use your Apple ID for message". Sign into your account (just as you must sign in for iMessage on your other devices), and just choose your phone number as the "Send & Receive" contact. (The option of the e-mail will be there too, but you don't have to check it. And later on, you can delete it as an option.)
    Now that all of your devices are signed in using your Apple ID, the other devices should register your phone number as a choice. It may take a little while, however. What I did was sign out of iMessage on my iPad, and then sign in again. If the option didn't appear, I just went back and signed in again, and kept doing this until the option for the phone number appeared.
    Again, this will work for Facetime as well. The solution is to sync your iPhone account with the other devices by using your Apple ID for messaging (and Facetime) purposes.
    I hope that this works for you, Todd!   ~ Brian

Maybe you are looking for