All Cisco visios you need download here..

Posted in Uncategorized on October 19, 2010 by itdaddy

Hey not much. I have been so busy finishing my college degree. I will grad this December 2010. I have 2 classes left.

So Sorry for not posting. Then it is back to CCNP, CCSP, CCVP in 3 years yes.




My Jobs Sucks – what do I do?

Posted in My Job Sucks on April 19, 2009 by itdaddy

Here’s the bottom line: You have to get a job, you have to go to work and someday, you’ll probably have to change jobs. “CAREER BUILDING: Your Total Handbook for Finding a Job and Making It Work” (Collins Business) is a one-stop guide for navigating all those times in your career.

There’s just no denying the signs. In fact you don’t need any signs at all, you just can’t stand your job. But how many of us have the luxury of just up and leaving a lousy job without having another lined up?

Having a job you hate is never an easy thing to deal with, but sometimes you just need to grin and bear it until you have another gig lined up. Whether you’re currently stuck because you just have to pay the bills or are holding out for the next great opportunity, here are some ways to get through the day:

Set weekly goals for yourself.
Sometimes it is easier to make it to 5 o’clock when you can keep your eye on the prize. Even if you hate your job now, there is something out there that will make you happy. Make weekly goals to help you find that golden opportunity. One week you might strive to send out five résumés or attend one networking event. Setting these goals will give you something to work toward.

Do one thing each day to help you reach your goals.
You don’t need to cross all your goals off your list every day, but you can chip away daily. When you get up in the morning, set a daily objective for yourself and make sure you achieve it. This will give you a sense of accomplishment and keep you feeling good about your progress.

Give yourself “me time” before work.
Going into a job you hate will be worse if you get to the office feeling rushed, stressed and frazzled. Set aside some moments of solitude each morning.

Develop a positive morning ritual.
Treat yourself to a latte, get up early enough to read the paper, or just set your alarm to play upbeat music when you wake up. Improving your mornings can do wonders for the rest of your day.

Create a diversion for yourself in the office.
Does being in your office make you yearn for the outdoors? Are the incessant ringing phones driving you batty? Do something to brighten your mood while you’re at work. Take in a tropical picture and use it as your screensaver. Buy yourself a “joke of the day” desk calendar. Plug headphones into your computer or bring your iPod to work. Go out for lunch.

Use your time to develop your skills.
Hating your job doesn’t mean you can’t learn new skills. Use your time to make yourself a better candidate down the road. If your company offers training courses, take advantage of them. Use downtime to learn something new on your computer. Pick up a management development book and read it at lunch. Turn this job into an opportunity for self-improvement.

Blow off some steam.
Most people have an activity that helps them unwind and get rid of tension. Go for a run after work, go swimming on your lunch hour, or take a nice long walk. Put this activity on your schedule so you will have something to look forward to every day.

Treat yourself.
To make up for your office misery, find little ways of treating yourself. Buy a good book to read. Treat yourself to ice cream. Buy some flowers. Shop for a new interview suit. Plan your next vacation. Find out what makes you feel better inside, no matter what is going on outside.

Maintain your performance.
It is important to continue to do your work and do it well, regardless of your current situation. Set personal performance goals. Then use the accomplishments in future interviews.

Keep your bridges intact.
It really is a small world, and you never know when you will run into co-workers from your past. Don’t burn any bridges at your company because you are unhappy. Maintain your contacts and keep your relationships positive. You might just need a reference or a good word from one of your colleagues in the future.

Realize that this too shall pass.
Right now, it might seem like you will be stuck in this job forever. Keep your chin up and remind yourself that you are in charge of your destiny. Search internal postings for new positions. Start your search for a new job externally.

From the editors of, CAREER BUILDING is filled with the statistics, tips and priceless information on job-hunting and working in the digital age, including good and bad résumé samples, using social networking, searching online, résumé “keywords” and e-mail mistakes to avoid. In today’s unstable economic climate, CAREER BUILDING is the guide you can’t afford to go without.

Ipv6 tunnel and relay concept displayed

Posted in ipv6 basics Tunneling on March 29, 2009 by itdaddy


SMTP Blocked outbound ESMTP/TLS fix ASA/PIX

