[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

dsl router with woody crashes sometimes



Title: Nachricht
Hi & have nice new year to all,

I've got a problem with my DSL Router running Debian woody kernel
2.4.18-bf2.4 with 2 realtek network cards crashing abnormal.
I was not able to find a reason for that strange behaviour and so I changed the
machine and have now a notebook with two xircom cardbus cards there.
Again after routing one day - I couldnt reach the internet, no pings to
my router possible, the screen of the router was black and pressing
keys on the keyboard showed no effect.
Maybe my dsl modem ( delivered by german t-online 4 years ago with dsl contract )
is sending packets that causes my machine to freeze ?

In /var/log/messages I cant find anything:
...
Dec 31 12:46:33 gumble2 -- MARK --
next line is my reboot:
Dec 31 13:02:28 gumble2 syslogd 1.4.1#10: restart.
... snip ...
Dec 31 14:02:43 gumble2 kernel: tulip_attach(device 14:00.0)
Dec 31 14:02:43 gumble2 kernel: tulip.c:v0.91g-ppc 7/16/99
becker@scyld.com (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Dec 31 14:02:43 gumble2 kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:7A:8C:68, IRQ 11.
Dec 31 14:02:43 gumble2 kernel: cs: cb_config(bus 21)
Dec 31 14:02:43 gumble2 kernel:   fn 0 bar 1: io 0x400-0x47f
Dec 31 14:02:43 gumble2 kernel:   fn 0 bar 2: mem 0x60015000-0x600157ff
Dec 31 14:02:43 gumble2 kernel:   fn 0 bar 3: mem 0x60014000-0x600147ff
Dec 31 14:02:43 gumble2 kernel:   fn 0 rom: mem 0x60010000-0x60013fff
Dec 31 14:02:43 gumble2 kernel:   irq 11
Dec 31 14:02:43 gumble2 kernel: tulip_attach(device 15:00.0)
Dec 31 14:02:43 gumble2 kernel: eth1: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x400, 00:10:A4:7A:8C:3A, IRQ 11.
... ...
iptables is:

iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
iptables -N myconf
iptables -A myconf -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A myconf -m state --state NEW -i ! ppp0 -j ACCEPT
iptables -A myconf -p tcp --destination-port 22 -j ACCEPT
iptables -A myconf -j DROP
iptables -A INPUT -j block
iptables -A FORWARD -j block
echo 1 > /proc/sys/net/ipv4/ip_forward

I read something about the tulip driver that it maybee helps to put the
network interfaces into promiscuous mode? May that really be the
solution?

I did a ifconfig eth0 promisc ifconfig eth1 promisc ...

Where can i look for further error diagnostics /var/log/messages doesnt
help me ...

I'd be very glad if someone could help me with a tip.
Many thanks in advance

tobias 
tobias.pirzer@web.de

Reply to: