Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Slovak]

What do these errors mean? Web pages are loading, sometimes not, sometimes with errors?

[INFO] Sat Mar 06 12:23:26 2004 Log viewed by IP address 192.168.0.199
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.185 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.182 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.181 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.180 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.179 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.178 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.177 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.176 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.175 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.174 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:26 2004 Dropped packet from 192.168.0.198 to 59.94.168.173 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.172 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.171 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.170 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.169 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.168 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.163 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.162 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.161 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.160 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.159 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.158 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.157 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.155 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.154 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.153 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.151 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.149 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.148 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.143 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.142 (IP protocol 6) as unable to create new session
[INFO] Sat Mar 06 12:23:25 2004 Dropped packet from 192.168.0.198 to 59.94.168.140 (IP protocol 6) as unable to create new session

[TaVARUS]

    More than likely, the requested ports at the destination IP has been closed by that host. IP Protocol version 6 is Torado IPv6 (RFC1883), so the PC at IP Address 192.168.0.198 is more than likely a Vista Machine.

    First we need to identify the local IP Address as being an authorized and known device on your local Network. If it's not a device known to you, then we need to kick it from the network via MAC Addres Filter. {ADVANCED tab >> NETWORK FILTER page}


     

[Slovak]

It's my sons computer, XP Home. So it is authorized on my network, now what?

[Slovak]

Bump

[TaVARUS]

I would now check to see if his PC's Network adapter has the "Internet Protocol Version 6(TCP/IPv6)" stack enabled. If so, and he has no IPv6 enabled applications running, I would disable it in the Network Adapters Properties, under the section labled "This connection uses the following items".

If you find that he need this to run a certain application, the only other thing would be to disable the SPI (statefull Packet Inspection) or set the routers Endpoint Filtering to a less restrictive NAT; both options are located under the ADVANCED tab >> FIREWALL section, both options will take your Routers firwalling capabilities to a less secure state.

[Slovak]

Well he does not have IPv6 listed anywhere in there, and SPI was already disabled. How to I relax the Endpoint Filtering? I see it but have no idea how to set it?

[TaVARUS]

The NAT endpoint filtering... pretty much is a communication specific filtering mechanism. It's split between UDP & TCP traffic. Without actually knowing, what the application on the XP home PC is trying to do... we can only guess!

To configure, I would first attempt setting TCP to "Address Restricted"; test it... then if the packets are still being dropped I would set to the "Least Restrictive" (said to be "like" a Full Cone NAT) which is "Endpoint Independent". Let me which setting resolves the problem.

[DLinkUserDude]

Perhaps you are confusing IP Version 6, with IP Protocol 6 (TCP).

When i read that log message, i read it as IPv4 Protocol 6, which is....TCP.

If indeed the text of this message is referring to IPv6, it needs to be changed in the firmware to read as such, as, indeed, "IP Protocol 6" refers to IPv4 Protocol 6 - TCP.  It should read something like "IPv6 etc etc"

Indeed, I didn't know this product had ANY support for IPv6 at all, since it isnt listed anywhere in any documentation i can find, including in the firmware settings etc.  It would be strange that the only support this product has for IPv6 would be to detect IPv6 traffic and then to log it (and do nothing else with it), which is why i doubt that that is a reference to IPv6, but rather refers to IP Protocol 6 - TCP.

[TaVARUS]

Yes, no IPv6 support on router, and, this is a just TCP connection that is unable to be established. The M$ IPv6 will fall back to Teredo in the presence of a NAT; which has 6to4 which actually encapsulates IPv6 in IPv4 packets for transport over the Internet to 6to4 relay server/router to get to "IPv6 Internet". Intially, that was what I had thought was happening; please disregard my misdiagnosis. But again, thats not what happened here. Indeed, your correct, this is just a SYN Sent to what looks to be almost consecutive IP Address, and still may be a problem at the PC (XP Home) that is requesting the communication. Do you know what the Application is that is running? If your son is running bit torrent, then it's not a true problem. If you just want log to stop displaying those dropped packets exclusively, and not all dropped packets... it cannot be currently done.

If you have attempted to set the NAT ENDPOINT FILTERING feature to a more relaxed state for TCP only, let us known what the outcome was? Thanks!

[DLinkUserDude]

Yes, no IPv6 support on router, and, this is a just TCP connection that is unable to be established.

Well, at least you recognize that now.......  You of course knew this all along, and werent simply posting assorted IPv6 related technical info as you went along as you learned it..no no, that surely wasnt on display here...

All in all, it seems pretty clear to me that you are really just educating yourself (as well as being educated by others..ahem) as you post along as to the technical vagaries of IPv6 (and anything else).

The M$ IPv6 will fall back to Teredo in the presence of a NAT; which has 6to4 which actually encapsulates IPv6 in IPv4 packets for transport over the Internet to 6to4 relay server/router to get to "IPv6 Internet".

"M$"?  I didnt realize this was the "I'm (emotionally) 13 and Windoze sukkz" forum.  Please, tell me you arent actually an employee of D-Link or a sub-contracted support organization.

I'm sure the additional IPv6 technical description is very handy to post "out loud" as you learn it, even if its totally irrelevant at this point.

Are you trying to convince someone you really do know what you are talking about? 

Intially, that was what I had thought was happening; please disregard my misdiagnosis.

So, instead of just typing that "mea culpa", it was instead important and necessary to convince anyone/everyone you knew SOMETHING about ANYTHING (in this case what you just read in a summary description somewhere, probably at MSDN) in order to minimize the appearance of lack of knowledge on your part, eh?

Dont worry, as soon as you typed and posted "M$", it pretty much confirmed that particular state of being.

But again, thats not what happened here.

You could always post more info you recently gleaned about IPv6 and Microsoft's implementation...

Indeed, your correct, this is just a SYN Sent to what looks to be almost consecutive IP Address, and still may be a problem at the PC (XP Home) that is requesting the communication.

Is it? Are you sure?  Perhaps you could post some information about how SYN is utilized in IPv6 connectivity scenarios..

Do you know what the Application is that is running?

I sure dont, but perhaps the original poster does?  Are you confusing responding to me with responding to the OP?

If your son is running bit torrent, then it's not a true problem.

Oh, ok.  As long as it isnt a "true" problem...  Again, perhaps you want to address this to the OP?

If you just want log to stop displaying those dropped packets exclusively, and not all dropped packets... it cannot be currently done.

If you have attempted to set the NAT ENDPOINT FILTERING feature to a more relaxed state for TCP only, let us known what the outcome was? Thanks!

I sure hope you didn't code the English text response strings for the firmware logging funtionality...

[TaVARUS]

WOW!
...O.K.,
check it...

IN RESPONSE: I thought that informing you of my misdiagnosis, would put your mind at ease (...you know...your the customer and your right)! Well! That could not be done... in your (...ahem) predisposition... ! Anyway, ...
ASSISTANCE: the router dropped your TCP connection, per the log.
YOU CAN: relax the NAT ENDPOINT FILTERING or not!
YOU WILL: need to provide more information about the PC that is having it's packets dropped; for further assiostance! Thank you!

PS... IF YOU: would like more information on IPv6... I can give it to you! PM me off line!!!   

[Lycan]

Dlinkuserdude,
Please remember that these forums are offered as a courtesy. I do not appreciate the snide tone of your responses after Tavarus was trying to help you.

Please refrain from name calling and other abusive tones.
Also remember that you're here for help, not to flex your verbal muscles.

Use of M$ often used and widely accepted as Microsoft on forums everywhere. Even their own.