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

ISDN and routing problems



I'm having trouble with adapting the ISDN device to a 2.0.38 system. A
helpful person told me that the routing table lacks of some
information but he couldn't help me further.
The kernel correctly detects the AVM ISDN PCI device .
Hoping that Debian users have more knowledge in system internals and
being quite desperate after fidling now for a few days in the system:


GOOFY:[rland] #route -n
Kernel IP routing table
Destination  Gateway    Genmask         Flags Metric Ref    Use Iface
192.168.1.0  0.0.0.0    255.255.255.0   U     0      0        3 eth0
127.0.0.0    0.0.0.0    255.0.0.0       U     0      0        2 lo

Would someone kindly explain which route is missing if this mashine
has a local internet connection by dailing up to a ISP and recieving a
temporary IP adress?

Then the IP 192.168.1.0 pertubes me because:

GOOFY:[rland] #cat /etc/hosts
127.0.0.1 localhost localhost.domain
192.168.1.1 GOOFY.ORION.DE GOOFY
194.25.2.129 t-online.de t-online  #this is the ISP

...it does not match with the static IP adress I gave the eth0 card!


dmesg | less gives out:

ISDN subsystem Rev: 1.44.2.9/1.41.2.11/1.48.2.28/1.28.2.3/1.8.2.2
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.1 (kernel)
HiSax: Layer1 Revision 1.15.2.19
HiSax: Layer2 Revision 1.10.2.11
HiSax: TeiMgr Revision 1.8.2.7
HiSax: Layer3 Revision 1.10.2.6
HiSax: LinkLayer Revision 1.30.2.13
HiSax: Approval certification valid
HiSax: Approved with ELSA Quickstep series cards
HiSax: Approval registration numbers:
HiSax: German D133361J CETECOM ICT Services GmbH
HiSax: EU (D133362J) CETECOM ICT Services GmbH
HiSax: Total 1 card defined
HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
HiSax: AVM PCI/ISAPnP driver Rev. 1.1.2.8
AVM PCI: stat 0x3020a
AVM PCI: Class A Rev 2
HiSax: AVM Fritz!PCI config irq:12 base:0xD000
AVM PCI: ISAC version (10): 2086/2186 V1.1
AVM Fritz PnP/PCI: IRQ 12 count 0
AVM Fritz PnP/PCI: IRQ 12 count 3
HiSax: DSS1 Rev. 1.16.2.8
HiSax: 2 channels added

...so this doesn't look to bad.
and /var/log/messages seems to start ippp0 afer booting linux:

Oct 18 12:04:32 GOOFY init: Entering runlevel: 3
Oct 18 12:04:35 GOOFY sshd[389]: log: Server listening on port 22.
Oct 18 12:04:35 GOOFY sshd[389]: log: Generating 768 bit RSA key.
Oct 18 12:04:36 GOOFY sshd[389]: log: RSA key generation complete.
Oct 18 12:04:37 GOOFY syslog: Found 1 devices: /dev/ippp0, 
Oct 18 12:04:38 GOOFY pppd[457]: pppd 2.2.0 started by root, uid 0
Oct 18 12:04:38 GOOFY pppd[457]: init_unit: 0 
Oct 18 12:04:38 GOOFY pppd[457]: Connect[0]: /dev/ippp0, fd: 7


...but does the last line mean that pppd tries to dail in?

Maybe I should add the system has a reliable analog modem dailout via
pppd which I would like to replace with the ISDN device. Thus are
there any conficts to be expected in the ppp-system?





Robert



Reply to: