Category: Jons Thoughts

Jon’s Thoughts

Posted on

What to live by. 2nd Amendment

Shooting Advice
Some words to the wise. Shooting Advice from various Concealed Carry Instructors. If you own a gun, you will appreciate this. If not, you should get one and learn how to use it:

A: Guns have only two enemies: rust and politicians.

B: Its always better to be judged by 12 than carried by 6.

C: Cops carry guns to protect themselves, not you.

D: Never let someone or something that threatens you get inside arms length.

E: Never say “I’ve got a gun.” If you need to use deadly force, the first sound they hear should be the safety clicking off. (I prefer the sound of a slug being chambered when you cock a shotgun)

F: The average response time of a 911 call is 23 minutes, the response time of a .357 is 1400 feet per second.

G: The most important rule in a gunfight is: Always win – cheat if necessary.

H: Make your attacker advance through a wall of bullets . . . You may get killed with your own gun, but he’ll have to beat you to death with it, cause it’ll be empty.
If you’re in a gun fight:
1. If you’re not shooting, you should be loading.
2. If you’re not loading, you should be moving,
3. If you’re not moving’, you’re dead.

J: In a life and death situation, do something . . . It may be wrong, but do something!

K: If you carry a gun, people call you paranoid. Nonsense! If you have a gun, what do you have to be paranoid about? (I call it being prepared)

L: You can say ‘stop’ or ‘alto’ or any other word, but a large bore muzzle pointed at someone’s head is pretty much a universal language. AMEN!

M: You cannot save the planet, but you may be able to save yourself and your family.

If you believe in the 2nd Amendment, please forward.

Posted on

Turn a Windows 8.1 PC Into a Wi-Fi Hotspot with the Command Prompt

1.   Using Windows’ Command Prompt, you can create a virtual network and share it to provide internet access to other devices. Launch a Command Prompt with Administrator privileges and enter the following command:

  1. netsh wlan set hostednetwork mode=allow ssid=wifi key=password

    Change the SSID value to choose a different name if you want, and use “key” to set a password. This will create a virtual network adapter.

  2. Start the new virtual adapter by running the following command: 
    netsh wlan start hostednetwork
  3. Go to the Control Panel and open up the Network and Sharing Center. You should see your new virtual adapter listed there (as shown in the screenshot above). Click the “Local Area Connection” link (or whatever shows up next to “Connections”).
  4. Click the Properties button in the window that appears.
  5. Head to the Sharing tab and then check the “Allow other network users to connect through this computer’s Internet connection” box.
  6. Use the drop down menu to select the virtual network adaptor you’ve created.
  7. Click OK followed by Close.

You should now be able to connect other devices to the network you created and enjoy a shared internet connection.

http://lifehacker.com/turn-a-windows-8-1-pc-into-a-wi-fi-hotspot-with-the-com-1593327340?utm_campaign=socialflow_lifehacker_facebook&utm_source=lifehacker_facebook&utm_medium=socialflow

Posted on

Windows 7: SSD Alignment

Verification

If you want to verify the alignment (e.g. for a SSD where you are not certain whether the proper alignment was done), you use the following commands.

Diskpart
List disk
Select disk n
List partition

Now you should see a result like this.

Partition ### Type Size Offset
————- —————- ——- ——-
Partition 1 Primary 59 GB 1024 KB – but 64KB or any number divisible by 4 is also good

The offset (in KBs) has to be divisible by 4.

Note: Some readers and users of this tutorial got confused because the alignment numbers in a typical Windows7 installation are shown as:

1024KB for the 100MB partition
101MB for the next partition – which is most likely the C partition

They think that 101MB is not divisible by 4 and that there must be a problem. But that is not so. If you convert 101MBs into KBs (multiply by 1024), then the number is divisible by 4 and the partition is aligned.

Posted on

Replace Dead Raid-5 Disk

1. Drive errors or Failed Redundancy detected.
2. Add new hard drive to computer (you must have an available SATA or whatever connector available to do this).
3. Run “Repair Volume” and select the new drive as the replacement drive to fix the volume.
4. When the system is done “Resyncing” you can remove bad hard drive.
At this point if you want to or need to, you can unplug the new drive (which will cause your array to fault) and then plug it into the old drive’s spot. This is only necessaryfor “housekeeping” if you have your drives in specific spots. When you plug the new drive back in, your volume will resync an all will be good again.
One last thing, because Window Server doesn’t offer a nice way to see which drive is actually “Drive4” or what ever, here is a command line you can run that will display all your drives and their serial number. Open a command prompt and type in…
wmic DISKDRIVE GET DeviceID, SerialNumber
If you want to output that to a text file add this to the end of that (without the curly brackets) { >> “c:\drive list.txt”}
The >> tells your DOS command to output to a file. You can name the file anything you want (within reason of course).

