ADSL debian internet woes

dear all

I run debian unstable and recently upgraded my kernel (via synaptic) to
2.6.12. This left me unable to use the internet as explained below - or
let's say that it was at this time that my internet connxn turned bad.

Out here in the country (in new zealand) I'm currently obliged to use as
an ISP our national monopolistic telco, the specific service provided
being ADSL. I am supplied with a D-Link DSL-302G ADSL modem.
Essentially, it seems I'm on a private subnet; I'm dynamically assigned
an IP address in the 10.*.*.* range. My immediate gateway lives at the
telco exchange, with the address 10.1.1.1. I'm also assigned name
servers when I connect. By logging into the modem config application on
the 10.1.1.1 box I can see various technical settings pertaining to my
connection, including the *external* gateway through which I access the
internet proper; currently this gateway is 222.153.169.179.

Since I did the kernel upgrade, I seem unable to get past this external
gateway. I can ping 10.1.1.1 and 222.153.169.179, but *not* the DNS
servers assigned to me or - for that matter - anything else.

And I should note that for all my aspersions directed against my new
kernel, I'm now getting the same result using either of my remaining
'old' ones: 2.6.8-2-686 and 2.4.26-1-386. Err...and I upgraded a whole
bunch of other stuff around the same time, too.

He added helpfully.

brendon@der:~$ uname -a
Linux der.z.gen.nz 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686
GNU/Linux

brendon@der:~$ ifconfig
eth0 Link encap:Ethernet HWaddrXX:XX:XX:XX:XX:XX
inet addr:10.1.1.151 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::250:baff:fe55:7f90/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:469 errors:0 dropped:0 overruns:0 frame:0
TX packets:390 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:359260 (350.8 KiB) TX bytes:42533 (41.5 KiB)
Interrupt:185 Base address 0xd800

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:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6304 (6.1 KiB) TX bytes:6304 (6.1 KiB)

brendon@der:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.0.0.0 U 0 0 0 eth0
default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0

# pinging "internal" gateway:

brendon@der:~$ ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=64 time=0.404 ms
[etc]

# pinging external gateway:

brendon@der:~$ ping 222.153.169.179
PING 222.153.169.179 (222.153.169.179) 56(84) bytes of data.
64 bytes from 222.153.169.179: icmp_seq=1 ttl=64 time=0.424 ms
[etc]

brendon@der:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 202.27.158.40
nameserver 202.27.156.72

brendon@der:~$ ping 202.27.158.40
PING 202.27.158.40 (202.27.158.40) 56(84) bytes of data.

....nope.

================================================== ===

So, I'm at my wits end, hoping this will ring some bells somewhere out
there. Help?

Thanks for yr time,
Brendon Ryniker.

brendon ryniker wrote:
> dear all
>
> I run debian unstable and recently upgraded my kernel (via synaptic) to
> 2.6.12. This left me unable to use the internet as explained below - or
> let's say that it was at this time that my internet connxn turned bad.
>
> Out here in the country (in new zealand) I'm currently obliged to use as
> an ISP our national monopolistic telco, the specific service provided
> being ADSL. I am supplied with a D-Link DSL-302G ADSL modem.
> Essentially, it seems I'm on a private subnet; I'm dynamically assigned
> an IP address in the 10.*.*.* range. My immediate gateway lives at the
> telco exchange, with the address 10.1.1.1. I'm also assigned name
> servers when I connect. By logging into the modem config application on
> the 10.1.1.1 box I can see various technical settings pertaining to my
> connection, including the *external* gateway through which I access the
> internet proper; currently this gateway is 222.153.169.179.
>
> Since I did the kernel upgrade, I seem unable to get past this external
> gateway. I can ping 10.1.1.1 and 222.153.169.179, but *not* the DNS
> servers assigned to me or - for that matter - anything else.
>
> And I should note that for all my aspersions directed against my new
> kernel, I'm now getting the same result using either of my remaining
> 'old' ones: 2.6.8-2-686 and 2.4.26-1-386. Err...and I upgraded a whole
> bunch of other stuff around the same time, too.
Well, can you ping an external IP address, e.g. 192.25.206.10 (which is
www.debian.org). If so (and you probably can), your name servers are
probably screwed. ASk your ISP about it (or with any luck it will soon
fix by itself).

Robert
>
> He added helpfully.
> [snip]

Robert Harris wrote:

>> Since I did the kernel upgrade, I seem unable to get past this
>> external gateway. I can ping 10.1.1.1 and 222.153.169.179, but *not*
>> the DNS servers assigned to me or - for that matter - anything else.
>>
> Well, can you ping an external IP address, e.g. 192.25.206.10 (which is
> www.debian.org). If so (and you probably can), your name servers are
> probably screwed. ASk your ISP about it (or with any luck it will soon
> fix by itself).
>

well no I can't, actually - that's the bleeding problem. As above, the
most remote interface I can ping is the out-facing gateway on the ADSL
exchange server - ie: the public interface of the 10.*.*.* network that
me and other ADSL punters connect to in the first instance.

cheers,
/b/

brendon ryniker wrote:
> Robert Harris wrote:
>
>>> Since I did the kernel upgrade, I seem unable to get past this
>>> external gateway. I can ping 10.1.1.1 and 222.153.169.179, but *not*
>>> the DNS servers assigned to me or - for that matter - anything else.
>>>
>> Well, can you ping an external IP address, e.g. 192.25.206.10 (which
>> is www.debian.org). If so (and you probably can), your name servers
>> are probably screwed. ASk your ISP about it (or with any luck it will
>> soon fix by itself).
>>
>
> well no I can't, actually - that's the bleeding problem. As above, the
> most remote interface I can ping is the out-facing gateway on the ADSL
> exchange server - ie: the public interface of the 10.*.*.* network that
> me and other ADSL punters connect to in the first instance.
>
> cheers,
> /b/
Your routing table looks fine, so if you can reach your external
gateway, your ISP's routing is screwed. Talk to your ISP.

Robert