Kinky linux command-line - Revision history

Lilith2: /* Configuring network interfaces */

2015-12-09T14:27:41Z

‎Configuring network interfaces

Alex at 08:33, 11 September 2015

2015-09-11T08:33:33Z

Lilith2 at 19:40, 10 August 2015

2015-08-10T19:40:54Z

Lilith2: /* Networking concepts */

2015-07-31T22:15:20Z

‎Networking concepts

Lilith2 at 16:12, 30 July 2015

2015-07-30T16:12:51Z

Lilith2: /* Network connections */

2015-07-29T23:29:41Z

‎Network connections

Lilith2: /* Related */

2015-07-22T14:55:34Z

‎Related

Lilith2: /* Serial line IP */

2015-07-21T18:56:15Z

‎Serial line IP

Lilith2: /* Network exploitation and monitoring */

2015-07-21T09:25:25Z

‎Network exploitation and monitoring

Lilith2: /* Reconnaissance */

2015-07-21T09:22:14Z

‎Reconnaissance

@@ Line 998: / Line 998: @@
   $ sudo ifconfig eth0 down
-Use macchanger to randomly generate new MAC address and assign it to eth0 network interface:
+. Use macchanger to randomly generate new MAC address and assign it to eth0 network interface:
   <pre>$ sudo macchanger -r eth0
@@ Line 1,004: / Line 1,004: @@
 Faked MAC:   32:cf:cb:6c:63:cd (unknown)</pre>
-Enable eth0 network interface and check new MAC address:
+. Enable eth0 network interface and check new MAC address:
   <pre>$ sudo ifconfig eth0 up

← Older revision		Revision as of 08:33, 11 September 2015
Line 1,274:		Line 1,274:
	== References ==		== References ==

−	[[Category:~~Resources~~]]	+	[[Category:How_To]]

@@ Line 1,187: / Line 1,187: @@
 For configuring the I/O address, IRQ, and name of serial devices: http://rampex.ihep.su/Linux/linux_howto/html/tutorials/Serial-HOWTO-6.html
 == Resources ==
@@ Line 1,204: / Line 1,273: @@
 == References ==

@@ Line 791: / Line 791: @@
 Connecting to a network from a linux box is easy, and on occasion not. If a network interface does not come up or requires manual setup, there are many commands for configuring interfaces, checking network connections and setting up special routing. Once connection is up there are more commands for getting information about networks your machine is connected to.
-=== Networking concepts ===
+See [[Networking concepts]].
-−
-* ''The Transmission Control Protocol/Internet Protocol (TCP/IP)'' uses a client - server model for communications. The protocol defines the data packets transmitted (packet header, data section), data integrity verification (error detection bytes), connection and acknowledgement protocol, and re-transmission.
-* ''TCP/IP Time To Live (TTL)'' is a counting mechanism to determine how long a packet is valid before it reaches its destination. Each time a TCP/IP packet passes through a router it will decrement its TTL count. When the count reaches zero the packet is dropped by the router. This ensures that errant routing and looping aimless packets will not flood the network.
-* ''A Media Access Control address (MAC Address)'' is the network card address used for communication between other network devices on the subnet. This information is not routable. The ARP table maps a (global internet) TCP/IP address to the local hardware on the local network. The MAC address uniquely identifies each node of a network and is used by the Ethernet protocol.
-* Inbound traffic is captured based on <code>ARP</code> and <code>IP</code> address configuration. Outbound traffic is managed by ''routes''. Routing determines the path these packets take so that they are sent to their destinations. This is required for all IP traffic, local and remote, including when multiple network interfaces are available. Routes are held by the ''kernel routing table''.
-** ''Direct routing'' table entries occur when the source and destination hosts are on the same physical network and packets are sent directly from the source to the destination.
-** ''Indirect routing'' table entries occur when the source and destination hosts are on different physical networks. The destination host must be reached through one or more IP gateways. The first gateway is the only one which is known by the host system.
-** ''Default routing'' defines a gateway to use when the direct network route and the indirect host routes are not defined for a given IP address.
-* For ''static routes'' IP uses the routing table to determine where packets should be sent. First the packet is examined to see if its destination is for the local or a remote network. If a remote network, the routing table is consulted to determine the path. If there is no information in the routing table then the packet is sent to the default gateway. Static routes are set with the <code>route</code> command http://linux.die.net/man/8/route.
-* For ''dynamic routes'' the ''Routing Information Protocol (RIP)'' is used https://en.wikipedia.org/wiki/Routing_Information_Protocol. If multiple routes are possible, RIP will choose the shortest route (fewest hops between routers not physical distance). Routers use RIP to broadcast the routing table over UDP port 520. The routers then add new or improved routes to their routing tables.
-* Regular network exchanges of data are peer to peer unicast transactions. An HTTP request to a web server (TCP/IP), email SNMP (TCP/IP), DNS (UDP), FTP (TCP/IP), etc, are all peer to peer unicast transactions. If you want to transmit a video, audio or data stream to multiple nodes with one transmission stream instead of multiple individual peer to peer connections, you can use ''multicasting''. Multicast and a network broadcast are different. Multicast is a UDP broadcast only and the messages are only "heard" by the nodes on the network that have "joined the multicast group", which are those that are interested in the information https://netref.soe.ucsc.edu/osnl/65.
 === Configuring network interfaces ===

@@ Line 209: / Line 209: @@
 The example then looks like <code>111 101 101</code><sub>2</sub>
-) Convert binary code to octal code. If not familiar with number conversions, a decent tutorial can be found in http://www.cstutoringcenter.com/tutorials/general/convert.php
+) Convert binary code. If not familiar with number conversions, a decent tutorial can be found in http://www.cstutoringcenter.com/tutorials/general/convert.php
-(111)<sub>2</sub> = 2<sup>0</sup> + 2<sup>1</sup> + 2<sup>2</sup> = 1 + 2 + 2*2 = 7<sub>8</sub>
+(111)<sub>2</sub> = 2<sup>0</sup> + 2<sup>1</sup> + 2<sup>2</sup> = 1 + 2 + 2*2 = 7<sub>10</sub>
-(101)<sub>2</sub> = 2<sup>0</sup> + 2<sup>2</sup> = 1 + 2*2 = 5<sub>8</sub>
+(101)<sub>2</sub> = 2<sup>0</sup> + 2<sup>2</sup> = 1 + 2*2 = 5<sub>10</sub>
-(100)<sub>2</sub> = 2<sup>2</sup> = 2*2 = 4<sub>8</sub>
+(100)<sub>2</sub> = 2<sup>2</sup> = 2*2 = 4<sub>10</sub>
-(001)<sub>2</sub> = 2<sup>0</sup> = 1 <sub>8</sub>
+(001)<sub>2</sub> = 2<sup>0</sup> = 1 <sub>10</sub>
-The example then looks like <code>7 5 5</code><sub>8</sub>. So the permissions for this <code>Pictures</code> directory in octal notation are 755 <sub>8</sub> and the base, 8, is often not mentioned.
+The example then looks like <code>7 5 5</code><sub>10</sub>. So the permissions for this <code>Pictures</code> directory are 755 <sub>10</sub> and the base, 10, is often not mentioned.
 '''Handy file permissions mental shortcuts:'''

@@ Line 1,245: / Line 1,245: @@
 * [[Linux security]]
 * [[Anonymising your traffic with linux]]
-* [[Clean up all teh things]]
+* [[Clean up all the things]]
 * [[Shell scripting]]
 * [[Encrypting everything]]
 == References ==

@@ Line 1,223: / Line 1,223: @@
 === Serial line IP ===
-* PPP
+* Point-to-Point Protocol (PPP) is the most common form of IP over serial line and is the most common technique used by telephone dial-up ISPs.
-* SLIP
+* Serial Line IP (SLIP) is older than PPP and less capable.
-* PLIP
+* Parallel Line IP (PLIP) is a computer networking protocol for direct computer-to-computer communications using the parallel port normally used for connections to a printer. It can be used for installing debian on machines without ethernet card https://www.debian.org/releases/squeeze/i386/apds04.html.en.
 To display detected serial support run <code>dmesg</code>:

← Older revision		Revision as of 09:25, 21 July 2015
Line 1,233:		Line 1,233:

	For configuring the I/O address, IRQ, and name of serial devices: http://rampex.ihep.su/Linux/linux_howto/html/tutorials/Serial-HOWTO-6.html		For configuring the I/O address, IRQ, and name of serial devices: http://rampex.ihep.su/Linux/linux_howto/html/tutorials/Serial-HOWTO-6.html
−
−	~~== Network exploitation and monitoring ==~~
−	<em>Warning: Do not execute these on a network or system that you do not own. Execute only on your own network or system for learning purposes. Do not execute these on any production network or system.</em>
−
−	~~=== Spoofing ===~~
−
−	~~=== Questioning servers ===~~
−
−	~~=== Brute-forcing authentication ===~~
−
−	~~=== Traffic filtering ===~~
−
−	~~=== Testing SSL implementation ===~~

	== Resources ==		== Resources ==

← Older revision		Revision as of 09:22, 21 July 2015
Line 1,233:		Line 1,233:

	For configuring the I/O address, IRQ, and name of serial devices: http://rampex.ihep.su/Linux/linux_howto/html/tutorials/Serial-HOWTO-6.html		For configuring the I/O address, IRQ, and name of serial devices: http://rampex.ihep.su/Linux/linux_howto/html/tutorials/Serial-HOWTO-6.html
−
−	~~== Reconnaissance ==~~
−
−	~~=== Querying DNS servers ===~~
−	The <em>whois</em> system is used by system administrators to obtain contact information for IP address assignments or domain name administrators. <em>Dig</em> is a networking tool that can query DNS servers for information. It can be very helpful for diagnosing problems with domain pointing and is a good way to verify that your server configuration is working. An alternative to <em>dig</em> is a command called <em>host</em>. This command functions in a very similar way to dig, with many of the same options. And if <em>dig</em> and <em>whois</em> do not provide you with enough information, tools like <em>dnsmap</em> and <em>dnsenum</em> can be handy.
−
−	~~=== Enumerating targets ===~~
−	Enumerating targets on your local network can be done with <em>nmap</em>, <em>arping</em>, <em>hping</em> and <em>fping</em>. The last three allow for constructing arbitrary packets for almost any networking protocol, for analysis of replies.

	== Network exploitation and monitoring ==		== Network exploitation and monitoring ==