Re: [Cooker] isdn - damien chaumatte somewhere ?
Am Sonntag, 6. Juli 2003 20:30 schrieb Thierry Vignaud: > [EMAIL PROTECTED] writes: > > You now have to wait for the next drakxtools to be packaged. > > which has to wait for rpm-build to be fixed ... :-( No problem. I guess it is anyway a bad time to start with cooker ;)(kernel/rpm/devfs) I can wait a week if it is better then or I can patch current version with the patch dams provided. I currently sync cooker and that takes some time over isdn ;) (Now it is 20h for today) I guess the planned Pre-Beta ISO(as scheduled) has to wait some time what I can see from mailinglist ;) Regards Steffen
Re: [Cooker] isdn - damien chaumatte somewhere ?
[EMAIL PROTECTED] writes: > You now have to wait for the next drakxtools to be packaged. which has to wait for rpm-build to be fixed ... :-(
Re: [Cooker] isdn - damien chaumatte somewhere ?
Steffen Barszus <[EMAIL PROTECTED]> said:
> Am Freitag, 4. Juli 2003 12:35 schrieben Sie:
>> Steffen Barszus <[EMAIL PROTECTED]> said:
>>
>> By te way, the last thing to check is the channel aggregation. It works
>> very well with isdn-light, it uses an additional service to handle the 2nd
>> channel dialup if needed.
>
> Thats one of the things that i have fixed in isdn4net. What you mean is ibod
> and ibod needs the slave in dialmode auto. For per minute dial up dialmode
> auto on the master is not wished, with old isdn4net master and slave are set
> to manuel then. This prevented channelbundling/ibod from working. I have no
> made an extra option for defining the dialmode of SLAVE seperate. The default
> is set to auto no matter which modew the master has. As the dialmode auto on
> the slave is not dangerous as it just defines how the second channel has to
> be added this is a save solution (the same as in isdn-light I guess).
>
> In short : it will work.
I have made the needed modifications in the cvs.
Now the virtual interface is ONBOOT=yes by default, and the up/down scripts
only dialup or hangup.
Are there other modifications to do?
btw your src.rpm seems alright, I'll try to make it included.
You now have to wait for the next drakxtools to be packaged. If you need to
test it before that, you can apply this patch to
/usr/lib/libDrakX/network/idsn.pm :
--- network/isdn.pm 28 May 2003 14:49:15 - 1.75
+++ network/isdn.pm 5 Jul 2003 17:36:53 -
@@ -84,16 +84,19 @@
substInFile { s/^FIRMWARE.*\n//; $_ .= qq(FIRMWARE="$isdn->{firmware}"\n)
if eof } "$prefix/etc/sysconfig/network-scripts/ifcfg-ippp0";
+# we start the virtual interface at boot (we dial only on demand.
+substInFile { s/^ONBOOT.*\n//; $_ .= qq(ONBOOT=yes\n) if eof }
+"$prefix/etc/sysconfig/network-scripts/ifcfg-ippp0";
+
write_secret_backend($isdn->{login}, $isdn->{passwd});
write_cnx_script($netc, "isdn",
-"/sbin/route del default
-/sbin/ifup ippp0
+"#/sbin/route del default
+#/sbin/ifup ippp0
/usr/sbin/isdnctrl dial ippp0
" . if_($isdn->{speed} =~ /128/, "service ibod restart
"),
"/usr/sbin/isdnctrl hangup ippp0
-/sbin/ifdown ippp0
+#/sbin/ifdown ippp0
" . if_($isdn->{speed} =~ /128/, "service ibod stop
"), $netc->{isdntype});
1;
END OF PATCH--
--
dams
Re: [Cooker] isdn - damien chaumatte somewhere ?
Steffen Barszus <[EMAIL PROTECTED]> said: > Am Freitag, 4. Juli 2003 12:35 schrieben Sie: >> Steffen Barszus <[EMAIL PROTECTED]> said: >> >> By te way, the last thing to check is the channel aggregation. It works >> very well with isdn-light, it uses an additional service to handle the 2nd >> channel dialup if needed. > > Thats one of the things that i have fixed in isdn4net. What you mean is ibod > and ibod needs the slave in dialmode auto. For per minute dial up dialmode > auto on the master is not wished, with old isdn4net master and slave are set > to manuel then. This prevented channelbundling/ibod from working. I have no > made an extra option for defining the dialmode of SLAVE seperate. The default > is set to auto no matter which modew the master has. As the dialmode auto on > the slave is not dangerous as it just defines how the second channel has to > be added this is a save solution (the same as in isdn-light I guess). > > In short : it will work. then perfect! I'll do the changes shortly. Thanks for the good work -- dams
Re: [Cooker] isdn - damien chaumatte somewhere ?
Am Freitag, 4. Juli 2003 12:35 schrieben Sie: > Steffen Barszus <[EMAIL PROTECTED]> said: > > By te way, the last thing to check is the channel aggregation. It works > very well with isdn-light, it uses an additional service to handle the 2nd > channel dialup if needed. Thats one of the things that i have fixed in isdn4net. What you mean is ibod and ibod needs the slave in dialmode auto. For per minute dial up dialmode auto on the master is not wished, with old isdn4net master and slave are set to manuel then. This prevented channelbundling/ibod from working. I have no made an extra option for defining the dialmode of SLAVE seperate. The default is set to auto no matter which modew the master has. As the dialmode auto on the slave is not dangerous as it just defines how the second channel has to be added this is a save solution (the same as in isdn-light I guess). In short : it will work.
Re: [Cooker] isdn - damien chaumatte somewhere ?
Steffen Barszus <[EMAIL PROTECTED]> said: By te way, the last thing to check is the channel aggregation. It works very well with isdn-light, it uses an additional service to handle the 2nd channel dialup if needed. -- dams
Re: [Cooker] isdn - damien chaumatte somewhere ?
Steffen Barszus <[EMAIL PROTECTED]> said: [...] > > isdn4linux scripts will allways be bloated once you have the most common > options running. Its a common flaw of isdn4linux. Once you beginn with a > small script and you add this and that, you will have in the and again a > bloated script or you do not support the most common uses of isdn4linux. > Further it is a pain to support isdn under mandrake if you first have to > determine which version the people have running. (I mean support on > mandrakeexpert here) > ok, then let's go for isdn4linux :) > [ ... ] > >> besides these modifications, are the mdk isdn4net script correct? do they >> work with drakconnect correctly? Is there a list of supported isdn cards by >> drakconnect+isdn4net ? > > Beside that drakconnect and isdn4net should work without problems. > > I could try to figure out wich cards should work with isdn4net and > drakconnect, faster I could make a list of supported cards of isdn4net alone. > Am I right that all modules that van be found in ldetect-lst with "ISDN:*" > should be known to isdn4net to support all cards ? yes, exactly. Be carefull, one ISDN card has a firmware, and this is written in the pcitable: "ISDN:hisax,type=28,firmware=/usr/lib/isdn/ISAR.BIN" > > If there were cards that worked with isdn-light and not with isdn4net i would > like to know about it, so i can support it with isdn4net. For me isdn4net > worked allways better then isdn-light. The only thing I can see is the firmware loading. One should check that configuring the Speed Fax+ PCI from Sedlbaueur works (with firmware loading) when configuring it with drakconnect + isdn4net > Further I have added an option to fast > add unsupported cards. > > As you know the scripts I guess you understand the following. > > 'ippp*') > echo "Loading driver defined in modules.conf ..." > /sbin/modprobe -v $I4L_MODULE >/dev/null > if test $? -ne 0; then > cleanup > fi > ;; > > A driver ippp0 can be added with an alias to the correct driver in > modules.conf. > >> If it works as good as it worked with isdn-light, I'll do the modifications > > Again if there were known problems with isdn4net that i do not know about i > would love to hear about it, so i can fix it. I would say it works as good as > isdn-light. I haven't heard the opposite. > > I will send the src.rpm to you per PM ok. I'll do the modifications then, and ask for the src.rpm to be included in main after I review it. I'll do all that tonight or tomorrow. Regards -- dams
Re: [Cooker] isdn - damien chaumatte somewhere ?
Am Donnerstag, 3. Juli 2003 14:46 schrieb [EMAIL PROTECTED]: > Steffen Barszus <[EMAIL PROTECTED]> said: > > Am Donnerstag, 3. Juli 2003 11:23 schrieben Sie: > >> Steffen Barszus <[EMAIL PROTECTED]> said: > >> > HI! > >> > > >> > I just want to ask. Is Damien away again ? Havent got any response > >> > since some days now. > >> > > >> > Anyone a clue ? > >> > >> If it has something to do with isdn, I might maybe help. Send me the > >> problem description, I'll try to figure out > > > > Hi Dams (Damian ?) > > > > I mailed with damien chaumette a while ago about isdn4net/isdn-light. As > > isdn is not the best maintained thing we agreed that to packages for isdn > > configuration are overkill. I have taken over the development of isdn4net > > a while ago and as isdn-light can not take care of all options of isdn we > > decided that isdn4net should be the only package. Thats the history. > > Ok :) I wrote isdn-light because I found isdn4net was bloated (at the > time), and I needed a simple package that works similary to an ethernet > interface, and also a simple way to handle firmware loading in the isdn > cards. But if you have taken over the development of isdn4net, isdn-light > can be dropped, now that cooker has you :) isdn4linux scripts will allways be bloated once you have the most common options running. Its a common flaw of isdn4linux. Once you beginn with a small script and you add this and that, you will have in the and again a bloated script or you do not support the most common uses of isdn4linux. Further it is a pain to support isdn under mandrake if you first have to determine which version the people have running. (I mean support on mandrakeexpert here) [ ... ] > besides these modifications, are the mdk isdn4net script correct? do they > work with drakconnect correctly? Is there a list of supported isdn cards by > drakconnect+isdn4net ? Beside that drakconnect and isdn4net should work without problems. I could try to figure out wich cards should work with isdn4net and drakconnect, faster I could make a list of supported cards of isdn4net alone. Am I right that all modules that van be found in ldetect-lst with "ISDN:*" should be known to isdn4net to support all cards ? If there were cards that worked with isdn-light and not with isdn4net i would like to know about it, so i can support it with isdn4net. For me isdn4net worked allways better then isdn-light. Further I have added an option to fast add unsupported cards. As you know the scripts I guess you understand the following. 'ippp*') echo "Loading driver defined in modules.conf ..." /sbin/modprobe -v $I4L_MODULE >/dev/null if test $? -ne 0; then cleanup fi ;; A driver ippp0 can be added with an alias to the correct driver in modules.conf. > If it works as good as it worked with isdn-light, I'll do the modifications Again if there were known problems with isdn4net that i do not know about i would love to hear about it, so i can fix it. I would say it works as good as isdn-light. I haven't heard the opposite. I will send the src.rpm to you per PM Regards Steffen
Re: [Cooker] isdn - damien chaumatte somewhere ?
Steffen Barszus <[EMAIL PROTECTED]> said: > Am Donnerstag, 3. Juli 2003 11:23 schrieben Sie: >> Steffen Barszus <[EMAIL PROTECTED]> said: >> > HI! >> > >> > I just want to ask. Is Damien away again ? Havent got any response since >> > some days now. >> > >> > Anyone a clue ? >> >> If it has something to do with isdn, I might maybe help. Send me the >> problem description, I'll try to figure out > > Hi Dams (Damian ?) > > I mailed with damien chaumette a while ago about isdn4net/isdn-light. As isdn > is not the best maintained thing we agreed that to packages for isdn > configuration are overkill. I have taken over the development of isdn4net a > while ago and as isdn-light can not take care of all options of isdn we > decided that isdn4net should be the only package. Thats the history. Ok :) I wrote isdn-light because I found isdn3net was bloated (at the time), and I needed a simple package that works similary to an ethernet interface, and also a simple way to handle firmware loading in the isdn cards. But if you have taken over the development of isdn4net, isdn-light can be dropped, now that cooker has you :) [...] > > I have a ready src-rpm for it i can send you. The next plans are to make a > manpage for isdn4net and make a web-page ready and release the new version on > the project page. The new location for isdn4net is http://isdn4net.berlios.de > . I mailed this URL allready to Stein Vrale, so he will add this information > to his isdn4net site . great! > > The next issue I have is that drakconnect/DrakX should have better defaults. > Currently the default is to have ONBOOT=no for configured connections > (/etc/sysconfig/network-scripts/ifcfg-ippp0) and to have > ifup=ippp0 > isdnctrl dial ippp0 > in /etc/sysconfig/network-scripts/net_cnx_up. > A better way would be to have as default for a configured connection > ONBOOT=yes. This way the pseudo-network-device is up and running on > startup.(net_cnx_up should have then only isdnctrl dial ippp0 ofcourse ) The > dial up is a bit faster and it is more compatible with tools for dial up. The > common solution/workaround till now was to put a /sbin/ifup ippp0 in the > rc.local script (see http://mandrakeuser.org). besides these modifications, are the mdk isdn4net script correct? do they work with drakconnect correctly? Is there a list of supported isdn cards by drakconnect+isdn4net ? If it works as good as it worked with isdn-light, I'll do the modifications > > I know a bit longish mail, but i wanted to summarize it a bit :) np > > I put too a CC to cooker in, hope you don't mind np :) -- dams
Re: [Cooker] isdn - damien chaumatte somewhere ?
Am Donnerstag, 3. Juli 2003 11:23 schrieben Sie: > Steffen Barszus <[EMAIL PROTECTED]> said: > > HI! > > > > I just want to ask. Is Damien away again ? Havent got any response since > > some days now. > > > > Anyone a clue ? > > If it has something to do with isdn, I might maybe help. Send me the > problem description, I'll try to figure out Hi Dams (Damian ?) I mailed with damien chaumette a while ago about isdn4net/isdn-light. As isdn is not the best maintained thing we agreed that to packages for isdn configuration are overkill. I have taken over the development of isdn4net a while ago and as isdn-light can not take care of all options of isdn we decided that isdn4net should be the only package. Thats the history. I have made a mainly bugfix release of isdn4net : - integrating the patches from the rpm - deleted timru options as it is obsolete - added an option for configuring dialmode of the slave and set it default to auto, since ibod will not work otherwise and dialmode auto is recommended for the slave by isdn-faq - added isdn link add/remove for easier setup of multiple isp's - isdn link list will now list only active connections instead of all profiles in /etc/isdn/profile/link/ - reactivated isdnlog in the rpm - added two additional driver as known driver to the startup script (capi4linux and hisax_fcpcipnp) I have a ready src-rpm for it i can send you. The next plans are to make a manpage for isdn4net and make a web-page ready and release the new version on the project page. The new location for isdn4net is http://isdn4net.berlios.de . I mailed this URL allready to Stein Vrale, so he will add this information to his isdn4net site . The next issue I have is that drakconnect/DrakX should have better defaults. Currently the default is to have ONBOOT=no for configured connections (/etc/sysconfig/network-scripts/ifcfg-ippp0) and to have ifup=ippp0 isdnctrl dial ippp0 in /etc/sysconfig/network-scripts/net_cnx_up. A better way would be to have as default for a configured connection ONBOOT=yes. This way the pseudo-network-device is up and running on startup.(net_cnx_up should have then only isdnctrl dial ippp0 ofcourse ) The dial up is a bit faster and it is more compatible with tools for dial up. The common solution/workaround till now was to put a /sbin/ifup ippp0 in the rc.local script (see http://mandrakeuser.org). I know a bit longish mail, but i wanted to summarize it a bit :) I put too a CC to cooker in, hope you don't mind Steffen
Re: [Cooker] isdn - damien chaumatte somewhere ?
Am Donnerstag, 3. Juli 2003 10:06 schrieb Frederic Crozat: > On Thu, 03 Jul 2003 01:46:44 +0200, Olivier Thauvin wrote: > > Le Mercredi 02 Juillet 2003 23:49, Steffen Barszus a écrit : > >> HI! > >> > >> I just want to ask. Is Damien away again ? Havent got any response since > >> some days now. > >> > >> Anyone a clue ? > > > > He still works at mdk, but he is notorius to not take to his packages ! > > I don't know a good way to get an answer or an action from this guys. > > no , see Frederics answer > > Can someone at mdk verify he his alive and he get and read his mails ? > > Damien is a trainee.. He is not working 1000f his time in MandrakeSoft > office.. Currently, he is at school, not in our office.. Yep i know that, and i just wanted to know the status where he is. If i know it right he is away now for 2 months, so my mails are for /dev/null for a long time ;) Thanks for the insight :D Steffen
Re: [Cooker] isdn - damien chaumatte somewhere ?
On Thu, 03 Jul 2003 01:46:44 +0200, Olivier Thauvin wrote: > Le Mercredi 02 Juillet 2003 23:49, Steffen Barszus a écrit : >> HI! >> >> I just want to ask. Is Damien away again ? Havent got any response since >> some days now. >> >> Anyone a clue ? > > He still works at mdk, but he is notorius to not take to his packages ! > I don't know a good way to get an answer or an action from this guys. > > Can someone at mdk verify he his alive and he get and read his mails ? Damien is a trainee.. He is not working 1000f his time in MandrakeSoft office.. Currently, he is at school, not in our office.. -- Frederic Crozat MandrakeSoft
Re: [Cooker] isdn - damien chaumatte somewhere ?
Le Mercredi 02 Juillet 2003 23:49, Steffen Barszus a écrit : > HI! > > I just want to ask. Is Damien away again ? Havent got any response since > some days now. > > Anyone a clue ? He still works at mdk, but he is notorius to not take to his packages ! I don't know a good way to get an answer or an action from this guys. Can someone at mdk verify he his alive and he get and read his mails ? -- Linux pour Mac !? Enfin le moyen de transformer une pomme en véritable ordinateur. - JL. Olivier Thauvin - http://nanardon.homelinux.org/
