From time to time, especially at home, ive been experiencing problems where pressing the home button takes ages for my phone to actually wake up, and then often when it does wake up, the slide to unlock screen is frozen, and I have to wait longer before I can actually slide and unlock.

Ive tried loads of things to try to figure this out, I am jailbroken, so wondered if it was that that caused the problems, but after putting the phone into flight mode, the problem went away..

After some digging around, I tried manually selecting my carrier – specifically the 3 3g one. Whilst this is far from ideal as it locks me to three’s 3g network, which means that should I go outside of that I will not automatically fall back onto the 2g infrastructure, it does seem to have sorted my problem.

More digging and reading suggests that when the phone switches from 3g to 2g, it can some times be a slow and painful process, and especially so with three’s network, as it seems they utilise other peoples 2g infrastructure, which would explain why I dont see this problem with a vodafone iPhone.

So if you are on three, it might be worth trying this, but remember you are likely to get more No Service messages if you go outside of a covered area and will need to manually either select automatic to get it back, or manually chose an alternative compatible carrier.

I used to get pretty much 2 days use out of a full charge – I dont use the phone loads, just normal texting, a few phone calls and a bit of facebook / twittering, but after the 3.1.3 firmware upgrade, I immediately found I was getting only a days worth of battery life

Wasn’t happy especially as apple stopped me from downgrading to 3.1.2 which was nice and lovely.

So to help me get the best of what I had I made 2 changes which made a big difference and have resulted in me getting my 2 days usage back, and maybe even a bit more.

1: Disable location services – Go into settings > general, and change location services to off.

This does mean you no longer have your GPS active, but if you like me only use this infrequently, i’d rather switch it on in the odd occasion I do use it, than have it sucking my battery away.

2: Disable wi-fi scanning – Go into settings > wi-fi and change Ask to Join Networks to off. This means that rather than constantly scanning for available wi-fi networks, it will only use the ones you have pre-configured. Should you want to connect to a new network, you can either switch this back on or go back into settings > wi-fi and pick it from the list or add it manually. Again this saves loads of battery time as the wi-fi is not scanning.

These 2 simple tips made a big difference to mine and a few friends iPhone life, hope it helps you too.

ATA (ata) Handshake sounds if modem speaker is enabled. Modem tries to answer call with handshake sounds. Press Enter to stop this process. The no carrier message is normal with this command. This command does not apply to Windows XP.

ATDT <ISP Phone Number>

For example, ATDT1234567 (where 1234567 is the connection number to dial for Internet service).

To connect to a test server in the US you can type:

ATDT18666633665 Login: _ Connects to a test server. If you can get to a login, your modem is working correctly.

ATDT (atdt) Dialtone if modem speaker is enabled. Indicates that the modem can get a dial tone. The message “no dial tone” indicates that either the modem or phone line is not working correctly. Press Enter to stop this process.

AT&F OK Resets most modems to factory defaults.

ATI0 (ati) 56000 ok The response varies between modems, but returns the modem speed..

ATI3 (ati) <Version and name> Returns the modem product type and firmware version.

ATZ (atz) ok This command resets the modem.

ATH (ath) ok Hangs up modem

ATS0=2 (ats0=2)

Zero, not the letter O . ok This command sets the modem to receive. Call the computer’s phone number and you should hear the handshake signal. Ring, ring displays on HyperTerminal screen, followed by no carrier , when the caller hangs up.

its usage is as follows to live debug traffic according to your filter:

# fw monitor -e “accept src=10.0.0.x;”

This will output in realtime the traffic going into your firewall from ip address 10.0.0.x

You will see output similar to the below:

Lan1:i[84]: 10.0.0.1 ->192.168.0.1 (ICMP) len=84 id=0 <———– This shows traffic coming into interface Lan1 but before rules have been processed thats the lowercase i.

ICMP: type=8 code=0 echo request id=64597 seq=5025

Lan1:I[84]: 10.0.0.1 -> 192.168.0.1 (ICMP) len=84 id=0 <——— This shows traffic still on interface Lan1 but after rules have been processed hence the uppercase I, if firewalls were dropping this packet you would not see this.

ICMP: type=8 code=0 echo request id=64597 seq=5025

Lan5:o[84]: 10.0.0.1 -> 192.168.0.1 (ICMP) len=84 id=0 <———-Now we see traffic going out of the destination interface Lan5 but again before the rules have been processed – lowercase o.

ICMP: type=8 code=0 echo request id=64597 seq=5025

Lan5:O[84]: 10.0.0.1 ->192.168.0.1 (ICMP) len=84 id=0 <———-Finally we see traffic going out of the destination interface Lan 5 after successfully traversing the rules – uppercase O

There is a load of filters you can apply, the example above uses src, but you can also use keywords such as dst, sport, dport etc..

Check this doc for a full list of what you can and can’t do..

http://www.checkpoint.com/techsupport/downloads/html/ethereal/fw_monitor_rev1_01.pdf

# cphaprob stat

This command shows you the current status of your ha configuration – ideally you will see OK’s rather than problem, it will also tell you the which node is the primary.

# cphaprob -ia list

This give you a bit more detail on any problems and which if any daemons have failed. So for example, if your fwd daemon has failed you would see a state of problem.

# cphaprob -a if

This shows you the interfaces, whether they are up, and whether they are running multicast or broadcast – this should be the same on the secondary node.

#fw stat

Shows you the host and the currently installed policy along with a list of your interfaces in use.

# netstat -i

Regular linux command, but useful as it shows you the state of your interfaces, and whether there is a possible network problem.

The Central Management Server has failed to start. Press ‘Retry’ to attempt

to start it again or ‘Cancel’ to skip any actions dependendent on the Central

Management Server. (STU000213)

When trying to do a Business Objects Xi3 install

I bashed my head against the wall for ages on this, the cms.exe service did actually seem to be starting – it was listed as a running process in task manager – I could see it bound to port 6400 using netstat, so I couldnt understand what was causing the issue and throwing the above error message.

The business objects help was far from helpful suggesting I click retry! wow – unsurprisingly this didnt work.

So trying to logically work through it, I came down to  the fact that it must be related to my install using an existing database.

I had read a few posts which talked about the CMS Administrator password – and it dawned on me that it might be because I was using a existing database that I needed to input the existing CMS Administrator password – which wasn’t blank.

I was trying to use the option, configure this later for the CMS Admin password, and just didnt really pay much attention to this, but when I tried to re-install for the 5th time, I put in the existing CMS Admin password, and HEY PRESTO, Business Objects FINALLY installed…

What in hindsight seems relatively obvious, caused me such pain! Please Business Objects, lets have some better / more verbose output / logging on your error messages…

Anywho.. .hope this helps someone, cos it took me ages

What you have to configure is a group which contains all the networks that will be behind the interface.

So you may have for example an interface say Lan 1 which has nets 192.168.0.0/24 and 192.168.1.1/24 behind it, you need to create a group for example called Lan1AntiSpoof and place these 2 network objects inside.

Once you have that group you need to configure your cluster to use that to define which nets are private and behind which interfaces.. the principle is the same for all interfaces.

right click your cluster and choose edit, Then click the topology item, click edit topology, Highlight the interface you want to configure – in this example Lan 1 and click edit, click the topology tab, and you will see an option for internal (assuming this is one of your internal interfaces) Choose the radio button specific, and select the group you created above – Lan1AntiSpoof. Save these changes and apply this new rule config. You will need to do this for all nets that are behind interfaces that are considered internal nets to be able to communicate without being blocked by the anti-spoofing rules.

If this post was useful, please click some of the ad blocks which helps me to keep this site running. Thanks!

Here are a few more usefull commands.

To list all your current VPN Tunnels – IKE / IPSec etc..

Open a command line on the firewall, go into expert mode and type: vpn tu

You then get the option to list tunnels, or kill them by peer ip or user (client) or just all.

This gives you a much more granular method to debug and view / kill tunnels on a per peer type basis.

To switch VPN debugging on, which logs to $FWDIR/log/vpnd.elg use the following:

vpn debug on

vpn debug ikeon

vpn debug trunc (this command is the equivalent of the above 2)

To switch debugging off use:

vpn debug off

vpn debug ikeoff

You can then export the log file to another machine for analysis.

To fix it change the bit in the url that says hl=uk to hl=gb and hit return and it’ll be in english.

But it didnt. When I tried to log onto the Central management console, it got the error message that the server was not running. Sure enough a quick netstat showed me that it was not bound to port 6400 which would indicate it was up.

After trying a few things, I noticed that for some reason in the database settings for the Server Intelligence Agent, on the configuration tab were all missing.

So after stopping the Server Intelligence Agent service I edited the CMS System database configuration, configured it as it needed to be and saved the settings. Restarted the Server Intelligence Agent, and tried to log on again. FAILED.

After a bit of poking around, I thought I would try restarting the BusinessObjects Data Services service. Bingo, everything kicked into life.