First make sure you have set up your ISDN-card correctly and started the ISDN-subsystem with /etc/rc.d/init.d/isdn4linux start (Please refer to Section 4.2 for more information). You may now try to start ipppd and set up the netdevice by: /sbin/ifup ippp0
Enter /sbin/ifconfig ippp0 and /sbin/route -n to see if your netdevice-settings and routing are correct. If you have set GATEWAYDEV="ippp0" in /etc/sysconfig/network, your default-route (Destination 0.0.0.0) should be set to the REMOTEADDR of Interface ippp0. On my machine it looks like:
[root@picard /]# /sbin/ifconfig ippp0 ippp0 Link encap:Point-to-Point Protocol inet addr:192.168.100.1 P-t-P:192.168.100.2 Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:3307 errors:0 dropped:0 overruns:0 frame:0 TX packets:3082 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 |
and:
[root@picard /]# /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.2 0.0.0.0 255.255.255.255 UH 0 0 0 ippp0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 20 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 12 lo 0.0.0.0 192.168.100.2 0.0.0.0 UG 0 0 0 ippp0 |
Make sure you have started your ipppd-device (take a look at Section 5.3). Now you may try to do a ping to your providerīs nameserver. In /var/log/messages you should see messages from your ipppd.
Enter /sbin/isdnctrl list ippp0 to see if isdnlog has changed your hup- timeout. Of course this is only true if you started isdnlog as well and set the right phone number in callerid.conf.
Enter /sbin/ifconfig ippp0 and /sbin/route -n.
[root@picard /]# ping -c 1 212.227.14.1 PING 212.227.14.1 (212.227.14.1): 56 data bytes 64 bytes from 212.227.14.1: icmp_seq=0 ttl=63 time=29.0 ms --- 212.227.14.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 29.0/29.0/29.0 ms [root@picard /]# /sbin/ifconfig ippp0 ippp0 Link encap:Point-to-Point Protocol inet addr:212.227.15.44 P-t-P:212.227.14.10 Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:3421 errors:0 dropped:0 overruns:0 frame:0 TX packets:3173 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 [root@picard /]# /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 212.227.14.10 0.0.0.0 255.255.255.255 UH 0 0 0 ippp0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 19 eth0 212.227.14.0 0.0.0.0 255.255.255.0 U 0 0 5 ippp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 11 lo 0.0.0.0 212.227.14.10 0.0.0.0 UG 0 0 0 ippp0 |
You should see your IP-addresses have changed due to dynamic-ip. If you have set DYN_IP="yes" in /etc/sysconfig/isdn, any pre-connect addresses will be rewritten upon connect to your dynamic address (look for messages of the kernel in /var/log/messages saying sth. like "shifting x.x.x.x to y.y.y.y") After huptime ipppd should automatically hang up (see Section 4.3. Your IP-addresses should be set back to the defaults in ifcfg-ippp0 (/sbin/ifconfig ippp0 and route -n should show similar results to Section 6.1).
Now you may add the startup of isdn4linux to the corresponding rc-levels by entering chkconfig --add isdn4linux. Make sure you have set ONBOOT to yes in Section 5.3. Reboot and look if everything's alright.
To ensure you will find your way to the internet you edit /etc/resolv.conf and enter your ISP’s name server IP. Or you might consider /etc/resolv.conf to be automatically changed by setting GET_DNS to "yes" in /etc/sysconfig/network-scripts/ifcfg-ippp0.
1999/12/29, http://www.webideal.de/rh-isdn/