"S. Champ" wrote:
>
> 3) having ipv6 configured into the kernel (on-install):
> would this be a possible problem-reason?
Don't know for sure, but I wouldn't be surprised. Also which kernel are
you using? I was unable to get the 2.2.17-pre-6 to work; it compiled and
booted fine but choked on net connections. With exactly the same kernel
configs, 2.2.15-3 works great.
> 4) something in the readme for the debian pppoe client (under what,
> paraphrased, reads like: "change * to dsl-provider" ) says something about
> "...and that line should now look like:" (what it doesn't hardly look like. )
In /etc/init.d/ppp you need to change a line in the start) and in the
stop) methods. Out of the box, the script just specifies "provider". You
need to change this to "dsl-provider" wherever you see "provider". That
happens in two places. (IE you're passing dsl-provider as the parameter
instead of provider.) So you end up with
pppd call dsl-provider
in the start) case and
poff dsl-provider
in the stop) case.
In /etc/ppp/peers/dsl-provider, you need to add a last line to the
script that consists of
user username
whatever your username is for your DSL account
> more details available, on-request. haven't cared to fuss-up a
> bug-report
> about it, between boots.
>
> maybe it's part of the reason(s) for the problems with connecting,
> maybe not.
> but it should probably be reported, sometime. ( with a net-connected
> debian-install, this should be no problem... .)
I don't think there is a bug here.
> 6) another odd thing:
>
> the following is a standard ifconfig-output, with notes aftewrwards:
>
> eth0 Link encap:Ethernet HWaddr 00:C0:F0:5A:DC:21
>
> inet addr:169.254.0.130 Bcast:255.255.255.255 Mask:255.255.0.0
> inet6 addr: fe80::c0:f05a:dc21/10 Scope:Link
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:100
> Interrupt:9 Base address:0xec00
>
> note: the value for "addr" is invalid, and seems to be a result of the
> router-table entry that i need to wipe-out. the 'mask' is for the ethernet
> card, not for the NAT (dsl router, dsl bridge, * . the mask for it is
> '255.255.255.0' . should i be using this net-mask, instead? )
You define what eth0 is in /etc/network/interfaces. If the mask is
wonky, it must be because you haven't configured that file correctly.
Since you're using pppoe, you must have a DSL account that dynamically
assigns your ip address, so you might as well give eth0 an "illegal"
address like 192.168.1.1. When you get connected to your ISP, your
"real" ip address will show up in the ppp0 device in ifconfig. But
obviously that won't happen until you get connected.
> the "RX packets" values have been around the hundreds, before. same for the
> "TX packets". this means that the software+hardware _is_ connnecting to the
> net, right?
Doesn't sound like it to me. Until you get pppoe working, you're not
connected.
HTH. Good luck.
