• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos0

Rule rejected TCP(6) every 10 seconds.

Started off as 4x "Rule  rejected  UDP(17)" every 10 minutes then 8 of them every minute, now it's "Rule rejected TCP(6)" every 10 seconds.

For the past 2 years their have been wireless devices connected to the network such as mobile phones, tablets, and laptops of the 2 other people that live in the house and it's only in the past few days that my computer has been under attack by a device connected to the network, now my computer is the only one connected directly to the modem via cat 6 cable and has no wifi receive or transmitter. this is what the attack looks like and the more days go by the more often it happens and more aggressive it gets.

Category: Firewall - Activities
Date & Time,Risk,Activity,Status,Recommended Action,Category
1/04/2015 1:37:03 a.m.,Info, Rule  rejected  TCP(6)  traffic with  (192.168.1.254  Port (39709) ),Detected,No Action Required,Firewall - Activities
 Firewall rule was matched:<br> Rule Name: Default Block SSDP<br> Rule Action: rejected<br> Rule Severity: normal<br> <br> Traffic Details:<br> Protocol:  TCP(6) <br> Direction: inbound<br> Local Host: NEREVAR<br> Local IP: 192.168.1.69<br> Local Service:  Port (2869) <br> Remote Host: <br> Remote IP: 192.168.1.254<br> Remote Service:  Port (39709) <br> Remote MAC:  -- <br> Adapter Index: 11<br> <br> Process Information:<br> Process ID: 4<br> Process Path: System<br>

Each time the "Remote Service:  Port" number changes.

I'd like to know if this is because one of the devices on the network is infected with a virus, also on my network settings all devices are set to restricted and have been like that for the past 2 years.

The "Remote IP: 192.168.1.254" is the Modem itself.

Replies

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

A reminder this has only just started happening in the past few days and as time goes on the more often it tries to get past Norton.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Went into the modem and disabled "UPnP" and it still bombards my computer.

Also "Rule  rejected  TCP(6)" is now happening every second now.

If this keeps increasing then eventually it'll be DDOSing my computer aka spamming my computer with requests to the point the line crashes the same way ddosing works.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

If you suspect the possibility of a "hacked router", it may behoove you to take a look at the following thread...

https://community.norton.com/en/forums/check-your-router-settings

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

FWIW ~ I had a slew of Rule rejected TCP(6)....so, I reset Firewall.  Purged Network Security Map.  PwDn computer.  PwCycled router.  PwUp computer.  Checked DNS server address.  Firewall reset and Network Security Map refresh.  Trust Level Protected (recommended setting)

Firewall Activities looks better.... do you want me to post export

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

This is the same question that the poster asked in an earlier thread.  UPnP and SSDP are related.  I would double check that you saved the setting when you disabled UPnP.  These are completely normal communications from a router or other device that has UPnP enabled.  They will not dos your computer.  And if you change the Norton Network Trust to "Shared" Norton will even allow the traffic, rather than blocking it - it is not dangerous.

https://community.norton.com/en/forums/inbound-rule-rejection-spamming-n...

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

I had 10 pages of Rule rejected TCP(6) ... which was not normal history for me. 

Now, I don't....your mileage may vary

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

UPnP is confirmed to be disabled.

I however disabled the wifi and the rule rejections stopped which confirms that a new device on the network is trying to make connections with my computer.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Torturim:

UPnP is confirmed to be disabled.

I however disabled the wifi and the rule rejections stopped which confirms that a new device on the network is trying to make connections with my computer.

So, you're wired now and the TCP(6) stopped.  I ask because...I'm always wired and was seeing TCP(6) rule rejections....

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

I've been wired for the pass 2 years, my computer build doesn't contant any wifi reciever, this pc hasn't ever been wifi capable.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Torturim:

I've been wired for the pass 2 years, my computer build doesn't constant any wifi receiver, this pc hasn't ever been wifi capable.

