Every session is expiring within 1 minute if it kept idle.


 
Thread Tools Search this Thread
Operating Systems Solaris Every session is expiring within 1 minute if it kept idle.
# 8  
Old 05-22-2008
Thanks for resolving my problem.

I had given 15 in putty for keepalive seconds.

Now its working fine.

Once again thanks.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Expiring password notifications

I have a Solaris 10 server that notified one of my users/database administrators of another users account expiring within X amount of days. It attempted to email the user@ server.com, which failed and was forwarded from the mailer-daemon@ server.com, to the DBA. She's not listed as an alias for... (2 Replies)
Discussion started by: Nvizn
2 Replies

2. Shell Programming and Scripting

Take minute per minute from a log awk

Hi, I've been trying to develop a script that performs the parsing of a log every 1 minute and then generating some statistics. I'm fairly new to programming and this is why I come to ask if I can lend a hand. this is my log: xxxx 16/04/2012 17:00:52 - xxxx714 - E234 - Time= 119 ms.... (8 Replies)
Discussion started by: jockx
8 Replies

3. UNIX for Dummies Questions & Answers

Non expiring password

Which files store the information about user with non expiring password in case of HP-UNIX like /etc/shadow in linux Two threads by Anu_1 merged (3 Replies)
Discussion started by: Anu_1
3 Replies

4. Solaris

Kill idle dt session

Hi, i need to kill the idle dt sessions through script, can anyone tell me how to do? RJS (2 Replies)
Discussion started by: rajasekg
2 Replies

5. UNIX for Dummies Questions & Answers

Every session is expiring within 1 minute if it kept idle.

Still it is not working. I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies

6. Solaris

Extension of passwd expiring

Hi all, Anyway to reset the passwd expiring time without user having to reset it themselve? Beside altering the maximum number of days the password is valid in the shadow file, is there any other ways? Reason, user forgot passwd and the account passwd cannot be reset, same passwd is need for... (3 Replies)
Discussion started by: egls
3 Replies

7. Shell Programming and Scripting

FTP session expiring when transferring files... Need some solution

Hi All, I am running a ftp script which is running fine even with crontab. But the problem is that when I connect to ftp server and transfer files , i observe that ftp session expires after few minutes and the file transfer is not completed as there are alot of files to be transfered . ... (4 Replies)
Discussion started by: aarora_98
4 Replies

8. AIX

Knowing when is the user id expiring

HI, Do we have a command in AIX which will let us know when is the user id password getting expired!! Any advice will be of great help!! Thanks, Siddharth (0 Replies)
Discussion started by: siddhhuu
0 Replies

9. Cybersecurity

Killing Idle session

does any one know how to kill an idle session? I want to kill any idle sessions after 30 min... Local or remote.... i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure..... ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies
Login or Register to Ask a Question
PPPOE-RELAY(8)						      System Manager's Manual						    PPPOE-RELAY(8)

NAME
pppoe-relay - user-space PPPoE relay agent. SYNOPSIS
pppoe-relay [options] DESCRIPTION
pppoe-relay is a user-space relay agent for PPPoE (Point-to-Point Protocol over Ethernet) for Linux. pppoe-relay works in concert with the pppoe client and pppoe-server server. See the OPERATION section later in this manual for details on how pppoe-relay works. OPTIONS
-S interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE servers may be connected to this interface. -C interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE clients may be connected to this interface. -B interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Both PPPoE clients and servers may be con- nected to this interface. -n num Allows at most num concurrent PPPoE sessions. If not specified, the default is 5000. num can range from 1 to 65534. -i timeout Specifies the session idle timeout. If both peers in a session are idle for more than timeout seconds, the session is terminated. If timeout is specified as zero, sessions will never be terminated because of idleness. Note that the idle-session expiry routine is never run more frequently than every 30 seconds, so the timeout is approximate. The default value for timeout is 600 seconds (10 minutes.) -F The -F option causes pppoe-relay not to fork into the background; instead, it remains in the foreground. -h The -h option prints a brief usage message and exits. OPERATION
pppoe-relay listens for incoming PPPoE PADI frames on all interfaces specified with -B or -C options. When a PADI frame appears, pppoe- relay adds a Relay-Session-ID tag and broadcasts the PADI on all interfaces specified with -B or -S options (except the interface on which the frame arrived.) Any PADO frames received are relayed back to the client which sent the PADI (assuming they contain valid Relay-Session-ID tags.) Likewise, PADR frames from clients are relayed back to the matching access concentrator. When a PADS frame is received, pppoe-relay enters the two peers' MAC addresses and session-ID's into a hash table. (The session-ID seen by the access concentrator may be different from that seen by the client; pppoe-relay must renumber sessions to avoid the possibility of duplicate session-ID's.) Whenever either peer sends a session frame, pppoe-relay looks up the session entry in the hash table and relays the frame to the correct peer. When a PADT frame is received, pppoe-relay relays it to the peer and deletes the session entry from its hash table. If a client and server crash (or frames are lost), PADT frames may never be sent, and pppoe-relay's hash table can fill up with stale ses- sions. Therefore, a session-cleaning routine runs periodically, and removes old sessions from the hash table. A session is considered "old" if no traffic has been seen within timeout seconds. When a session is deleted because of a timeout, a PADT frame is sent to each peer to make certain that they are aware the session has been killed. EXAMPLE INVOCATIONS
pppoe-relay -C eth0 -S eth1 The example above relays frames between PPPoE clients on the eth0 network and PPPoE servers on the eth1 network. pppoe-relay -B eth0 -B eth1 This example is a transparent relay -- frames are relayed between any mix of clients and servers on the eth0 and eth1 networks. pppoe-relay -S eth0 -C eth1 -C eth2 -C eth3 This example relays frames between servers on the eth0 network and clients on the eth1, eth2 and eth3 networks. AUTHORS
pppoe-relay was written by David F. Skoll <dfs@roaringpenguin.com>. The pppoe home page is http://www.roaringpenguin.com/pppoe/. SEE ALSO
adsl-start(8), adsl-stop(8), adsl-connect(8), pppd(8), pppoe.conf(5), pppoe(8), adsl-setup(8), adsl-status(8), pppoe-sniff(8), pppoe- server(8) 4th Berkeley Distribution 26 January 2001 PPPOE-RELAY(8)