I love trains. I have always loved them. Bet it the odd family vacation or a trip to roommate’s town for his wedding or YouTube videos, I have always been a fan of trains.
I was probably eight or nine. I was returning with my family from my granny’s home via, no points for guessing, a train. As usual, while others kept sitting on their uncomfortable wooden seats, I kept running around the entire train coach, trying to test myself by guessing the next train station. Yes, by now I had memorised all the stations along the way or so I thought. Other times, I just kept looking out of the ugly heavy metal door towards the horizon and yet other times, I kept trying to spot the engine when the train tried to negotiate a turn.
Around midway, a couple of women entered the train, they were typical village women who seemed out of place and confused in a train. I can still recall, they kept looking out all the time. Eventually they got tired, I guess, as both of them dozed off while I kept running around in the coach. After a while, they woke up, started asking everyone frantically whether their stop had arrived or not.
They even asked me, a kid. I nodded. I think I did. Palms met their respective foreheads and they looked quite frightened. The two women were almost at the brink of crying. As soon as the next station came, they jumped off the train. I saw them get down and run towards the station building. The train chugged off again. I went back to doing my usual train stuff.
Then the train stopped again after a long while. I looked out to know which station it was. It was the very station at which the village women wanted to get down.
So you have checked the forums everywhere and have found out that it is caused because of MTU mismatch?
You have made sure that the MTU is correct on both the ends?
Still getting the same error? Confused?
Try an extended ping between the neighbors using ‘size’ and ‘df-bit’ option. Example:
ping 172.18.0.189 so 172.18.0.190 size 2000 df-bit
Type escape sequence to abort.
Sending 5, 2000-byte ICMP Echos to 172.18.0.189, timeout is 2 seconds:
Packet sent with a source address of 172.18.0.190
Packet sent with the DF bit set
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
As soon as it’s done, your OSPF neighborship should come up in no time.
Strange right? Worked for me. Hope it helps you too.
PS: In my case, the OSPF neighbors were a Cisco router & a Juniper router. Ideally, if you’re on all Cisco gear, you shouldn’t be on this blog. :)
Offered without comment.
To my utter horror, just discovered that Google has pulled down its app called Listen from the Play store. It’s a shame that not many people know about it and don’t have problem now that it has been culled.
There are many podcast-catching apps out there but Listen had one big advantage. [combined with Feed Flipper] Once you add a podcast to Listen, it automatically syncs with your Google Reader account by creating a folder called ‘Listen Subscriptions’and voila. You can listen to your pod-casts on your laptop or your phone now. Nifty!!!
This leaves me saddened but I’m a tad happy that I have still have it on my Android phone.
I hate you world for you made Google kill Listen. Thanks for nothing. :’(
Don’t ask if it’s me. Thanks.
Had a bout of insomnia last night and here’s the result.