Sponsored Content
Special Forums IP Networking Linksys 4 port cable/dsl routers Post 26371 by norsk hedensk on Thursday 15th of August 2002 10:26:45 PM
Old 08-15-2002
Linksys 4 port cable/dsl routers

i was reading this thread and someone mentioned problems with the linksys 4 portcable/dsl routers, (BEF4somethingsomethingsomething) this is what i use on my network, and works great, BUT i have had a few strange problems, well my question is not too much of a question, but i would like to know other peoples expierences with this piece of hardware. this router works fine for me, actually it works great, but one thing that is very very weird is when i try to access my webserver using the externail IP address, what happens is it will start to load, but will go very very slow, this slowdown happens fast until i lose all internet access completley, and my network goes dead, the link light will blink rapidly with my dsl modem, and in half hour maybe, the red diagnostic light will go on and the router will seem to reset and everything will be fine, turning of fthe router does not help, nor does turning off and on the cable modem, it is weird, i have mentioned this on another thread but it wasnt really about that, well anyone with similer problems and any other expierences with the linksys router or similar product from linksys please post! i really would like to know others expieriences. thanks. also i wasnt too sure where to put this thread, i am sorry to the moderators if this thread is innapropriate.



i just found this on the website "http://www.practicallynetworked.com/support/linksys_router_help_pg4.htm#servers"


this is what i found:

(this is in reference to linksys 4 port routers)

(Broken in all other revs since V1.22)
(The following information is for reference only.)

If you have Web, FTP, or other servers on your LAN that you have mapped or forwarded so that they are accessible from the Internet, you would expect to be able to get to them by using the IP address assigned to you by your ISP. If you use a dynamic IP service, you'd also probably expect to be able to access the server by your domain name.

Unfortunately, the router doesn't presently support this capability, sometimes referred to as "loopback". You'll need to use the private IP address, i.e. 192.168.1.X of the desired server when you are trying to use it from a computer on your LAN. The ISP-assigned address will work only from computers connecting from the Internet.





-----but why??

Last edited by norsk hedensk; 08-15-2002 at 11:40 PM..
 

8 More Discussions You Might Find Interesting

1. IP Networking

UNIX Routers/VPN

There is a small company with 3 locations in Idaho. Currently they are using UNIX with multiplexors from 10 years ago. They would like to speed up their downloads and connection speeds but don't want to pay more than they are paying right now. They currently pay $200/mo. The main office is in... (4 Replies)
Discussion started by: Jodibaxter
4 Replies

2. IP Networking

two routers

It is possible to connect wireless router that has 4 ethernet connections and WAN connection with regular router that has UPLINK and WAN and 4 ethernet ports? (9 Replies)
Discussion started by: kasia
9 Replies

3. IP Networking

linksys

hi, i have a linksys wireless card wc11 v3 and everytime i plug it into my toshiba, knoppix freezes. Im reading in some places to run iwconfig, but how can i if i cant plug it in to detect it. Also, during the bootup, if it is plugged in, i get a beep near the end of the boot process and the... (4 Replies)
Discussion started by: jestra
4 Replies

4. Solaris

Is the cable you are using a null modem cable or a modem cable

Hi all, Is there any difference between a null modem cable or a modem cable ? i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup. please correct if i am wrong, thks (2 Replies)
Discussion started by: waterbear
2 Replies

5. Red Hat

Different hostnames with reboot while lan cable, no lan cable

I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable Reboot with lan cable: The hostname is ubunut Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies

6. Shell Programming and Scripting

Script for Ping for 10 routers in a mesh

Hello All, I have 10 routers, and need to write a script so that each router pings each other and get the result in a file. We need to further extract the min/avg/max result and write a script to put in a excel file. E.g. LAB-R3A-7609#ping 6.6.6.6 Type escape... (1 Reply)
Discussion started by: sanjugab
1 Replies

7. Shell Programming and Scripting

Perl Telnet cisco routers

Hi all i have little problem finding solution about simple telnet script .... i have 250 routers and on some i have different password and on some they ask just for password no username. So for example 1,2,3 have username and password (user,password) 4, and 5 have different username and password... (0 Replies)
Discussion started by: IvanMP
0 Replies

8. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
in.rdisc(1M)						  System Administration Commands					      in.rdisc(1M)

NAME
in.rdisc, rdisc - network router discovery daemon SYNOPSIS
/usr/sbin/in.rdisc [-a] [-f] [-s] [send-address] [receive-address] /usr/sbin/in.rdisc -r [-p preference] [-T interval] [send-address] [receive-address] DESCRIPTION
in.rdisc remains part of the software distribution of the Solaris Operating Environment. It is, however, not used by default. in.routed(1M) includes the functionality provided by in.rdisc. See routeadm(1M) for details of how to specify the IPV4 routing daemon. in.rdisc implements the ICMP router discovery protocol. The first form of the command is used on hosts and the second form is used on routers. in.rdisc can be invoked in either the first form (host mode) or second form (router mode). On a host, in.rdisc populates the network routing tables with default routes. On a router, advertises the router to all the hosts. Host (First Form) On a host, in.rdisc listens on the ALL_HOSTS (224.0.0.1) multicast address for ROUTER_ADVERTISE messages from routers. The received mes- sages are handled by first ignoring those listed router addresses with which the host does not share a network. Among the remaining addresses, the ones with the highest preference are selected as default routers and a default route is entered in the kernel routing table for each one of them. Optionally, in.rdisc can avoid waiting for routers to announce themselves by sending out a few ROUTER_SOLICITATION messages to the ALL_ROUTERS (224.0.0.2) multicast address when it is started. A timer is associated with each router address. The address will no longer be considered for inclusion in the routing tables if the timer expires before a new advertise message is received from the router. The address will also be excluded from consideration if the host receives an advertise message with the preference being maximally negative or with a lifetime of zero. Router (Second Form) When in.rdisc is started on a router, it uses the SIOCGIFCONF ioctl(2) to find the interfaces configured into the system and it starts lis- tening on the ALL_ROUTERS multicast address on all the interfaces that support multicast. It sends out advertise messages to the ALL_HOSTS multicast address advertising all its IP addresses. A few initial advertise messages are sent out during the first 30 seconds and after that it will transmit advertise messages approximately every 600 seconds. When in.rdisc receives a solicitation message, it sends an advertise message to the host that sent the solicitation message. When in.rdisc is terminated by a signal, it sends out an advertise message with the preference being maximally negative. OPTIONS
-a Accept all routers independent of the preference they have in their advertise messages. Normally, in.rdisc only accepts (and enters in the kernel routing tables) the router or routers with the highest preference. -f Run in.rdisc forever even if no routers are found. Normally, in.rdisc gives up if it has not received any advertise message after soliciting three times, in which case it exits with a non-zero exit code. If -f is not specified in the first form then -s must be specified. -r Act as a router, rather than a host. -s Send three solicitation messages initially to quickly discover the routers when the system is booted. When -s is specified, in.rdisc exits with a non-zero exit code if it can not find any routers. This can be overridden with the -f option. -p preference Set the preference transmitted in the solicitation messages. The default is zero. -T interval Set the interval between transmitting the advertise messages. The default time is 600 seconds. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWroute | +-----------------------------+-----------------------------+ SEE ALSO
in.routed(1M), routeadm(1M), ioctl(2), gateways(4), attributes(5), icmp(7P), inet(7P) Deering, S.E., editor, ICMP Router Discovery Messages, RFC 1256, Network Information Center, SRI International, Menlo Park, California, September 1991. SunOS 5.10 5 Nov 2004 in.rdisc(1M)
All times are GMT -4. The time now is 12:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy