Routers & Other Networking Stuff

Cad

Cad

<Bronze Donator>
24,487
45,378
a_skeleton_03 said:
I wire absolutely everything that isn't a laptop or a handheld device without a jack.

I put one drop at each location and a 5 port switch there.
Click to expand...

Well yea I was questioning the 4 drops to each location thing...

Going to end up with an 80 port switch in the garage for a 3 bedroom house...
 
Flipmode

Flipmode

EQOA Refugee
2,090
311
Cad said:
Well yea I was questioning the 4 drops to each location thing...

Going to end up with an 80 port switch in the garage for a 3 bedroom house...
Click to expand...

Nah not that bad lol. Won't need more than a 24 port switch at max. I'm just trying to plan ahead for more than I need in case my needs increase. That's all. I've been told the cost increase is minimal for the increased drops up to a point.
 
Crone

Crone

Bronze Baronet of the Realm
9,707
3,210
Cad said:
Yea you could use them all, but why separate cables for each? If you're paying for them to run wire I guess 4 isn't much more expensive than 1, but it's not like xbox uses gigabit bandwidth ever so sharing a port would hurt them somehow...
Click to expand...
Then you have multiple devices with the same ip and you open up a can of worms trouble shooting network problems down the line.

4 seemed like a lot to me as well but I don't use to apps on my tv, and only have a ps4 that's just on wireless, but after he said a few of his use cases it made more sense.

Edit: should have read further replies. Yea, 1 drop and a switch at each location is way nicer!
 
Crone

Crone

Bronze Baronet of the Realm
9,707
3,210
Big_w_powah said:
Umm, how? You know that DHCP assigns IPs to the nic, right?
Click to expand...
Don't mind me, I had it in my head incorrectly that it would cause issues with your public IP address, which ISPs only give you 1 of, and it would cause issues. Except of course it won't, because DHCP will do it's job, and then it will just NAT it out for whatever. Derp derp. My bad.
 
  • 1Like
Reactions: 1 user
Big_w_powah

Big_w_powah

Trakanon Raider
1,887
750
Crone said:
Don't mind me, I had it in my head incorrectly that it would cause issues with your public IP address, which ISPs only give you 1 of, and it would cause issues. Except of course it won't, because DHCP will do it's job, and then it will just NAT it out for whatever. Derp derp. My bad.
Click to expand...

Oh, well, your forgiven.
 
P

Picasso3

Silver Baronet of the Realm
11,333
5,322
Hardwired basement w/ switch, moved nighthawk to garage, d-link unhooked. Seems to be fine and good reception on wifi still. It is a bummer the leviton wall box it's in is metal, so when i put the cover on i can see it shitting up wifi a bit.

I did realize the house has all the phones wired with cat 5e as well so if i start nerding out of control i'll be able to convert those to ethernet.
 
P

Picasso3

Silver Baronet of the Realm
11,333
5,322
I assume it'll be patched pretty soon which I'll install. I'm wondering if they can get my dick pic collection off pc or just fuck with the router itself and if a lowly cretin like me would even be a target.
 
Brikker

Brikker

Trump's Staff
6,087
4,402
Any of you IT guys good with networking? I want to figure out what these retarded Africans did to the internet 5 days ago that makes WoW unplayable (and other sites shitty too). Used the battle.net diagnostic tool and got the following traceroute/ping:
TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.726 ms 0.766 ms 0.856 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.710 ms 8.740 ms 8.758 ms
4 37.244.0.34 (37.244.0.34) 2.574 ms 2.618 ms 2.741 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.623 ms 37.643 ms 37.699 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.771 ms 37.570 ms 37.552 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.300 ms 37.443 ms 37.446 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.495 ms 37.309 ms 37.302 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.050 ms 37.175 ms 37.158 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.667 ms 153.071 ms 153.055 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.923 ms 152.936 ms 152.837 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.948 ms 152.844 ms 152.422 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.707 ms 152.723 ms 152.894 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.834 ms 152.705 ms 152.582 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.627 ms 152.666 ms 152.884 ms


14/12/2016 05:52:45 UTC
--------------------

TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.398 ms 0.455 ms 0.495 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.244 ms 8.260 ms 8.302 ms
4 37.244.0.34 (37.244.0.34) 3.072 ms 4.482 ms 4.501 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.384 ms 37.409 ms 38.752 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.698 ms 38.759 ms 38.753 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.166 ms 37.231 ms 37.317 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.596 ms 37.657 ms 37.661 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.084 ms 37.065 ms 37.072 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.881 ms 152.840 ms 152.905 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.756 ms 152.806 ms 152.764 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.706 ms 152.467 ms 152.357 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.516 ms 152.530 ms 152.719 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.806 ms 152.649 ms 152.532 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.470 ms 152.564 ms 152.535 ms


14/12/2016 05:52:45 UTC
--------------------

PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.

--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms


14/12/2016 05:52:45 UTC
--------------------

PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.

--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms


14/12/2016 05:52:50 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.3 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 3.1 4.9 2.9 8.3 1.9
4. 37.244.0.34 0.0% 10 2.8 3.3 2.6 6.3 1.2
5. te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 37.4 37.4 37.2 37.5 0.1
6. be3032.ccr21.lax01.atlas.cogentco.com 0.0% 10 37.8 37.7 37.3 38.3 0.3
7. be2931.ccr21.phx02.atlas.cogentco.com 0.0% 10 37.9 37.5 37.1 37.9 0.2
8. be2929.ccr21.elp01.atlas.cogentco.com 0.0% 10 37.5 37.5 37.2 37.7 0.2
9. be2927.ccr41.iah01.atlas.cogentco.com 0.0% 10 37.2 37.1 36.9 37.3 0.1
10. be2687.ccr41.atl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.6 153.2 0.2
11. be2112.ccr41.dca01.atlas.cogentco.com 0.0% 10 152.8 153.1 152.7 154.3 0.6
12. be2806.ccr41.jfk02.atlas.cogentco.com 0.0% 10 152.6 152.7 152.5 153.0 0.2
13. be2915.ccr21.alb02.atlas.cogentco.com 0.0% 10 152.8 152.9 152.7 153.4 0.2
14. be2088.ccr21.ymq01.atlas.cogentco.com 0.0% 10 152.8 152.8 152.7 152.8 0.0
15. be3042.ccr21.lpl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.7 153.3 0.2
16. be2391.ccr41.lon13.atlas.cogentco.com 0.0% 10 153.0 153.2 153.0 153.3 0.1
17. be12497.ccr41.par01.atlas.cogentco.com 0.0% 10 152.4 152.5 152.3 152.8 0.2
18. be3092.ccr21.mrs01.atlas.cogentco.com 0.0% 10 164.0 163.9 163.8 164.0 0.1
19. be2345.agr21.mrs01.atlas.cogentco.com 0.0% 10 164.3 164.3 164.1 164.5 0.1
20. djibouti-telecom.demarc.cogentco.com 0.0% 10 224.2 226.3 224.2 232.2 2.2
21. 41.189.226.149 0.0% 10 225.8 226.0 225.6 226.5 0.3
22. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23. 41.189.226.254 0.0% 10 224.9 225.0 224.5 225.5 0.3
24. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25. 41.189.226.254 10.0% 10 225.7 225.4 224.7 225.9 0.4
26. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27. 41.189.226.254 10.0% 10 226.1 225.5 225.0 226.2 0.5
28. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29. 41.189.226.254 10.0% 10 226.3 225.9 225.4 226.3 0.3
30. ??? 100.0 9 0.0 0.0 0.0 0.0 0.0

--------------------


I don't know how to read any of this shit; is anything on there obviously out of the ordinary? Game played fine with a 200-300 average ping for 5.5 months, then they do a "service update" and I can't play. Log in, sometimes it's okay for about 15 minutes, sometimes it is just instant lag (usually shows normal ping but it's actually in the 4000-5000 range) and can't do a thing. Eventually boots me.

Netflix has also gotten much worse; used to stream 720p np but now it struggles even loading and when it does it's very low quality.

*Note that this is internet on a deployed military base in Africa.
 
S

SaucyJake

