Topic: dialup connection with sme 7.2

[Daniel B.]

Hi.
Most of the time, I use SME with permanent DSL connection, it works like a charm. For the first time today, I had to configure a dialup connexion. But I cannot get it working. I'm not sure if it's a bug or not as I don't have any experience with this. Here's what I get:

When I boot, I have this:

ifconfig:

Code: [Select]

eth0      Lien encap:Ethernet  HWaddr 00:00:B4:BB:F5:89 
          inet adr:192.168.0.254  Bcast:192.168.0.255  Masque:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:6575 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3154 errors:0 dropped:0 overruns:0 carrier:0
          collisions:103 lg file transmission:1000
          RX bytes:573775 (560.3 KiB)  TX bytes:663413 (647.8 KiB)
          Interruption:169 Adresse de base:0xd000

lo        Lien encap:Boucle locale 
          inet adr:127.0.0.1  Masque:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2034 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2034 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:139105 (135.8 KiB)  TX bytes:139105 (135.8 KiB)

sl0       Lien encap:IP ligne s�rie 
          inet adr:192.168.0.254  P-t-P:0.0.0.0  Masque:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4548 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:10
          RX bytes:0 (0.0 b)  TX bytes:293250 (286.3 KiB)

The first strange thing for me is that sl0 has the same IP as eth0. It's not a real problem as my routes are like this:

Code: [Select]

default         *               255.255.255.255 UH    1      0        0 sl0
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
default         *               0.0.0.0         U     1      0        0 sl0

On demand connection doesn't seems to work properly, but this is another point. If I run sv t /service/wan, I can initiate the connexion. The modem is initialized, the number is dialed, everything seems to be ok until there:

Code: [Select]

Nov 20 19:29:56 sas diald[5982]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name ***** noauth noipdefault ipparam diald
Nov 20 19:29:56 sas pppd[5982]: pppd 2.4.4 started by root, uid 0
Nov 20 19:29:56 sas pppd[5982]: Using interface ppp0
Nov 20 19:29:56 sas pppd[5982]: Connect: ppp0 <--> /dev/ttyS0
Nov 20 19:29:56 sas diald[5887]: Running pppd (pid = 5982).
Nov 20 19:29:56 sas kernel: divert: not allocating divert_blk for non-ethernet device ppp0
Nov 20 19:30:26 sas pppd[5982]: LCP: timeout sending Config-Requests
Nov 20 19:30:26 sas pppd[5982]: Connection terminated.
As we can see, ppp0 is linked to ttyS0, but if I run ifconfig during the minute before the time out, I can see a ppp0 interface, but it's not up, nor configured (no IP), then I've got the LCP: timeout sending config-request message, and the connection is aborted.

I'll report this in the bug tracker too, but I'd like to here any positive or negative experience with SME7.2/dialup command.

Cheers, Daniel

[Daniel B.]

Sorry, forget about that, changing the modem did the trick. SME is just great !!!

[CharlieBrady]

I'll report this in the bug tracker too ...

As a member of the documentation team you shouldn't need to be reminded to always report problems only via the Bug Tracker.