How to Create a PayTM Account & PayTM Wallet [Guide]

Here i have shown you the exact step by step guide for creating a paytm account and paytm wallet. This guide will be helpful to you when you will be signing up for your paytm account.

So if you are not a paytm user yet, then it’s not late you should create your paytm account right now.

It’s very easy to create a paytm account. But, I think many people will still find this guide helpful. Here I have given complete details about how to create a paytm account. I have attached some screenshots which will help you to understand the entire process better. So don’t waste any more time and jump into the main part of the post below.

How to Set Up a Paytm Account

For creating a paytm account, you have two options, either you can download the paytm app, or you can go to their website. For this instance, I’m presuming that you guys will step up your paytm account from the paytm website. So lets Start following the step by step guide below.

Networking Basics: How ARP Works

Understanding how ARP works can allow you to do many useful things. For example, a machine was recently set up accidentally with the IP address of another machine. This is an hour away, and accessing the system was tested before leaving the location, but after traveling back another machine was responding to that IP. Knowing ARP can allow you to fix this without having to go back to the location.

Networking layers

Outside of the classroom and interview environments, the OSI model network layers boil down mainly to layers 2, 3, and 7. The number of times I've encountered the other layers in the real world over the last several decades amounts to only a handful. For ARP, we are talking about layer 2.

Layer 2 is the level that lower-end switches operate at, and is all about the MAC addresses. The MAC address is an ID, typically assigned by the manufacturer (though usually can be changed by software), which you see next to "HWaddr" if you run "ifconfig". It is a string of 6 pairs of hex digits, usually with the pairs separated by colons, for example: "3c:97:0e:44:be:ef".

The MAC address is how machines on a subnet communicate. When machine A sends packets to another machine on its subnet, it sends it using the MAC address. When sending a packet to a machine on the public Internet, the packet is sent to the MAC address of the router interface that is the default gateway. IP addresses are used to figure out the MAC address to send to using ARP.

ARP Basics

ARP stands for Address Resolution Protocol. When you try to ping an IP address on your local network, say 192.168.1.1, your system has to turn the IP address 192.168.1.1 into a MAC address. This involves using ARP to resolve the address, hence its name.

Systems keep an ARP look-up table where they store information about what IP addresses are associated with what MAC addresses. When trying to send a packet to an IP address, the system will first consult this table to see if it already knows the MAC address. If there is a value cached, ARP is not used.

If the IP address is not found in the ARP table, the system will then send a broadcast packet to the network using the ARP protocol to ask "who has 192.168.1.1". Because it is a broadcast packet, it is sent to a special MAC address that causes all machines on the network to receive it. Any machine with the requested IP address will reply with an ARP packet that says "I am 192.168.1.1", and this includes the MAC address which can receive packets for that IP.

The ARP Table

In the case where multiple machines have the same IP address, you may get multiple responses. The one that gets placed in the ARP table can vary depending on the networking implementation, how busy hosts are, and how quickly they respond, etc... Once it's in the ARP table, that MAC address is cached and continues to be used until the entry expires or is forcibly cleared. At that point another ARP is done and you may or may not get the same MAC in the ARP table.

On Linux systems, you can display the ARP table with the command "arp -an". For example:

# arp -an | grep 10
? (10.241.1.114) at 00:25:90:3e:dc:fc [ether] on vlan241
? (10.252.1.8) at 00:c0:b7:76:ac:19 [ether] on vlan244
? (10.252.1.9) at 00:c0:b7:76:ae:56 [ether] on vlan244
? (10.241.1.111) at 00:30:48:f2:23:fd [ether] on vlan241
? (10.252.1.6) at 00:c0:b7:74:fb:9a [ether] on vlan244
? (10.241.1.121) at 00:25:90:2c:d4:f7 [ether] on vlan241
[...]

An entry for the IP address 192.168.1.1 can be deleted from the ARP table using the command "arp -d 192.168.1.1". The next time a packet needs to go to that IP, a new ARP negotiation will be done.

If you want to make a specific MAC address be used for an IP, you can use the command: "arp -s 192.168.1.1 [MAC ADDR]".

If you are in a situation where you have two machines that have the same IP address, the above can be used so that you access a specific one. How do you know what the MAC addresses are?

Figuring out the MAC Address

If you are able to access the system, you can find the MAC address by using the "ifconfig" or "ip addr ls" commands. That doesn't help if you are in a remote location and accidentally gave the same IP address to two machines though.

tcpdump is a wonderful tool for this. Open two terminals on a system on the network that has two machines with the same IP. In one, run "tcpdump -lni any arp", and in the other delete the ARP entry with "arp -d [IP ADDRESS]". Now ping that IP address, you should see some ARP packets go by.

For example, running the tcpdump in the background and then doing the arp and ping in another shell instance:

[root@host ~]# tcpdump -lni any arp & ( sleep 1; arp -d 10.0.0.254; ping -c1 -n 10.0.0.254 )
[1] 31920
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
17:58:02.155495 arp who-has 10.2.1.224 tell 10.2.1.253
17:58:02.317444 arp who-has 10.0.0.96 tell 10.0.0.253
17:58:02.370446 arp who-has 10.3.1.12 tell 10.3.1.61
PING 10.0.0.254 (10.0.0.254) 56(84) bytes of data.
17:58:02.636895 arp who-has 10.0.0.254 tell 10.0.0.24
17:58:02.637160 arp reply 10.0.0.254 is-at 00:25:90:03:b3:98
64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=1.23 ms

--- 10.0.0.254 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.238/1.238/1.238/0.000 ms 

In this case, there is only one system at the MAC address 10.0.0.254, and we can see it in the "is-at" line above. As you can see above, if you are on a busy network or busy machine, you may get a lot of ARP packets and you will have to hunt to find the one you need.

Gratuitous ARP

Normally, ARP "is-at" replies, which cause machines to update their ARP tables, are sent in response to an ARP "who-has" request packet. However, if an IP address changes the MAC address it is at, for example if you move a service from one machine to another, other machines on that subnet will continue to cache the old value for some period of time.

You can cause machines on a subnet to update their ARP tables by broadcasting an ARP reply packet which is not in response to a specific request. This is called a "Gratuitous ARP".

You can send a Gratuitous ARP using the "arping" command. Say that your IP address is 172.16.42.161 on interface eth0:

arping -A -I eth0 172.16.42.161

This will send "ARP Reply" packets to the broadcast MAC address on eth0, over and over until you press Control-C. Other machines on the network will update their ARP tables when they see these packets.

"Bridging": Proxy ARP

An Ethernet "learning bridge" is a device with multiple interfaces, which figures out what MAC addresses are on each of its segments. It will forward packets onto segments that they are destined for. A network switch is a bridge with many ports.

Proxy ARP can produce similar results, by manually publishing ARP entries on one interface for machines on another interface. In this way, machines on one network segment know that they can reach machines on the other segment via this intermediary machine.

This does require that the IP addresses be in the same subnet, of course. Ethernet (at layer 2) doesn't understand routing at all. When a packet is sent to an IP that isn't in a local subnet, the routing table is consulted to find a machine on the local network that can reach the destination network, and packets are sent using the MAC of the router.

I once used this trick to set up a DMZ for a client, with the machine between the segments doing firewalling. These days you also have the option of using "ebtables" to implement firewall rules on an Ethernet bridge, but that wasn't an option when I set up the firewall for this client. Their ISP would only give them 5 usable IPs, so subnetting it and routing was not an option.

To do this, you need to use the "-i" option to "arp" which specifies the interface to publish it on. So you can take an IP address for a machine that is on eth0 interface, and publish it on eth1 using the eth1 MAC address. The "-Ds" option simplifies this by figuring out what MAC address to use:

arp -i eth1 -Ds 10.0.0.1 eth1 pub

You also need to enable IP forwarding and proxy ARP:

echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
echo 1 > /proc/sys/net/ipv4/ip_forward

Conclusions

I've been doing IT work since the early '90s. While I don't often end up having to consult ARP tables or use the "arp" command, understanding ARP makes many networking situations much more clear. It's one of the things you need to understand to be in the top 10% of IT professionals.

How to Create an AdSense Account

As a blogger, you have surely heard of the AdSense program from Google which is regarded as one of the best contextual advertisement programs available.

In this post, I will demonstrate how you can create an AdSense account for your website.

There are many AdSense alternatives available, but no matter what network you try, you will likely find that Adsense is the best.

If you have some marketing skills, however, you may also want to look into affiliate marketing.  My post on Affiliate vs AdSense will give you my personal insights into both networks.

When I started blogging, “AdSense” was a foreign concept to me. When I initially signed up for AdSense, I needed a lot of help from my friends, and I still was not sure I was doing it right.

