Which port number can be used other than 4370 while connecting to biometric


I am connecting to biometric device using API connect\_net() which takes two parameters as ip address and port number. I am using there dll called zkemkeeper.dll .In there SDK there have given default port number as 4370. I want to know if I can use any other port number other than 4370..
> 
> I want to know if I can use any other port number other than 4370
> 
> 
> 


That depends on the configuration of your biometric device.
biometric devices. debates are currently raging over the ethics of bringing this cutting edge tech to the classroom, but it is a possibility. what is it and what does it do? biometrics are typically used for security through iris pattern, voice, and fingerprint recognition. some educators, however, are considering their application in the classroom. Power off the router. 


Get yourself a copy of TeraTerm (it is old, but good)  

Connect your PC serial port to the CON port on the router and run TeraTerm, configured for the serial port, at 9600, 8 bits, no parity.


Press return a few times, and make sure you can see the output from the router.


Power off the router.  

Power it back on again, and when you see something, send a ‘BREAK’ by pressing Alt+B  

The router shoud return a boot> prompt.  

Type 


<b>config-reg 0x2142</b>


Then type


<b>boot</b>


Let the router load, and it will come up with the prompts asking if you want to use the configuration utility.  

Say <b>NO</b> to this.


Type the following when it gets to the > prompt


<b>en  

copy start run</b>  

{press return to the prompts from this command}


When it has finished


<b>show run</b>


Check and see if it has an ‘enable password’ command or an ‘enable secret’


<b>conf t  

config-reg 0x2102  

enable secret {whatever you want as a password}  

no enable password</b> (if it has one of these)  

<b>end  

wr</b>


And the password is changed. 


You should reboot to make the config register change, and also to confirm the password has changed correctly. 


I did all this from memory, so if it doesn’t work, then post here and I will double check, or someone will point out my stupid mistake 😉 you can try a factory reset. push and hold the reset button for 15 seconds and then release. the button should be located on the back of your gateway/modem/router, and you will need a ballpoint pen or toothpick. you should then be able to access your gateway using the standard means with the passwords listed on the label on the gateway.  \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_how can you be in two places at once, when your not anywhere at all?i really want to become a procrastinator, but i keep putting it off.there are three kinds of people, those that can count, and those that can't.'our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them.' :bertrand russell hi, are those credentials used to scan devices? are they on the credentials list on the scan settings page? Magda, have you found what you need, yet?


I did this many years ago. It is simple… the 2nd time you do it!  

Exit points are simply “interrupts” that IBM supplies. You can attach programs to them, and the programs will automatically run at that point. For setting your AS/400 up to accept FTP logons, for example, the exit point is:  

QIBM\_QTMF\_SVR\_LOGON and the format you wil use is: TCPL0100.


A program inserted there can control WHO can log on, and when.  

To control WHAT they can do, you use another exit point, QIBM\_QTMF\_SERVER\_REQ and use format VLRQ0100.


My notes (from 1999) say I used the IBM TCP manual to get this info, specifically: TCP/IP manual SC41-5420-01 page I-14.


I do not know if it will allow me to post code here, it is long and complex due to the number of variables and some of them being in hex.


Write me (drow@waxie.com) if you would like me to email you my program code.


David Row  

WAXIE Sanitary Supply  

San Diego, CA





This is a link for [Add-ons for Firefox](https://addons.mozilla.org/en-US/firefox/). These are programs written by users or developers that the browser knows how and when to call. The developers of Firefox designed it to allow external programs to be hooked in by users of the browser.


IBM did something similar for a lot of the TCP/IP and other server functions. (And a lot of other things.) When you connect to the FTP server for example, the server checks to see if a program has been registered to process FTP logon requests. The registered program is an ‘exit program’.


Browser add-ons get an entry added to a file someplace within the browser directory structure. In your iSeries, the entry would be added to the Registration Facility. (Not always, but that’s the commonly recognized object for exit points and programs.) Use WRKREGINF to review your registration facility.


To create an exit program, you need to know the parameter list that will be passed to your program and the exit protocol. To find the parameter list, you should start looking at the documentation for the server the exit program will be associated with. The protocol, the meanings of the parms and what to with them, is also there.


A FTP exit program would be structured after documentation within the [File Transfer Protocol exit programs](http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaiq/rzaiqreferenceexit.htm) topic of the Information Center for your release.


Once registered, a server logon exit program (for example) would be called just before the server decides whether or not to accept the logon. Your exit program directly influences that decision by returning an ‘accept or reject’ parameter. It chooses based on examination of the input parms.


The exit program may control who can and cannot logon, where they may logon from, what times of day logons are accepted, or it might accept all logons — its purpose can be simply to write all logons to a log file or to send a message when particular logons happen. Your exit program can do whatever it is programmed to do at that point in the logon process.


It doesn’t have to be a ‘security’ function. It’s whatever you want it to be.


For the FTP server, there are two general exit points. One is just before a logon is accepted. The other is just before each transaction in a session is processed. You can control individual transactions just as you can logons. (FTP client has its own exit points.)


Most other exit programs work on similar principles.


A few issues complicate things.


* An exit program needs enough authority to do whatever it needs to do; it can’t always rely on the authority of the session user.
* An exit program shouldn’t unduly delay transactions; there’s no way to know how often an exit program may be called, so you don’t want it slowing down every single transaction.
* Exit programs may be called by many instances of a server at the same time; it shouldn’t be locking things that are needed by a different instance.
* IBM changes the interfaces at times and the servers themselves can get PTFs; regular, on-going maintenance can be needed — keep the programs direct with little complication.
* There are other issues, but those are enough to consider.


Code a very simple exit program that accepts the parms and returns an ‘Accept’ indication. Don’t have it do anything except maybe send a message to a message queue. That lets you see how the registration facility works and how the parms work. It also gives you a program that you can register and deregister in the future to check whether or not the server is stilling calling your program correctly. (Problems can happen.)


Tom 79 is correct for sysfs port.

the formula is (port * 8) + offset

the pin is j7

tegra\_gpio\_port\_j = 9 so ( 9 * 8 ) + 7 = 79

from gpioinfo…

line 79: “i2s0\_sclk” unused input active-high thank you [@colin](/u/colin)! i enabled port 1880 on my pi using "sudo ufw allow 1880" and after it worked! US phones use Bellcore FSK caller id. India uses DTMF caller id. Buy a DTMF- FSK converter at a telecom shop. i think the setting you want is in inbound routes. you can set the callerid number. the hover help reads: 
define the callerid number to be matched on incoming calls. 
leave this field blank to match any or no cid info. in addition to standard dial sequences, you can also put private, blocked, unk… [@udo](/u/udo),

you should be verifying the token no matter what, which would require decoding it. if you are using our sdk then this is already happening.

the important distinction here is which token. are you talking about the id token or the access token? the permissions may be in the at, but the at is n…