[Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1847 [EMAIL PROTECTED] changed: What|Removed |Added Version|9.1-26mdk |9.2-0.7mdk --- Additional Comments From [EMAIL PROTECTED] 2003-01-07 17:12 --- This bug has been automatically updated to last version of product available. Please check if it is still valid. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands.
[Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1847 [EMAIL PROTECTED] changed: What|Removed |Added Version|9.1-21mdk |9.1-26mdk --- Additional Comments From [EMAIL PROTECTED] 2003-04-03 23:31 --- Still valid in final. ONBOOT of network device ippp0 ist set to no and I get not asked like on normal NICs --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands.
Re: [Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
On Thursday 06 March 2003 17:56, andre wrote: > On Thursday 06 March 2003 17:22, Steffen Barszus wrote: > > On Thursday 06 March 2003 13:34, rcc wrote: > > > definitely, Germany (=ISDN country) is the second largest market next > > > to the US. I just don't understand how mdk can afford to surrender that > > > market to SuSE. I've personally converted lots of people to Mandrake > > > but I always am somwhat reluctant when I meet people with ISDN because > > > of the rather suboptimal ISDN support of mdk. > > > > Yes and that is bugging me a lot. It seems there aren't a lot of people > > using isdn on cooker, but I know there are a lot outside from cooker, > > mostly people, that try to understand linux. Even Redhat is better on > > isdn now then mandrake. And that there redhat is a full american distro. > > I cant currently do more then try to help. I guess ISDN will get at least > > in europe more important. Maybe DSL is more and more important for > > internet connection, but isdn is not only internetconnection. I would not > > complain so much if it wouldn't be a problem since 6.1 to have isdn nice > > and running. It got better , but it is far from optimal. > > Dial up in general seems to be problematic for mandrake. I don't know why > > modems are detected if the users are using kppp or similar apps anyway > > and have to configure it by hand then. > > To run cooker you need a lot of cheap bandwidth. ISDN doesn't deliver that > so running cooker is not likely Yes this could explain it. I have the cooker-list only for checking whats going on, since I can't run cooker too. A sat-feed with cooker would be good , so that anybody with digital sat could get it. But I guess something like that is not realistic. -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
On Thursday 06 March 2003 17:22, Steffen Barszus wrote: > On Thursday 06 March 2003 13:34, rcc wrote: > > definitely, Germany (=ISDN country) is the second largest market next to > > the US. I just don't understand how mdk can afford to surrender that > > market to SuSE. I've personally converted lots of people to Mandrake but > > I always am somwhat reluctant when I meet people with ISDN because of > > the rather suboptimal ISDN support of mdk. > > Yes and that is bugging me a lot. It seems there aren't a lot of people > using isdn on cooker, but I know there are a lot outside from cooker, > mostly people, that try to understand linux. Even Redhat is better on isdn > now then mandrake. And that there redhat is a full american distro. I cant > currently do more then try to help. I guess ISDN will get at least in > europe more important. Maybe DSL is more and more important for internet > connection, but isdn is not only internetconnection. I would not complain > so much if it wouldn't be a problem since 6.1 to have isdn nice and > running. It got better , but it is far from optimal. > Dial up in general seems to be problematic for mandrake. I don't know why > modems are detected if the users are using kppp or similar apps anyway and > have to configure it by hand then. To run cooker you need a lot of cheap bandwidth. ISDN doesn't deliver that so running cooker is not likely
Re: [Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
On Thursday 06 March 2003 13:34, rcc wrote: > definitely, Germany (=ISDN country) is the second largest market next to > the US. I just don't understand how mdk can afford to surrender that > market to SuSE. I've personally converted lots of people to Mandrake but > I always am somwhat reluctant when I meet people with ISDN because of > the rather suboptimal ISDN support of mdk. Yes and that is bugging me a lot. It seems there aren't a lot of people using isdn on cooker, but I know there are a lot outside from cooker, mostly people, that try to understand linux. Even Redhat is better on isdn now then mandrake. And that there redhat is a full american distro. I cant currently do more then try to help. I guess ISDN will get at least in europe more important. Maybe DSL is more and more important for internet connection, but isdn is not only internetconnection. I would not complain so much if it wouldn't be a problem since 6.1 to have isdn nice and running. It got better , but it is far from optimal. Dial up in general seems to be problematic for mandrake. I don't know why modems are detected if the users are using kppp or similar apps anyway and have to configure it by hand then. -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
On Thursday 06 March 2003 01:16, rcc wrote: > On Wed, 5 Mar 2003 22:23:49 +0100 > > Steffen Barszus <[EMAIL PROTECTED]> wrote: > > Currently I test LineControl as GUI dial up tool (very nice) ;) > > why does that remind me of kinternet? I think the concept is similar > when used on a local machine... > *grin* Yes the pixmap is very similar . (the same ?) And yes something like kinternet is needed for mandrake. I had last week a user that asked how to establish the internet connection without setting it to "dialup at boot" and reboot. (<= LOL) > > it would be fine to create a group dialup on installation (or is there > > one in mandrake?) > > pppusers? But that has given me headaches without end. On all dial up > machines I installed there were weird permissions probs. I guess I could help you on that. ;) The pppd manpages proposes to use peer scripts. A user can execute pppd , but can only do well defined things. One of this things is to start defined dial up connections. This connections are configured under /etc/ppp/peers/, for example /etc/ppp/peers/isp1. pppd call isp1 would start the dialup then. The pppd should be running as uid root then so no ownership of devices needs to be changed. (I know you have not asked ;)) Related question: Where do the device settigs belong to ? Are they initially set by the kernel package ? > > > and set the rights and ownership on /sbin/isdnctrl > > and the devices right. As I read is a user (with isdn4k-utils 3.2pre3) > > only allowed to dial and hangup with isdnctrl, so another reason for > > updating isdn4k-utils. > > I guess I have to do that myself for now it's probably too late for 9.1 > _If_ you going to make it, I have yet another bug open for some changes on isdn4k-utils-packaging and i can mail you a .config for the package. Since there are no important security flaws in it I guess it is to late. BTW: The vbox-examples are missing too. (another open bug from me ;)) Some notes for after release: The packaging: Currently : 1 monster rpm with 5mb As it is proposed by isdn4linux and done by debian: isdn-utils isdn-active-cards vbox2 . For active cards (and AVM cards) would capi4hylafax be interesting (something for contrib). I know all that has time now, but maybe it would be good for next release. -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
On Wednesday 05 March 2003 21:07, rcc wrote: > On Wed, 5 Mar 2003 14:50:04 -0500 (EST) > > st_barszus wrote: > > Still valid, the device should be set to ONBOOT="yes" after > > configuration or it should be asked like it is done for network cards. > > thanks for bringing this up again, I almost forgot about it. How's the > capi stuff doing? > It would be fine to have updated isdn4k-utils as pppdcapiplugin is missing, would be needed anyway, as currently they seems to be not maintained and are in main. I filed a bug for this in cooker too (current in cooker 3.1pre1 , current : 3.2pre3) The only I can do about it is complaining complaining complaining. I'm working together with [http://teledat.sourceforge.net] for the usb devices, to get a normal ./configure; make && make install approach. This one I will use to make an RPM. First steps are done. As soon as the usb devices are ready I will extend that for the intern cards => doing rpm and then I will have a look at the Fritz!DSL. What belongs to the usb I guess I'm ready this weak. I guess I should sign up as volunteer for the Club then. The usb devices have more priority for me as they have no free driver. > Will you make it available somewhere ? I could use sourceforge, but it would be better to put it in the club. I will take care of it then I'm ready or nearby. As the drivers are not free I guess there will be something to clear before. > > Further if ISDN is configured and kisdndial is in the distro it should > > be installed/started for easier dial out. This would need to ensure > > the correct rights on devices and needed commands. > > I think kisdndial is not in mdk's repository. The rpm for 9.0 from the > author's site was made with checkinstall (boo!). I've made a quick spec > (by adapting k3b's spec because of the dreaded CXX error) and the > latest version of kisdndial builds fine and the applet loads. Can't test > further because I don't have ISDN. kisdndial would need a patch (I can provide the patch if time permits): - it wants /sbin/isdnctrl setuid root which is not acceptable, it doesn't even try if it has the needed permissions. I asked the author of the program but he does not want to change it. it crashes the taskbar if you close the applet (very ugly) Currently I test LineControl as GUI dial up tool (very nice) ;) it would be fine to create a group dialup on installation (or is there one in mandrake?) and set the rights and ownership on /sbin/isdnctrl and the devices right. As I read is a user (with isdn4k-utils 3.2pre3) only allowed to dial and hangup with isdnctrl, so another reason for updating isdn4k-utils. > > - Mark -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
[Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1847 --- Additional Comments From [EMAIL PROTECTED] 2003-03-05 20:50 --- On Wednesday 05 March 2003 19:53, qa wrote: Still valid, the device should be set to ONBOOT="yes" after configuration or it should be asked like it is done for network cards. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands.
