FARPN

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Using the BPQ32 Web Terminal With Your Node - Quick Start ======
If you're on the same machine, or the same network, as your node, using the browser based terminal is another quick and easy way to interact with your node.  The only catch with this method is that you'll only see the interactions you have with your node - you won't have a window displaying a live feed of packets sent and received, like you would with [[qttermtcp-node|QTtermTCP]].

First things first - when you set up your station following the FARPN guides, you made a couple of entries in your Telnet section that will be applicable here. The telnet section of ~/.config/linbpq/bpq32.cfg should look something like this:

<code>
;******************  Port 4 Telnet  ******************;
PORT                                                  ;
  PORTNUM=4                                           ; Port number
  ID=Telnet                                           ; PORTS command text
  DRIVER=TELNET                                       ; Driver type
  CONFIG                                              ; Driver specific configuration from here to ENDPORT
  SECURETELNET=1                                      ; Restrict outbound telnet
  LOGGING=1                                           ; Log all connections
  DisconnectOnClose=0                                 ; Disconnect on close of application instead of return to node
  TCPPORT=8010                                        ; Port for telnet connections
  HTTPPORT=8008                                       ; Port for web interface
  FBBPORT=8011                                        ; Port for FBB protocol BBS connections
  CMDPORT=8015                                        ; Ports for APPS
  LOGINPROMPT=u:                                      ; Telnet login prompt
  PASSWORDPROMPT=p:                                   ;
  RELAYAPPL=BBS                                       ; Relay CMS to BBS application instead of WL2K
  LOCALECHO=NO                                        ; Do not echo input
  MAXSESSIONS=10                                      ; Maxmimum simultaneous connections
  LOCALNET=192.168.1.0/24                             ; LAN Subnet
  CTEXT=N3VEM BPQ Telnet Server\n'?' for Help>\n      ; Telnet connect message
  USER=call,password,N3VEM,NODE,SYSOP                 ; Telnet user
ENDPORT                                               ;
</code>


The applicable entries to the activity we're doing now, are the HTTPPORT, the LOCALNET, and the USER.

If you are accessing your node from the Pi you installed it on, just fire up the web browser and go to:

//localhost:8008// (where 8008 is the HTTPPORT defined in your config)

If you are accessing it from another computer on the same network, and you entered the correct LOCALNET you can open up your broswer, and enter the IP address of the Pi, followed by the port, like so:

//192.168.1.100:8008// (where the IP address is the address of your node, and 8008 is the HTTPPORT defined in your config)

If you aren't sure of the IP address of your Pi, from the PI's command line you type:
<code>
ifconfig
</code>

and you should find an inet entry under eth0 that tells you the IP address. (Assuming you set everything up as per our guides)

If you are accessing your node from anywhere else, you'll need to have likely sorted out port forwarding etc. and you will need the username and password from the USER line to log in.

Once you're on the webpage for you node, you can simply click the "Terminal" option.  

{{:bpqwebmenu.png?400|}}


If you are on the Pi directly, or on the same network with the LOCALNET set up properly, you should be automatically authenticated, and will find yourself at your node's prompt, with a connected message.

At the prompt, type ? and hit enter to see your nodes menu.

{{:bpqwebprompt.png?400|}}

 play around with the options and see what happens! A nice cheat sheet of commands for you as the SYSOP is available here, thanks to PY2BIL

For additional “things to do” now that you have this up and running, check out our “[[now-what|Now What?]]” section.