ASA TCP Idle Connection Timeout Suspense

Hello I upgraded our Cisco ASA 5520 with a Cisco ASA 5585. Though both ASA were configured with default TCP Idle Connection Timeout values people are now starting to complaint that idle SSH connections are being terminated. This is proper behavior but they were claiming it didn't occur with the old firewall. Our users are setting keepalives for 1800 seconds to get around this before I can bump the setting to infinite (setting 0). Is there a bug with the feature in older ASA OS?

Hi,
Before looking for a bug I would check the ASA logs (hopefully you are storing them to a separate Syslog server) and see why the connections are torn down (Teardown reason) and how long have they been on the ASAs connection table before they were torn down.
You also have the option to perform traffic capture on the ASA for the traffic in question and confirm why or which party terminates the connection.
I guess you can use the MPF on the ASA to configure separate idle timeouts for just these SSH Connections if you do not want to touch the global timeout values.
I have not run into any problems with the timeout settings on the older softwares. In the newer softwares (8.3+) I have run into these problems. In those situation the ASA has not removed the connection that have reached the timeout value. I have seen connection that have been idle for over 1000h.
- Jouni

Similar Messages

DPS 6 idle connection timeout?

Ok I must be blind... where is the idle connection timeout setting for DPS 6? I would assume in the connection handler. Migrating from v5 and in the old version its in the network group.

Is this what you're looking for?
$ dpconf help-properties | grep -i idle
ldap-data-source monitoring-inactivity-timeout rwd 1s <= DURATION | unlimited Maximum time the availability monitor detects no activity before performing a search on the idle connection to keep it alive. (Default: 2m)
ldap-listener connection-idle-timeout rwd DURATION | unlimited Maximum time a client connection can remain idle before being closed (Default: 1h)
ldaps-listener connection-idle-timeout rwd DURATION | unlimited Maximum time a client connection can remain idle before being closed (Default: 1h)

Avoiding the idle connection timeout?

Our DBAs have implemented an idle connection timeout.
Is there an option in SQL-Developer to keep the connection alive by having it periodically send "dummy" commands to keep the connection alive?

Hi,
Even though there is no listing for it on the Third Party Extensions Exchange on the SQL Developer Community page here,
http://www.oracle.com/technetwork/developer-tools/sql-developer/community/index.html
a "Keep-Alive" extension exists and you may wish to try it. Here is the post for it on this forum:
SQL Developer Keep-Alive Extension Created!
If you don't wish to install an extension, an alternative is here:
How to reconnect without using the "keep alive" plug-in?
Regards,
Gary
SQL Developer Team

OID Firewall / Data Connection Timeouts

Hello
I have an OID cluster (11.1.0.5) setup within our environment and have a firewall installed between the OID servers and the database servers. The defualt connection timeout for the DB connection was increased to three hours, but after three hours I keep getting the periodic failures of OID / enterprise manager. I have set the idle connection timeout and retries in the OID configuration, but this still seems to occur even with the timeouts / retries configured. Is there a max session length or some other way to tell OID to close db connections after a period of time so that the max session is not reached?
Also, if I am just querying OID with a script, it seems to work past the three hours but I think this is more of a cache thing whereby it is responding with cached entries. When I go to enterprise manager and try to manage OID, I will get the failure after the timeout with a LDAP error code 49 error and need to submit a bunch of requests to OID to refresh the connection to the database.
Any help you can give would be appreciated.
Thanks
Nick

Alex,
Thanks for the prompt reply.
Not having Maximum times in ODP will make things complicated and a myriad of race conditions can occur.
There is an involved example of a Transaction Timeout Cancel that I could implements with a an application Maximum timer on page 5-27 of the Oracle Data Provider for .NET Developer's Guide and it is not easy to implement
However, it is not described anywhere on how to implement a Maximum Connection Timeout.
In the example below from the docs the application will block at the Open() call:
// Connect
string constr = "User Id=scott;Password=tiger;Data Source=oracle";
OracleConnection con = new OracleConnection(constr);
con.Open();
So do we do the following:
// Connect
string constr = "User Id=scott;Password=tiger;Data Source=oracle";
OracleConnection con = new OracleConnection(constr);
*//Set_Application Timer*
con.Open();
OnApplicationTimer()
con.Close()
//Do application timeout processing
What will the Close() do for us here? What will happen if the Connection open is still in progress when we try to close it?
Should we forget attempting to Close() and wait until Oracle decides to return in the first method as shown below?
OnApplicationTimer()
//Do application timeout processing but don't explicitly send Close()
// Connect
string constr = "User Id=scott;Password=tiger;Data Source=oracle";
OracleConnection con = new OracleConnection(constr);
*//Set_Application Timer*
con.Open();
//Eventually it will timeout. If succesful, clo0se immediatly since it is too lpate.
Nathan

SMTP connection timeout

Hi,
This question might sound naive, but I just couldn�t find the answer.
For POP, IMAP and HTTP it is easy to setup idle connection timeout (just use configutil).
But what about SMTP connections?
It is set by default on some value (if I just telent on port 25 and live the connection idle, the message �Connection to host lost� will appear after aproximetly 5 minutes), but I cannot find where it can be changed.
On the other hand, what if connection is not idle, but the user is trying to send a bit biger mail but the link is really slow� how is this treated, what is the timeout for this situation and where this can be changed?
Thanks a lot, as always :)

The thing I�m having on my mind is to set this timeout to bigger number, and let slow connections to stay alive for more than 10 minutes.
The only parameter I found is MAX_IDLE_TIME in dispatcher.cnf file, by default it is set to 600.
But the explanation for this parameter is a bit confusing:
MAX_IDLE_TIME=integer
Specifies the maximum idle time for a server process. When an server process has had no active connections for this period, it becomes eligible for shutdown. This option is only effective if there are more than the value of MIN_PROCS server processes currently in the Dispatcher's pool for this service.
Anyway, for testing purposes I set this parameter to 6000 instead of 600, and did:
./imsimta cnbuild
./imsimta restart
Again I telnet to port 25 and live the connection idle, the message �Connection to host lost� appear again after approximately 10 minutes), so it seems like nothing was changed.
So, is this the wrong parameter, or for some other reason time is not expanded?
Btw,
./imsimta version
iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)
libimta.so 5.2 HotFix 1.21 (built 18:35:22, Sep 8 2003)

Difference between Idle Connection Time and HTTP Keepalive Duration?

What is the difference between the Idle Connection Timeout and the HTTP Keepalive Duration configuration parameters? I thought that setting one or both of these values would cause the webLogic web server to terminate client requests that result in processes that run much longer then the time value set in these parameters.

Both of these settings are protection against denial of service at the protocol level, Brian.
Idle Connection Timeout is a generic timeout for idle connections, whereas HTTP Keepalive Duration is specifically for HTTP keepalive connections. (which doesn't cover T3, IIOP or jCOM)
Both of those configuration options are related to freeing up resources like sockets and server-side objects in memory from idle clients.
There's actually no way of stopping long-running processing on the server triggered by a client request that I'm aware of - there are ways you can alert system administrators that something is wrong however.
The best bet there is defining a value for Stuck Thread Max Time, and also for Stuck Thread Timer Interval. That won't stop processing on the server, but it will cause a log message that can be sent on to a monitoring console like Openview.
Beyond that, it's really an issue for application development. There are ways that you can put the brakes on, like ensuring that poentially long-running operations run under a transactional context, and setting a reasonable transaction timeout value. Also, checking for rollback-only settings inside EJB code.
I could be wrong, but I'm pretty sure there's no easy answer here.
Does that help at all, Brian?
 
Kevin Powe
http://www.integral-techsolutions.com

ASA-5585-X 8.4(6)5 Idle connections are not being removed according to timeout settings

Hi,
Just a quick question if anybody has run into a bug where the ASAs "timeout" settings are not being applied to idle connections.
It seems that our ASA running the software level 8.4(6)5 is not tearing down connections. This mainly seems to be a problem in one Security Context where there are around 300k UDP connections (related to VOIP phones) that are not being torn down. Idle timers on the connections are going as far as 700 hours. Common to all the UDP connections is also the fact that only 19 Bytes of data has been transmitted on the connection built on the firewall. I am not sure what the purpose of these UDP Connections is as both the source and destination port is a random high port.
I was not able find any Bug ID which description would match the situation I am seeing. I did not see anything in the release notes of 8.4(7) or its interrim release either that would list thing kind of bug.
- Jouni

Hi Jouni,
This caveat seems to be the closest match as 8.4.6 is the affected ASA code.
CSCuh13899
Symptoms:-
Some connection may not removed even after reaching idle timeout.
https://tools.cisco.com/bugsearch/bug/CSCuh13899/?reffering_site=dumpcr
You can upgrade to the next stable ASA code as suggested in the referred document.
HTH
Regards,
Dinesh Moudgil
P.S. Please rate helpful posts.

Lan connection timeout after ASA reload

hi guys
i have 2 asa 5520 HA .
i have a problem ..
whenever reload this asa my lan users for tcp and udp and icmp connection is time out , and i force restart users pc , and after restart ok ...
but without restart my connection timeout
please help .

Hi,
It seems to suggest somekind of problem between the ASA firewalls as the "comm failure" is listed.
What does the "show failover" command show?
Have you checked both the GigabitEthernet0/2 and GigabitEthernet0/3 links on both units and the network between the ASA units through those interfaces? I think you should go through those interfaces and the network segment between the ASAs and confirm that there is a working Failover/Statefull link between the ASAs.
Did you log into the Standby ASA and check the output of "show conn". If you got connections active through the Active ASA and the Standby ASA does not have anything in its connection table then you have a problem with the Failover setup.
- Jouni

How to set TCP connection timeout in solaris 9

Hello All,
I am new to solaris. While using oracle, sometimes I face tcp connection timeout.
The timeout happens after a long delay like more than 8 min. I want to reduce the tcp connection timeout to 2 min in solaris.
Please help me to change this setting.
My current configuration is
SunOS testmachine 5.9 Generic_122300-13 sun4u sparc SUNW,Sun-Fire-V440
Thanks
Purushoth

There's a fair amount of tunables. Without known what is timing out (dns, lost packet...), it's hard to say what you want to tweak. The list of parameters can be seen by using ndd:
ndd /dev/tcp \?
or
ndd /dev/ip \?
and can be set by using ndd -set (see ndd(1M) ). Note that anything you set has to be reset on reboot, so you have to stick this in a script somewhere, or know what the variable translates to to stick it into /etc/system.
-r

TCP Connect Timeout

Does anyone know of a way to increase the TCP connection timeout on Linux (RedHat ES 3.0, 2.4.21-9.0.3.ELsmp). We currently always keep a "dead" server in our imqAddressList for failover. The server has nothing listening on the portmapper port, 7676. When I telnet over regular Internet it takes less than a second to get a connection refused response:
telnet: Unable to connect to remote host: Connection refusedWhen I telnet to this server over a low bandwidth satellite connection, I get a timeout after 3 minutes:
[root@client# time telnet server 7676
Trying X.X.X.X...
telnet: connect to address X.X.X.X: Connection timed out
real    3m15.393s
user    0m0.010s
sys     0m0.000sWe currently have 3 servers in our imqAddressList and imqReconnectAttempts is set to 0. However, since one of the 3 servers is dead, 1/3 of the time it takes over 3 minutes to get a connection. I'd imagine that the socket connection from IMQ is exhibiting the same behavior as telnet.
Is there anywhere that I can tweak this timeout?
Thanks,
Aaron

You need to call connect on a socket set to non-blocking mode with fcntl, and then use select with a timeout to limit the amount of time you will wait for the connect to complete. If select returns because you timed out, then close the socket and return an error. If select returns because of an event on the socket, you use getsockopt to determine if the connect succeeded or not.
See Stevens, Unix Network Programming Vol 1 for details. Comments in the code I'm looking at say page 411.
Hope this helps.

EclipseLink timeout on idle connections

Hi,
I'm using EclipseLink 2.1.0 + MySql for a web application. Internal connection pool is used instead of Tomcat maintained pool.
The issue I'm currently facing is that connections in the pool become idle during the night (when the application is indeed idle).
In the morning the first attempt to use a connection fails, but further attempts work fine.
I've heard that H3C0 (Hibernate) and other connection pools support a feature that sends a sort of heartbeat packet to
keep the connection alive so that every connection in the pool does not timeout (e.g. using the testConnectionOnCheckout
property).
Is it possible to get the same behaviour on EclipseLink in order to avoid that an idle connection times out ?
Matteo

It turned out that the feature I was looking for is not implemented in EclipseLink 2.1.0.
In order to fix my problem I had to change the configuration of EclipseLink to use the Tomcat connection pool (dbcp). This provides the following useful parameters:
     testWhileIdle="true"
     validationQuery="select count(*) from dual"
     minEvictableIdleTimeMillis="2880000"
Basically this checks every 8h idle connections performing the validation query, thus avoiding timeout. Simple and good!

TCP/IP connection in UDF Timeout

Hi Guys,
Can someone please tell me if there's some way to trace this. I'm doing a TCP/IP connection to an external server from our PI Dev system in a UDF. I've designed this code in an external java tool and everything works fine. I can send the message over the protocol and I get a response back but if I test the UDF in my MM it times out and kicks me off the network. I've asked the firewall guys to have a look but all they they there's no scanning on this rule and nothing's being blocked. I need to find out how come I can't get a connection to this IP and Port. Any idea? Also would I be able to run a tracert command in R/3 itself?
Thanks,
Jan
Edited by: Jan de Lange on Oct 19, 2011 9:54 AM

Hi,
I've tested my code in my 3G which gets a connection and send/receive data. However if I deploy it on PI It times out after a while. At s.connect(serverAddress, 30000); it can't get a connection to the host. There's no error message, just times out. I'll see what I can come up with working with the network people. They just HAVE to do a trace on it.
try
            System.out.println("Creating Socket: " + ip + ":" + port);
            //Create Socket Address
            SocketAddress serverAddress = new InetSocketAddress(ip, Integer.parseInt(port));
            s = new Socket();
            //Set Keep Alive Parameter
               s.setKeepAlive(true);
               //Set Read/Write Timout
               s.setSoTimeout(20000);
               //Open Connection with Address + Process Timout
            s.connect(serverAddress, 30000);
            System.out.println("Socket Created: " + s);
        catch(UnknownHostException uhe)
            // Host unreachable
            System.out.println("Unknown Host :" + ip);
               errorTrace+=(";Unknown Host :" + ip);
            s = null;

ASA 5550 Open Connections Increase

We have seen a dramatic rise in open connections on the ASA in the past couple days. From about 20,000 to close to 40,000 now. My first question is how efficiently monitor these connections. We graph the total number via SNMP, but in this case, I need to narrow down the problematic host(s). Currently, I am issuing a "sh conn", displaying all connections and then copying and pasting to a text file which I then load into a spreadsheet to sort. There has got to be a better way.
I am also not quite sure what to do about this situation. Using the method above, I can see that there are 15,000+ connections open to our mail servers (which is abnormal), but there is no abnormal usage or open tcp connections on the mail servers themselves. So what are these connections exactly? What should be done to minimize them?
Here is an example:
TCP out 86.195.154.184:3633 in 66.245.177.215:25 idle 0:08:36 bytes 15615 flags UfIOB
TCP out 86.195.154.184:4852 in 66.245.177.215:25 idle 0:38:58 bytes 15852 flags UfIOB
TCP out 83.20.185.182:5140 in 66.245.177.215:25 idle 0:00:55 bytes 2799 flags UfFRIOB
TCP out 69.40.127.71:60260 in 66.245.177.215:25 idle 0:00:15 bytes 1135 flags UfIOB
TCP out 24.132.222.168:62983 in 66.245.177.215:25 idle 0:00:04 bytes 483 flags UfOB
TCP out 24.132.222.168:63729 in 66.245.177.215:25 idle 0:04:12 bytes 759 flags UfIOB
I should also mention that approximately 11,000 of these 15,000 connections have the UfIOB flags.

These are half open connections which may be left after the client closing the connection but it is still active on ASA. It may happen because of TCP timeout value set at very high. If you need the connection timeout value for TCP to be set high for a certain IP flow, then it is recommended to use a policy map.

ASA 60 minute inactivity timeout - Poor choice?

Hello Friends!
We had an issue the other day where doing backups through the firewall (don't ask) caused the "control" session to timeout while the backups were still going on over the "data" connection. This broke the backup about two hours into the job. My first thought was that the backup solution vendor should implement some kind of tcp keepalive for the control connection. A packet capture showed they indeed were -- after 2 hours! Ah ha! Busted! How could they choose such a poor choice of TCP keepalive timer for their application that would not be compatible with the 60 minute inactivity timer that so many firewall vendors use (Cisco, Juniper, Checkpoint and Fortinet all use a default 60 minute inactivity timer for TCP)?
Well, a colleague of mine pointed out that there is actually an old RFC that covers this. RFC 1122. It says:
Keep-alive packets MUST only be sent when no data or acknowledgement packets have been received for the connection within an interval. This interval MUST be configurable and MUST default to no less than two hours.
Now I know that RFC is old (October 1989), but that's all I could find. Is there something that supercedes that? Maybe common sense perhaps? I understand not wanting to fill up your connection table because of mis-behaving applications, but I'm just looking for ammunition to use against the backup solution vendor. Surely they're going to point to this RFC.
Thanks!
ASA(config)# timeout conn ?configure mode commands/options: 0:0:0 | <0:5:0> - <1193:0:0> Idle time after which a TCP connection state will be closed, default is 1:00:00 <0-0> Specify this value to never time out

Hi,
Certain application behaviour sometimes forces our hand to reconfigure the "timeout" values for certain customer connections. Though this has been pretty rare in my own case atleast.
I would imagine that any kind of keepalive would be something that would be constantly transmitted on the connection that needs to stay up and it would certainly be something that the application handles itself.
I did a quick try on my home ASA to check if this could be corrected by the ASA wihtout globally affecting all connections through the ASA and it seems to work fine
Here is the configuration I did
Where
TIMEOUT = Is simply the name for each configuration (ACL, Class-Map and Policy-Map) that I chose
x.x.x.x = Is the destination IP address for which I want to create these rules for
LAN = Is my ASAs "inside" interface
access-list TIMEOUT extended permit ip host 10.0.1.1 host x.x.x.x
class-map TIMEOUT
match access-list TIMEOUT
policy-map TIMEOUT
class TIMEOUT
set connection timeout idle 3:00:00
service-policy TIMEOUT interface LAN
Output of "show conn long" with 2 connections through the ASA. Other going with default "timeout" values and other matching the configured "timeout" values.
TCP WAN:x.x.x.x/80 (x.x.x.x/80) LAN:10.0.1.1/59074 (y.y.y.y/59074), flags UO, idle 15s, uptime 17s, timeout 3h0m, bytes 2
TCP WAN:a.a.a.a/80 (a.a.a.a/80) LAN:10.0.0.21/57482 (y.y.y.y/57482), flags UIO, idle 13s, uptime 14s, timeout 1h0m, bytes 598
Where
x.x.x.x = Is the destination IP for the connection for which you want to configure its own "timeout" values
y.y.y.y = Is my ASA public IP
a.a.a.a = Is the connection destination IP address for which the global "timeout" values are applied
Theres is also an option called "dcd" in the same "set connection timeout" configuration
Here is the Command Reference section for "set connection timeout"
set connection timeout To specify connection timeouts within a policy map for a traffic class, use the set connection timeout command in class configuration mode. To remove the timeout, use the no form of this command. set connection timeout {[embryonic hh:mm:ss] [idle hh:mm:ss [reset]] [half-closed hh:mm:ss] [dcd [retry_interval [max_retries]]]} no set connection timeout {[embryonic hh:mm:ss] [idle hh:mm:ss [reset]] [half-closed hh:mm:ss] [dcd [retry_interval [max_retries]]]} Syntax Description
dcd
Enables dead connection detection (DCD). DCD detects a dead connection and allows it to expire, without expiring connections that can still handle traffic. You configure DCD when you want idle, but valid connections to persist. After a TCP connection times out, the ASA sends DCD probes to the end hosts to determine the validity of the connection. If one of the end hosts fails to respond after the maximum retries are exhausted, the ASA frees the connection. If both end hosts respond that the connection is valid, the ASA updates the activity timeout to the current time and reschedules the idle timeout accordingly.
embryonic hh:mm:ss
Sets the timeout period until a TCP embryonic (half-open) connection is closed, between 0:0:5 and 1193:0:0. You can also set the value to 0, which means the connection never times out. A TCP connection for which a three-way handshake is not complete is an embryonic connection.
half-closed hh:mm:ss
Sets the idle timeout period until a half-closed connection is closed, between 0:5:0 and 1193:0:0. You can also set the value to 0, which means the connection never times out. Half-closed connections are not affected by DCD. Also, the ASA does not send a reset when taking down half-closed connections.
idle hh:mm:ss
Sets the idle timeout period after which an established connection of any protocol closes. The valid range is from 0:0:1 to 1193:0:0.
max_retries
Sets the number of consecutive failed retries for DCD before declaring the connection as dead. The minimum value is 1 and the maximum value is 255.
reset
For TCP traffic only, sends a TCP RST packet to both end systems after idle connections are removed.
retry_interval
Time duration in hh:mm:ss format to wait after each unresponsive DCD probe before sending another probe, between 0:0:1 and 24:0:0.
Defaults The default embryonic timeout is 30 seconds. The default half-closed idle timeout is 10 minutes. The default dcd max_retries value is 5. The default dcd retry_interval value is 15 seconds. The default tcp idle timeout is 1 hour. The default udp idle timeout is 2 minutes. The default icmp idle timeout is 2 seconds. The default esp and ha idle timeout is 30 seconds. For all other protocols, the default idle timeout is 2 minutes. To never time out, enter 0:0:0.
Source:
http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/s1.html#wp1453113
I can't really say anything else to this other than it seems stupid to me to not have a mechanism to keep the Control connection active with frequent (enough) messages that will keep it active as long as there is data transfer on the actual Data connection. I dont know what kind of keepalive it is that polls at minimum on 2hour interval. Kind of beats the whole purpose of keepalive.
Though then again this is not a subject I could comment on any kind of certainty. Only comment on the way it seems to me.
- Jouni

The TCP/IP connection was unexpectedly terminated by the server (NNTP)

I had a prior thread on this topic which was apparently closed to further posts:
http://homecommunity.cisco.com/t5/Wireless-Routers/The-TCP-IP-connection-was-unexpectedly-terminated...
so I'm opening this new thread. The problem was never solved and I could not deal with the help being offered here previously.
The problem is...
My connection to a NNTP news service which I use very frequently is reset every 10 minutes so that I get the message: The TCP/IP connection was unexpectedly terminated by the server.
I have been getting this error at least a dozen times per day for more than a year. So it has become a major annoyance and I want to fix it if possible. I wonder if there's any new insight available? I'm not a rank beginner but am far from being a router expert. I do not understand many of the router settings.
Here's a more detailed description of the problem...
After getting the error, I must then click on something else in my email client (Outlook Express) then return to click on a newsgroup under that news service, whereupon it reestablishes a valid connection for another 10 minutes. If I am active and click on various messages to read them in the newsgroup, the 10 minute timeout does not happen. It's only when I have left the connection idle without activity for 10 minutes that it times out.
This is a news server which requires an authenticated login with username and password. The same problem happens at a different news server which also requires an authenticated login with username and password. So it is not a problem unique to just one news service. It affects all news services which have an authenticated login requirement. An example news service with a sample newsgroup which has this type of problem is
news:\\news.eternal-september.org\alt.free.newsservers
It's free but you must register at http://eternal-september.org/ to use this news service.
It does not happen at open news services without any login requirements. So it is definitely related to the login requirement.
Perhaps most importantly, it does not happen if I remove the Linksys E2000 router from the circuit and connect my DSL modem directly to computer. So it is definitely a router-related problem causing this inactivity timeout every 10 minutes.
Windows XP Home SP3
Outlook Express 6
Zone Alarm 6.1.744.001
Linksys E2000 router
firmware 1.0.04 build 7
software 1.3.11006.1
connection type (WAN) DHCP
mostly the default settings used

[It is very frustrating to try to work with this board because of the short timeout invoked when editing a message! The following is what I intended to post after a bit of reflection...]
I researched this a bit and bridge mode is available via a setting in my Speedstream 4100 modem, so I don't have to call my ISP. But I'll need to research the consequences a bit more and record some variables to make sure I can get back to my current configuration. There are 3 available settings (radio buttons) in my modem...
PPP Location
WARNING
Changing these settings may interfere with your ability to connect to the Internet.
* PPP is on the modem. This is the normal mode for this modem when connected to a single computer. In this mode, the PPP session is initiated from the modem. Gateways and routers should work in this mode but their configuration may have to be changed to do so (e.g., you may need to have the gateway/router IP address changed to 192.168.1.1).
* PPP is on the computer. This mode is normally used if you need to run a PPPoE client on your PC. This mode can be used with a gateway or router which initiates a PPPoE session. To return to the DSL modem user interface you will need to directly connect your PC to the modem without any gateway or router between the modem and the PC.
* Bridged Mode (PPPoE is not used). This mode must be used if you are connecting to a non-PPPoE network. Selecting this mode will cause the modem to automatically restart.

ASA TCP Idle Connection Timeout Suspense

Similar Messages

Maybe you are looking for