If by Hex, you mean hexadecimal conversion to binary and/or decimal, I already know that..

if you mean they're adding more octets to the IP address format- (Which I hope not), then I don't know that!

We're currently dabbling in VoIP right now.

Truthfully, I don't see the benefit... The PSTN Infrastructure is in place, paid for, and LD service is so cheap now- it's ridiculous...

 

Current IP: 32-bit addresses.

IP v6: 128-bit addresses. Enough room to give every electronic gadget it's own IP address and web-enable it.

 

Hey dzervit -

I work with technology for the DoD and they have the IPv6 "mandate" in all their RFPs. It is stated that IPv6 is mandatory for all network devices as of January 1, 2007.

I have also seen quite a few major retailers that have similar mandates within their IT infrastructure.

That being said, what is the main difference between current IP technology and IPv6 ?

Just a condensed answer would be nice.

Thanks !!!

 

Jeeezuz H. Kriest.

I could just hear a person on teh phone trying to give the HSI tech their IP address to call in a trouble.

Yeah, my ip address is, 192.48.56.104.99.27.66.19.66.67.68.77.92.101.207.1 83

And your Subnet?
255.255.255.255.255.255.255.255.255.255.255.255.25 5.255.255.000

What's your MAC address?

Dang, I'm sorry- could you repat your IP for me again?

 

cia - like it was said, due to the increase in address space it's gonna be Hex to try to simplify things.

And many devices have been IPv6 ready for years and years, but still nobody's using it.

 

Ah, OK- that makes sense then...

It's still gonna be long though.

 

Ahhh....IPX and arcnet....what fun....

I'll be sad to see the little octets go....

 

I miss my old self-diagnosing token-ring lans...

 

token ring....never worked with it...but sure did look interesting in print.

 

token ring

Isnt that just a bunch of PCs with a peer to peer connection?

 

I'm sure Dzervit is madly typing away a detailed explanation but token ring is the topology/protocol for the lan where as p2p refers to more how the network shares its resources.

Server/Clients (domains, etc)

p2p every client is essential equal and no central control.

Token ring describes the method of transmitting the data, with a token.

 

I can go all teh way back to X.25 packet switching...

When all the troubleshooting we did on that thing was- if it stops working, power cycle it.

 

All the way back...I still have one in use!

Smoking speed....and you are right about troubleshooting...

"Oh it's down? Turn it off and back on"

We use it for a connection for an old properietary software package my company uses. Worst part is it is still considered mission cricitcal software.

 

I haven't had much time to get back to this, but I sure do appreciate all of your responses.

First... I'll try to make this brief, so that I don't bore you, but I think it's relative.

I am a communications guy, I started out in the USAF doing Telephone, Fiber, Network Cabling...etc..etc. Basically I was a cable guy (kbldawg).

I got a job out of the service with a small Mom and Pop computer store. They needed someone to install Cat5 and Fiber, but since they don't have enough of that stuff, I also learned to work on computers. Just basic stuff at first, then I moved into more advanced troubleshooting and repair.

I can setup a simple windows network, map drives..etc, just simple stuff. I have played with Linux a few times, but never really got serious about it.

Which brings us to the root of my question...

The boss tells me one day he wants to sale wireless internet. Be a WISP, sure sounds cool. I can do that, right? Well...sure, I have read a lot of books, subscribed to a few wireless lists.

Well, almost a year later, we have 3 towers, running linux based APs (StarOS). Our Internet Admin (BSD Guy) setup the routing and all the IP stuff on our APs, but I need to be able to do this as well. He's one of those guys that doesn't want you knowing what he knows and is just an @ss, so...asking him these questions isn't going to happen.

I pretty much do everything that has to be done, except the routing and IP stuff. I haven't been in this long enough to know what I'm doing with that.

Currently each AP is setup on it's own subnet. We setup private IPs on the customers wireless bridge, and give their router/pc public IPs. The routing and all that has been done on the APs already. But we are still building our infrastructure and new routers, APs...etc are still going up. I would like to be able to figure this stuff out, so I don't have to depend on him.

Now, another question...

Let's say I have a total of 4 Access Points before the customer.

AP1 - connected to our backbone
AP2 - connected to AP1, and also a POP for wireless clients.
AP3 - connected to AP2, and also a POP for wireless clients.
AP4 - connected to AP3, and also a POP for wireless clients.

Each AP is on it's own subnet. So in order for all of these different subnets to communicate they all have to have a static route(?) setup pointing all the way back to AP1, correct?

Thanks for the info!

edit
oh and I suppose they would also need another route to connect the private IPs (on the client side) to that APs public subnet?

 

Your APs only need one route - a default route to the internet. The internet-facing router only needs 4 routes - one static route for each AP's subnet. I'm assuming all clients connected to each AP are on the same subnet, so routing isn't an issue since the AP sees them all as direct connects.

Sounds like a brain-dead simple layout with huge security issues. I'm betting anyone on your wireless plan can check out other customers networks, since their all on the same subnet w/ private address scheme. Granted each customer should have some firewall in place, but I'm sure they don't and it's a hacks playground!