Sorry, thought you wrote < I however disabled the wifi >

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Yeah I disabled the wifi that is on the router.
The router is both wireless and wired, with 4 ports on the back for cat 6 cables.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Re-enabled the wifi on the router, don't see Rule rejected TCP(6) anymore however it's gone back to Rule rejected UDP(17) 8 times every 10 minutes.

UPnP is still disabled.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

WiFi is disable on my router also...just trying to share my Rule rejected recent occurrence.   I'm sure it's un-related to your issue.  Cheers

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Found this interesting:

http://blog.sucuri.net/2014/09/quick-analysis-of-a-ddos-attack-using-ssdp.html

"The first packets we found had the source port 1900 (SSDP) and were hitting destination port 7 (echo). This is what it looked like:

19:11:48.918266 IP 5f44d7e8.dynamic.mv.ru.1900 > serverX.sucuri.net.echo: UDP, length 274
19:11:48.918271 IP 111.226.144.199.1900 > serverX.sucuri.net.echo: UDP, length 320
19:11:48.918275 IP 95.67.190.27.1900 > serverX.sucuri.net.echo: UDP, length 307
19:11:48.918279 IP 111.226.144.199.1900 > serverX.sucuri.net.echo: UDP, length 326
19:11:48.918283 IP c-69-141-76-209.hsd1.nj.comcast.net.1900 > serverX.sucuri.net.echo: UDP, length 300
19:11:48.918287 IP 145.255.28.15.dynamic.ufanet.ru.1900 > serverX.sucuri.net.echo: UDP, length 307
19:11:48.918291 IP c-69-141-76-209.hsd1.nj.comcast.net.1900 > serverX.sucuri.net.echo: UDP, length 302
19:11:48.918294 IP 16.77.223.77.akado-ural.ru.1900 > serverX.sucuri.net.echo: UDP, length 323
19:11:48.918301 IP 120.192.146.173.1900 > serverX.sucuri.net.echo: UDP, length 268

This was a new attack vector, leveraging SSDP. UDP-based DDoS is common, many in this business see it often. Often enough that rulesets exist to proactively block and mitigate attacks, but the use of SSDP is rare, at least for us. Interestingly enough, based on the Community Emergency Response Teams (CERT) blog, SSDP can lead to a 30x amplification of the attack, which might explain why attackers are using it now. "

Should also note that not so long ago the Spark ISP started crashing and having issues due to a large number of customer computers becoming infected and being remotely controlled to land DDOS attacks which caused great strain on the ISP.

http://www.nzherald.co.nz/business/news/article.cfm?c_id=3&objectid=11320100

"A handful of our customers' computers have been infected with malware and that's generating very high volumes of traffic to overseas sites," Roberts elaborated. This traffic was slowing down web access for broadband and mobile Spark customers."

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

The Rule rejected UDP(17) as stated on Norton;
Showing 8 rejections per 10 minutes, 4 targeting svhost.exe and the other 4 targeting BitTorrent.exe.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Seems you have pretty much traced this to your router's Wi-Fi access...

Consider examining your router's logs for recently attached, unrecognized devices (on your LAN).  If your router supports device access control, consider enabling it and configuring it with your known devices list (MACs), then setting it to block all new unauthorized devices (those which you've not registered their MACs with the router).  If your router has WPS capability consider disabling it (assuming your router permits you to do so - but not all do).  FWIW, WPS has long been known as a security hole in many (perhaps most) Wi-Fi router implementations - doing a quick web-search will confirm this feature flaw...  Also verify that remote administration is disabled on the router and that you have updated your router's Admin login to use a complex pw ...

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Well, I'm hoping my history for these events is normal noise....I'll be watching your progress....

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Category: Firewall - Activities
Date & Time,Risk,Activity,Status,Recommended Action,Category
1/04/2015 9:25:21 a.m.,Info, Rule  rejected  UDP(17)  traffic with us.launcher.battle.net (192.168.1.254  Port (47455) ),Detected,No Action Required,Firewall - Activities
 Firewall rule was matched:<br> Rule Name: Default Block UPnP Discovery<br> Rule Action: rejected<br> Rule Severity: normal<br> <br> Traffic Details:<br> Protocol:  UDP(17) <br> Direction: inbound<br> Local Host: <br> Local IP: 239.255.255.250<br> Local Service:  Port ssdp(1900) <br> Remote Host: us.launcher.battle.net<br> Remote IP: 192.168.1.254<br> Remote Service:  Port (47455) <br> Remote MAC:  -- <br> Adapter Index: 11<br> <br> Process Information:<br> Process ID: 4792<br> Process Path: C:\Windows\System32\svchost.exe<br>

