• February 24, 2025, 04:17:14 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: DIR 825 blocking incoming/outgoing TCP/UDP packet  (Read 17835 times)

cessna1466u

  • Level 2 Member
  • **
  • Posts: 30
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #15 on: July 10, 2009, 01:15:08 PM »

FatMan once again I am confused. I think we might be mixing two posts and twisting our equipment. Let me explain my setup and see if we can figure something out:

Comcast 20+ mbps internet account
Motorola DocSys3 Surfboard Modem
Dlink DIR-825 Wireless router

To this I have 2 linksys VoIp Vonage routers hooked up with DHCP/Wireless and other features turned off. These are basically phone modems. It is not assigning or allowing any computers to go online.

on the other 2 porst of the Dir-825 I have my Xbox and my laptop. That is it.

I am not using the Linksys Voip routers because they are not Gigabit and they dont offer Wireless N capabilities. My laptop is Gigabit and so is the cable modem. I have ran cat6 wire and connectors through out the house. This is how I was told to set it up by the Advanced (Paid) technical support from Linksys.

My biggest concern right now is this message on the log file:

Blocked outgoing TCP packet from 192.168.0.251:49913 to 74.125.53.121:80 as FIN:ACK received but there is no active connection

The first ip Address is the address of my laptop. The rest I dont know.

I ran a spybot check, a virus check and even turned anything in the house that might have wireless internet off. iPhones, Wii, Roku Media Player. Could I have a virus I dont know of and its trying to send information out of my laptop. I get the same kind of message but with outgoing changed to incoming.

Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #16 on: July 10, 2009, 01:31:52 PM »

You are right, I had a crossed wire, I was confusing which earlier thread this thread had been hijacked from.  I am straightened out now.

That message means the packet has been dropped by SPI (SPI is not the only SPI setting endpoint filtering plays in here too in a not terribly well defined way).  Period.

Also, I realize it doesn't matter at this point but even if your modem is gigabit (I haven't seen one personally but hey anything is possible), your WAN pipe is not (20+ is way less than 100, and not on the same scale as 1000) and having gigabit on your modem is not a benefit in the slightest.

Regardless of where on your LAN the DIR is it's LAN ports are gigabit, however even that is a non-issue in your environment because you only have 1 gigabit device you are therefore getting zero benefit from gigabit.  If you paid someone for that network layout and your criteria was making use of gigabit then you could have burned the money and at least gotten a little heat out of it, as such even that was lost.
Logged
non progredi est regredi

cessna1466u

  • Level 2 Member
  • **
  • Posts: 30
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #17 on: July 10, 2009, 01:48:39 PM »

I might be completely wrong here but here is my reason for having the gigabit modem. I have a gigabit computer, a gigabit router and now a gigabit modem. So the time that it takes my computer to get to the modem has been decreased and when downloading a file the cyber waterhose is now a firemans hose. So files get back to my computer faster. Now why would you say that the WAN pipe is not gigabit? What do you consider the WAN pipe. I do plan on getting a gigabit NAS device in the near future which is another reason for the Gigabit.
Logged

cessna1466u

  • Level 2 Member
  • **
  • Posts: 30
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #18 on: July 10, 2009, 02:03:08 PM »

One note on this blocking of incoming TCP packets:

I checked all the items in my house that have used the internet: Wii, iphone etc., and none of them have that mac adress that is showing up on there. Does this mean that someone outside of my network is trying to penetrate my firewall and the fact that its blocking it, it means that the firewall is working right?
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #19 on: July 10, 2009, 02:13:28 PM »

I mean that the additional capacity of gigabit is unused for WAN traffic.

If you have 20Mbps coming down, that will not saturate a 100Mbps pipe, so a 1000Mbps pipe is no benefit over a 100Mbps pipe.

Now if you had that gigabit storage device we are finally talking about adding capability, as long as the PC and the network storage device are both connected to a gigabit switch (tha LAN of the DIR is one) then you could (potentially) see benefit.

Then you get to ask yourself if your single PC's file requests can saturate the network storage device's capability to fulfil them and if so what is your total potential throughput.  In my experience with home class storage devices (in as simple a network as you have explained to me) that saturated best case throughput is still less that 100Mbps.

As such even with that additional equipment (which would require some moving things around in your current network) it is questionable if gigabit will be a boon to you.

Since when do we have a MAC address involved?  Where are we seeing this MAC, in what context?  PM me the MAC so I can take a look at it, it might tell me more than it tells you.
Logged
non progredi est regredi

emod

  • Level 1 Member
  • *
  • Posts: 5
Re: DIR 825 blocking incoming/outgoing TCP/UDP packet
« Reply #20 on: February 08, 2010, 12:45:35 PM »

Very sorry for not following up on my own thread.
The one and only solution that worked for my ffxi connection problem, after climbing the tech support ladder to level3? higher? was....

They had me change my router address to 192.168.10.1
That solved all the problems but they/me tried everything else to get it to work.
Logged
Pages: 1 [2]