rev.dennis

You utilize EC2 (which stands for Elastic Cloud) Launch Instance (I personally choose Red Hat since its used in more of a Business model) Create a Key Pair (it will download automatically and this file is very important for access) Accessing site chmod 600 /path/to/your_keyname.pem Get your EC2 name (something of the form *.compute.amazonaws.com). Now we can SSH into the EC2 instance by running the following command ssh -i /path/to/your_keyname.pem ubuntu@your_instance.compute.amazonaws.com

You utilize EC2 (which stands for Elastic Cloud) Launch Instance (I personally choose Red Hat since its used in more of a Business model) Create a Key Pair (it will download automatically and this file is very important for access) Accessing site chmod 600 /path/to/your_keyname.pem Get your EC2 name (something of the form *.compute.amazonaws.com). Now we can SSH into the EC2 instance by running the following command ssh -i /path/to/your_keyname.pem ubuntu@your_instance.compute.amazonaws.com

netcat is known as the swiss army of network tools found in linux. It's used for monitoring, testing and sending data across network connections and its free. By default, netcat (nc) operates by initiating a TCP connection to a remote host. The basic syntax is: nc [options] host port This attempts a TCP connection to the defined host on the port number specified. Something very similar to the old telnet command. Keep in mind your connection is entirely unencrypted. If you prefer to test a UDP connection instead of TCP, you can use the -u option nc -u host port Sometimes you prefer to test a range of ports nc host firstport-lastport Of course this is typically used with other flags. Netcat for Port Scanning nmap is a better tool for this sort of thing but you can use netcat to do this also to find what ports are open. We simply specify a range of ports to scan along with the -z option which performs a scan instead of trying to initiate a connection. For example, we can scan all ports up to 1000 by issuing: nc -z -v domain.com 1-1000 Notice I also threw in the -v option to tell netcat to provide more verbose information. You would get an output like the following: nc: connect to domain.com port 1 (tcp) failed: Connection refused nc: connect to domain.com port 2 (tcp) failed: Connection refused nc: connect to domain.com port 3 (tcp) failed: Connection refused nc: connect to domain.com port 4 (tcp) failed: Connection refused nc: connect to domain.com port 5 (tcp) failed: Connection refused nc: connect to domain.com port 6 (tcp) failed: Connection refused nc: connect to domain.com port 7 (tcp) failed: Connection refused . . . Connection to domain.com 22 port [tcp/ssh] succeeded! . . . If you know the IP address you want to scan on instead of domain name it will go much faster if you don't need to resolve the address using DNS, but you have to include in the command to not use DNS to resolve. Something like this nc -z -n -v 12.34.56.78 1-1000 You can also start filtering on the results like this... nc -z -n -v 12.34.56.78 1-1000 2>&1 | grep succeeded Now it will only show successful connections on the successful port. usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length] [-P proxy_username] [-p source_port] [-q seconds] [-s source] [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol] [-x proxy_address[:port]] [destination] [port] The options are as follows: -4 Forces nc to use IPv4 addresses only. -6 Forces nc to use IPv6 addresses only. -b Allow broadcast. -C Send CRLF as line-ending. -D Enable debugging on the socket. -d Do not attempt to read from stdin. -h Prints out nc help. -I length Specifies the size of the TCP receive buffer. -i interval Specifies a delay time interval between lines of text sent and received. Also causes a delay time between connections to multiple ports. -k Forces nc to stay listening for another connection after its current connection is completed. It is an error to use this option without the -l option. -l Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. It is an error to use this option in conjunction with the -p, -s, or -z options. Additionally, any timeouts specified with the -w option are ignored. -n Do not do any DNS or service lookups on any specified addresses, hostnames or ports. -O length Specifies the size of the TCP send buffer. -P proxy_username Specifies a username to present to a proxy server that requires authentication. If no username is specified then authentication will not be attempted. Proxy authentication is only supported for HTTP CONNECT proxies at present. -p source_port Specifies the source port nc should use, subject to privilege restrictions and availability. -q seconds after EOF on stdin, wait the specified number of seconds and then quit. If seconds is negative, wait forever. -r Specifies that source and/or destination ports should be chosen randomly instead of sequentially within a range or in the order that the system assigns them. -S Enables the RFC 2385 TCP MD5 signature option. -s source Specifies the IP of the interface which is used to send the packets. For UNIX-domain datagram sockets, specifies the local temporary socket file to create and use so that datagrams can be received. It is an error to use this option in conjunction with the -l option. -T toskeyword Change IPv4 TOS value. toskeyword may be one of critical, inetcontrol, lowcost, lowdelay, netcontrol, throughput, reliability, or one of the DiffServ Code Points: ef, af11 ... af43, cs0 ... cs7; or a number in either hex or decimal. -t Causes nc to send RFC 854 DON'T and WON'T responses to RFC 854 DO and WILL requests. This makes it possible to use nc to script telnet sessions. -U Specifies to use UNIX-domain sockets. -u Use UDP instead of the default option of TCP. For UNIX-domain sockets, use a datagram socket instead of a stream socket. If a UNIX-domain socket is used, a temporary receiving socket is created in /tmp unless the -s flag is given. -V rtable Set the routing table to be used. The default is 0. -v Have nc give more verbose output. -w timeout Connections which cannot be established or are idle timeout after timeout seconds. The -w flag has no effect on the -l option, i.e. nc will listen forever for a connection, with or without the -w flag. The default is no timeout. -X proxy_protocol Requests that nc should use the specified protocol when talking to the proxy server. Supported protocols are â4â v.4), â5âconnectâ -x proxy_address[:port] Requests that nc should connect to destination using a proxy at proxy_address and port. If port is not specified, the well-known port for the proxy protocol is used (1080 for SOCKS, 3128 for HTTPS). -Z DCCP mode. -z Specifies that nc should just scan for listening daemons, without sending any data to them. It is an error to use this option in conjunction with the -l option. destination can be a numerical IP address or a symbolic hostname (unless the -n option is given). In general, a destination must be specified, unless the -l option is given (in which case the local host is used). For UNIX-domain sockets, a destination is required and is the socket path to connect to (or listen on if the -l option is given). port can be a single integer or a range of ports. Ranges are in the form nn-mm. In general, a destination port must be speciâ fied, unless the -U option is given.

