cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Expert
1,197 Views
Message 41 of 87

Re: Strange items in log since HH3A update

OK, I understand now. The openreach box. I dont know how much to replace but you carnt buy them from Amazon or ebay. I think it will need replacing but BT will know you have unlocked it and they will claim you have broke there terms so they will bill you for a new one. Simples!. 😉

 

You can buy one from Ebay, cheap so go for that option but I am a little bit worried about the new update and how that will work. I hope someone can help you out buddy. Goodluck!. 🙂 Definate contact BT about it, but I suppose then they will know..eh...not sure on this one. But they will know anyway by reading this thread.

Please click on white star to the left and say thanks if I have helped you at all!. 🙂 Thank you. Some handy links Copy & Paste:-
http://bthomehub.home/
http://netalyzr.icsi.berkeley.edu/index.html
http://diagnostics.bt.com/login/?workflow=Speed
0 Ratings
Highlighted
Contributor
1,189 Views
Message 42 of 87

Re: Strange items in log since HH3A update

MBR123.....please read the posts properly.

The items that are in question come from the HH3A log (which BT just updated).

These items are freely available to ANYONE with a HH3A on Infinity, BUT the other poster has also given stats that he's collected from the OR Modem (just to confuse the issue).

It doesn't matter if the OR Modem is unlocked or not the issue is with the HH3A, a totally seperate piece of kit.

And for info...........Homehubs are supplied by BT retail and the White Modems are from Openreach, seperate pieces of equipement from seperate organisations.

 

Got it now..........simples

0 Ratings
Highlighted
Aspiring Expert
1,181 Views
Message 43 of 87

Re: Strange items in log since HH3A update

Im sorry for posting those stats, i just wanted to show that it wasnt my actual internet that was disconnecting it was just the wired lan ports disconnected, renewing dhcp requests way before they should be, along with all the others like spoofing protection and invalid connections and stuff, please can we get backl to the hhb3 event log issues , no more posting about equipment being unlocked and stats, its my bad, i shouldnt of posted the stats, i apologise for that, and apologise to the person who started the thread.

0 Ratings
Highlighted
Aspiring Expert
1,173 Views
Message 44 of 87

Re: Strange items in log since HH3A update

Im also started getting CCA failures now, i dont know what it means on a router but it usually meqns the harware is failing in engineering. It l,ooks to me it is seriously damaged.

0 Ratings
Highlighted
Aspiring Expert
1,153 Views
Message 45 of 87

Re: Strange items in log since HH3A update

I am getting these logs on my hh3 too.

16:50:50, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:50:12, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
  
16:48:43, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:48:17, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:48:16, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 212.183.159.229:80->86.160.218.216:61063 on ppp1)
16:48:15, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
16:48:11, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:48:11, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 212.183.159.229:80->86.160.218.216:61061 on ppp1)
16:48:08, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 77.72.118.160:80->86.160.218.216:61032 on ppp1)
16:48:08, 01 Dec.BLOCKED 6 more packets (because of Packet invalid in connection)
16:48:07, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 77.72.118.160:80->86.160.218.216:61031 on ppp1)
16:48:07, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:48:07, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 213.165.64.202:80->86.160.218.216:61005 on ppp1)
16:48:02, 01 Dec.BLOCKED 6 more packets (because of Packet invalid in connection)
16:48:01, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 195.20.250.231:80->86.160.218.216:61035 on ppp1)
16:48:01, 01 Dec.BLOCKED 6 more packets (because of Packet invalid in connection)
16:48:01, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 213.165.64.202:80->86.160.218.216:61005 on ppp1)
16:47:59, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:47:59, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 213.165.65.109:80->86.160.218.216:61010 on ppp1)
16:46:52, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 174.133.95.85:80->86.160.218.216:60892 on ppp1)
16:46:41, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:46:01, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
16:44:35, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:44:07, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
16:42:27, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:41:58, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
16:41:04, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:41:03, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:41:02, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60664 on ppp1)
16:40:58, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:40:57, 01 Dec.BLOCKED 3 more packets (because of Packet invalid in connection)
16:40:57, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60663 on ppp1)
16:40:44, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 91.198.174.233:80->86.160.218.216:60647 on ppp1)
16:40:43, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:40:42, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 91.198.174.233:80->86.160.218.216:60636 on ppp1)
16:40:41, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:40:40, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 91.198.174.233:80->86.160.218.216:60636 on ppp1)
16:40:40, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:40:40, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 91.198.174.233:80->86.160.218.216:60637 on ppp1)
16:40:26, 01 Dec.BLOCKED 2 more packets (because of Packet invalid in connection)
16:40:26, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60565 on ppp1)
16:40:22, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:40:21, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:40:20, 01 Dec.BLOCKED 3 more packets (because of Packet invalid in connection)
16:40:20, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60565 on ppp1)
16:40:11, 01 Dec.BLOCKED 1 more packets (because of Packet invalid in connection)
16:40:10, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60529 on ppp1)
16:40:09, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 87.248.106.141:80->86.160.218.216:60519 on ppp1)
16:40:07, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on eth1)
16:40:05, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60531 on ppp1)
16:40:04, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 188.125.66.215:80->86.160.218.216:60529 on ppp1)
16:40:02, 01 Dec.IN: BLOCK [9] Packet invalid in connection (TCP 87.248.106.141:80->86.160.218.216:60519 on ppp1)
16:38:54, 01 Dec.(55177.960000) Device disconnected: Hostname: sue-PC IP: 192.168.1.67 MAC: e0:69:95:9f:32:e8
16:38:19, 01 Dec.IN: BLOCK [12] Spoofing protection (IGMP 86.160.218.216->224.0.0.22 on ppp1)
16:37:56, 01 Dec.

IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.

 

 

 

pages and pages

0 Ratings
Highlighted
Contributor
1,138 Views
Message 46 of 87

Re: Strange items in log since HH3A update

Seems my Homehub is reporting the same as the OP causing websites to hang and the homehub will randomly reboot.

 

Thought it was a PC issue since I just build a new one.

0 Ratings
Highlighted
Aspiring Expert
1,134 Views
Message 47 of 87

Re: Strange items in log since HH3A update

Looks like a bug in the upgrade

0 Ratings
Highlighted
Beginner
1,117 Views
Message 48 of 87

Re: Strange items in log since HH3A update

Hi

 

I'm getting these entries in the log also, and I have spotted a huge problem also.

I have my own webserver, which uses NoIP to update the External IP address, everything was going great until last night when the update happened and now my webserver isn't visible at all outside my LAN and it all points to this stupid frickin update!

 

I am going to go mental at BT on monday morning!!!

 

 

0 Ratings
Highlighted
Beginner
1,083 Views
Message 49 of 87

Re: Strange items in log since HH3A update

I called BT today, told them I'd run all sorts of tests but nothing had changed in my setup, it appears that the update actually happened on the 25th november, anyway they're sending me out a new router!! I would like to know from anyone who can provide an answer, will the new router be exactly the same? will it update and stop anyone seeing my webserver again?

What other routers could I buy to allow me to stop using the BT HH3 instead.

Thanks
0 Ratings
Highlighted
Distinguished Sage
Distinguished Sage
1,067 Views
Message 50 of 87

Re: Strange items in log since HH3A update


@christiansacks wrote:


What other routers could I buy to allow me to stop using the BT HH3 instead.

Thanks

There is a small list here.

Replacements for BT home hub 3

0 Ratings