Root Access

12:39 AM

>

I once renamed shutdown.exe from the Windows resource kit to DONOTRUN.exe, and sent it in a mail round to the company (in the I love you/Melissa days), warning people in the subject, and message to NOT RUN THE ATTACHED attachment.

People then started coming to me complaining they'd lost work because their computer had shutdown.

It's amazing, it really is.

Psycogeek

1:16 AM

That was real nice of him, does he put blankets over manholes with $10 bills in them to also test human behaviour :-)

I think for his next experiment i suggest he stand in the middle of the freeway, and see if people will stop for him .

Psycogeek

1:43 AM

(We all know what most people would do, but in the spirit of proper testing he should stand firm)

Journeyman Geek

theverge.com/2015/1/13/7537367/pc-market-growth-likely-in-2015 heh. The same folks were screaming that the PC was dead till last quarter.

Bob

@JourneymanGeek "Everything is fine, carry on" doesn't sell

They are more likely to die than the PC.

HackToHell

@CanadianLuke Err, I sorta slept

Journeyman Geek

@Bob Yup.

HackToHell

1:58 AM

@CanadianLuke The email id in the email field is real freelancing.stackexchange.com/users/605/hacktohell

Psycogeek

@JourneymanGeek does this mean we can look foreward to huge desktop advancements, and that not "everything" is all about portables/mobile?

Tom Wijsman

2:36 AM

@WilliamHilsum: Are you here?

William Hilsum

BLOODY HELL! First notification in ages... scared the life out of me!

and yeah, here

Tom Wijsman

(Or anyone with sufficient network and more specifically NIC knowledge)

@WilliamHilsum: Okay, I've been having some weird high ping problems.

William Hilsum

and, as it is you... I can skip over the basic troubleshooting! :)

ok...

Tom Wijsman

Could it be that the Raspberry Pi interface (being 100 instead of giga) slows my network down?

William Hilsum

only if you have a really terrible switch...

Tom Wijsman

2:38 AM

@WilliamHilsum: WRT610N with DD-WRT firmware.

William Hilsum

some really really old ones operate at the lowest speed... I think it was some really cheap old ones based off of a cheap chinese copy of a atheros chipset... haven't seen it for many years

... dd-wrt enabled devices shouldn't

sorry, but, have you done the basic thing of doing a constant ping, unplug the pi, then plug it back in and see if it changes anything?

Tom Wijsman

'cause I was playing a game with 100+ latency, the moment I pulled cable it dropped to 40. Of course that's one attempt, need to see if lag returns and/or pulling cable helps.

@WilliamHilsum Broadcom.

@WilliamHilsum Can't test it at this moment, let me explain the setup a bit more clearly:

1. Laptop connected to WiFi that experiences the trouble.

William Hilsum

I would say, could be a mini broadcast storm or similar... seen a few issues in houses with students/more than 5 people that have tonnes of modern devices... sonos, apple tv, media streamers, home plugs... then all running btsync.dropbox and more... all broadcasting and conflicting...

Tom Wijsman

2. Raspberry Pi connected through Ethernet.

3. Computer connected through Ethernet.

William Hilsum

ok

Tom Wijsman

2:41 AM

It only happens when two computers are connected through ethernet.

But yeah, I can try the constant ping thing.

@WilliamHilsum When I debugged a while ago, I saw LLC packets in Wireshark and perhaps 1 or 2 other unusual ones.

William Hilsum

something that may sound silly, but hear me out... can you see if you can get a block diagram up of your router/chipset, or just try a different port - rare, but, something else I have seen when I did all the router testing at the ISP is that the bridge of the wireless may be going in to a bridge interface that is hard connected to a single port...

sorry, retyped that a few times, I can't get the words out :/

Tom Wijsman

@WilliamHilsum: I think there are at least pictures of the electronics, might look into that.

William Hilsum

so... if you imagine you have a router:

eth0 - wan
eth1-6 - lan
wlan0 - wlan

br0 is made up of eth1-6 +wlan0 virtually, but, depending on the chipset involved, wlan0 may go straight in to eth1 and share the bandwidth

Tom Wijsman

@WilliamHilsum: Does that mean that if the port is slow the WiFi would suffer from it?

William Hilsum

it could be... but, I am making a lot of guessing and assumptions

Tom Wijsman

2:45 AM

Ok, so 1) ping test, 2) packet capture and 3) try swapping cables around.

I'll leave the RPi disconnected for as long as I don't need it.

William Hilsum

its worth a try... and, could always be good old interference!

Tom Wijsman

Which reveals if it happens in RPi-less situations too...

William Hilsum

I can't quickly find something that demonstrates wireless... but, here is an example of a router schematic : i.mt.lv/routerboard/files/Block-RB1100AHx2.pdf

you can see where bandwidth is shared - e.g. if you maxed out eth6 to eth1 whilst doing eth7 to eth2, they would each split the bandwidth as there are actually 2 switches between a cpu...

that is technically why, low end routers have one switching chip for everything and the higher end ones have one switching chip per port... and where the price differences come in!

here is the only one I can find for wireless - i.mt.lv/routerboard/files/Block-RB2011UAS-2HnD.pdf - just imagine the wireless chip going straight in to the switch...

I hope that makes sense? :/

Tom Wijsman

Yeah, not sure if I can find that for this device.

@WilliamHilsum: Scrolling down till u get images on infodepot.wikia.com/wiki/Linksys_WRT610N_v2.0 shows the electronic board.

I have the v1 tho, so rather infodepot.wikia.com/wiki/Linksys_WRT610N_v1.0

@WilliamHilsum: If I understand correctly, we need information about what's underneath that heatsink, right?

Not sure if that's available...

William Hilsum

@TomWijsman its more complicated than that... when I say schematic, I mean more of a block diagram like how I showed you in the links... just far too hard to examine a pre built board without a lot of time and patience!

It says which chip it is in the description...

but you can see all the lan ports (and wan port) going to that heatsink

just can't easily make out where the two wireless chips go

That Brazilian Guy

3:00 AM

Eusjwidhavwhsidusvw

William Hilsum

@TomWijsman hmm... looking at the underside, I am tempted to say that the two wireless ones go straight in to the main chip (most likely cpu) whilst the switch ones go in to the other chip...

so, most likely not a port bandwidth issue

but... hard to tell

Tom Wijsman

Yeah, I'll resort to further diagnostics when it happens again.

@WilliamHilsum: On Linux this manifested itself as bugzilla.kernel.org/show_bug.cgi?id=56581

the interesting part being git.kernel.org/cgit/linux/kernel/git/iwlwifi/iwlwifi-fixes.git/…

but I'm not using Linux anymore.

And this might just be a side effect of the actual trouble, because others sometimes experience it too.

/me happens to have the oldest WiFi network adapter.

William Hilsum

so much to read through :/

skim read first one... you aren't roaming though?

Tom Wijsman

@WilliamHilsum Not sure how to check, but roaming aggressiveness is set to the default Medium.

William Hilsum

Right now, if I was you, I would treat this as standard bad wireless and rule out the pi (sorry for taking so long on that - it was just a guess)... I recommend you try phones/other devices and just move around and test general speed/stability

just ping your router constantly... rule out other devices

and, even try changing the channel... you may be surprised :/

Tom Wijsman

3:18 AM

Okay, that's a fourth thing I can try; thanks.

William Hilsum

sorry i couldn't be exact... wireless issues are horrible, but, I hope this put you on the right track... let me know if you need anything else

I'm going to sleep now! Goodnight!

Tom Wijsman

Reply from 10.0.0.1: bytes=32 time=8ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=8ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=10ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=148ms TTL=64
Reply from 10.0.0.1: bytes=32 time=145ms TTL=64

@WilliamHilsum The above happens when turning on my television, which some meters from router.

William Hilsum

goes from 7/8 up to that?

can you make sure/turn it off and see it drop?

Tom Wijsman

Yeah.

Well, it drops after a few seconds.

William Hilsum

smart tv?

Tom Wijsman

3:22 AM

WiFi, smart TV yes.

William Hilsum

try disabling the wireless in it and see... just to make sure it is the wireless feature and not emi interference...

then, on your router, try doing a packet capture or similar... maybe it is bad firmware, trying to do many outbound connections/check for updates or similar

...does it continually do that until it is turned off or just for a few minutes when you turn it on?

Tom Wijsman

@WilliamHilsum The moment it says "Logged on as ..." on the TV (when it talks) it does 10 secs of high ping.

@WilliamHilsum Not seeing the 10 secs of high ping with wireless disabled.

William Hilsum

see if the tv has a firmware update available or if anyone else is reporting it

and damn... got wireless issues of my own! :(

Tom Wijsman

It's up-to-date, but I'm pretty sure TV is not the only cause.

William Hilsum

need to go to bed, but, want to complete this! hard choice!!!

Tom Wijsman

3:26 AM

Anyhow ... got me a device I can further test with. \o/

Probably should check it with my phone, a bit more energy efficient than having a TV turn on/off/on/off.

@WilliamHilsum: Thanks.

William Hilsum

@TomWijsman haha

oh ffs... far too tired for this... wondering why my dns change wasn't kicking in... would help if I actually loaded the modified zone and increased the version counter :(

I missed having a chat room to vent in! :P I'll have to stay around more often again!

Tom Wijsman

@WilliamHilsum Well, N-only 5GHz seems to not have this 100+ms ping issue.

So, yeah, low power antenna / congestion / ... something like that.

Looks like I don't have to complain about that either.

There were other problems regarding having both a 2.4Ghz and 5Ghz network which is why it has been 2.4Ghz for a long while; not sure about the details, but I'll hear soon enough.