Posted in ESMTP over TLS email blocking issue fix on March 20, 2009 by itdaddy


glad you are here. I first discovered this when I checked my Windows Exchange SMTP logs and had seen errors in the SMTP log like this:

Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2009-03-20 05:57:35
#Fields: time c-ip cs-method cs-uri-stem sc-status
05:57:35 – – 0
05:57:35 EHLO – 0
05:57:35 – – 0
05:57:35 STARTTLS – 0
05:57:35 – – 0
05:57:35 EHLO – 0
05:57:35 – – 0
05:57:35 AUTH – 0
05:57:35 – – 0
05:57:35 – – 0
05:57:35 MAIL – 0
05:57:35 – – 0
05:57:35 RCPT – 0
05:57:35 – – 0
05:57:35 DATA – 0
05:57:35 – – 0
05:57:35 – – 0
05:57:35 QUIT – 0
05:57:35 – – 0
05:58:04 – – 0
05:58:04 EHLO – 0
05:58:04 – – 0
05:58:04 STARTTLS – 0
05:58:04 – – 0


so what I did was this in CONFIG T mode I typed:

Cisco Firewall disabling TLS initiation by default

I have found my Cisco ASA 5510 is masking out STARTTLS initiation because of the SMTP packet inspection. This is enabled by default.

How to enable the firewall to start TLS on ESMTP sessions;

Option one;

policy-map type inspect esmtp esmtp_map
allow-tls [action log]

Option two;

no fixup protocol smtp 25

yeah!!!!!!!!!!!!!!!!!! mail is leaving outbound now!!!!!!!!!

IPV6 site explains how to config your devices

Posted in ipv6 6 to 4 tunnel config DHCP WAN on March 17, 2009 by itdaddy


I will explain my configs and my testing when I am done setting up my ASA 5505 to route to an ipv6 relay server system soon….so much fun…so little time!

Ipv6 Basics Tunneling 6 to 4 (temporary)

Posted in ipv6 basics Tunneling on February 27, 2009 by itdaddy

Set your firewall (cisco device) to these settings to be able to access: If you can access this site, you have it set up correctly.

Do it soon. Will  tell you about my experience of tunneling to ipv6 (internet 2) world….cool huh! hee hee


router# conf t
router#(config) ipv6 unicast-routing
router#(config) ipv6 cef
router#(config) ipv6 general-prefix DYN 6to4 Dialer1
router#(config) interface ethernet0
router#(config-if) ipv6 address DYN 0:0:0:1::/64 eui-64
router#(config-if) interface tunnel0
router#(config-if) ipv6 unnumbered Ethernet0
router#(config-if) tunnel source dialer1
router#(config-if) tunnel mode ipv6ip 6to4
router#(config) ipv6 route 2002::/16 tunnel0
router#(config) ipv6 route ::/0 2002:c058:6301::1


6to4 tunneling Basics

6to4 (sometimes written 6 to 4) is a system that allows IPv6 packets to be transmitted over an IPv4 network (generally the IPv4 internet) without the need to configure explicit tunnels. Routing conventions are also in place that allow 6to4 hosts to communicate with hosts on the IPv6 internet. It is typically used when an end site or end user wants to connect to the IPv6 internet using their existing IPv4 connection.

Since IPv6 is not required to be configured or supported on any nearby networking devices relative to the host, 6to4 is especially relevant during the initial phases of deployment to full, native IPv6 connectivity. However, it is intended only as transition mechanism and is not meant to be used permanently.

6to4 may be used by an individual host, or by a local IPv6 network. When used by an individual host, that host must have IPv4 connectivity and a global IPv4 address, and the host is responsible for encapsulation of outgoing IPv6 packets and decapsulation of incoming 6to4 packets. Many host operating systems implement this encapsulation and decapsulation via a 6to4 pseudo-interface.

When 6to4 is used by a local network, the entire local network needs only a single IPv4 address. Within that network, hosts learn their IPv6 addresses and routing using ordinary router discovery protocols, just as on a native IPv6 network.

6to4 does not facilitate interoperation between IPv4-only hosts and IPv6-only hosts.

How 6to4 works

6to4 performs three functions:

1. Assigns a block of IPv6 address space to any host or network that has a global IPv4 address.
2. Encapsulates IPv6 packets inside IPv4 packets for transmission over an IPv4 network.
3. Routes traffic between 6to4 and “native” IPv6 networks.

Address Block Allocation

For any 32-bit global IPv4 address that is assigned to a host, a 48-bit 6to4 IPv6 prefix can be constructed for use by that host (and if applicable the network behind it) by prepending 2002 (hex) to the IPv4 address. Thus for the global IPv4 address, the corresponding 6to4 prefix would be 2002:CF8E:83CA::/48. (IPv4 addresses use decimal notation while IPv6 addresses use hexadecimal notation). This gives a total prefix length of 48 bits, the same as an end site is supposed to be allocated under normal IPv6 address alocation leaving room for a 16 bit subnet field and a 64 bit address within the subnet.

Any IPv6 address that begins with the 2002::/16 prefix is known of as a 6to4 address, as opposed to a native IPv6 address which does not use that prefix.

Encapsulation and Transmission

6to4 embeds an IPv6 packet in the payload portion of an IPv4 packet with protocol type 41. To send an IPv6 packet over an IPv4 network to a 6to4 destination address, an IPv4 header with protocol type 41 is prepended to the IPv6 packet. The IPv4 destination address for the prepended packet header is derived from the IPv6 destination address of the inner packet, by extracting the 32 bits immediately following the IPv6 destination address’s 2002:: prefix. The IPv4 source address in the prepended packet header is the IPv4 address of the host or router which is sending the packet over IPv4. The resulting IPv4 packet is then routed to its IPv4 destination address just like any other IPv4 packet.

Routing Between 6to4 and Native IPv6

To allow hosts and networks using 6to4 addresses to exchange traffic with hosts using “native” IPv6 addresses, “relay routers” have been established. A relay router connects to an IPv4 network and an IPv6 network. 6to4 packets arriving on an IPv4 interface will have their IPv6 payloads routed to the IPv6 network, while packets arriving on the IPv6 interface with a destination address prefix of 2002::/16 will be encapsulated and forwarded over the IPv4 network.

To allow a 6to4 router to communicate with the native IPv6 Internet, it must have its IPv6 default gateway set to a 6to4 address which contains the IPv4 address of a 6to4 relay router. To avoid the need for users to set this up manually, the 6to4 relay anycast address of (which when wrapped in 6to4 with the subnet and hosts fields zero becomes 2002:c058:6301::) has been allocated for the purpose of sending packets to a relay router. For routing reasons the whole of has been allocated for routes pointed at 6to4 relay routers that use the anycast IP. Providers willing to provide 6to4 service to their clients or peers should advertise the anycast prefix like any other IP prefix, and route the prefix to their 6to4 relay.

Packets from the IPv6 Internet to 6to4 systems must be sent to a 6to4 relay router by normal IPv6 routing methods. The specification states that such relay routers must only advertise 2002::/16 and not subdivisions of it to prevent IPv4 routes polluting the routing tables of IPv6 routers. From here they can then be sent over the IPv4 Internet to the destination.

Running Example

This example resembles the scenario in RFC 3056 Section 5.5. In the RFC scenario, there are multiple IPv6 sites, connected to one IP backbone. While in this scenario, there is only one IPv6 site connected to the IP backbone. Site A and Site C are 6to4 sites while Site B is 6to4 relay and Site B pure IPv6.

IPv6…6to4 Tunnel with DHCP WAN Side

Posted in ipv6 6 to 4 tunnel config DHCP WAN on February 27, 2009 by itdaddy



I have a ASA 5505 and am going to set it up on the WAN side. I have DHCP from my ISP so I need to follow this. By doing this it helps me understand IPV6 alittle better.

This tunnel configuring is only meant to be a transition mechanism and is not meant to be used permanently. Eventually all businesses will be given ipv6 blocks and then every pc will have its own ipv6 address and I do beleive NAT will not be used any more but don’t quote me on this…unless they have Ipv6 private block address NAT’d to IPV6 public address blocks. Not sure yet.

There are IPV6 relays out there on the internet. If you can tunnel to them by the config setup on your Cisco device, you can then access the ipv6 network.

test that your config worked:

Here is the config easier to read: