Lab 5 mnjk - Revision history

NateHaleen: /* Checking Your Work */

2021-04-20T01:14:20Z

Checking Your Work

← Older revision		Revision as of 01:14, 20 April 2021
Line 297:		Line 297:
	</ol>		</ol>
	<br><br>		<br><br>
			=Web App=
	You can check your progress on any of the labs in the ITC-2480 course from a webapp from this link: <br>		You can check your progress on any of the labs in the ITC-2480 course from a webapp from this link: <br>
	[http://webcheck.itc2480.campus.ihitc.net webcheck.itc2480.campus.ihitc.net]<br>		[http://webcheck.itc2480.campus.ihitc.net webcheck.itc2480.campus.ihitc.net]<br>
	You must be logged into the campus VPN to use this application.		You must be logged into the campus VPN to use this application.

NateHaleen: /* Checking Your Work */

2021-04-16T22:36:14Z

Checking Your Work

← Older revision		Revision as of 22:36, 16 April 2021
Line 296:		Line 296:
	</nowiki></code>		</nowiki></code>
	</ol>		</ol>
			<br><br>
			You can check your progress on any of the labs in the ITC-2480 course from a webapp from this link: <br>
			[http://webcheck.itc2480.campus.ihitc.net webcheck.itc2480.campus.ihitc.net]<br>
			You must be logged into the campus VPN to use this application.

JonQuinn: /* Checking Your Work */

2021-03-22T23:37:32Z

Checking Your Work

← Older revision		Revision as of 23:37, 22 March 2021
Line 284:		Line 284:
	</ol>		</ol>
	==Checking Your Work==		==Checking Your Work==
	~~<br><br>~~
	<ol>		<ol>
	<li>Ping your assigned IP for your pod</li>		<li>Ping your assigned IP for your pod</li>
	<ul>Your ping should return a response.</ul>		<ul>Your ping should return a response.</ul>
	<li>Open a browser on your own PC and navigate to your IP address</li>		<li>Open a browser on your own PC and navigate to your IP address.</li>
	<ul>Your custom link page should appear in your browser window.</ul>		<ul>Your custom link page should appear in your browser window.</ul>
	<li>Check your home directory for the logtail.txt file you created</li>		<li>Check your home directory for the logtail.txt file you created.</li>
	<ul>The logtail.~~yxy~~ file should be in your home directory</ul>		<ul>The logtail.txt file should be in your home directory.</ul>
	<li> Automatically check your results by running this command:</li>		<li> Automatically check your results by running this command:</li>
	<code><nowiki>		<code><nowiki>

JonQuinn: /* Checking Your Work */

2021-03-22T23:35:14Z

Checking Your Work

← Older revision		Revision as of 23:35, 22 March 2021
Line 285:		Line 285:
	==Checking Your Work==		==Checking Your Work==
	<br><br>		<br><br>
			<ol>
			<li>Ping your assigned IP for your pod</li>
			<ul>Your ping should return a response.</ul>
			<li>Open a browser on your own PC and navigate to your IP address</li>
			<ul>Your custom link page should appear in your browser window.</ul>
			<li>Check your home directory for the logtail.txt file you created</li>
			<ul>The logtail.yxy file should be in your home directory</ul>
	<li> Automatically check your results by running this command:</li>		<li> Automatically check your results by running this command:</li>
	<code><nowiki>		<code><nowiki>
	curl https://raw.githubusercontent.com/mnjk-inver/Linux-2480-Rebuild/main/lab_05_test.py \| python3		curl https://raw.githubusercontent.com/mnjk-inver/Linux-2480-Rebuild/main/lab_05_test.py \| python3
	</nowiki></code>		</nowiki></code>
			</ol>

NateHaleen: /* View Logfiles */

2021-03-02T22:05:09Z

View Logfiles

← Older revision		Revision as of 22:05, 2 March 2021
Line 283:		Line 283:
	:'' Note: After the first rotated file other files are usually compressed with gzip. You can decompress and view these on the fly using the '''zcat''' program.		:'' Note: After the first rotated file other files are usually compressed with gzip. You can decompress and view these on the fly using the '''zcat''' program.
	</ol>		</ol>
			==Checking Your Work==
			<br><br>

			<li> Automatically check your results by running this command:</li>
			<code><nowiki>
			curl https://raw.githubusercontent.com/mnjk-inver/Linux-2480-Rebuild/main/lab_05_test.py \| python3
			</nowiki></code>

JonQuinn: /* View Logfiles */

2021-02-20T12:42:11Z

View Logfiles

← Older revision		Revision as of 12:42, 20 February 2021
Line 275:		Line 275:
	: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).		: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).
	<li>Save the tail output to a file</li>		<li>Save the tail output to a file</li>
	: Often we may want to save the output from a '''tail''' command to share with others or document an issue. This can easily be done using redirection we learned in a previous lab. Experiment with how to save some tail commands.		: Often we may want to save the output from a '''tail''' command to share with others or document an issue. This can easily be done using redirection we learned in a previous lab. Experiment with how to save some tail commands. Keep in mind you may need to escalate privileges for some files to be redirected. Try the following:
	: <code>tail -20 /var/log/syslog > logtail.txt</code>		: <code>sudo tail -20 /var/log/syslog > logtail.txt</code>
	<li>Explore some other log files</li>		<li>Explore some other log files</li>
	: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''		: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''

JonQuinn: /* View Logfiles */

2021-02-20T12:40:03Z

View Logfiles

← Older revision		Revision as of 12:40, 20 February 2021
Line 275:		Line 275:
	: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).		: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).
	<li>Save the tail output to a file</li>		<li>Save the tail output to a file</li>
	: Often we may want to save the output from a '''tail''' command to share with others or document an issue. This can easily be done using redirection we learned in a previous lab.		: Often we may want to save the output from a '''tail''' command to share with others or document an issue. This can easily be done using redirection we learned in a previous lab. Experiment with how to save some tail commands.
	<code>tail -20 /var/log/syslog > logtail.txt</code>		: <code>tail -20 /var/log/syslog > logtail.txt</code>
	<li>Explore some other log files</li>		<li>Explore some other log files</li>
	: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''		: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''

JonQuinn: /* View Logfiles */

2021-02-20T12:39:12Z

View Logfiles

← Older revision		Revision as of 12:39, 20 February 2021
Line 274:		Line 274:
	:[[Media:Lab5_tail.png\|Click here for a larger image]]		:[[Media:Lab5_tail.png\|Click here for a larger image]]
	: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).		: Linux log files are typically standard text files and can be read with standard text file utilities like cat or less. One additional utility which comes in hand is the '''tail''' program which displays the last 10 lines (by default) of a text file and which can be configured to display more or less lines using a command like '''tail -20 /var/log/syslog''' which will display the last 20 lines of the main system log file. The manual page for the '''tail''' command contains additional information like how to use the ''-f'' option to view a log in realtime (exit with Ctrl-C).
			<li>Save the tail output to a file</li>
			: Often we may want to save the output from a '''tail''' command to share with others or document an issue. This can easily be done using redirection we learned in a previous lab.
			<code>tail -20 /var/log/syslog > logtail.txt</code>
	<li>Explore some other log files</li>		<li>Explore some other log files</li>
	: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''		: Take a look at some of the log files on your system and see what kinds of information they contain specifically you should probably look at ''syslog'', ''auth.log'', ''kern.log'', ''apache2/access.log'', and ''apache2/error.log''

JonQuinn: /* Set a static IP */

2021-02-18T02:40:57Z

Set a static IP

← Older revision		Revision as of 02:40, 18 February 2021
Line 111:		Line 111:
	<li>Apply your static IP address</li>		<li>Apply your static IP address</li>
	* Now we are going to apply the static IP change. Try using '''ip address show''' to view your active configuration now and you should see that your old address is still active.		* Now we are going to apply the static IP change. Try using '''ip address show''' to view your active configuration now and you should see that your old address is still active.
	'''NOTE: You should only make network configuration changes when you have physical access to a machine. This way, if you mess up your configuration you will be able to fix it from a local console.''' If you lose working SSH access to your system after making these changes you'll need to connect in through the NetLab console interface (which is equivalent to physical access) and find and correct your configuration issues.		:''NOTE: You should only make network configuration changes when you have physical access to a machine. This way, if you mess up your configuration you will be able to fix it from a local console.''' If you lose working SSH access to your system after making these changes you'll need to connect in through the NetLab console interface (which is equivalent to physical access) and find and correct your configuration issues.
	* Using the '''ifdown''' and '''ifup''' command, we are going to restart the network interface, this step is required to apply the change.		* Using the '''ifdown''' and '''ifup''' command, we are going to restart the network interface, this step is required to apply the change.
	'' Note: A good method to watch this change is to have to ping windows open on your local machine ping both your old IP address and your new IP address with a '''ping 172.17.50.xx -t''' this will allow you to see how quickly the change will happen. The first image below is with the DHCP address, the second is after the static address is applied.		:'' Note: A good method to watch this change is to have to ping windows open on your local machine ping both your old IP address and your new IP address with a '''ping 172.17.50.xx -t''' this will allow you to see how quickly the change will happen. The first image below is with the DHCP address, the second is after the static address is applied.
	:[[File:Lab5_ping_ifup_ifdown.png\|link=https://wiki.ihitc.net/mediawiki/images/2/2f/Lab5_ping_ifup_ifdown.png\|500px]]		:[[File:Lab5_ping_ifup_ifdown.png\|link=https://wiki.ihitc.net/mediawiki/images/2/2f/Lab5_ping_ifup_ifdown.png\|500px]]
	:[[Media:Lab5_ping_ifup_ifdown.png\|Click here for a larger image]]		:[[Media:Lab5_ping_ifup_ifdown.png\|Click here for a larger image]]

MikeTieden: /* Introduction */

2021-02-14T01:18:58Z

Introduction

← Older revision		Revision as of 01:18, 14 February 2021
Line 7:		Line 7:
	*Explore the standard log files on your system.		*Explore the standard log files on your system.

	You will ~~use~~ the following commands:		You will be introduced to the following commands:

	*'''[https://linux.die.net/man/8/ifup ifup]'''		*'''[https://linux.die.net/man/8/ifup ifup]'''