Hello, all

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.

Argh, like this bit of imprecise. The modem, cables and voip router all work fine on this Windows compy. Also, the green LED is on..and...it's Linspire, not Linpire...

Type ifconfig -a and post here what it says.

Ok, here we go.

eth0 Link encap:Ethernet Hwaddr 00:50:22:E7:AA:92
inet6 addr: fe80::250:22ff:fee7:aa92/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5166 (5.0 KiB)
Interrupt:11 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:184 errors:0 dropped:0 overruns:0 frame:0
TX packets:184 errors:0 dropped;0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13787 (13.4 KiB) TX bytes:13787 (13.4 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0)

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

0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139/8139C/8139C+ (rev 10)

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
and

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'
later on
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

Here is a similar thread in which I had a similar problem. THe problem was my DNS wasn't configured properly and I couldn't connect to my ISP. http://www.linuxquestions.org/questi...d.php?t=433869
Write dns information you've got from your ISP like this:
Change the Ip address (the first *.*.*.*) to the one you have and the gateway server (the second *.*.*.*) to what you have (netmask is generally 255.255.255.0)
to see if you can reach your gateway.

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*

Thanks again for your help.

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*

Thanks again for your help.

Just to let you know it won't hold thru on reboot. At least not for me and I don't know how to do it so it does.
Sorry.