netcat is known as the swiss army of network tools found in linux. It's used for monitoring, testing and sending data across network connections and its free. By default, netcat (nc) operates by initiating a TCP connection to a remote host. The basic syntax is: nc [options] host port This attempts a TCP connection to the defined host on the port number specified. Something very similar to the old telnet command. Keep in mind your connection is entirely unencrypted. If you prefer to test a UDP connection instead of TCP, you can use the -u option nc -u host port Sometimes you prefer to test a range of ports nc host firstport-lastport Of course this is typically used with other flags. Netcat for Port Scanning nmap is a better tool for this sort of thing but you can use netcat to do this also to find what ports are open. We simply specify a range of ports to scan along with the -z option which performs a scan instead of trying to initiate a connection. For example, we can scan all ports up to 1000 by issuing: nc -z -v domain.com 1-1000 Notice I also threw in the -v option to tell netcat to provide more verbose information. You would get an output like the following: nc: connect to domain.com port 1 (tcp) failed: Connection refused nc: connect to domain.com port 2 (tcp) failed: Connection refused nc: connect to domain.com port 3 (tcp) failed: Connection refused nc: connect to domain.com port 4 (tcp) failed: Connection refused nc: connect to domain.com port 5 (tcp) failed: Connection refused nc: connect to domain.com port 6 (tcp) failed: Connection refused nc: connect to domain.com port 7 (tcp) failed: Connection refused . . . Connection to domain.com 22 port [tcp/ssh] succeeded! . . . If you know the IP address you want to scan on instead of domain name it will go much faster if you don't need to resolve the address using DNS, but you have to include in the command to not use DNS to resolve. Something like this nc -z -n -v 12.34.56.78 1-1000 You can also start filtering on the results like this... nc -z -n -v 12.34.56.78 1-1000 2>&1 | grep succeeded Now it will only show successful connections on the successful port. usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length] [-P proxy_username] [-p source_port] [-q seconds] [-s source] [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol] [-x proxy_address[:port]] [destination] [port] The options are as follows: -4 Forces nc to use IPv4 addresses only. -6 Forces nc to use IPv6 addresses only. -b Allow broadcast. -C Send CRLF as line-ending. -D Enable debugging on the socket. -d Do not attempt to read from stdin. -h Prints out nc help. -I length Specifies the size of the TCP receive buffer. -i interval Specifies a delay time interval between lines of text sent and received. Also causes a delay time between connections to multiple ports. -k Forces nc to stay listening for another connection after its current connection is completed. It is an error to use this option without the -l option. -l Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. It is an error to use this option in conjunction with the -p, -s, or -z options. Additionally, any timeouts specified with the -w option are ignored. -n Do not do any DNS or service lookups on any specified addresses, hostnames or ports. -O length Specifies the size of the TCP send buffer. -P proxy_username Specifies a username to present to a proxy server that requires authentication. If no username is specified then authentication will not be attempted. Proxy authentication is only supported for HTTP CONNECT proxies at present. -p source_port Specifies the source port nc should use, subject to privilege restrictions and availability. -q seconds after EOF on stdin, wait the specified number of seconds and then quit. If seconds is negative, wait forever. -r Specifies that source and/or destination ports should be chosen randomly instead of sequentially within a range or in the order that the system assigns them. -S Enables the RFC 2385 TCP MD5 signature option. -s source Specifies the IP of the interface which is used to send the packets. For UNIX-domain datagram sockets, specifies the local temporary socket file to create and use so that datagrams can be received. It is an error to use this option in conjunction with the -l option. -T toskeyword Change IPv4 TOS value. toskeyword may be one of critical, inetcontrol, lowcost, lowdelay, netcontrol, throughput, reliability, or one of the DiffServ Code Points: ef, af11 ... af43, cs0 ... cs7; or a number in either hex or decimal. -t Causes nc to send RFC 854 DON'T and WON'T responses to RFC 854 DO and WILL requests. This makes it possible to use nc to script telnet sessions. -U Specifies to use UNIX-domain sockets. -u Use UDP instead of the default option of TCP. For UNIX-domain sockets, use a datagram socket instead of a stream socket. If a UNIX-domain socket is used, a temporary receiving socket is created in /tmp unless the -s flag is given. -V rtable Set the routing table to be used. The default is 0. -v Have nc give more verbose output. -w timeout Connections which cannot be established or are idle timeout after timeout seconds. The -w flag has no effect on the -l option, i.e. nc will listen forever for a connection, with or without the -w flag. The default is no timeout. -X proxy_protocol Requests that nc should use the specified protocol when talking to the proxy server. Supported protocols are â4â v.4), â5âconnectâ -x proxy_address[:port] Requests that nc should connect to destination using a proxy at proxy_address and port. If port is not specified, the well-known port for the proxy protocol is used (1080 for SOCKS, 3128 for HTTPS). -Z DCCP mode. -z Specifies that nc should just scan for listening daemons, without sending any data to them. It is an error to use this option in conjunction with the -l option. destination can be a numerical IP address or a symbolic hostname (unless the -n option is given). In general, a destination must be specified, unless the -l option is given (in which case the local host is used). For UNIX-domain sockets, a destination is required and is the socket path to connect to (or listen on if the -l option is given). port can be a single integer or a range of ports. Ranges are in the form nn-mm. In general, a destination port must be speciâ fied, unless the -U option is given.