For beginners who are not familiar with AdSense, it is an advertisement program for publishers started by Google (See Wiki details), wherein contextual ads are placed on your blog and you get paid when someone clicks on these ads.

In this blog post, I present an essential guide for beginners who are not sure how to apply for AdSense.

There are a couple requirements which you must meet before you can apply for AdSense:

First, of course, you need to have a website.

You also must be above the age of 18, otherwise you will need to apply using the name of a parent or guardian who gives you permission to do so.

Watch this video to understand what your blog needs to have before you apply for AdSense:

Steps to create an AdSense account:

AdSense has recently changed the account approval process to include the following steps:

Sign up for AdSense

• Add AdSense ads to your blog
• Wait while your account is reviewed and either accepted or rejected
• Although the new AdSense account approval process is quite lengthy, the process will ultimately help to maintain the quality of AdSense for all users.
• It is also important to make sure your blog or website is abiding by AdSense policies before applying.
• Also, be sure to read the terms and conditions mentioned on the signup page to learn more.
• Step-by-Step Guide to Creating an AdSense Account:
• First, go to the Signup page for AdSense.

You will see an option to create a new Google account, or you can choose to use your existing Google account.

How to mirror an Android device on your TV

Putting your Android device's screen on a TV screen is simple, so long as you have a Chromecast.

Mirroring your Android device's display on your TV can be useful when you're giving a demonstration, showing off photos from a recent trip, or playing a game.

In order to mirror the screen of your Android smartphone or tablet, you'll need a device running Android 4.4.2 and above as well as a Chromecast device. (Alternatively, you can mirror your Android device using a Roku by following these instructions.)

Typically, you can check the version of Android running on your device by going into Settings > About Phone and looking for "Android version."

Google notes on its support page any device running Android 4.4.2 and above is capable of casting its screen to a TV, however some devices are better suited for such a task. The company goes so far to offer a list of optimized devices, which you can view here. I've tested devices not listed and didn't see a drastic difference in performance, but as always, your results may vary.

So how does one go about casting the screen of an Android device to a television? It's quite simple, actually.

• Make sure you have the Google Home app installed on your Android device. You can download it from the Play store.
• Ensure that you're connected to the same Wi-Fi network as your Chromecast device.
• After opening the Google Home app, slide out the menu and select Cast Screen/Audio.
• Tap on the blue button, followed by the device you'd like to connect to

Another method present on some devices is found in the quick settings pane, found by swiping down from the top of your device's screen. If a Cast or Cast Screen button is present, you can select it followed by the device you'd like to cast your screen to instead of going through the Google Home app.

Once you begin casting -- or mirroring -- your screen, an alert will appear in your notification shade, making it possible to stop mirroring with a tap.

how to make configure cisco sg300-28 switch

The Cisco SG300-28 switch has the default password of cisco. The password is case sensitive so it must be entered that exact way - don't capitalize Cisco!

Along with this password, like most Cisco devices, the SG300-28 uses the default username of cisco to login with administrative privileges.

To access the Cisco SG300-28 switch, use the default IP address 192.168.1.254.

Note: Default passwords are sometimes different for certain hardware or firmwareversion, but what's described above should work for any SG300-28 switch.

What to Do If the SG300-28 Default Password Doesn't Work

It's important to secure any managed network hardware by changing the default login information. If you don't, anyone with network access can be granted administrator rights. If you've taken this wise step, then the above information won't work.

However, if you've forgotten what you've changed the password to, you can easily reset it to the factory defaults to restore the username and password to cisco.

You'll need physical access to the switch. Here's how it's done:

1. Make sure your SG300-28 is powered on and then turn it to its backside so you can see the cables. 
2. Disconnect the switch from the network. 
3. Find the small hole on the back (the Reset button) and press and hold it down for 5-10 seconds with something pointy, like a paperclip or pin. 
4. Unplug the power cable from the switch for a few seconds and then reattach it. 
5. Provide enough time for the switch to fully turn back on - a few minutes at most. 

1. Reconnect the SG300-28 switch to the network. 
2. Login to the switch at http://192.168.1.254 using cisco as both the username and password. 
3. Change the default switch password to something more secure.

Any custom settings that were previously stored in the switch will now have to be reconfigured.

What to Do If You Can't Access the SG300-28 Switch

If 192.168.1.254 isn't your Cisco SG300-28 IP address, it just means that someone has changed it to something else, similar to how you can change the username and password.

For most networks, if your switch's default IP address has been changed, the new IP address can be determined using tracert, a command available from the Command Prompt in Windows.