Posted on

Basic Samba Share Ubuntu 12.04 Server.

Here are simple instructions for a simple samba file share on ubuntu 12.04 server.

All commands are ran as root. If you are not root use sudo before the commands.

1. Install samba.

apt-get install samba

2. nano /etc/samba/smb.conf

[share]
comment = share
path = /share
browsable = yes
guest ok = no
read only = no
available = yes
public = no
writable = yes
valid users = user

3. (the share is called share. make sure you have a user called user on your server or replace with a valid user on your server)
save and restart samba.
4. restart smbd
restart nmbd

5. chmod -R 0775 share (You can use filezilla over sftp if you want)

https://help.ubuntu.com/12.04/serverguide/samba-fileserver.html
http://ubuntuserverhelp.com/basic-samba-configuration/

Posted on

Setting Static IP in Ubuntu Server 12.04.1

from the command line as root or su

nano /etc/network/interfaces

iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1 8.8.8.8

First change your adapter from dhcp to static.
Enter the information as above with your ip address settings.
crtl-x in nano and overwrite interfaces file.

restart networking with this command. (if over ssh make sure to adjust your ssh connection to the new ip address)

/etc/init.d/networking restart

Posted on

Enabling Telnetd on the RV042 / RV082 and RV016

This Tutorial was first shown on the RV042 Information Thread (started by noaaah)

I have now extracted the relevant information on enabling the Telnet Daemon, and found whilst playing with the ifconfig that the Port Interfaces MTU settings , amoungst other things, can be changed.

Enabling Telnetd

1. From your web browser type the following:

http://<Router IP Address>/sysinfo123.htm?ConsoleSimulation=1

eg: http://192.168.1.1/sysinfo123.htm?ConsoleSimulation=1

This has temporarily enabled Telnet. (A reboot and it has gone)

To make Telnet permanent

2. Using PuTTy or some other telnet client, logon to the routers OpenRG’s command line inferface. (cli)

telnet?192.168.1.1

Username:admin
Password:admin

rg_conf_set /nk/telnetd_enabled 1
flash_commit
reboot

cli example:

Username: admin
Password: ***********
> rg_conf_set /nk/telnetd_enabled 1
Returned 3280760
> flash_commit
Returned 0
> reboot

Once the router has rebooted the telnetd is now permanent. (except for full reset)

Now comes the fun part.

If you have the chance of having Dual WAN internet service from independant sources, like Cable and DSL, you could possibly have a problem on your hands. The fact is MTU settings for Cable defaults at 1500, and for DSL connections it is 1492. However in the GUI of the router you can only set a default MTU for both ports.

Note: MTU set to Auto = 576. this should NEVER be used. set to manual and use 1500 (Cable) or 1492 (DSL)

So how do we get both WANS to have a seperate MTU size? Telnet!!!

once again we goto Telnet and logon in. Now. the RV main OS is OpenRG. if has is own commands, but the easiest option is to load the BusyBox shell.

So one you have logged into OpenRG cli type:

> shell
Returned 0
>

BusyBox v0.50 (2006.06.08-12:45+0000) Built-in shell (lash)
Enter ‘help’ for a list of built-in commands.

/ #

From he we now type ifconfig (the linux variant of windows ipconfig)

LAN = ixp0
WAN1 = ixp1
WAN2 = ixp2

/ # ifconfig
ipsec0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xx.xx.xx.xxx Mask:255.255.252.0
UP NOTRAILERS RUNNING MULTICAST MTU:1440 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ipsec1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xx.xx.xx.xxx Mask:255.255.255.0
UP NOTRAILERS RUNNING MULTICAST MTU:1440 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ixp0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xx.xx.xx.xxx Bcast:xx.xx.xx.xxx Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:369768 errors:0 dropped:0 overruns:0 frame:0
TX packets:413845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:65344557 (62.3 Mb) TX bytes:186222521 (177.5 Mb)

ixp1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xx.xx.xx.xxx Bcast:xx.xx.xx.xxx Mask:255.255.252.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:367303 errors:0 dropped:0 overruns:0 frame:0
TX packets:355931 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:171435537 (163.4 Mb) TX bytes:60698066 (57.8 Mb)

