Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I run Ubuntu and yesterday the internet just...quit. Everything looks to be fine, but I'm not connected. I went so far as to start a reinstall on Ubuntu, and network configuration fails. So I popped in Linpire, ran it Live and same thing. It seems detected, and so on, but no connectivity. I don't know much, but I did a ping and pretty much got this
64 bytes from localhost (127.0.0.1) icmp sej=45 tume=0.100
Everything ran great til yesterday. Any help is grandly appreciated and what ever information is needed, I'll hook up again, and get.
Great resource you have here.
My first post, so..sorry if it is not precise enough, raging newbie here.
I've been looking at simliar threads and doing thier suggested console commands, as well
route -n shows nothing under Gateway, Genmask or anything, if that helps at all.
I hope I didn't make any mistakes, I did not see any.
Without internet, couldn't CCP the terminal. This was typed on my eeny iMac 350, on it's eeny KB on it's eeny screen, hooked up to the same Voip Linksys router that the Linux box is on. 'Nother odd little thing. Terminal was not found on Ubuntu, I had to boot a Live CD to run the console. Weirdness.
Anyhow, there it is, and thanks for your response!
Also, I did lspci for the heck of it, dunno if this is relevant, but here it shows
lsnod shows, what I assume from the numbee, to be relevant to the ethernet controlller
8139too 25216 0
mii 4992 1 8139too
mii-tool shows eth0: negotiated 100baseTx-FD, link ok
You know..but for the frustration factor, this would be almost fun. I am feeling a lot more confident in the console.
I noticed this in dmesg
PCI: IRQ 0 for device 0000:00:0b.0 doesn't match PIRQ mask - try pci=usepirqmask
8139too Fast Ethernet driver 0.9.27
PCI: Enabling device 0000:00:0b.0 (0004 -> 0007)
then the irq comment is repeated
PCI: setting IRQ 11 as level-triggered
PCI: Assigned IRQ 11 for device 0000:00:0b.0
eth0: RealTek RTL8139 at 0xd0a94000, 00:50:22:e7:aa:92, IRQ 11
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0:link up, 100 mbps, full-duplex, lpa 0x45E1
NET:registered protocol family 17
eth0: no IPv6 routers present
this...dunno if it is related the ethernet...or some other badness
Device 'i823650' does not have a release() function, it is broken and must be fixed.
Badness in device_release at drivers/base/core.c:85
Well, thank you. You had it right. Though why on earth that particular system, no matter which distro was on it, refused to detect the gateway, all of a sudden, out of nowhere...well, it's a noodle scratcher. Hope it holds through reboot! *frets*
Well, thank you. You had it right. Though why on earth that particular system, no matter which distro was on it, refused to detect the gateway, all of a sudden, out of nowhere...well, it's a noodle scratcher. 'Specially since Ubuntu Live found it fine on the Windows box, with the same modem, router and cabling, just different ethernet card. Hope it holds through reboot! *frets*