See How To Identify Network Hardware IP Addresses on a Local Network if you need help using that command to find the SG300-28 default IP.

Cisco SG300-28 Manual & Firmware Download Links

The Cisco SG300-28 Support page on Cisco's website is the official location of all things related to the switch, be it downloads, videos, or documentation.

From this link, you can find the Cisco SG300-28 Downloads page where you can get the latest firmware and managed switch MIB downloads. Depending on the versionyou choose, the firmware might be downloaded as either a ROS file or a ZIP archive that you have to open before finding the firmware file.

Note: Switches that are available as different hardware versions will usually use unique firmware, making it vitally important to download the right one for your specific device. The Cisco SG300-28 switch, however, doesn't have any other hardware versions, so the firmware you find through the link above is the same firmware for all SG300-28 switches ever made.

The Cisco SG300-28 Documentation page holds all the brochures, command references, data sheets, install/upgrade guides, release notes, and other related documents for the device.

This Cisco SG300-28 Quick Start Guide is a direct link to the PDF file that can help you setup your switch.

Cisco IOU L2 L3 lab with GNS3 | Switching in GNS3

Cisco IOS on Unix, also known as Cisco IOU,  is released for internal Cisco use only. IOU permits to run IOS natively on x86 platform while GNS3 must emulate the whole hardware. The big difference is that IOU can run more IOS instance than GNS3, but GNS3 can run real IOS version. The purpose of this article is to let you know how IOU can be integrated with GNS3 emulator software to practice switching concepts.

**Pay Attention:** Cisco IOU binaries are not for public use. If you are a Cisco guy you must ask your company how you can get IOU binary files and license. Other do not have rights to use IOU images.

Make sure you have...

Before we start I want to make sure that you all have the required tools and softwares. I have listed down them with download links below,

GNS3  - http://www.gns3.com

Virtual Box 4.3.12 (I had some bad experience with version 5.0, Check my article to know more VirtualBox EFAIL error) - https://www.virtualbox.org/wiki/Download_Old_Builds_4_3_pre24

IOU Images - As already mentioned, strictly for Cisco guys! But still you might get these images by Googling!  

GNS3 IOU VM - Available from sourceforge, I downloaded and used a older version in this post. But you can use any version from this link. - http://sourceforge.net/projects/gns-3/files/IOU%20VMs/

IOURC - Cisco license file for IOU Images. It is not available for public use, but while surfing I found this link which could help you! http://forum.gns3.net/topic9032.html

Setting Up GNS3 IOU VM in Virtual Box

Download the IOU Virtual Machine from the given Sourceforge link.

In the above image I have marked the file which I downloaded, However you can use any of the available versions. Once downloaded extract the tar file using 7zip or Winzip. You would see below files inside the zip file,

Open Virtual Box 4.3.12 application from the start menu. Make sure that you have already downloaded and installed it. I downloaded it from the below URL,

In Virtual Box, Click on File -> Import Appliance. It will prompt below window, 

Select the path of your ovf file (you can find it in extracted folder) and click Import as depicted in the above snapshot. And ensure that Network settings looks like below,

As shown, Make sure that VM is attached to Host-only Adapter before we start the VM. Now start the VM and check for the IP configuration using ifconfig command. Use username root and password cisco to login into the appliance. Refer the below image for example,

Now it's time to upload the IOU images. Well! I happened to find some IOU Images from this link. Type 192.168.56.101:8000/upload on your browser address bar. Click on 'Choose file', a file browser window will open. Select the downloaded IOU image and click 'Upload', this might take few minutes.

Make a note of displayed path, /home/gns3/GNS3/images/IOU/xxxxxxxx. Later you will have to enter this path in GNS3.

With this step, we have completed IOU end configuration. Let's start with GNS3...

GNS3 IOU Server Configuration

By default, GNS3 is binded with server address 127.0.0.0:8000. We have to change this value with our new IOU server address. Follow the below instructions to bind the new server.

Go to Edit -> Preferences -> GNS3 Server. Click on Local server tab. From the Host Binding drop down window select '192.168.56.101'. Make sure that port is also set to 8000. Then click Apply and OK.

Again go to Edit -> Preferences -> GNS3 Server. This time click on Remote access tab. Add a host by entering UNIX GNS3 IOU VM IP address that we found using ifconfig (mine 192.168.56.101) and 8000 as port.

Integrating GNS3 and Cisco IOU