"Rule  rejected  UDP(17)  traffic with us.launcher.battle.net"

This was interesting since my computer is the only one with the battle.net app installed on and it's not installed on the other 2 laptops in the network which atm are turned off.

That rule rejection happened 82 times in the space of a second when I rebooted the router remotely on my computer.

The BitTorrent rule rejections stopped when I closed down BitTorrent.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Well clicked (once) on refresh list on Norton 360s history and Norton 360 stopped responding and windows promptly closed all n360.exe processes down and disappeared off task manager.

Haven't seen something like this happen to norton in over 5 years and when it happened 5 years ago my computer was using 100% of it's CPU and GPU resources running a game, and this just happened while my computer had only windows media player opened and internet explorer.

And just noticed windows media player jump up to 400,000k memory usage and then steady out to 250,000k memory usage when it's only playing a playlist of 30 .mp3 songs.

Closed it down started it back up and it's gone back up to 250,000k spiking at 400,000k, restarted the computer and it has done the same thing.

http://i.imgur.com/mtcVNRY.png

Picture of it at 364,000k.

This is definitely not normal behaviour.

A full norton system scan and malwarebytes anti-malware scan was completed 7 hours ago with scanning for rootkits ticked as well no threats were found.
 

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Rule  rejected  TCP(6) has come back however has no port or IP address, is my computer trying to loop back on itself whenever wifi is enabled on the router?

Category: Firewall - Activities
Date & Time,Risk,Activity,Status,Recommended Action,Category
1/04/2015 9:55:21 a.m.,Info, Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities
 Firewall rule was matched:<br> Rule Name: Default Block SSDP<br> Rule Action: rejected<br> Rule Severity: normal<br> <br> Traffic Details:<br> Protocol:  TCP(6) <br> Direction: inbound<br> Local Host: <br> Local IP: ::0<br> Local Service:  Port (2869) <br> Remote Host: <br> Remote IP: ::0<br> Remote Service:  Port (0) <br> Remote MAC:  -- <br> Adapter Index: 0<br> <br> Process Information:<br> Process ID: 4<br> Process Path: System<br>

http://i.imgur.com/ecOfXj0.png

Picture of it on history.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Does this seem odd 2 U...>   1/04/2015

Kudos1 Stats

Re: Rule rejected TCP(6) every 10 seconds.

No I live in New Zealand we are a day ahead of America.

UTC+12:00

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Thanks...I've had a few of those with 0

