External Access - Revision history

Wikisailor: /* Port Assignments */

2026-02-13T02:00:54Z

Port Assignments

← Older revision		Revision as of 02:00, 13 February 2026
Line 23:		Line 23:
	* Satsuma ****11		* Satsuma ****11
	It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@		It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@

			'''Update we will have to fwd the port on the new edge router and these will not work from outside until that is done''' it should work from within the LAN though

	==SFTP Access==		==SFTP Access==

Sailor: /* Passwordless SSH */

2025-03-12T21:01:39Z

Passwordless SSH

← Older revision		Revision as of 21:01, 12 March 2025
Line 40:		Line 40:
	The response will be Are you sure you want to continue connecting (yes/no/[fingerprint])? Type yes The last thig is to add a friendly name to		The response will be Are you sure you want to continue connecting (yes/no/[fingerprint])? Type yes The last thig is to add a friendly name to
	nano ~/.ssh/config		nano ~/.ssh/config
	* Host is hostname		* Host is hostname or anything that is more friendly
	* Hostname is hostname.seaoffate.local (or ip address)		* Hostname is hostname.seaoffate.local (or ip address)
	* User is nigel or whatever you want		* User is nigel or whatever you want
	* IdentityFile is the path to the key pair so probably ~/.ssh/hostname		* IdentityFile is the path to the key pair so probably ~/.ssh/hostname

Sailor: /* Passwordless */

2025-03-12T20:58:34Z

Passwordless

← Older revision		Revision as of 20:58, 12 March 2025
Line 32:		Line 32:
	The server that will receive all or most of the SFTP uploads needs to have the /mnt/shared chowned by root:root or the connection may be refused even before the password is entered. So if the SFTP client keeps refusing connection the first thing to do is to ssh to the box and do ls -l on /mnt/shared and if it is not owned by root do a sudo chown root:root /mnt/shared. The SFTP client should work after that.		The server that will receive all or most of the SFTP uploads needs to have the /mnt/shared chowned by root:root or the connection may be refused even before the password is entered. So if the SFTP client keeps refusing connection the first thing to do is to ssh to the box and do ls -l on /mnt/shared and if it is not owned by root do a sudo chown root:root /mnt/shared. The SFTP client should work after that.

	==Passwordless==		==Passwordless SSH==

	To setup passwordless ssh between two hosts first generate a key and put it in the home/username/.ssh/ dir and named as the name of the host		To setup passwordless ssh between two hosts first generate a key and put it in the home/username/.ssh/ dir and named as the name of the host

Sailor: /* SFTP Access */

2025-03-12T20:58:14Z

SFTP Access

← Older revision		Revision as of 20:58, 12 March 2025
Line 31:		Line 31:

	The server that will receive all or most of the SFTP uploads needs to have the /mnt/shared chowned by root:root or the connection may be refused even before the password is entered. So if the SFTP client keeps refusing connection the first thing to do is to ssh to the box and do ls -l on /mnt/shared and if it is not owned by root do a sudo chown root:root /mnt/shared. The SFTP client should work after that.		The server that will receive all or most of the SFTP uploads needs to have the /mnt/shared chowned by root:root or the connection may be refused even before the password is entered. So if the SFTP client keeps refusing connection the first thing to do is to ssh to the box and do ls -l on /mnt/shared and if it is not owned by root do a sudo chown root:root /mnt/shared. The SFTP client should work after that.

			==Passwordless==

			To setup passwordless ssh between two hosts first generate a key and put it in the home/username/.ssh/ dir and named as the name of the host
			ssh-keygen -t rsa -b 4096 -f ~/.ssh/hostname
			You will be asked to enter passphrase either add one or not twice once it is done there will be a new key pair stored in .ssh/,now we can copy the pub file to the destination. The easiest is to copy by ssh-copy-id
			ssh-copy-id -i ~/.ssh/hostname.pub username@FQDN
			The response will be Are you sure you want to continue connecting (yes/no/[fingerprint])? Type yes The last thig is to add a friendly name to
			nano ~/.ssh/config
			* Host is hostname
			* Hostname is hostname.seaoffate.local (or ip address)
			* User is nigel or whatever you want
			* IdentityFile is the path to the key pair so probably ~/.ssh/hostname

Sailor: /* Port Assignments */

2025-03-12T18:49:50Z

Port Assignments

← Older revision		Revision as of 18:49, 12 March 2025
Line 11:		Line 11:
	As previously stated each host will listen to SSH on a different port. The assignments are		As previously stated each host will listen to SSH on a different port. The assignments are

			* Mandarin ***01
	* Raisin ..***02		* Raisin ..***02
	* Lime ...****03		* Lime ...****03

Sailor: /* Port Assignments */

2025-03-10T09:41:19Z

Port Assignments

← Older revision		Revision as of 09:41, 10 March 2025
Line 19:		Line 19:
	* Alpine .****08		* Alpine .****08
	* Plum ...****09		* Plum ...****09
	* ~~strawberry~~**10		* Strawberry**10
			* Satsuma ****11
	It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@		It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@


	==SFTP Access==		==SFTP Access==

Sailor: /* Introduction */

2025-03-07T01:32:29Z

Introduction

← Older revision		Revision as of 01:32, 7 March 2025
Line 1:		Line 1:
	==Introduction==		==Introduction==

	I will want access to various hosts for file shares and configuration. This is where I will describe it.		I will want access to various hosts for file shares and configuration of the '''[[Home Lab]]'''. This is where I will describe it.


	==SSH Access==		==SSH Access==

Sailor at 01:16, 7 March 2025

2025-03-07T01:16:24Z

← Older revision		Revision as of 01:16, 7 March 2025
Line 22:		Line 22:
	* strawberry**10		* strawberry**10
	It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@		It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@


			==SFTP Access==

			SFTP will also use port 22 by default and for the same reason as SSH it also cannot be easily port forwarded in that every SFTP server will be listening to 22. So the same port forwards from that allow SSH to work will also work here. As most of the DNS names from Cloudflare are proxied they will only forward HTTP/S traffic, we have two DNS entries that are not proxied and they should not be used for HTTP/S as these may not get the full SSL treatment on webbrowsers. They will still be secure in that SFTP is in itself secure.

			===Additional Note===

			The server that will receive all or most of the SFTP uploads needs to have the /mnt/shared chowned by root:root or the connection may be refused even before the password is entered. So if the SFTP client keeps refusing connection the first thing to do is to ssh to the box and do ls -l on /mnt/shared and if it is not owned by root do a sudo chown root:root /mnt/shared. The SFTP client should work after that.

Nigel: /* Port Assignments */

2025-03-04T18:18:05Z

Port Assignments

← Older revision		Revision as of 18:18, 4 March 2025
Line 11:		Line 11:

	As previously stated each host will listen to SSH on a different port. The assignments are		As previously stated each host will listen to SSH on a different port. The assignments are
	* Mandarin ***01
	* Raisin ..***02		* Raisin ..***02
	* Lime ...****03		* Lime ...****03
Line 20:		Line 20:
	* Alpine .****08		* Alpine .****08
	* Plum ...****09		* Plum ...****09
			* strawberry**10
	It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@		It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@

Nigel: /* Port Assignments */

2025-03-04T17:35:14Z

Port Assignments

← Older revision		Revision as of 17:35, 4 March 2025
Line 19:		Line 19:
	* Lemon ..****07		* Lemon ..****07
	* Alpine .****08		* Alpine .****08
			* Plum ...****09
	It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@		It would make sense to have them as aliases in Pfsense, each alias will take the form SSH_int_''hostname''. when testing try the user nigel@