Ronald Prettyman

Comcast recently upgraded the neighborhood to DOCSIS 3.0 quad bonded incoming. My current modem was well failing….I spilled a drink on it. So after a little research I found a modem for a 100 bucks at bestbuy and thought I’d give it a wirl.

Well I had to turn in my old modem before they would activate the new one but other then that it was pretty painless. However new modem has gigabit eithernet port on it and can scale to 160mbps, old one was the crap they gave out, looked it up and it was a low end DOCSIS 2.0 I was getting burst of up to 24mbps but averaged around 15, with 2-3mbps up. Hooked up the new one, did a quick speed test, 50mpbs down 2 up, tested it 10 different times 10 different sites, on each one it maxed out what ever their limit was, so i’m not entirely sure how fast its capable of, but its measuring at 50mbps. Pretty freaking impressive for a one time purchase, sure didn’t upgrade my plan so they could what, give my packets higher priority, i don’t exact live someone where bandwidth is in high demand, never had slow downs, sounds like marketing BS to me.

But still, if you have comcast, you can go to their site and check your area for DOCSIS 3.0, we got it here, won’t say where, but the only thing is, the down stream is not bonded, its just a single connection, upstream is a quad connection so its technically capable of 160mbps, when I get that 20Mbps download i’ll be sure to post a screen shot.

Comcast Docsis 3.0

Surfboard Extreme

If you decide to upgrade with this you can reach the status page via 192.168.100.1 as long as you don’t have a route rule for that subnet
Also the lights are speed sensitive, the lights are green for old school or nonbonded and blue for bonded, the ethernet port reflect gigabit-ethernet blue, or green for fast-ethernet

Firstly, and can’t stress this enough, is wins

I’m sure theirs a way to make dns work on a peer-to-peer network more effectively, maybe some reg edits here and their but on standard windows pc, which you can usualy assume, WINS, is going to be the best bet.

First set your samba server to be the master wins server, these options have worked best for me
#WINS SHIT
#Just cause i like a sure thing
os level = 99
# well this is needed
wins support = yes
name resolve order = wins lmhosts hosts bcast
domain master = yes
preferred master = yes
#Because I auth to a local ddns server with my dhdns proxy = yescp server
#the following helps with peer-to-peer traffic
dns proxy = yes
The above pretty much guarantees your be the WINS master server.

Now onto dhcp, because I just don’t like dicking with wins
option netbios-name-servers SAMBASERVERIP;
option netbios-node-type 8;

This will help increase the access time of your windows clients to your samba server, pretty much instant. \\hostname and bam, also speeds up windows – windows, network neighhood(network i guess is what its called now)

To increase the speed on the samba server even more I increase the buffer size and set some socket options
socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384