Who will block your last phones IMEI? Samsung or Airtel or Police

It is taking ages for me to get the phone IMEI blocked while police doesn’t like filing complaint on one end and  at the other end mobile manufacturer as well as network providers through stones at each other.

Here is what Samsung CEO’s office has to say about this once it was escalated beyond customer service:

Dear Mr. Omshivaprakas,

Samsung Namaskar!

Thank you contacting our CEO’s Office.

Firstly, we are sorry to know that your handset has been lost. With reference to your query, kindly get in touch with your mobile communication service provider (eg: Airtel, Vodafone etc). They will be able to advise you on the further course of action in this regard.

I hope this information will be useful to you.

Assuring you of prompt services at all times. We’ll always be happy to assist you.

With warm regards,

CEO’s Office
Samsung India Electronics Pvt. Ltd.

 

Airtel in response:

Dear Customer,

Greetings from all of us at airtel!

This is in reference to your complaint to TRAI dated 04 July 2012, regarding block the IMEI handset of your mobile handset.

 

As per your telephonic conversation with the undersigned, we would like to inform you that we are infeasible to block the IMEI of your handset model. We would request you to please contact your mobile operator.

We truly hope that the above details address your query adequately.

 

Yours Sincerely

Tanpreet Kaur

Customer Services

Bharti Airtel Limited

When contacted police about the lost phone so far I have been asked to write the complaint as its lost and not stolen just for the sake of getting FIR and they won’t be blocking IMEI either. So, what am I supposed to do? I don’t care of the mobile that has been lost but would definitely want me phone’s IMEI to be blocked as I don’t want that to be used by any one else.

Who will tie the bell?

Still searching for a solution…..

Fix: iptables: Unknown error 4294967295

Following error is noticed when you are running in the VM.

: Unknown error 4294967295

Main reason for this error iptables support missing in OpenVZ.

Here are the quick steps to resolve this issue permanently:

1. Define which iptables modules are available for VEs.

a)
Edit /etc/sysconfig/iptables-config file on a OpenVZ hardware node:

IPTABLES_MODULES=”ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”

b)
Edit /etc/sysconfig/vz file on a OpenVZ hardware node:

IPTABLES=”ipt_REJECT
ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”

Note:– iptables modules list in IPTABLES and IPTABLES_MODULES parameters in /etc/sysconfig/vz and /etc/sysconfig/iptables-config files should be placed in one single line, no linebreaks is allowed in this parameter.

Restart OpenVZ server
# service vz restart

2. Increase ‘numiptent’ parameter for the VE you need to install APF into. This parameter limits the amount of iptables rules available for a VE. Default APF configuration requires ~400 rules. Lets set it to 400 in the example below for VE #101:

# vzctl set 101 --numiptent 400 --save

3. Start APF inside the VE:
# /etc/init.d/apf start

Tags: , ,

Article on Password Security in Prajavani

Article published in Prajavani on 12th December 2010 Tags: ಇ-ಮೈಲ್ ಸೆಕ್ಯೂರಿಟಿ, ಭಯೋತ್ಪಾದಕರು, ಮಾಹಿತಿ ತಂತ್ರಜ್ಞಾನ, ಸುರಕ್ಷತೆ

Enable/Disable cphulkd at Console

————————————————————————————— This account is currently locked out because a brute force attempt was detected. Please wait 10 minutes and try again. Attempting to login again will only increase this delay. If you frequently experience this problem, we recommend having your username changed to something less generic. ————————————————————————————— If you’re getting the above error while accessing […]

[cPanel-News] Tech Advisory: BIND: Red Hat and CentOS

Here is an update on BIND for cPanel server admin’s

Recent versions of Bind distributed by RedHat and?CentOS enable strict zone checking at startup time. This setting can potentially cause problems for Bind users with a large number of zone files or syntax errors in individual zone files. In these circumstances, users may experience an inability to restart Bind after a shutdown.?cPanel has produced and distributed an autofixer for this condition. This repair will run automatically on all systems with updates enabled. However, cPanel checks only occur at specific times and depending upon update schedules, users experiencing issues restarting Bind may benefit from manually executing the code to disable strict zone checking. You may safely execute the autofixer at your discretion by running the following command:

/scripts/autorepairbind_disable_checkzone

Source: cPanel Blog