This story will be a turning point for my blog future starting with a change in writing methods and changing those methods to a more causal fashion.
For now all my text here where somehow depersonalized and tech oriented in a way that it was all written like in some book. User manual to me concise. Maybe this is the main reason that now when I got back to revise some parts of the texts there was an impression that those text are very boring. There is something missing inside them, maybe me?
Of course, I didn’t start to write this blog two years ago because there was a huge need for someone new to write about old networking stories about protocols and networking standards. I did start to write because I was young enthusiastic freshy networker who was in his all day job searching, part-time Cisco teaching and CCNP studying period.
That was actually not job free time for me, but it was intense and fulfilling time. Having some experience with web before and now spending whole days with my head inside Cisco Press books it was somehow natural to start a blog. Yes I know, everybody wants to write something on the web, but that is the main reason for this post, I you wondered what is this all about. I can now finally say that if I did not give up writing this blog until now then it’s the real proof that there is actually somebody reading it and that I can finally consider myself a networking blogger but more that all an networking geek. Jup, that’s right, there are people who are not ashamed of being geeky technicians.
Reading more and more about different networking technologies I did find a lot of high quality blogs out there. From my point of view the best are those where the people are saying what they mean in a casual way without using to much of strict english words but more funny comparisons and real-life examples. For now packetpushers.com would be one of the best place to start with amazing and great networking connoisseurs as podcast guests. A place to be for networking geek techie in search for interesting topic. There are more others that are also worth of mentioning but it will make one day a link list somewhere around this blog for sure. What I wanted to say here is that being funny and giving more personality into this place can surely help to rise this internet place and make it a better place for networkers out there looking for explanations. One of those explanations/suggestion is in this article after all this chatting to myself stuff…
THE OUTCOME – THE REAL ARTICLE FROM THE SUBJECT
The outcome is simple, If you have 192.168.1.0/24 subnet in your work network and you have people connecting to your network using VPN from outside the headquarters you will have issues with those using MAC OS X, iPad and iPhone device. If your staff uses local WiFi or cable LAN network with this same subnet 192.168.0.0/24 for connecting with VPN to the office, they will experience routing problems as they are trying to communicate across VPN tunnel between two different sites but between same subnet (from 192.168.1.0 to 192.168.1.0) and VPN will go crazy as it will not know what to send across the tunnel to outer side and what not. It will result simply unreachable issue for remote site IPs.
192.168.1.0/24 it will normally be on most home and small private networks because vendors usually put this DHCP pool onto SOHO APs. It’s a routing issue that is resolved in Windows OS but for Apple products and their OS for now there is only some solution with adding some kinds of routes on the Apple computer every time the connection is established but with iPad and iPhone you will not be able to use command prompt to do so and those users will stay without the mobile access across the VPN to headquarters because of “lame” network design.
If you used let’s say 10.8.8.0/24 for work subnet there would not be problems like that. Think like this, how big is the chance that someone who is connecting from home to the office has 10.8.8.0/24 subnet in his home network? Or in beer pub WiFi network?