OPNsense Forum

Archive => 17.1 Legacy Series => Topic started by: xmichielx on January 07, 2017, 06:12:24 pm

Title: SSH installation on APU 2
Post by: xmichielx on January 07, 2017, 06:12:24 pm
Hi,

How can I install OPNsense 17.1 beta on an PCEngines APU 2 over SSH?
I can create an USB installation and boot from USB but what should I do next to install OPNsense over SSH?
Connect port 1 to LAN DHCP and connect to SSH (find out which DHCP lease OPNsense installer has with nmap) and then use which credentials?
I tried the documentation/wiki and reading the blog but could not find anything related except for the mention:
'installer now boots up with SSH for headless remote installation'

Any help is much appreciated :)

PS..I want to try to avoid using the console installation as it is a b!t(ch to run with the different speed settings etc.
I rather do it relaxed from my couch over SSH ;)

Cheers,

Michiel
Title: Re: SSH installation on APU 2
Post by: franco on January 07, 2017, 06:20:09 pm
Hi Michiel,

If 192.168.1.1 is up as expected (first port normally, but you can see where it gives out 192.168.1.x DHCP leases for the device you plug).

# ssh installer@192.168.1.1

Password is "opnsense". :)


Cheers,
Franco
Title: Re: SSH installation on APU 2
Post by: xmichielx on January 07, 2017, 10:20:35 pm
Do you mean the first port will have IP 192.168.1.1 or will it get a DHCP lease?
I already got a router running at 192.168.1.1 with DHCP, if Port1 already has 192.168.1.1 then I have to hook up a seperate switch or crosslink cable to connect to Port1 and use static ip on my laptop over the crosslink I guess.
Title: Re: SSH installation on APU 2
Post by: franco on January 08, 2017, 10:09:21 am
Hi Michiel,

The first port has 192.168.1.1 and will give out leases by itself. This is the LAN interface.

The second port attempts to get a DHCP lease, but since it is WAN you won't be able to access SSH from there.

The system is meant for plugging a Laptop into a live OPNsense system that can be operated in its main use case, not just provide/grab an IP for installation.

The default config *could* do this if modified, but there is no way to anticipate what the user wants to do with the system during image builds so we stick with the principle of least astonishment. :)


Cheers,
Franco