Thursday, November 20, 2014

Raspberry Pi panics on boot with no HDMI

One of the Pis started playing up and it's got some odd symptoms.

Initially it would boot and and then reboot just after the login prompt appeared.  I think that was a process not seeing the hardware it expected and trying to recover but diagnosing this I hooked it up to the monitor to see what was going on.

The odd thing that is since then it won't restart without a monitor attached.  If there is no monitor it kernel panics and says it can't it can't mount the root file system.  I tried hooking up a cable with nothing on the end but that fails as well so it needs to get the information from a monitor to start.

the /boot/cmdline.txt file is

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline root-wait

I think the problem is root-wait.  This might have got auto corrected when I loaded the file onto the Mac to add init=/bin/sh to do some trouble shooting. It looks like it should be root-wait no hyphen.



Looks to be sorted now.  So be careful editing that file on machines that want to auto correct things.

Wednesday, November 12, 2014

IPSEC VPN Fortigate to ISA 2006

We had to set one of these up today and it was a bit odd.

The easiest way is to say what settings worked :-)

Stick with SHA and 3DES.  Group2 for DH, supposedly 14 will work but it didn't for us.

Use proxies, this was our final stumbling block.  ISA wanted proxies in phase 2 or came up with INVALID-ID-INFORMATION in the Fortigate debugs.

Otherwise it's defaults for times, DPD etc.

Edit later:

ISA summarises multiple networks rather than creating a second phase 2. dumb..

ie we had 10.0.1.0/24 at the remote site and 10.0.2.0/24 at the head office end.  They want to add 10.0.3.0/24 so debugging (you can't set this or see it in ISA by the looks of it) the HO end proxy goes from 10.0.2.0/24 to 10.0.0.0/16. So what happens when you add a second network to the remote office end?