Mfl

[Back] [Content] [Next]

---

To be on the save site, you should reboot now and load your desktop with long filename support. Go to drive u: and open folder u:/bin. Now start the bash with a doubleclick, you can just click OK in the appearing box and now you should be in the unix shell, put away your mouse it is not needed now.:)
If this works o.k., at this point a little congratulation to you! Enter pppd at the bash prompt and press RETURN, the LED's on your modem should start to flicker and the modem should start to dial, on the screen there should appear something like this:

             Apr 20 19:10:58 HOSTNAME pppd[104]: pppd 2.2.0 started by root, uid 0

           

After the usual tittering of the modem, there should appear something like this:

             Apr 20 19:11:28 HOSTNAME pppd[104]: Serial connection established.
             Apr 20 19:11:30 HOSTNAME pppd[104]: Using interface ppp0
             Apr 20 19:11:30 HOSTNAME pppd[104]: Connect: ppp0 <--> /dev/ttyb
             Apr 20 19:11:30 HOSTNAME pppd[104]: Remote message:
             Apr 20 19:11:30 HOSTNAME pppd[104]: local  IP address 195.227.9.249
             Apr 20 19:11:30 HOSTNAME pppd[104]: remote IP address 195.227.9.5

           

Congratulations you are with MiNT-Net in the internet!

Mfl

Enter ifconfig at the bash prompt, when no connection is established, then there should appear something like this:

             lo0:    flags=0x4b
             inet 127.0.0.1 netmask 255.0.0.0 broadcast 127.255.255.255
             metric 0 mtu 16384
             in-packets  64 in-errors  0 collisions 0
             out-packets 64 out-errors 0

             

With an established connection it looks like this:

              lo0:    flags=0x4b
                      inet 127.0.0.1 netmask 255.0.0.0 broadcast 127.255.255.255
                      metric 0 mtu 16384
                      in-packets  4 in-errors  0 collisions 0
                      out-packets 4 out-errors 0
              ppp0:   flags=0x51
                      link-level-flags=0x13
                      inet 62.155.253.103 netmask 255.255.255.0 dstaddr 193.158.133.13
                      metric 0 mtu 1500
                      in-packets  1527 in-errors  3 collisions 0
                      out-packets 1590 out-errors 0
              

Mfl

route shows when there is no connection established, something like this:

               Destination         Gateway             Flags   Ref      Use Metric Iface
               127.0.0.0           *                   U         1        0      0 lo0
               127.0.0.1           *                   UH        1      132      0 lo0

              

When a connection is established route shows this:

               Destination         Gateway             Flags   Ref      Use Metric Iface
               default             193.158.133.13      UGD       1      585      0 ppp0
               62.155.253.103      *                   UH        1      413      0 lo0
               127.0.0.0           *                   U         1        0      0 lo0
               127.0.0.1           *                   UH        1       12      0 lo0
               193.158.133.13      *                   UHD       1        0      0 ppp0

              

Mfl

Now we will test if we're able to get out in the wide world, you can test this with the program u:/usr/etc/ping. You have to enter the following at the bash prompt:

            bash-2.03# ping 194.97.97.10


            

With this comand we have pinged the nameserver of NDH, ping gives us something like this:

                PING 194.97.97.10 (194.97.97.10): 56 data bytes
                64 bytes from 194.97.97.10: icmp_seq=0 ttl=252 time=190 ms
                64 bytes from 194.97.97.10: icmp_seq=1 ttl=252 time=140 ms
                64 bytes from 194.97.97.10: icmp_seq=2 ttl=252 time=185 ms
                64 bytes from 194.97.97.10: icmp_seq=3 ttl=252 time=165 ms
                64 bytes from 194.97.97.10: icmp_seq=4 ttl=252 time=900 ms
                64 bytes from 194.97.97.10: icmp_seq=5 ttl=252 time=165 ms
                64 bytes from 194.97.97.10: icmp_seq=6 ttl=252 time=160 ms
                64 bytes from 194.97.97.10: icmp_seq=7 ttl=252 time=160 ms

            

Now you can look at this until the end of days, but we break this now with Ctrl C and get this:

                --- 194.97.97.10 ping statistics ---
                8 packets transmitted, 8 packets received, 0% packet loss
                round-trip min/avg/max = 140/258/900 ms

            

If you got nothing after entering ping, cancel connection, and read the whole stuff from the /etc/ppp/options. Usually there is an error in resolv.conf or you have played with the options in /etc/ppp/options -file, although I told you, not to do that.;^)
But if the test with ping is alright, you can try, if you can go behind the nameserver, enter this:

                bash-2.03# ping www.suse.de

            

There should appear something like above, when this was alright you can lay back, smoke a cigarette or suck a lolli and knock heavy on your shoulders, because now you will be a member of the exclusive MiNT-Net user club.;-)
It wasn't so heavy, wasn't it?

Mfl

With traceroute you can pursue over, which servers an inquiry is going and how long this does take.
As an example we have tried the SuSE-Server, enter the following:

              bash-2.03# traceroute www.suse.de

            

There should appear something like this on the screen:

             traceroute to Turing.suse.de (194.112.123.200), 30 hops max, 38 byte packets
             1  193.158.133.13 (193.158.133.13)           210 ms  115 ms  120 ms
             2  193.158.133.14 (193.158.133.14)           140 ms  125 ms  120 ms
             3  KO-gw1.KO.net.DTAG.DE (193.158.127.198)   120 ms  120 ms  115 ms
             4  GI-gw1.GI.net.DTAG.DE (194.25.121.133)    125 ms  115 ms  120 ms
             5  F-gw12.F.net.DTAG.DE (194.25.120.249)     850 ms  140 ms  720 ms
             6  M-gw12.M.net.DTAG.DE (194.25.121.26)      115 ms  115 ms  160 ms
             7  s11-0-0-r3-MUC.ecrc.net (194.221.13.49)   160 ms  120 ms  125 ms
             8  s11-0-0-r3-MUC.ecrc.net (194.221.13.49)   115 ms  155 ms  120 ms
             9  fe1-0-0-r3-MUC.ecrc.net (62.208.255.3)    760 ms  120 ms  165 ms
            10  pos1-0-0-r1-MUC2.ecrc.net (62.208.240.6)  155 ms  115 ms  160 ms
            11  s1-0-0-r2-NBG.ecrc.net (194.221.49.114)   120 ms  150 ms  160 ms
            12  suse-gw-r2-NBG.ecrc.net (195.27.61.78)    485 ms  615 ms  525 ms
            13  * * *
            14  * * *
            15  * * *
            

If you got errors like "unknown host", then you should check the /etc/resolv.conf if the nameserver is correct.

Mfl

With the tool nslookup you can get the whole name of an IP address, establish a connection and enter this:

              bash-2.03# nslookup 194.97.97.10.

            

there should appear something like this:

              Server:   atlantic.ndh.net ---- this could be various
                                              depending on
                                              the entered DNS
              Address:  194.97.97.10     -----'

              Name      atlantic.ndh.net
              Address:  194.97.97.10

            

Now we experienced, that the "name" of the IP address 194.25.2.130 is atlantic.ndh.net.
If you only enter nslookup at the bash prompt, you got a shell where you can enter all kinds of IP addresses.:) You can exit this shell, with the comand exit.

Mfl

Oh I've lost to tell you how you can disconnect from your provider. We provisionally make this with the brutal method, no not with the chain saw.;-) But we kill the pppd, no, I told you, not with the chainsaw.;-) Enter ps at the bash prompt, then you get something like this:

             078  000   4     4  TSR     4200240 00:00.01  LPDEV
             079  066   4     4  Wait     133488 00:01.31  COPS
             081  000   4     4  Wait     233776 00:00.06  GLUESTIK
             082  000   4     4  TSR      111360 00:00.02  WDIALOG
             084  066  20    20  Wait     275744 00:06.79  TOSWIN2
             087  066   0     0  Ready    140656 00:02.98  TASKBAR
             088  000  20    20  TSR       43968 00:00.00  68882
             089  066   4     4  Wait     408512 00:49.56  QED
             110  066   4     4  Wait     366208 00:00.37  micokonf
             112  066   4     4  Wait     270464 00:11.56  micodial

             114  000  20    20  Sleep    185200 00:00.26  pppd ----------
             ^^^
             119  084   4     4  Sleep    486208 00:02.09  tcsh
             122  119   4    20  Ready     32784 00:00.17  ps
            

This may look various, depending on which programs you are running. But we're only interested in the pppd. In the beginning of the line of pppd there is a digit, this is the so called pid (process identification), when entering the following at the bash prompt:

             bash-2.03# kill 114


            

the modem should hangup. You can also find the pid, when looking into the folder u:/proc, there are all running processes specified, the file extension is the pid.

---

[Back] [Content] [Next]