HELP: suse 7.1 drops kernel route ????
hi all, this now happened 3 times on suse 7.1 and kernel 2.4 which comes with suse 7.1 : the kernel seems to drop the routing table after a while. after starting the network (eth0 & eth1) & route & alias-ip (eth0:0 - eth0:38) adresses, everything works fine. route shows up the correct entrys, the domains can be reached and the server can connect to the internet (so route's are set up ok) after a while the connections are lost. the route command no longer shows any entrys ('hangs', i.e. can only terminated with ctrl-c) and the domains are no longer reachable. also, not always all ip's are unreachable, some still work, some not. and even worse, sometimes it can still be reached inside the network, but not from outside (i.e. ping to an adress from inside the net is ok but not from outside the net. and again, not all ip's are affected....) this is driving me crazy........ has anybody an idea what can cause this ?? greets, chris -- visit me at http://mamalala.de
Does route -n hang? If not, you may have flaky DNS and route is
waiting for it.
Jeffrey
Quoting Christian Klippel
hi all,
this now happened 3 times on suse 7.1 and kernel 2.4 which comes with suse 7.1 :
the kernel seems to drop the routing table after a while. after starting the network (eth0 & eth1) & route & alias-ip (eth0:0 - eth0:38) adresses, everything works fine. route shows up the correct entrys, the domains can be reached and the server can connect to the internet (so route's are set up ok) after a while the connections are lost. the route command no longer shows any entrys ('hangs', i.e. can only terminated with ctrl-c) and the domains are no longer reachable. also, not always all ip's are unreachable, some still work, some not. and even worse, sometimes it can still be reached inside the network, but not from outside (i.e. ping to an adress from inside the net is ok but not from outside the net. and again, not all ip's are affected....)
this is driving me crazy........
has anybody an idea what can cause this ??
greets,
chris
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
hi jeffrey, Am Freitag, 8. Juni 2001 17:29 schrieb Jeffrey Taylor:
Does route -n hang? If not, you may have flaky DNS and route is waiting for it.
Jeffrey
will try next time. but i ping the adresses via their ip-numbers instead of their names. just in this moment it is so, that for example 195.80.222.121 is set up as eth0:35 inside the network (from another machine) i can ping it, but not from outside (from my home) but, for example, 195.80.222.171 (eth0:36) can be pinged from booth ...... web:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 195.80.222.254 0.0.0.0 UG 0 0 0 eth0 is what route shows actually. part of ifconfig output : ........ eth0:35 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.121 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0:36 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.171 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ........ this really makes me crazy ..... greets, chris -- visit me at http://mamalala.de
IIRC, all ethernet cards have a register for the address, so
filtering that this packet is for this host is done in hardware.
Some cards have two address registers. I don't think there are any
that have 37 registers, so the NIC is in promiscuous mode and address
filtering is done is software. You may be finding the limits of the
software filtering. If this hypothesis is correct, reducing the
number of IP aliases or getting a faster CPU should help.
I read somewhere that a way to sometimes find packet sniffers on you
network is that they are slow to respond to pings because of the
address filtering load in promiscuous mode.
HTH,
Jeffrey
Quoting Christian Klippel
hi jeffrey,
Am Freitag, 8. Juni 2001 17:29 schrieb Jeffrey Taylor:
Does route -n hang? If not, you may have flaky DNS and route is waiting for it.
Jeffrey
will try next time. but i ping the adresses via their ip-numbers instead of their names. just in this moment it is so, that for example 195.80.222.121 is set up as eth0:35 inside the network (from another machine) i can ping it, but not from outside (from my home) but, for example, 195.80.222.171 (eth0:36) can be pinged from booth ......
web:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 195.80.222.254 0.0.0.0 UG 0 0 0 eth0
is what route shows actually.
part of ifconfig output :
........ eth0:35 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.121 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:36 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.171 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ........
this really makes me crazy .....
greets,
chris
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
re again, Am Freitag, 8. Juni 2001 18:37 schrieb Jeffrey Taylor:
IIRC, all ethernet cards have a register for the address, so filtering that this packet is for this host is done in hardware. Some cards have two address registers. I don't think there are any that have 37 registers, so the NIC is in promiscuous mode and address filtering is done is software. You may be finding the limits of the software filtering. If this hypothesis is correct, reducing the number of IP aliases or getting a faster CPU should help.
I read somewhere that a way to sometimes find packet sniffers on you network is that they are slow to respond to pings because of the address filtering load in promiscuous mode.
HTH, Jeffrey
huh, no. the nic is actually not in promiscuous mode : web:~ # /etc/rc.d/network status eth0 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.160 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11986023 errors:0 dropped:0 overruns:0 frame:0 TX packets:24995921 errors:0 dropped:0 overruns:116 carrier:0 collisions:0 eth1 Link encap:Ethernet HWaddr 00:50:BA:39:50:3A inet addr:195.80.222.161 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10783535 errors:0 dropped:0 overruns:0 frame:0 TX packets:1281557 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 but, i think we have found the problem : it may be the switch who makes some trouble. the "missing" ip-numbers have just reappeared, one by one. so i connected the nic's to another switch, did network & route restart and voila, all is there ........ so it must have been the switch. thanks for your quick help anyway, chris -- visit me at http://mamalala.de
Hi !! I have finish to install SuSE 7.1 on my IBM ThinkPad 770... KDE works fine at 1224x728 :) But my console stays at 80X25... it uses only a very small part of the screen... is there any way to use the full Screen ? in any virtual console ? thanks bye --ed
Linux - User wrote:
Hi !!
I have finish to install SuSE 7.1 on my IBM ThinkPad 770... KDE works fine at 1224x728 :)
But my console stays at 80X25... it uses only a very small part of the screen... is there any way to use the full Screen ? in any virtual console ?
thanks
add a line like: append="vga=0x0301" to the global section of lilo.conf. I do not know the setting 1224x728. See the SuSE manual for this. Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
Linux - User wrote:
Hi !!
I have finish to install SuSE 7.1 on my IBM ThinkPad 770... KDE works fine at 1224x728 :)
But my console stays at 80X25... it uses only a very small part of the screen... is there any way to use the full Screen ? in any virtual console ?
thanks
add a line like: append="vga=0x0301" to the global section of lilo.conf. I do not know the setting 1224x728. See the SuSE manual for this.
Juergen AFAIK, the hex vga modes may be hardware specific, so proceed with caution. A safe technique is to insert 'vga=ask' in the global section of
On Fri, 8 Jun 2001, Juergen Braukmann wrote: lilo.conf. Then on the next boot, it'll give you a menu of available modes. When you find one you like, code it in lilo.conf. ...as usual, after any change to lilo.conf, run /sbin/lilo to make it effective. -- Rick Green "I have the heart of a little child, and the brain of a genius. ... and I keep them in a jar under my bed"
Rick Green wrote:
On Fri, 8 Jun 2001, Juergen Braukmann wrote:
Linux - User wrote:
Hi !!
I have finish to install SuSE 7.1 on my IBM ThinkPad 770... KDE works fine at 1224x728 :)
But my console stays at 80X25... it uses only a very small part of the screen... is there any way to use the full Screen ? in any virtual console ?
thanks
add a line like: append="vga=0x0301" to the global section of lilo.conf. I do not know the setting 1224x728. See the SuSE manual for this.
Juergen AFAIK, the hex vga modes may be hardware specific, so proceed with caution. A safe technique is to insert 'vga=ask' in the global section of lilo.conf. Then on the next boot, it'll give you a menu of available modes. When you find one you like, code it in lilo.conf. ...as usual, after any change to lilo.conf, run /sbin/lilo to make it effective.
Yes, that it better. There is a list of modes in the manual, but "ask" is the best option for experimenting. I hope, I memorise that for the next time I am asked. ;-) And you're right: It's a good idea to re-run lilo. With linux I reboot so seldom, that I forget these basic things. ;-) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
participants (5)
-
Christian Klippel -
Jeffrey Taylor -
Juergen Braukmann -
Linux - User -
Rick Green