When you need to generate a sha256 key, use linux.. its so easy. echo -n worksux | sha256sum

When you need to generate a sha256 key, use linux.. its so easy. echo -n worksux | sha256sum

Reduce the Risk of Change, Improve Efficiency, and Ensure Security Policy Enforcement NetMRI provides automatic network discovery, switch port management, network change automation, and continuous security policy and configuration compliance management for multi-vendor routers, switches, and other layer-2 and layer-3 network devices. NetMRI is the only platform that supports traditional and virtual network constructs (such as VRF) for multi-vendor network automation. NetMRI helps customers move away from out-of-date spreadsheets, error-prone manual processes like scripts and CLI access, and ad hoc audit teams. Network automation reduces the risk of outages, frees networking staff from mundane tasks, and makes sure your network configurations actually stay within standards. infoblox-datasheet-netmri_1.pdf Appliance Versions: infoblox-datasheet-network-automation-appliances_0_0.pdf infoblox-note-automate-multi-vendor-network_0.pdf Network_Products_Device_Support_List.pdf

Reduce the Risk of Change, Improve Efficiency, and Ensure Security Policy Enforcement NetMRI provides automatic network discovery, switch port management, network change automation, and continuous security policy and configuration compliance management for multi-vendor routers, switches, and other layer-2 and layer-3 network devices. NetMRI is the only platform that supports traditional and virtual network constructs (such as VRF) for multi-vendor network automation. NetMRI helps customers move away from out-of-date spreadsheets, error-prone manual processes like scripts and CLI access, and ad hoc audit teams. Network automation reduces the risk of outages, frees networking staff from mundane tasks, and makes sure your network configurations actually stay within standards. infoblox-datasheet-netmri_1.pdf Appliance Versions: infoblox-datasheet-network-automation-appliances_0_0.pdf infoblox-note-automate-multi-vendor-network_0.pdf Network_Products_Device_Support_List.pdf