Final step of this tutorial would be to add IOU templates to GNS3. Go to Edit -> Preferences -> IOS on UNIX. And click 'General Settings' tab, click browse to set the path to IOURC.txt file. IOURC license file would like below,

Once you have given license file details, click Apply. And now go to IOU Devices, click New button and select server type as Remote. Your remote server will be listed there → Next

Here you will receive a message “You have chosen to use a remote server, please provide the path to IOU image located on the server!”, just click OK.

Now type a Name for the IOU image and set IOU image path to be the one that you noted already while uploading the image through through browser. Refer the snapshot below to understand what I am trying to say,

Click Finish! Yes, we are done with all the configurations. By repeating the above steps, you can upload as many as images you want and you can add them to your GNS3 emulator window. For example I have uploaded 2 images (L3 and L2) as shown below.

Now go to GNS3 main window, pull the configured IOU devices. Power them on, start building your labs! Since you can configure all the devices inside your GNS3 itself, I guess this method is much better than IOU Web.

That's all folks! I believe I have covered all the required steps to get IOU running with GNS3, In case of any clarifications, do let me know through comment section below. 

How to install PFSense 

Download pfSense

• visit on pfsense.org
• Pick the chosen Computer Architecture, Platform, and Console type
• Download the SHA256 checksum file to verify the image later
• Pick a mirror and click the link on its row to download the image from there
• Wait for the download to complete
• Verify Downloaded Files

Prepare Installation Media

The downloaded image must be written to target media before it can be used. For a Full Install, this media is used to boot and install and then will not be needed again. For Embedded, the target media is the disk (CF/SD) that will contain the Operating System.

• Write the installer ISO: If the .iso file was downloaded, it must be burned to a disc as an ISO image. See Writing ISO Images for assistance.
• Writing Memstick or NanoBSD images: This task is covered with great detail in the Writing Disk Images article here on the wiki.

Connect to Serial Console (NanoBSD, Memstick-serial)

Before attempting to install or boot, if a serial-based image was used, such as NanoBSD or Memstick-Serial, connect to the serial console with a null modem cable and with appropriate terminal options. See Connecting to the Serial Console for specifics.

Performing a Full Install (ISO, Memstick)

Power on the target system and connect the install media: Place the CD into the drive or plug the Memstick into a USB port. If the BIOS is set to boot from CD/USB, pfSense will start.

For other boot issues, Installation Troubleshooting.

As the operating system boots and pfSense starts, a prompt is presented with some choices and a countdown timer. At this prompt, press i to invoke the installer now.

Alternately, allow the system to boot the rest of the way, assign interfaces, and then choose option 99 to invoke the installer.

The Quick/Easy Install option is, as the name implies, both Quick and Easy. That is the method which will be demonstrated here.

First, the installer console can be changed to use a different font, screenmap, or keymap. Most people do not need to change these, but it may help with some international keyboards.

At the Select Task prompt, choose Quick/Easy Install.

The Quick/Easy Install option assumes the first located disk is the intended target, so be sure there is only one SSD/HDD is present in the system.

NOTE: A GEOM mirror (software RAID) may also be configured by choosing Custom Install and then invoking the option to create the mirror and select the disks. Once that has been completed, then it is possible to return to the Select Task screen and proceed with a Quick/Easy Install

Because the next step is destructive to whatever is currently on the target disk, confirmation is required to proceed. Select OK then press Enter.

The install will proceed, wiping the target disk and installing pfSense. Copying files may take some time to finish.

After the files have been copied to the target disk, a choice is presented to select the console type. Standard defaults to the VGA console. Embedded defaults to serial console.

Now the system must reboot so that pfSense may start from the target disk. Select Reboot and then press Enter. Be sure to remove the disc or USB memstick so that the system will not attempt to boot from there next time.

 

After the system reboots, pfSense will be running from the target disk. The next step is to Assign Interfaces on the Console below.

Embedded / NanoBSD

Before attempting to boot, if ALIX hardware is being used, ensure the device has the latest BIOS (at least 0.99h) and set CHS mode in the BIOS. See ALIX BIOS Update Procedure for details.

Install the target media into the device, and ensure the BIOS is configured to boot from that disk.

If everything is configured correctly the kernel will begin to load. For serial console images, systems with VGA output will stop displaying with a "/" on the screen or may stop at a "BTX" message. From that point on all output is sent to COM1. Connect to the serial console to view the remaining output.

Assign Interfaces on the Console