ixp2 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xx.xx.xx.xxx Bcast:xx.xx.xx.xxx Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5932 (5.7 kb) TX bytes:2986 (2.9 kb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK NOTRAILERS RUNNING MULTICAST MTU:16436 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5004 (4.8 kb) TX bytes:5004 (4.8 kb)

/ #

Now I have highligthed the MTU settings of ixp0/ixp1 (WAN1/WAN2)

but if we had cable on WAN1 and DSL on WAN2 then WAN2 could run into problems. now we set MTU for ixp1 to 1492 so type:

/ # ifconfig ixp2 mtu 1492
/ #
and to check:

/ # ifconfig ixp2
ixp2 Link encap:Ethernet HWaddr 00:12:17:4D:0C:4E
inet addr:89.75.1.100 Bcast:89.75.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1492 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:8404 (8.2 kb) TX bytes:13189 (12.8 kb)

/ #

so now you have WAN1 MTU 1500 and WAN2 MTU 1492

One last MTU setting is for VPN tunnels. The MTU setting for ipsec0 (IPSec over WAN1) and ipsec1 (IPSec over WAN2) defaults to 1440 for IPSEC VPN Tunnels. If you need to change them you can. using this command within the Busybox shell of the RV0x2 Unit.

ifconfig <interface name> mtu bytes

Router Interface
LAN = ixp0
WAN = ixp1
WAN2 = ixp2

VPN IPSec Interfaces
WAN1 = ipsec0
WAN2 = ipsec1

Available commands for OpenRG 
Once you are logged onto the OpenRG cli, Press the TAB key. it will list all available commands.

Available commands for shell
Once you are logged onto the OpenRG cli, type “shell” (without the “”) then Press the TAB key. it will list all available commands.

Note: 

1. I was told a while back the RV016 has no known workaround yet for the Telnet feature. however this Tutorial does work on the RV016 with v2.0.10 firmware.

2. Rebooting the router will reset the MTU setting. no known fix as yet. if you find one let me know!

 

Original source:  http://www.linksysinfo.org/index.php?threads/enabling-telnetd-on-the-rv042-rv082-and-rv016.16069/

Posted on

Fing Usage

 

Configure the Network Discovery

Posted in Documentation

 

The network discovery provides a complete view of any network: fing engine automatically detects the underlying network type and uses the best technique to take the picture of the target network.

The best results are surely achieved on ethernet LAN’s (WiFi ones included), where fing can make use of the dedicated data-link layer discovery engine which is the faster one and the more accurate one also, as it’s able to detect all the hosts present in the network, super-firewalled ones included!

Discoveries performed on non-local networks (or non-ethernet networks) are handled by a network layer discovery engine, which relies on TCP/IP network layer, i.e. ICMP (ping) and TCP queries. When you start a discovery fing tells you the actual engine which is being used; in case of specific needs, it is possible to configure and tune each engine for optimal results, creating dedicated discovery profiles in the related configuration properties file: discovery.properties.

fing configuration files are all in the same format: properties format, i.e. a list of declarations like settings=value. Configuration files are placed in /etc/fing on Linux and Mac, while on Windows they are placed in your application data folder: %APPDATA%\Overlook\Fing\conf. On Windows you also have a shortcut to that folder in fing’s program files start menu.

When you start fing without arguments, it takes the nearest of your available networks and starts performing a discovery on it, reporting stuff directly on console. But you can perform discovery on any network, by providing your target network to fing in the command line:

fing -n 192.168.1.0/24 or fing -n www.overlooksoft.com/24

If you do not provide any output parameter, fing uses default ones (as specified in its fing.propertiesconfiguration file). But for a running discovery you can setup as many output formats as you need, by providing a command line argument like: fing -o setupFormat1 setupFormat2 … setupFormatN

The output format setup syntax is pretty simple: there are 2 main categories of output flows, table and log. The table flow produces a network table dump every time a discovery round is completed, while the log flow logs each network event as soon as it’s detected.

If you want to change the discovery round frequency, edit the related round.interval setting indiscovery.properties configuration file. Note that for each profile you declare you must provide both configurations for data-link and network layer discovery classes.

The log flow allows you to log network events in real-time, on the console itself or in a specific file. Currently there are two formats supported for log flows: text and CSV.E.g. to start fing producing textual log in console and a CSV log in a file:

fing -o log,text log,csv,my-network-log.csv

The table flow instead produces a network table view refreshed each time a discovery round finishes. The most popular formats are text and HTML but here it is the complete list: stext (short text for 80-columns console), text (plain text), html, csv, and xml. E.g. on Windows to make fing report network discovery to an HTML file on your desktop and also produce a short text console output both as table and log:

fing -o log,text table,stext table,html,"%USERPROFILE%\Desktop\network.html"

 

The network table report contains details for each host found in the network, and it’s refreshed in real-time at each round: IP address, MAC address, hostname and host friendly name. The latter is a friendly name you can associate to the hosts by means of the hosts.properties configuration file, where you are able to define your custom names for hosts (by IP address or MAC address) and for networks.

By default when you close fing the discovery session is lost, unless you want to save session data into a session file; in this case fing can be closed and restarted when you need, without losing any discovery session data. To exploit discovery session feature you have to simply provide fing the session file name to use. E.g. to make fing generate an HTML report and save session data in a folder named report:

fing -n 192.168.1.0/24 -o table,html,c:\report\lan.html --session c:\report\lansessiondata