Was having a hell of time with any SQL repair or check showing: An error occured with the SQL server: mySQL query error: ALTER TABLE ipb_topic_views ADD INDEX views_tid (views_tid) So I opened a support ticket with Invision Power which replied .I replied with: They replied with simply stating My reply (kinda pissed they just threw it over the wall to have someone else deal with it: There final reply was So the mission started to figure this out. So what eventually worked was First... force a dump on the table mysqldump -f thezahco_hosangit-comDB ipb_topic_views This created ipb_topic_views.sql I also ran the following command, thinking I could just drop the table now mysql use thezahco_hosangit-comDB; SET FOREIGN_KEY_CHECKS=0; DROP TABLE ip_topic_views; SET FOREIGN_KEY_CHECKS=1; quit; Inside the ACP of IPB I was now able to fix the issue with Database Tools when prompted if they wanted to try and repair it (it worked)

Was having a hell of time with any SQL repair or check showing: An error occured with the SQL server: mySQL query error: ALTER TABLE ipb_topic_views ADD INDEX views_tid (views_tid) So I opened a support ticket with Invision Power which replied .I replied with: They replied with simply stating My reply (kinda pissed they just threw it over the wall to have someone else deal with it: There final reply was So the mission started to figure this out. So what eventually worked was First... force a dump on the table mysqldump -f thezahco_hosangit-comDB ipb_topic_views This created ipb_topic_views.sql I also ran the following command, thinking I could just drop the table now mysql use thezahco_hosangit-comDB; SET FOREIGN_KEY_CHECKS=0; DROP TABLE ip_topic_views; SET FOREIGN_KEY_CHECKS=1; quit; Inside the ACP of IPB I was now able to fix the issue with Database Tools when prompted if they wanted to try and repair it (it worked)

Gantry just released a plugin update to Joomla and after I applied this update when I attempted to utilize the p8bridge to go to phpbb3 I would receive the following error: I renamed .htaccess to htaccess.txt and went direct to the forum and it worked so I knew it was Joomla related. Went into the Gantry - system plugin and there is an option that says Compile Twig and it was set to Yes. Changed this to No and clicked Save and tried again... BAM! everything works.

Gantry just released a plugin update to Joomla and after I applied this update when I attempted to utilize the p8bridge to go to phpbb3 I would receive the following error: I renamed .htaccess to htaccess.txt and went direct to the forum and it worked so I knew it was Joomla related. Went into the Gantry - system plugin and there is an option that says Compile Twig and it was set to Yes. Changed this to No and clicked Save and tried again... BAM! everything works.

A common step in troubleshooting is finding out what not to troubleshoot. With a packet capture you can confirm things such as routing, firewall rules, and remote services. Layer 1[/b] hardware is probably on and functioning Layer 2 Addressing is likely working Layer 3 Routing would appear to be working Layer 4 Transport is likely working Layer 5(Session), Layer 6(presentation) and Layer 7(application) might not be working at this point, but you’ve ruled out several things that don’t need to be tested. You can do detailed packet captures that look for additional information to verify if layers 5,6 and 7 are working, but this should save you some time to know that layers 1-4 are operational. It’s possible that intermittent errors, or bandwidth related errors could be hiding, and a packet capture can still help you find this type of error too. Here are some tcpdump notes. Basic tcpdump flags [table][tr][td]-i [/td] [td]Specify which intterface to capture, defaults to lowest numbered interface[/td][/tr] [tr][td]-q[/td] [td]Quick output. Print less protocol information so output lines are shorter, easier to read.[/td][/tr] [tr][td]-X[/td] [td]Show binary and hex data[/td][/tr] [tr][td]-n[/td] [td]Do not perform DNS lookup, just show the IP[/td][/tr] [tr][td]-v[/td] [td]Show additional information, -vv shows more, -vvv shows even more[/td][/tr] [tr][td]-s [/td] [td]Size of the Packet, (-s 1514)[/td][/tr] [tr][td]-S[/td] [td]Print absolute, rather than relative TCP sequence numbers[/td][/tr] [tr][td]src (net)[/td] [td]The source IP of the filter (src 1.1.1.1). src net can be used to specify a network, in CIDR: (dst net 1.1.1.0/24)[/td][/tr] [tr][td]dst (net)[/td] [td]The destination IP of the filter (dst 1.1.1.1). dst net can be used to specify a network, in CIDR: (dst net 1.1.1.0/24)[/td][/tr] [tr][td](src|dst) port[/td] [td]which port specifically, can be named ports, or specific port. (dst port 80)[/td][/tr] [tr][td]-w [/td] [td]The name of the file to write out your packet capture to (-w filename.cap)[/td][/tr] [tr][td]and[/td] [td]combine filters (and src net 1.1.1.0/24)[/td][/tr] [tr][td]not[/td] [td]negate filters (and not dst port 22)[/td][/tr][/table] tcpdump filter examples Here is a list of several ways to build filters, and some of the more common ways that you might want to view data. tcpdump -nS Very basic communication. tcpdump -nnvvS Basic, verbose communication. tcpdump -nnvvXS Get the packet payload, but that’s all tcpdump -nnvvXSs 1514 Full packet capture with all details tcpdump host 1.2.3.4 Show traffic to and from 1.2.3.4 tcpdump src 1.2.3.4 Show all traffic from 1.2.3.4 tcpdump dst 4.3.2.1 Show all traffic to 4.3.2.1 tcpdump net 1.2.3.0/24 Look at traffic to and from 1.2.3.0/24 tcpdump port 3389 Remote Desktop example tcpdump udp and src port 53 specify protocol combined with src port (DNS filter example) tcpdump portrange 1000-2000 Do you need an explanation? If so, perhaps another article is better for you. tcpdump -i any -nnvvXSs 1514 -c 100 src 1.2.3.4 port 443 -w capturefile Capturing full packet, fully verbose, limit to 100 of them, with IP and port filter, write to capturefile for later analysis. tcpdump -nnvvXSs 1514 src net 192.168.0.0/16 and dst net 10.0.0.0/8 not dst port 22 Like previous tcpdump filter, but also limiting between 2 networks, and ignoring port 22 3 way Handshake Troubleshooting With tcpdump We are able to confirm routing, firewall rules, and remote service response by looking at the type of packet that comes back: tcpdump ‘tcp[13] & 2!=0’ SYN messages tell us that at least our client is sending it’s initial outbound message. If that’s all we see, then nothing is coming back and routing could be bad, or the remote server could be down. tcpdump ‘tcp[13] & 16!=0’ ACK is the acknowledge message. We can see that the traffic is going all the way to and from the client/server and the server is responding. tcpdump ‘tcp[13]=18’ SYN ACK packets shows active communication between client and server. Routes, ACLs, and Firewall rules are good. tcpdump ‘tcp[13] & 4!=0’ RST packets. RST packets are sent back from the service, so at least you know the path is good and not blocked by an ACL or firewall. tcpdump ‘tcp[13] & 1!=0’ FIN packets. FIN packets are sent back from the service, so you also know path and firewall or ACL rules are not blocking. tcpdump Statistics Often, on a network a few hosts will be infected, but it’s hard to tell which ones those hosts are. Here is a quick method to help you determine who is spewing the most traffic: First, get a packet capture of the data that is of interest to you, you can get basic packets, or all of it if you want to review it later. In my example I want to review it later, so I’m capturing the entire packet, with a bit of detail: # tcpdump -i any -nn -X -vv -s 1514 -c 1000 -w packetcap.cap Next run it through awk to display some statistical information: # tcpdump -nr packetcap.cap | awk '{print }' | grep -oE '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}' | sort | uniq -c | sort -n

A common step in troubleshooting is finding out what not to troubleshoot. With a packet capture you can confirm things such as routing, firewall rules, and remote services. Layer 1[/b] hardware is probably on and functioning Layer 2 Addressing is likely working Layer 3 Routing would appear to be working Layer 4 Transport is likely working Layer 5(Session), Layer 6(presentation) and Layer 7(application) might not be working at this point, but you’ve ruled out several things that don’t need to be tested. You can do detailed packet captures that look for additional information to verify if layers 5,6 and 7 are working, but this should save you some time to know that layers 1-4 are operational. It’s possible that intermittent errors, or bandwidth related errors could be hiding, and a packet capture can still help you find this type of error too. Here are some tcpdump notes. Basic tcpdump flags [table][tr][td]-i [/td] [td]Specify which intterface to capture, defaults to lowest numbered interface[/td][/tr] [tr][td]-q[/td] [td]Quick output. Print less protocol information so output lines are shorter, easier to read.[/td][/tr] [tr][td]-X[/td] [td]Show binary and hex data[/td][/tr] [tr][td]-n[/td] [td]Do not perform DNS lookup, just show the IP[/td][/tr] [tr][td]-v[/td] [td]Show additional information, -vv shows more, -vvv shows even more[/td][/tr] [tr][td]-s [/td] [td]Size of the Packet, (-s 1514)[/td][/tr] [tr][td]-S[/td] [td]Print absolute, rather than relative TCP sequence numbers[/td][/tr] [tr][td]src (net)[/td] [td]The source IP of the filter (src 1.1.1.1). src net can be used to specify a network, in CIDR: (dst net 1.1.1.0/24)[/td][/tr] [tr][td]dst (net)[/td] [td]The destination IP of the filter (dst 1.1.1.1). dst net can be used to specify a network, in CIDR: (dst net 1.1.1.0/24)[/td][/tr] [tr][td](src|dst) port[/td] [td]which port specifically, can be named ports, or specific port. (dst port 80)[/td][/tr] [tr][td]-w [/td] [td]The name of the file to write out your packet capture to (-w filename.cap)[/td][/tr] [tr][td]and[/td] [td]combine filters (and src net 1.1.1.0/24)[/td][/tr] [tr][td]not[/td] [td]negate filters (and not dst port 22)[/td][/tr][/table] tcpdump filter examples Here is a list of several ways to build filters, and some of the more common ways that you might want to view data. tcpdump -nS Very basic communication. tcpdump -nnvvS Basic, verbose communication. tcpdump -nnvvXS Get the packet payload, but that’s all tcpdump -nnvvXSs 1514 Full packet capture with all details tcpdump host 1.2.3.4 Show traffic to and from 1.2.3.4 tcpdump src 1.2.3.4 Show all traffic from 1.2.3.4 tcpdump dst 4.3.2.1 Show all traffic to 4.3.2.1 tcpdump net 1.2.3.0/24 Look at traffic to and from 1.2.3.0/24 tcpdump port 3389 Remote Desktop example tcpdump udp and src port 53 specify protocol combined with src port (DNS filter example) tcpdump portrange 1000-2000 Do you need an explanation? If so, perhaps another article is better for you. tcpdump -i any -nnvvXSs 1514 -c 100 src 1.2.3.4 port 443 -w capturefile Capturing full packet, fully verbose, limit to 100 of them, with IP and port filter, write to capturefile for later analysis. tcpdump -nnvvXSs 1514 src net 192.168.0.0/16 and dst net 10.0.0.0/8 not dst port 22 Like previous tcpdump filter, but also limiting between 2 networks, and ignoring port 22 3 way Handshake Troubleshooting With tcpdump We are able to confirm routing, firewall rules, and remote service response by looking at the type of packet that comes back: tcpdump ‘tcp[13] & 2!=0’ SYN messages tell us that at least our client is sending it’s initial outbound message. If that’s all we see, then nothing is coming back and routing could be bad, or the remote server could be down. tcpdump ‘tcp[13] & 16!=0’ ACK is the acknowledge message. We can see that the traffic is going all the way to and from the client/server and the server is responding. tcpdump ‘tcp[13]=18’ SYN ACK packets shows active communication between client and server. Routes, ACLs, and Firewall rules are good. tcpdump ‘tcp[13] & 4!=0’ RST packets. RST packets are sent back from the service, so at least you know the path is good and not blocked by an ACL or firewall. tcpdump ‘tcp[13] & 1!=0’ FIN packets. FIN packets are sent back from the service, so you also know path and firewall or ACL rules are not blocking. tcpdump Statistics Often, on a network a few hosts will be infected, but it’s hard to tell which ones those hosts are. Here is a quick method to help you determine who is spewing the most traffic: First, get a packet capture of the data that is of interest to you, you can get basic packets, or all of it if you want to review it later. In my example I want to review it later, so I’m capturing the entire packet, with a bit of detail: # tcpdump -i any -nn -X -vv -s 1514 -c 1000 -w packetcap.cap Next run it through awk to display some statistical information: # tcpdump -nr packetcap.cap | awk '{print }' | grep -oE '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}' | sort | uniq -c | sort -n

Yes CentOS 7 is out but it won't work on my old HP Proliant DL380 G4 so I am using my old CentOS 6.5 install CD and it is working great. So what did I do.... First if you have a Smart Array, I configured two of the 6 drives in 1+0 for the default drive and the other 4 are RAID 5. Once these logical drives are configured you can move on and if you don't have a smart array, you can also move on. CentOS booted up, I picked my location information and I did configure network device just because it makes it easier later. When CentOS boots up, I had no network connection. I did a ifconfig and all it showed me was the loopback (lo) interface. vi /etc/sysconfig/network-sccripts/ifconfig-eth0 had to change ONBOOT=no to ONBOOT=yes and saved my changes Ran /etc/init.d/network restart I was able to ping 8.8.8.8 (which is google DNS server) Next is to update the old CentOS system so I ran yum -y update This installed 561 updates on my system.

Yes CentOS 7 is out but it won't work on my old HP Proliant DL380 G4 so I am using my old CentOS 6.5 install CD and it is working great. So what did I do.... First if you have a Smart Array, I configured two of the 6 drives in 1+0 for the default drive and the other 4 are RAID 5. Once these logical drives are configured you can move on and if you don't have a smart array, you can also move on. CentOS booted up, I picked my location information and I did configure network device just because it makes it easier later. When CentOS boots up, I had no network connection. I did a ifconfig and all it showed me was the loopback (lo) interface. vi /etc/sysconfig/network-sccripts/ifconfig-eth0 had to change ONBOOT=no to ONBOOT=yes and saved my changes Ran /etc/init.d/network restart I was able to ping 8.8.8.8 (which is google DNS server) Next is to update the old CentOS system so I ran yum -y update This installed 561 updates on my system.

I've been fighting an issue with EasyBlog where no matter what I do the guest user can not see the full post of any blog unless they log into the site. This is nice for some blogs but the majority I want guest users to just be able to browse the posts. Opened a ticket with StackIdeas tonight so we'll see what they come up with.

I've been fighting an issue with EasyBlog where no matter what I do the guest user can not see the full post of any blog unless they log into the site. This is nice for some blogs but the majority I want guest users to just be able to browse the posts. Opened a ticket with StackIdeas tonight so we'll see what they come up with.

Upgraded JomSocial on the website from 4.1.1 to 4.1.4 and it took a very long time which made me believe it wasn't going to work.

Upgraded JomSocial on the website from 4.1.1 to 4.1.4 and it took a very long time which made me believe it wasn't going to work.

What a big pain in the butt this install has been so far. The install was easy but I selected multi-site and it instantly broke anything to do with wordpress. Oddly, the install doesn't come with a htaccess.txt file with what is required that you can later rename to .htaccess, you must follow the documentation. Hopefully corephp support answers my support ticket eventually and I'll find out the answers. I did the best I can with the .htaccess file, I also added the required info in wp-config.php as it states but it blurs out the sitename so you have no idea what the format of the sitename is suppose to be (http:// included or not), so its a guessing game. I have cleared cache on my browser and I can not log into wp-admin no matter what I do. Recently I uninstalled and then removed the associated directory from the site (which the uninstall doesn't do) and reinstalled and no difference, still can't get in. You have to log into the database and remove anything that starts with wp_ to get back to the beginning to try again.

What a big pain in the butt this install has been so far. The install was easy but I selected multi-site and it instantly broke anything to do with wordpress. Oddly, the install doesn't come with a htaccess.txt file with what is required that you can later rename to .htaccess, you must follow the documentation. Hopefully corephp support answers my support ticket eventually and I'll find out the answers. I did the best I can with the .htaccess file, I also added the required info in wp-config.php as it states but it blurs out the sitename so you have no idea what the format of the sitename is suppose to be (http:// included or not), so its a guessing game. I have cleared cache on my browser and I can not log into wp-admin no matter what I do. Recently I uninstalled and then removed the associated directory from the site (which the uninstall doesn't do) and reinstalled and no difference, still can't get in. You have to log into the database and remove anything that starts with wp_ to get back to the beginning to try again.

To shut down Red Hat or CentOS Linux, the root user may issue the /sbin/shutdown command. The shutdown man page has a complete list of options, but the two most common uses are: /sbin/shutdown -h now/sbin/shutdown -r now After shutting everything down, the -h option halts the machine, and the -r option reboots.

To shut down Red Hat or CentOS Linux, the root user may issue the /sbin/shutdown command. The shutdown man page has a complete list of options, but the two most common uses are: /sbin/shutdown -h now/sbin/shutdown -r now After shutting everything down, the -h option halts the machine, and the -r option reboots.

I use to get this cool message of the day (motd) when I logged into by Ubuntu box and since upgrading I don't get it anymore. I use to get this: Now I get this: To get back the great motd I just had to run the following command: sudo run-parts /etc/update-motd.d/ | sudo tee /etc/motd