Re: configuring the network under knoppix

Christian Perle wrote:
> Hi Joris,
> 
> On Fri, Apr 16, 2004 at 13:55:30 +0200, Joris Huizer wrote:
> 
> 
>>So I tried knoppix, and, appart from not being able to write to the 
>>screen during loading/shutting down, it worked - everything except for 
>>the netwerk. I use an adsl modem of which I know it's usable in knoppix: 
>>on my own computer I use the same adsl modem;
> 
> 
> I don't know anything about asdl in the Netherlands. Does it actually
> use PPPoE or a different protocol?
> 
> 
>>I don't know anything about the netwerk card - it's only reported as 
>>?nbord 10/100 mbit network card" - but it uses the modem I normally use 
>>so the only problem it can be is the netwerk card. I tried pppoe in 
>>knoppix but no luck
>>
>>I attached two output files, from lsmod output and dmesg output; And a 
>>logfile containing output from `ping localhost`, `ifconfig -a` , `ping 
>>10.0.0.138`, and I attached the error from `pppoe`
> 
> 
> The adsl "modem" could be a router with integrated dhcp server.
> Try "pump -i eth0".
> 
> 
>>eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
> 
> 
> This doesn't look like a adsl modem. The link should be 10mbps
> half-duplex. At least this is what I see when I connect my dsl modem
> (german telekom) to my machine.
> 
> 
>>Module                  Size  Used by    Not tainted
> 
> [...]
> 
>>8139too                17160   1 
> 
> 
> Maybe the 8139 has an interrupt problem when APIC is turned on.
> Try "knoppix noapic" at the Knoppix boot prompt.
> 
> You can also monitor outgoing/incoming network packets on the ethernet
> card before starting pppoe or pump:
> tcpdump -ni eth0
> 
> bye,
>   Chris

Thanks for your reply.
I tried this but it didn't really help. I got some output from the 
tcpdump but it ended with "network is down"

I forgot to tell you my adsl connection is over dhcp. relevant data from 
the boot log on this other computer:

Sat Apr 17 21:00:29 2004: For info, please visit 
http://www.isc.org/dhcp-contrib.html
Sat Apr 17 21:00:29 2004:
Sat Apr 17 21:00:30 2004: Listening on LPF/eth0/00:80:ad:75:b5:88
Sat Apr 17 21:00:30 2004: Sending on   LPF/eth0/00:80:ad:75:b5:88
Sat Apr 17 21:00:30 2004: Sending on   Socket/fallback/fallback-net
Sat Apr 17 21:00:31 2004: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 4
Sat Apr 17 21:00:31 2004: receive_packet failed on eth0: Network is down
Sat Apr 17 21:00:33 2004: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 5
Sat Apr 17 21:00:38 2004: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 13
Sat Apr 17 21:00:51 2004: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 10
Sat Apr 17 21:00:51 2004: DHCPOFFER from 10.0.0.138
Sat Apr 17 21:00:53 2004: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sat Apr 17 21:00:54 2004: DHCPACK from 10.0.0.138
Sat Apr 17 21:00:54 2004: bound to 10.0.0.151 -- renewal in 3600 seconds.
Sat Apr 17 21:00:54 2004: done.

Can you tell how I could try to get dhcp to work? I found there is a 
/sbin/dhcpd3 but I didn't see how to make it work as the configuration 
file was read-only (even for root) and the program didn't do configuring 
by itself

I hope you can help,

Joris