FiOS: pros and cons?

[Skuzzy]

Originally posted by Puck
Ohhh...that's a pity.  Why?

PPPoE sucks.  More prone to problems due to router/terminal server overhead for the encapsualtion and decapsulation of the data packet.

Absolutely no benefit to the user.  The only benefit is to the ISP who wants to control the connection, but is too lazy to deal with a non-PPPoE connection.

[Puck]

Originally posted by Skuzzy
PPPoE sucks.  More prone to problems due to router/terminal server overhead for the encapsualtion and decapsulation of the data packet.

Absolutely no benefit to the user.  The only benefit is to the ISP who wants to control the connection, but is too lazy to deal with a non-PPPoE connection.

Yes, yes, yes, and yes.  Why?

I thought PPoE was banned by recent Geneva conventions as cruel and unusual punishment.  They might as well frame it Fibre and make it completely, rather than mostly, useless.

Ohhhh...I just had an evil thought.  Advertise the native speed of the fiber, run it PPoE to choke it down, and make them pay for fiber speeds...

[Skuzzy]

It's nmot like they need to throttle it down any further.  They already handicap the poop out of the connection by supplying the cheapest DLink router they could get.

Sheesh.  I could hand encode data faster than that router does it.

You have to give them credit though.  They own all the fiber they are placing in the ground, outright.  The government cannot force them to share it with anyone, unless the government wants to buy it all from Verizon.

In the long run, Verizon is going to own/control a vaste portion of the data distribution network in this country.

[Puck]

I just got this rather vivid visual of a vi session full of 1s and 0s with the IP and TCP headers in templates and the data packet built with a binary ASCII chart.

Would that cause lag in the main arena?



  What's the ASCII code for a 37mm HE round?

 

[Skuzzy]

Nah, use vi to create the templates, then use sed to fill them on the fly and route it to the open fd, making sure to configure the fd with proper stty parameters.  One for reading, one for writing.

Could toss in some rudimentary header checks and timers.  

Bingo, a DLink router, only faster.

[Puck]

That's not encoding by hand then, is it?  If you're using sed you might as well be using perl.  Perl leads to C, C leads to .NET, .NET leads to suffering...



NOT a DLink router.  [Your method] would work.

[fuzeman]

Man I need a translator.

[Puck]

Sorry.  That was a total hijack; my apologies, but you will land this thread in Cuba or I start shorting out bits.

[fuzeman]

I don't consider it a hijack and I started the darn thing.
I'm glad you asked because I had no idea what PPPoE was and was embarrassed to show my ingorance.

I got alot of that to show too, believe me.

[Skuzzy]

Originally posted by Puck
That's not encoding by hand then, is it?  If you're using sed you might as well be using perl.  Perl leads to C, C leads to .NET, .NET leads to suffering...



NOT a DLink router.  [Your method] would work.

Hehe.  Man, that was a leap Puck.  From C to .NET?  ROFL!  I dunt(tm) do Perl anyway.  I went straight from shell programming, to assembly, to C.  .NET is an abomination.  People who use it are not programmers.  Applications which use it (I cannot bring myself to say, "written to use it".  You are not writting anything.  You are being lead about the nose by MS) are the worst things to happen to the computer.

We did sort of hijack this thread.  Sorry fuzeman.  Happens when a couple of UNIX pukes get together.  If you think it is bad on a forum, you should see what happens if they meet at a Starbuck's!

[fuzeman]

Makes me feel worse. I used to know Unix when TRW trained me on Altos computers.
I still need a translator.

[Puck]

It's easy to forget.  I STARTED on bitnet and VAX/PDP/11s.  Can't remember DCL at all, and would probably be lost on a VAX command line.

CMS...well...I used electroshock therapy to FORGET that one...