The default configuration file on pfSense 2.3 has em0 assigned as WAN, and em1 assigned as LAN. If the target hardware has em0 and em1, then the assignment prompt is skipped and the install will proceed as usual. Several other common platforms such as our SG systems, APU, and ALIX are also recognized and will have their interfaces assigned in the expected order.

If the hardware platform cannot be identified, a list of network interfaces and their MAC addresses that were located on the system will appear, along with an indication of their link state if that is supported by the network card. The link state is denoted by "(up)" appearing after the MAC address if a link is detected on that interface. The MAC (Media Access Control) address of a network card is a unique identifier assigned to each card, and no two network cards should have the same MAC address. After that, a prompt will be shown for VLAN configuration.

VLANS

The option to assign VLANs is presented first. If VLANs are not required, or they are not known, enter No here. VLANs are optional and are only needed for advanced networking. VLAN-capable equipment is also required if they are to be used. See VLAN Trunking for details.

LAN, WAN, OPTx

The first interface prompt is for the WAN interface. If the interface is known, enter its name, such as igb0 or em0 and press Enter. If the identity of the card is not known, see the next section for the Auto Assign Procedure.

The second interface prompt is for the LAN interface. Enter the appropriate interface, such as igb1 or em1, and press Enter again. If only the WAN interface is to be used, and no LAN, press Enter without giving any other input.

Only one interface (WAN) is required to setup pfSense. If more interfaces are available they may be assigned as LAN and OPTx interfaces. The procedure is the same for additional interfaces: Enter the appropriate interface name, then press Enter.

When there are no more interfaces to add, press Enter. The list of assigned interfaces is displayed. If the mappings are correct, enter y, otherwise enter n and repeat the assignment.

NOTE: If only one NIC is assigned (WAN), This is called Appliance Mode. In this mode, pfSense will move the GUI anti-lockout rule to the WAN interface so the firewall may be accessed from there. The usual routing functions would not be active since there is no "internal" interface. This type of configuration is useful for VPN appliances, DNS servers, etc.

Auto Assign Procedure

For automatic interface assignment, first unplug all network cables from the system, then type a and press Enter. Now plug a network cable into the interface that should connect to the WAN, and press Enter. If all went well, pfSense should know now which interface to use for the WAN. The same process may be repeated for the LAN, and any optional interfaces that will be needed. If a message is displayed such as No link-up detected, see Installation Troubleshooting for more information on sorting out network card identities.

pfSense Default Configuration

After installation and interface assignment, pfSense has the following default configuration:

• WAN is configured as an IPv4 DHCP client
• WAN is configured as an IPv6 DHCP client and will request a prefix delegation
• LAN is configured with a static IPv4 address of 192.168.1.1/24
• LAN is configured to use a delegated IPv6 address/prefix obtained by WAN (Track IPv6) if one is available
• All incoming connections to WAN are blocked
• All outgoing connections from LAN are allowed
• NAT is performed on IPv4 traffic leaving WAN from the LAN subnet
• The firewall will act as an IPv4 DHCP Server
• The firewall will act as an IPv6 DHCPv6 Server if a prefix delegation was obtained on WAN, and also enables SLAAC
• The DNS Resolver is enabled so the firewall can accept and respond to DNS queries
• SSH is disabled.
• WebGUI is running on port 443 using HTTPS
• Default credentials are set to a username of admin with password pfsense

Post-Install Tasks

After installation and assignment, a shell menu is presented on the console with a number of options. pfSense now is ready to be accessed via the network, either on the LAN interface (if one is assigned), or on the WAN interface in a single interface deployment.

Connect to the GUI

The WebGUI is used to configure the vast majority of items in pfSense. It may be accessed by any modern browser, though Firefox and Chrome are preferred.

Connect a client PC to the LAN of the firewall and ensure it obtained an IP address. If it did not, it may be plugged into the wrong port.

Open a web browser and navigate to https://192.168.1.1/, using the default username admin and password pfsense to login.

The first visit to the WebGUI will be redirected to the setup wizard, which is also accessible at System > Setup Wizard. Proceed through the wizard and configure things as desired.

Installation Troubleshooting

If the installation did not proceed as planned, see Installation Troubleshooting for help.

Additional Information

For additional information on Installing pfSense, see the page Category:Installation. Sign up for a Gold Subscription, which gives access to the official pfSense book and monthly hangouts that cover a variety of topics as well as our Auto Config Backup service, a secure place to store and retrieve off-site backups.