3/31/2015 12:36:57 PM,Info,    Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 12:36:56 PM,Info,    Rule  rejected  TCP(6)  traffic with  (192.168.1.1  Port (3558) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 12:36:56 PM,Info,    Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 12:36:56 PM,Info,    Rule  rejected  TCP(6)  traffic with  (192.168.1.1  Port (2537) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 12:36:56 PM,Info,    Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities,,,,,,

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

3/31/2015 10:36:56 AM,Info,    Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 10:36:56 AM,Info,    Rule  rejected  TCP(6)  traffic with  (192.168.1.1  Port (2581) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 10:36:56 AM,Info,    Rule  rejected  TCP(6)  traffic with  (::0  Port (0) ),Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 10:36:39 AM,Info,"An instance of \"C:\Windows\System32\SearchFilterHost.exe\" is preparing to access the Internet.",Detected,No Action Required,Firewall - Activities,,,,,,
3/31/2015 10:36:39 AM,Info,"An instance of \"C:\Windows\System32\SearchProtocolHost.exe\" is preparing to access the Internet.",Detected,No Action Required,Firewall - Activities,,,,,,

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

How did you determine that 192.168.1.254 was your router?

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

https://answers.yahoo.com/question/index?qid=20120216233505AAuqcyF

Don't forget about the Toredo Tunneling pseudo- interface. Sorry I can't explain what it is.

Success always occurs in private and failure in full view. Windows 10 Pro 64 bit Norton Core Security Plus 22.18.0.213 Core Firmware 282 I E 11 Chrome latest version.
Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

SendOfJive:

How did you determine that 192.168.1.254 was your router?

Because to get to the routers login screen you type in "192.168.1.254" into the address bar of internet explorer. 

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Did you check the client list in the router configuration pages to see what devices are listed?

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Is this by chance a 2Wire Gateway?  Possibly connected to an AT&T service connection?

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Hello John

I doubt it. O/P is from New Zealand. I doubt if AT&T is all the way over there.

Success always occurs in private and failure in full view. Windows 10 Pro 64 bit Norton Core Security Plus 22.18.0.213 Core Firmware 282 I E 11 Chrome latest version.
Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

I'm with the ISP:Telecom re-named to Spark

Last night it started doing UDP(17) and TCP(6) 4 times every second.

However it also changed to:

Category: Firewall - Activities
Date & Time,Risk,Activity,Status,Recommended Action,Category
1/04/2015 11:01:53 p.m.,Info, Rule  rejected  UDP(17)  traffic with  (192.168.1.69  Port (61256) ),Detected,No Action Required,Firewall - Activities
 Firewall rule was matched:<br> Rule Name: Default Block LLMNR<br> Rule Action: rejected<br> Rule Severity: normal<br> <br> Traffic Details:<br> Protocol:  UDP(17) <br> Direction: inbound<br> Local Host: <br> Local IP: 224.0.0.252<br> Local Service:  Port (5355) <br> Remote Host: <br> Remote IP: 192.168.1.69<br> Remote Service:  Port (61256) <br> Remote MAC:  -- <br> Adapter Index: 11<br> <br> Process Information:<br> Process ID: 1384<br> Process Path: C:\Windows\System32\svchost.exe<br>

Category: Firewall - Activities
Date & Time,Risk,Activity,Status,Recommended Action,Category
1/04/2015 11:01:53 p.m.,Info, Rule  rejected  UDP(17)  traffic with  (fe80::eca9:ead:65c4:5a37%11  Port (61256) ),Detected,No Action Required,Firewall - Activities
 Firewall rule was matched:<br> Rule Name: Default Block LLMNR<br> Rule Action: rejected<br> Rule Severity: normal<br> <br> Traffic Details:<br> Protocol:  UDP(17) <br> Direction: inbound<br> Local Host: <br> Local IP: ff02::1:3<br> Local Service:  Port (5355) <br> Remote Host: <br> Remote IP: fe80::eca9:ead:65c4:5a37%11<br> Remote Service:  Port (61256) <br> Remote MAC:  -- <br> Adapter Index: 11<br> <br> Process Information:<br> Process ID: 1384<br> Process Path: C:\Windows\System32\svchost.exe<br>

Now that it showed a proper IP address I was able look at the IP addresses of the tenants devices to see which one it is, turns out it is a new laptop and has no anti-virus software or firewall software installed on it, also made sure that all "sharing" options were turned off on the laptop however in doing so it made no difference the Laptop keeped sending my pc its IP address trying to share files, and UPnP was still disabled.

Earlier this morning ran a full system scan with Norton and again no threats were found however about 10 minutes after that I went off to make breakfast, came back to the computer and Norton was requesting to restart the computer to resolve a threat it found during an idle scan.

When I went off to make breakfast Norton did its usual idle scans whenever the pc goes idle now from the space between the completion of the full system scan that told me no threats were found and the time it took me to make my lunch 20 minutes later I installed no programs, downloaded no files, didn't even visit a webpage, and was currently the only person in the house.

The threat it discovered was a Backdoor.Regin hidden in a .tmp file.

http://www.symantec.com/security_response/writeup.jsp?docid=2013-121221-3645-99

Here are the details:

Filename: 00006923.tmp
Threat name: Backdoor.Regin
Full Path: c:\program files (x86)\malwarebytes anti-malware\00006923.tmp

____________________________

Details
Very Few Users,  Very New,  Risk High

Origin
Downloaded from
 Unknown

Activity
Actions performed: Actions performed: 1

____________________________

On computers as of 
2/04/2015 at 7:16:26 a.m.


Last Used 
2/04/2015 at 7:18:28 a.m.


Startup Item 
No

Launched 
No
____________________________

Very Few Users
Fewer than 5 users in the Norton Community have used this file.

Very New
This file was released less than 1 week  ago.

High
This file risk is high.

Threat type: Virus. Programs that infect other programs, files, or areas of a computer by inserting themselves or attaching themselves to that medium.

____________________________

Source: External Media

Source File:
00006923.tmp
____________________________

File Actions

Infected file: c:\program files (x86)\malwarebytes anti-malware\ 00006923.tmp Removed
____________________________


File Thumbprint - SHA:
188dca8920994bfe6ac0cf213172efb3f9a159e7db9f63a8fdb8316f42a224f8
File Thumbprint - MD5:
Not available

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Your malicious file is a temp file in Malwarebytes' Program files.  Most likely a program conflict between Norton and Malwarebytes, rather than an actual threat. 

Please visit the Microsoft website and search for articles on file sharing and networking for the operating system installed on the laptop.  You may need to make several settings changes to stop the laptop from seeking out other devices.  And remember, Norton is blocking the traffic from the laptop, so there is no cause for concern about this.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Maybe I missed something but what is the tennents IP address?

Was it on your local 192.168.1.xx subnet?

If it is, it's connected to your router and you need to chage the password.  If it's coming in from the WAN (internet) then I don't see how that is possible unless your router is in DMZ mode and everything is being forwarded.

Dave

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

moved..

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

DaveH:

Maybe I missed something but what is the tennents IP address?

Was it on your local 192.168.1.xx subnet?

If it is, it's connected to your router and you need to chage the password.  If it's coming in from the WAN (internet) then I don't see how that is possible unless your router is in DMZ mode and everything is being forwarded.

Dave

There is a reason why he's on the network because he is a tenant of the house, being a tenant of the house he pays board per week to live here which pays for his room, power, internet, food. 

He has also lived here for 2 years however when he got his new laptop is when the rule rejections in Norton started up and they continue even when his laptop isn't connected to the network.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Hello

Is he using a Norton product on that new Laptop?

Success always occurs in private and failure in full view. Windows 10 Pro 64 bit Norton Core Security Plus 22.18.0.213 Core Firmware 282 I E 11 Chrome latest version.
Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

No he isn't.

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Is this any good info, towards a resolution. (Could be way off track.)
__________________

A Win7 Starter Crash, running NIS.

I have a Netbook running Win7 Starter. Recent, x3 Optional Microsoft Updates, registered "Installed", OK. During the next boot-up, the screen appeared to drop back into Safe Mode, the Security Centre lit up, and the pc was dead in the water. Simplest thing to do, 3-pin reset, "Restart". The pc came up, and looking in the logs told me that one of the MS Updates failed to install correctly.

So, I had a look in MS Updates, "Most recent check for updates", and "Updates were installed", both indicated "Never". "Installed Updates" indicated hundreds.

Pressed "Check for Updates", after 1hour 30mins it returned x2 Optional Updates, Skype and Printer Drivers. I can only guess that it was seaching for Updates from "day 0" to current.

Ever since this crash, I've had the associated problem of this post: "RULE REJECTED, et al."

I guess there's something out there pinging in, looking for something that doesn't reply. I've had this problem appear before, on previous pc's. I've left it alone, and it stops.

NIS keeps me safe, the "Firewall" is doing it's job. You can't spend too much time on stuff like this; unless, it's your occupation or hobby.

Be safe out there !
The Silver Surfer.
AK 

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

If UPnP is enabled in the router and whatever other devices are connected to it, your PC will see the multicast traffic.  If your network trust level is Private or Shared, the Norton firewall allows the traffic; if your trust level is Public, Protected, or Restricted, the firewall will block it.  How busy the firewall gets is not a concern.  It monitors all traffic all the time, it's always busy.  The only question worth asking is, "do I want UPnP enabled or not?"  It will make connecting a new device to your network easier on you;  other than that it should be disabled.   credit: SOJ
UPnP Discovery and Simple Service Discovery Protocol SSDP allow devices on a local network to find each other and communicate without the user having to make any settings changes, such as manually opening needed ports, etc.  It makes it easy to add a new device to your network because the configurations are done automatically.  Norton allows these protocols on a private or shared network where they are useful, but blocks them on public or protected networks where they are not needed.  credit: SOJ

Forum Search UPnP / Rule Rejected will offer numerous posts. 

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

ITMA.
​All my troubles started with one of those MS Monthly Win10 Updates. My machine threw a "mental", and when it finally came back up; the troubles began.

22.5.0.124 appears to have solved all. Simple "history"; no great strings of ping-ping-ping. All is good !

Be safe out there !
"It's That Man Again."
The Silver Surfer. AK.  [ CC/1960. "Concordia Res Parvae Crescunt" ] 

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

photo308:

ITMA.
​All my troubles started with one of those MS Monthly Win10 Updates. My machine threw a "mental", and when it finally came back up; the troubles began.

22.5.0.124 appears to have solved all. Simple "history"; no great strings of ping-ping-ping. All is good !

Be safe out there !
"It's That Man Again."
The Silver Surfer. AK.  [ CC/1960. "Concordia Res Parvae Crescunt" ] 

Why post this twice?  It just adds clutter.

A little bit of knowledge is... well a little bit of knowledge.
Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Krusty13:

Why post this twice?  It just adds clutter.

ITMA.

Two different threads, two different posts. I would of thought that people would only follow their own posts. Not everybody reads all of the forum posts, all of the time ?

Be safe out there !
"It's That Man Again."
The Silver Surfer. AK.  [ Nil illegitimi carborundum ]  

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Yes, but you posted exactly the same thing twice.  Perhaps I just don't understand your logic here.,

A little bit of knowledge is... well a little bit of knowledge.
Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

Krusty13:

Yes, but you posted exactly the same thing twice.  Perhaps I just don't understand your logic here.,

ITMA.

I had incurred both sets of 
symptoms. It seems courteous to me, to let both posts know, that all had gone.

Be safe out there !
The Silver Surfer. AK.  [ CC/1960. "Concordia Res Parvae Crescunt" ] 
previously [ photo762 ] : Nil illegitimi carborundum !

Kudos0

Re: Rule rejected TCP(6) every 10 seconds.

photo308:
Krusty13:

Yes, but you posted exactly the same thing twice.  Perhaps I just don't understand your logic here.,

ITMA.

I had incurred both sets of 
symptoms. It seems courteous to me, to let both posts know, that all had gone.

Be safe out there !
The Silver Surfer. AK.  [ CC/1960. "Concordia Res Parvae Crescunt" ] 
previously [ photo762 ] : Nil illegitimi carborundum !

Ah!  I see.  

A little bit of knowledge is... well a little bit of knowledge.

This thread is closed from further comment. Please visit the forum to start a new thread.