switchfin.org Report : Visit Site

Technical data of the switchfin.org

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host switchfin.org. Currently, hosted in Bulgaria and its service provider is East quarters - Iavorov .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

blog forum faq about switchfin join switchfin home login form username password remember me forgot your password? forgot your username? create an account jrpassphrase registration control in order to register on this site, you must first submit the passphrase below. designed by: joomla templates copyright © 2010, all rights reserved switchfin org. -- switchfin gui supports italian written by administrator tuesday, 25 june 2013 14:03 as you may know switchfin gui can be configured in english, french, russion, portuguese now italian language is added to the above. thanks go to amleto rostellato. last updated on tuesday, 25 june 2013 14:12 ademco contactid support added in switchfin written by administrator monday, 01 april 2013 15:44 hi guys, in a typical alarm system scenario there are numerous alarm panels spread in a different armed premises. those premises are often spread in a very different geographical locations within a town or even country. the best practice is to collect all the 'alarm events' from all alarm panels in a single central station . so the question is what is the best communication media and protocol used for this. thanking into account the old infrastructure heritage it is not a surprise that the pots analog telephone lines have been widely used in the past and even now. and the protocol is contact id invented by a company called ademco which become de-facto a standard for this kind of alarm panel <-> central station communication. it uses based on a sequence of dtmf tones with handshake and a control sum incorporated. here we go we have alarmsender() asterisk application implemented in switchfin . (note that alarmreceiver() supporting contact id protocol is available in asterisk mainstream since asterisk 1.2) to test please build switchfin with alarmsender enabled in the switchfin menuconfig. then in asterisk cli you can do switchfini1*cli> originate dahdi/g1/phone_number application alarmsender 111118162601000 -- executing alarmsender("dahdi/phone_number", "111118162601000") in new stack > alarmsender: setting read and write formats to u-law > alarmsender: sending ademco contact id > alarmsender: determining protocol ademco contact id... > alarmsender: protocol ademco contact id determined ! > alarmsender: trying to send for 1 time (max 4) > alarmsender : digits_to_send : 1111181626010006 with checksum : 6 > alarmsender: verifying 1400hz 100ms burst (ack) > alarmsender : launching receving loop > alarmsender: verifying 2300hz 100ms burst (ack) > alarmsender : launching receving loop alarmsender: sending dtmf digits successful !! > alarmsender : launching receving loop > alarmsender : not a voice frame, trying with next frame > alarmsender: ademco contact id sent successfully ! -- executing [ dahdi @alarm:3] hangup(" dahdi / phone_number ", "") in new stack you should have alarmreceiver (either commercial alarm central station or asterisk box with alarmreceiver application) listening on the phone_number side. the message is actually the last 15 digits. for more information about the protocol itself please check contact id recommendation the asterisk alarmreceiver application from the remote side responds: switchfini2*cli> -- executing [6000@alarm:4] alarmreceiver("dahdi/channel 1", "") in new stack > alarmreceiver: answering channel > alarmreceiver: waiting for connection to stabilize > alarmreceiver: waiting for first event from panel... > alarmreceiver: sending 1400hz 100ms burst (ack) > alarmreceiver: waiting for first event from panel... > alarmreceiver: sending 1400hz 100ms burst (ack) > alarmreceiver: sending 2300hz 100ms burst (ack) > alarmmonitoring: detected format ademco_contact_id. == alarmreceiver: received event 1111181626010006 this open the door for a few interesting applications based on ip0x as a component in the smart alarm systems. last updated on monday, 01 april 2013 16:55 ppp in switchfin written by administrator friday, 15 june 2012 12:06 ppp over serial link ppp is a data link layer protocol mainly intended to establish point to point connection over the serial link like the console port we have on our switchfin targets. let's see how we can demonstrate this. in the latest switchfin we have ppp option in the menuconfig. please enable it and build the image. connect the serial port of a pc with ppp support with the pr1 appliance console port. establish the ssh sessian with the pr1 appliance. on the pr1 appliance set the ppp configuration file #/etc/ppp/options lock nocrtscts 10.0.0.209:10.0.0.2 linkname ppp0 local nodefaultroute /dev/ttybf0 115200 -detach those lines say: pr1 appliance will use /dev/ttybf0 device for the ppp pr1 appliance will get address 10.0.0.209 and the other end will be 10.0.0.2 the pr1 appliance console has no flow control signals wired (rts,cts, dtr, dsr, etc.) so we say nocrtscts we will give name ppp0 to the link on the host we may have configuration like this: #/etc/ppp/options lock nocrtscts 10.0.0.2:10.0.0.209 linkname ppp0 local nodefaultroute /dev/ttys0 115200 -detach finally let's load the ppp over serial link module root@pr1:~> modprobe ppp_async and we will get the link up root@pr1:~> ifconfig ..... ppp0 link encap:point-to-point protocol inet addr:10.0.0.2 p-t-p:10.0.0.209 mask:255.255.255.255 up pointopoint running noarp multicast mtu:1500 metric:1 rx packets:6 errors:0 dropped:0 overruns:0 frame:0 tx packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 and we may ping pr1 appliance from the pc (or vice versa) like this: [root@switchfin ~]# ping 10.0.0.209 ping 10.0.0.209 (10.0.0.209) 56(84) bytes of data. 64 bytes from 10.0.0.209: icmp_seq=1 ttl=64 time=26.7 ms 64 bytes from 10.0.0.209: icmp_seq=2 ttl=64 time=25.9 ms 64 bytes from 10.0.0.209: icmp_seq=3 ttl=64 time=25.9 ms similarly you may ssh the pr1 appliance thru the new ppp0 interface. point-to-point tunneling protocol and vpn ppp can work not only over serial link. let's see how it can be used to create vpn over the ethernet. in addition we will test the mppe (microsoft point-to-point encryption/compression) support built in as kernel module. let's use one of the linux pc in the network as pppoe server. pppoe is a simple protocol and basically it is pretty much like the dhcp negotiation. description how to do pppoe server can be found at pppoe server under ubuntu/debian the necessary configuration at the pc are # /etc/ppp/pppoe-server-options # ppp options for the pppoe server # lic: gpl lcp-echo-interval 10 lcp-echo-failure 2 debug auth # mppe requires mschap-v2 require-mschap-v2 require-mppe refuse-pap refuse-chap refuse-mschap #/etc/ppp/ chap-secrets # secrets for authentication using chap # client server secret ip addresses # allow any client, any server, any ip addr * * "" * chap is an authentication schema. to prevent exchanging the username/password (as it is in the other popular authentication pap) this method sends random number (challenge) which is processed by both ppp ends using hash function. the results of the hash is compared. let's load the mppe module and start the server root@switchfin:~# modprobe ppp-mppe root@switchfin:~# /usr/sbin/pppoe-server -t 60 -i eth0 -n 250 -r 192.168.0.1 now let's go to the pr1 appliance side. we use the same image with the built ppp option. the required configuration files are: # /etc/ppp/peers/mylink plugin rp-pppoe.so eth0 mtu 1492 mru 1492 require-mppe debug pppoe we will start using pppd plugin rp-pppoe.so. we will use eth0 as carrier interface. we will use microsoft point-to-point encryption mppe # /etc/ppp/chap-secret # secrets for authentication using chap # client server secret ip addresses # allow any client, any server, any ip addr * * "" * some of the ppp stuff is compiled as modules. we don't need ppp_async now but we need few others: root@pr1:~>modprobe sha1_generic root@pr1:~>modprobe ppp_mppe root@pr1:~>modprobe pppoe now we have the f

URL analysis for switchfin.org

http://www.switchfin.org/index.php?option=com_quickfaq&view=quickfaq&itemid=55
http://www.switchfin.org/index.php?limitstart=11
http://www.switchfin.org/index.php?option=com_agora&task=topic&id=163&p=1&itemid=54#p1179
http://www.switchfin.org/index.php?limitstart=33
http://www.switchfin.org/index.php?option=com_agora&task=topic&id=156&p=1&itemid=54#p1180
http://www.switchfin.org/index.php?option=com_content&view=article&id=46&itemid=56
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptk0onbwcc1pbi1zd2l0y2hmaw4my2f0awq9mtpsyxrlc3qtbmv3cw==
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptk2onn3axrjagzpbi1ndwktc3vwcg9ydhmtaxrhbglhbi0my2f0awq9mtpsyxrlc3qtbmv3cw==
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptg4om11bhrpbgluz3vhbc1zdxbwb3j0lwlulxn3axrjagzpbi1ndwkmy2f0awq9mtpsyxrlc3qtbmv3cw==
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptkzom5ldy1icmktagfyzhdhcmutdgfyz2v0lwfkzgvklwlulxn3axrjagzpbizjyxrpzd0xomxhdgvzdc1uzxdz
http://www.switchfin.org/index.php?option=com_content&view=frontpage&itemid=53
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptkxomhvbwutyxv0b21hdglvbi1zzxr1cczjyxrpzd0zndpibg9n
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptk1onr1cm4tew91ci1pcdb4lwludg8tyw4tywxhcm0tcgfuzwxjb250ywn0lwlklwfsyxjtlxnlbmrlci1pbnbszw1lbnrlzczjyxrpzd0xomxhdgvzdc1uzxdz
http://www.switchfin.org/index.php?option=com_mailto&tmpl=component&link=ahr0cdovl3d3dy5zd2l0y2hmaw4ub3jnl2luzgv4lnbocd9vchrpb249y29tx2nvbnrlbnqmdmlldz1hcnrpy2xljmlkptkwonn3axrjagzpbi1zdxbwb3j0cy13bhrjlwlwmhgtbw9kdwxllwzvci1ob21llwf1dg9tyxrpb24my2f0awq9mzq6ymxvzw==
http://www.switchfin.org/index.php?option=com_user&view=remind

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

WHOIS LIMIT EXCEEDED - SEE WWW.PIR.ORG/WHOIS FOR DETAILS

  REFERRER http://www.pir.org/

  REGISTRAR Public Interest Registry

SERVERS

  SERVER org.whois-servers.net

  ARGS switchfin.org

  PORT 43

  TYPE domain

  REGISTERED unknown

DOMAIN

  NAME switchfin.org

NSERVER

  NS1.FREE.DOM.BG 87.120.109.61

  NS2.FREE.DOM.BG 87.120.13.238

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .