Simple Network Question: Part 2
|
|
|
||||||||
|
On Thu, 2009-11-05 at 16:06 -0500, Dennis Mattingly wrote:
> I have (another) simple question involving my router. > > Is this a Linux Bug, or simply a Bad Router? > > 1) My internet is perfect (normal setup) > 2) Plug my computer internet directly into ethernet router > 3) $ ping 192.168.1.1 > network is unreachable > > So, is this my router, do I need to turn-off network manager, Linux > bug, what next? > > Thanks in advance > -- > fedora-list mailing list > [hidden email] > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines What kind of router do you have? If I am reading this right, you are unplugging the Modem from your Linux computer and then putting it in the Router. I assume your computer is also plugged into the network router. Is this correct? -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
signature.asc (204 bytes)
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
On Thu, 2009-11-05 at 22:16 +0100, Athmane Madjoudj wrote:
> On Thu, Nov 5, 2009 at 10:06 PM, Dennis Mattingly > <[hidden email]> wrote: > > I have (another) simple question involving my router. > > > > Is this a Linux Bug, or simply a Bad Router? > > > > 1) My internet is perfect (normal setup) > > 2) Plug my computer internet directly into ethernet router > > 3) $ ping 192.168.1.1 > > network is unreachable > > > > So, is this my router, do I need to turn-off network manager, Linux bug, > > what next? > > > > Thanks in advance > > > > > > Some router (like mine) has a different ip (192.168.1.254) > > To discover your router's ip : > > $ route > > or > > Discover all active ip on your network using nmap: > $ nmap -sP 192.168.1.1-254 > > NB: > Some router has a firewall that block ICMP traffic (pings) > > > -- > Athmane Madjoudj > route to begin with.. So he may not be able to do the above. Otherwise it would spit out "Destination Host Unreachable" if it could get to the network and/or 100% packet loss if the router IP was different. -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
|
In reply to this post
by Dennis Mattingly
Dennis Mattingly wrote:
> I have (another) simple question involving my router. > > Is this a Linux Bug, or simply a Bad Router? > > 1) My internet is perfect (normal setup) > 2) Plug my computer internet directly into ethernet router > 3) $ ping 192.168.1.1 > network is unreachable > > So, is this my router, do I need to turn-off network manager, Linux bug, > what next? > connect using something like PPPoE, then you have to make a few modifications when you add in a router between the computer and the modem. The usual change is to set up the router to do the PPPoE for you, and then change your computer to use DHCP and turn off the PPPoE connection. Another thing to keep in mind is that the network and default gateway that the computer is set up to use man not give you a route to the 192.168.1.0 network. For example, my DSL modem defaults to 192.168.0.1. If I were connected to the modem directly, my computer would be set up to use the 192.168.0.0 network with the gateway being 192.168.0.1. With the default setup, I would also have to configure the computer to make the PPPoE connection. But I have the DSL modem configured to do that, and I have the router configured to use DHCP to get its WAN IP address. So, without a lot more information about your setup, it is not possible to answer your question. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
||||||||
|
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
||||||||
|
|
In reply to this post
by Dennis Mattingly
> I've had this issue since February (and Fedora 10). > One day my router-setup just didn't work anymore. had to plug directly > to wall / cablemodem > Could your router have malfunctioned? Can you test it with any other PC to verify? This makes it sound like a hardware error.. does your NIC link show green when it is plugged into the router? -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
|
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
||||||||
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
In reply to this post
by Dennis Mattingly
|
||||||||
|
|
On Mon, 2009-11-09 at 14:17 -0500, Dennis Mattingly wrote:
> >> So I finally think it's a hardware issue. > >> > >> Thanks for all the input. > >Routers normally have their own static addresses (different for > >different router companies) which allows you access their > configuration > >interface. > > Some network-admins at my job examined the router and it looks like a > hardware issue. > Not only did they confirm the LED lights are very dim, but they > couldn't detect the router using any hardware / OS / computer / > network cable. > > So thanks again all for your help. > I'll go to Microcenter soon and purchase a nice new LinkSys router. > > I heard someone mention NFS and static-IP addresses. > So I'll start playing in that ballpark and see how far I can go. > -- you create a server (for NFS or whatever else you want) just give it a static IP outside of the DHCP scope. For example, a router has an IP of 192.168.1.1 gives a scope of 192.168.1.100 to 192.168.1.200. You can use any IP from 192.168.1.2 through 192.168.1.99 and 192.168.1.201 through 192.168.1.254. The gateway would be 192.168.1.1 for this router setup (coincidentally the same as most Linksys routers). The documentation that comes with the router will tell you what to do, don't bother using the CD but power it up, plug in your modem and connect a PC to it and set the PC to use DHCP. You will then be able to access the router and set it up that way. After which you can google for "linksys DHCP scope" and should get lots of info that way. Good luck! PS. I have had a lot of Linksys equipment die on me, for a pretty solid router I would go for the Dlink DIR-655 extreme, 4 x gigabit switch is integrated and it is around $120 CAD. -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
|
|
||||||||
|
|
On Wed, 2009-11-11 at 01:28 +1030, Tim wrote:
> On Mon, 2009-11-09 at 15:11 -0500, Tait Clarridge wrote: > > for a pretty solid router I would go for the Dlink DIR-655 extreme > > Have they improved their interface in recent years? The DLink I bought, > a year or so ago, has the most awful web interface to use. A friend's > Netgear was a lot better. > > I believe they have, at least I do not have any issues with navigating the web interface now. Everything seems to be in the right place and it "looks" modern compared to the Linksys I used to have (although looks rarely matter if it doesn't work properly). If you download the manual for the router I'm sure it will give you a glimpse of the features/web interface. If you don't require wireless there are some other options out there that may be cheaper and just as good. Netgear probably have some good offerings here. -- fedora-list mailing list [hidden email] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
||||||||
|
|
In reply to this post
by Dennis Mattingly
|
||||||||
| Free Embeddable Forum Powered by Nabble | Help |