Golden Knight of the Realm
1
2
Brikker said:
Any of you IT guys good with networking? I want to figure out what these retarded Africans did to the internet 5 days ago that makes WoW unplayable (and other sites shitty too). Used the battle.net diagnostic tool and got the following traceroute/ping:
TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.726 ms 0.766 ms 0.856 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.710 ms 8.740 ms 8.758 ms
4 37.244.0.34 (37.244.0.34) 2.574 ms 2.618 ms 2.741 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.623 ms 37.643 ms 37.699 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.771 ms 37.570 ms 37.552 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.300 ms 37.443 ms 37.446 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.495 ms 37.309 ms 37.302 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.050 ms 37.175 ms 37.158 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.667 ms 153.071 ms 153.055 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.923 ms 152.936 ms 152.837 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.948 ms 152.844 ms 152.422 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.707 ms 152.723 ms 152.894 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.834 ms 152.705 ms 152.582 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.627 ms 152.666 ms 152.884 ms


14/12/2016 05:52:45 UTC
--------------------

TRACEROUTE:
traceroute to 41.189.243.1 (41.189.243.1), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.398 ms 0.455 ms 0.495 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 8.244 ms 8.260 ms 8.302 ms
4 37.244.0.34 (37.244.0.34) 3.072 ms 4.482 ms 4.501 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.384 ms 37.409 ms 38.752 ms
6 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 37.698 ms 38.759 ms 38.753 ms
7 be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 37.166 ms 37.231 ms 37.317 ms
8 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 37.596 ms 37.657 ms 37.661 ms
9 be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 37.084 ms 37.065 ms 37.072 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 152.881 ms 152.840 ms 152.905 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 152.756 ms 152.806 ms 152.764 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 152.706 ms 152.467 ms 152.357 ms
13 be2915.ccr21.alb02.atlas.cogentco.com (154.54.40.61) 152.516 ms 152.530 ms 152.719 ms
14 be2088.ccr21.ymq01.atlas.cogentco.com (154.54.43.17) 152.806 ms 152.649 ms 152.532 ms
15 be3042.ccr21.lpl01.atlas.cogentco.com (154.54.44.161) 152.470 ms 152.564 ms 152.535 ms


14/12/2016 05:52:45 UTC
--------------------

PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.

--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms


14/12/2016 05:52:45 UTC
--------------------

PING:
PING 41.189.243.1 (41.189.243.1) 56(84) bytes of data.

--- 41.189.243.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms


14/12/2016 05:52:50 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.3 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 3.1 4.9 2.9 8.3 1.9
4. 37.244.0.34 0.0% 10 2.8 3.3 2.6 6.3 1.2
5. te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 37.4 37.4 37.2 37.5 0.1
6. be3032.ccr21.lax01.atlas.cogentco.com 0.0% 10 37.8 37.7 37.3 38.3 0.3
7. be2931.ccr21.phx02.atlas.cogentco.com 0.0% 10 37.9 37.5 37.1 37.9 0.2
8. be2929.ccr21.elp01.atlas.cogentco.com 0.0% 10 37.5 37.5 37.2 37.7 0.2
9. be2927.ccr41.iah01.atlas.cogentco.com 0.0% 10 37.2 37.1 36.9 37.3 0.1
10. be2687.ccr41.atl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.6 153.2 0.2
11. be2112.ccr41.dca01.atlas.cogentco.com 0.0% 10 152.8 153.1 152.7 154.3 0.6
12. be2806.ccr41.jfk02.atlas.cogentco.com 0.0% 10 152.6 152.7 152.5 153.0 0.2
13. be2915.ccr21.alb02.atlas.cogentco.com 0.0% 10 152.8 152.9 152.7 153.4 0.2
14. be2088.ccr21.ymq01.atlas.cogentco.com 0.0% 10 152.8 152.8 152.7 152.8 0.0
15. be3042.ccr21.lpl01.atlas.cogentco.com 0.0% 10 152.7 152.8 152.7 153.3 0.2
16. be2391.ccr41.lon13.atlas.cogentco.com 0.0% 10 153.0 153.2 153.0 153.3 0.1
17. be12497.ccr41.par01.atlas.cogentco.com 0.0% 10 152.4 152.5 152.3 152.8 0.2
18. be3092.ccr21.mrs01.atlas.cogentco.com 0.0% 10 164.0 163.9 163.8 164.0 0.1
19. be2345.agr21.mrs01.atlas.cogentco.com 0.0% 10 164.3 164.3 164.1 164.5 0.1
20. djibouti-telecom.demarc.cogentco.com 0.0% 10 224.2 226.3 224.2 232.2 2.2
21. 41.189.226.149 0.0% 10 225.8 226.0 225.6 226.5 0.3
22. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23. 41.189.226.254 0.0% 10 224.9 225.0 224.5 225.5 0.3
24. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25. 41.189.226.254 10.0% 10 225.7 225.4 224.7 225.9 0.4
26. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27. 41.189.226.254 10.0% 10 226.1 225.5 225.0 226.2 0.5
28. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29. 41.189.226.254 10.0% 10 226.3 225.9 225.4 226.3 0.3
30. ??? 100.0 9 0.0 0.0 0.0 0.0 0.0

--------------------


I don't know how to read any of this shit; is anything on there obviously out of the ordinary? Game played fine with a 200-300 average ping for 5.5 months, then they do a "service update" and I can't play. Log in, sometimes it's okay for about 15 minutes, sometimes it is just instant lag (usually shows normal ping but it's actually in the 4000-5000 range) and can't do a thing. Eventually boots me.

Netflix has also gotten much worse; used to stream 720p np but now it struggles even loading and when it does it's very low quality.

*Note that this is internet on a deployed military base in Africa.
Click to expand...

Howdy...

It looks like something is having a problem past hop 21/22 (some kind of routing issue) :

20. djibouti-telecom.demarc.cogentco.com 0.0% 10 224.2 226.3 224.2 232.2 2.2
21. 41.189.226.149 0.0% 10 225.8 226.0 225.6 226.5 0.3
22. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23. 41.189.226.254 0.0% 10 224.9 225.0 224.5 225.5 0.3
24. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25. 41.189.226.254 10.0% 10 225.7 225.4 224.7 225.9 0.4
26. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27. 41.189.226.254 10.0% 10 226.1 225.5 225.0 226.2 0.5
28. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29. 41.189.226.254 10.0% 10 226.3 225.9 225.4 226.3 0.3
30. ??? 100.0 9 0.0 0.0 0.0 0.0 0.0

The ??? means nothing responded. Being that it keeps repeating 41.189.226.254 means the packet can't get past that point. Since hop 20 reads - djibouti-telecom.demarc.cogentco.com, that looks like the router where your network provider connects in with Congent (a large internet service provider). Since you are seeing issues with Netflix as well... I looks to me that Djibouti Telecom is the one with the problem. From a google search, Djibouti is a country in Africa, I guess its safe to assume that is who provides the internet service to your base.

The problem with this is... the issue is not with your PC/local network so there isn't much you can do about it directly. I would send that traceroute/mtr over to your IT department or whoever manages the relationship with your ISP. You can't be the only PC on the base with this issue.

Netflix has their own test site - Internet Speed Test | Fast.com but that is only a speed test. I would still run it just to see what you get. If the # is super low (not sure how fast your connection is), or if you receive some kind of error, that would be another data point to hand off to your IT staff.

I don't know how your IT staff is, but if possible, I would run these tests from another PC on your base (if you have access to one) and give both sets of data over to them. Most IT staff will blame your PC first (which is what I would do), so if you can start right off the bat with data from 2 different PC's, they won't waste time troubleshooting your PC. Make sure both of those PC's are not sharing the same "jack" (if its a wired connection and laptop, make sure you are not using the same port for both tests).

Sorry I couldn't be of more help.
 
  • 2Like
Reactions: 1 users
A

a_skeleton_06

<Banned>
1,923
2,410
Probably a baboon broke into the mpoe and stole the WRT-54 G that Djibouti is using to host the entire countries traffic.
 
  • 2Like
Reactions: 1 users
TrollfaceDeux

TrollfaceDeux

Pronouns: zie/zhem/zer
<Bronze Donator>
19,577
3,743
recently my router has been acting up (D815) and we just purchased a AC1750 which I assume is good for HD and other download stuff.
 
A

a_skeleton_06

<Banned>
1,923
2,410
That's a pretty decent router. Keep in mind that right now it's on the list of susceptible routers that have an exploit working against them.
 
You must log in or register to reply here.