Sure - here is the network config and a small demonstration. With the
router on 192.168.0.1 things (ftp,wget,apt-get) work nicely (but over
ISDN); using 192.168.0.2 as router things do not work. Using my wintel
box and Knoppix, things look the same, but here things work! Strangely
enough I net-installed Sarge on my 7500, but this was with the 2.6
kernel on the netinst cd, while i was forced to use the 2.4 kernel,
since I couldn't get my SCSI disks to mount root during boot-up. Thanks
for your help!
Matthia
debian:/home/matts# *ifconfig*
eth0 Protokoll:Ethernet Hardware Adresse 00:05:02:14:B6:8E
inet Adresse:192.168.0.33 Bcast:192.168.0.255
Maske:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128 errors:0 dropped:0 overruns:0 frame:0
TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:6154 (6.0 KiB) TX bytes:5784 (5.6 KiB)
Interrupt:14 Basisadresse:0x1000
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:65 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:3633 (3.5 KiB) TX bytes:3633 (3.5 KiB)
debian:/home/matts# route -n
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
debian:/home/matts# route del default
debian:/home/matts# route add default gw 192.168.0.2
debian:/home/matts# route -n
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 eth0
debian:/home/matts# traceroute www.debian.org
traceroute to www.debian.org (194.109.137.218), 30 hops max, 38 byte packets
1 xdsl-195-14-205-1.netcologne.de (195.14.205.1) 51.792 ms 52.136
ms 52.264 ms
2 195.14.247.178 (195.14.247.178) 52.808 ms 51.418 ms 50.890 ms
3 core-maw2-vl201.netcologne.de (195.14.195.153) 50.731 ms 51.777
ms 50.442 ms
4 core-pg2-vl203.netcologne.de (195.14.215.201) 51.618 ms 51.602 ms
51.844 ms
5 rtint3-g12.netcologne.de (195.14.247.195) 50.785 ms 51.493 ms
49.270 ms
6 rtamsix-po20.netcologne.de (81.173.192.18) 65.522 ms 64.026 ms
67.737 ms
7 ams-ix.tc2.xs4all.net (195.69.144.166) 65.900 ms 66.716 ms 65.225 ms
8 0.so-7-0-0.xr1.d12.xs4all.net (194.109.5.9) 64.978 ms
0.so-7-0-0.xr2.d12.xs4all.net (194.109.5.13) 66.596 ms
0.so-7-0-0.xr1.d12.xs4all.net (194.109.5.9) 65.706 ms
9 0.ge-1-3-0.cr1.d12.xs4all.net (194.109.5.74) 65.317 ms 64.243 ms
0.so-3-0-0.cr1.d12.xs4all.net (194.109.5.58) 65.452 ms
10 klecker.debian.org (194.109.137.218) 118.246 ms 63.232 ms 66.931 ms
debian:/home/matts# route del default
debian:/home/matts# route add default gw 192.168.0.1
debian:/home/matts# traceroute www.debian.org
traceroute to www.debian.org (194.109.137.218), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 4.880 ms 4.010 ms 4.662 ms
2 as5800-rs4-lo0.netcologne.de (195.14.247.73) 212.355 ms 26.589 ms
27.374 ms
3 cat6509-pg2-vl50.netcologne.de (194.8.216.222) 27.489 ms 26.768
ms 27.503 ms
4 rtint3-g12.netcologne.de (195.14.247.195) 27.416 ms 27.409 ms
26.645 ms
5 rtamsix-po21.netcologne.de (195.14.215.210) 43.154 ms 44.085 ms
45.005 ms
6 ams-ix.tc2.xs4all.net (195.69.144.166) 41.610 ms 48.272 ms 54.323 ms
7 0.so-7-0-0.xr1.d12.xs4all.net (194.109.5.9) 45.322 ms
0.so-7-0-0.xr2.d12.xs4all.net (194.109.5.13) 47.328 ms
0.so-7-0-0.xr1.d12.xs4all.net (194.109.5.9) 44.276 ms
8 0.ge-1-3-0.cr1.d12.xs4all.net (194.109.5.74) 42.773 ms
0.so-3-0-0.cr1.d12.xs4all.net (194.109.5.58) 44.497 ms
0.ge-1-3-0.cr1.d12.xs4all.net (194.109.5.74) 155.132 ms
9 klecker.debian.org (194.109.137.218) 47.405 ms 46.081 ms 42.775 ms
david@qednet.biz schrieb:
Can you post the routing table output with regard to the two instances, ie
the output of "route -n"
d
Hi!
I have a weired network problem. I have an ISDN router on 192.168.0.1
and a DSL router on 192.168.0.2. Both work nicely from other OS. Now I
set up the default route to point to teh ISDN router with "route add
default gw 192.168.0.1" and everything is up and running over ISDN.
Traceroute to some host shows the first hop to go to 192.168.0.1 and
then over a few more steps to the target. ftp,lynx, apt-get update and
so on work fine. A traceroute to 192.168.0.1 shows just that one hop
(this is correct). So far so good, now let's try to speed things up a bit
Now to the weired part: I Delete the default route and add it back using
"route add default gw 192.168.0.2". Try to ping some host and it works
nicely. Try to ping 192.168.0.2 and it is OK. Try a traceroute to some
host, this time the list *misses* the hop to 192.168.0.2 and goes
directly to the follwing hosts reaching the target eventually.
Trying to ftp somewhere yields no connection now. Access within the
local network is OK, but besides ping (which works when trying to access
anything beyond the router nicely) and traceroute does not give a
connection.
Both routers are netgear devices and work nicely from Knoppix, Windows,
MacOS 8 and 9 give a good connection on first attempt. Any ideas?
Regards
Matthias
--
To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
-------------------
david howe
www.qednet.biz
-------------------