Sponsored Content
Special Forums Hardware Netgear C3700 Modem Router Problem Post 303011001 by milhan on Thursday 11th of January 2018 02:15:41 PM
Old 01-11-2018
Netgear C3700 Modem Router Problem

I was wondering if anyone had any knowledge about how these routers work.. I bought a Netgear C3700 modem router on eBay about a month ago and couldn't get it to broadcast internet, neither wired nor wireless. When I plug it in and turn it on, all lights come on, but the internet light keeps blinking steadily even if the mac address is activated by the isp which is Comcast. I am able connect to the modem/router's interface at 192.168.0.1 and change the settings and so on. For the internet tab it says "not connected". In other words, everything looks fine but it just doesn't receive or broadcast the internet. Any idea?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Modem problem: "Sorry, modem is busy"

Hi! I have a little prob with dialing up to the internet... When I try connect, it says "Sorry, modem is busy"... Specs: Laptop 56K modem Slackware 8.0 Kernel 2.4.5 Cheers;) (4 Replies)
Discussion started by: satan404
4 Replies

2. UNIX for Dummies Questions & Answers

Hi Modem Problem And cpp

Hi am very new to unix.I got installed linux mandrake and the first problem is whith the modem i don't know why but it does not work. i config it on /dev/modem and some time it says "the modem is bussy" and some time it says: "Modem ready" but the modem did'n switch on Ok the other question... (3 Replies)
Discussion started by: user666
3 Replies

3. Solaris

inbuilt modem problem

when I use the on-board modem.........and I dial in I get the login prompt when I enter id and password it gives..........invalid login.... i hv sun fire 280R system pls help me urgently........i m frustated thx girish (3 Replies)
Discussion started by: girish_shukla
3 Replies

4. BSD

cable modem problem

hi I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system. When I type, I get # ifconfig -a lo0 : .... ... ... rl0 : .... ... ... vr0 : ... ... ... I have two network cards (the machine will be a router). I created... (1 Reply)
Discussion started by: fnoyan
1 Replies

5. SCO

Problem with USRobotics modem

We have problem with new USRobotics modem (V.92). Old one was also USRobotics but K56. I put all jumpers at this same positions like old has, but we still can get connection (modem not responding). New modem works fine under winXP. SCO OpenServer R5 installed (console only). Any idea? (2 Replies)
Discussion started by: JackTheKnife
2 Replies

6. IP Networking

Netgear wireless router as Access Point

Hi guys, I want to setup AP using an NETGEAR WGR614 54 Mbps 802.11g Wireless Router The router works fine, but I don't have internet access. I will describe the structure of the net to explain it: I have one server (Free BSD 7) with 2 LAN PCI cards: re0 - it is connected to my ISP ... (2 Replies)
Discussion started by: sitemap
2 Replies

7. Ubuntu

How ttyUSB* created on my 3G modem problem

Hi I would like to ask if someone knows the explaination of the /dev/ttyUSB*. I had a internet connection 3G usb dongle modem and need to restart before it detected the mobile broadband in the network manager. Before i reinstalled the lucyd lynxs i never meet this problem. But after i... (0 Replies)
Discussion started by: jao_madn
0 Replies

8. IP Networking

Router problem or ISP problem ?

Hi everyone, I am experiencing discontinuity of Internet service, this started 1 month ago. Everything worked very well for 1 year of intensive use, but now, I have problems reaching my gateway. The gateway is not my router but a node belonging to my ISP and I share the same public IP with... (3 Replies)
Discussion started by: remic
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 10:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy