Updated adsl HOWTO
Hi! Here is the updated adsl HOWTO. Sory, but we still are having problems with the new Orkit model. Dani = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Updated adsl HOWTO
Hi! Here is the updated adsl HOWTO. Sory, but we still are having problems with the new Orkit model. Dani -- Attached file included as plaintext by Listar -- -- File: HOWTO-ADSL-BEZEQ HOWTO-ADSL-BEZEQ Originally written by Dr. Daniel Arbel ([EMAIL PROTECTED]) Additions and clarifications by mulix [EMAIL PROTECTED] The most recent version of this document can be found at http://www.pointer.co.il/~mulix/adsl-howto.txt ver 1.0 Aug 2000 ver 1.0.1 Sep 2000 - corrections for pap authentication and stopping sessions. ver 1.0.2 Jan 2001 - changes after the beginning of commercial service. Ver 1.1 Jan 2001 - additions and clarifications by mulix added "note about different ADSL modems" added "where to get more help" (mulix) Ver 1.1.1 Jan 2001 - added note about pppd patch (mulix) Ver 1.1.2 Jan 2001 - note on how to get the modem version string (mulix) Ver 1.1.3 Jan 2001 - added note on modem names (ATUR2 and ATUR3) (mulix) ver 1.1.4 Feb 2001 - addes info about Alcatel modems, a patch to pptp to support Alcatel ISDN ADSL modem. DISCLAIMER: The info in this doc is based mostly on our own experiences. Use it at your own risk, and if you find any omissions or mistakes, please don't hesitate to let us know. A NOTE ABOUT THE DIFFERENT ADSL MODEMS - read first! Orkit modems There are at least three different Orckit ADSL modems. You can differentiate between them by examining the version string the modem gives. So far, we know of the following modems: The modem known by bezeq technical support as "ATUR2": "Modem version 5.00.0.3 Orckit Release 2.0 , Version 4 (16:00 June 1 1999)" and the modem known (by us) as "ATUR3": "Orckit ATUR3 version: Adsl 4.0.0.34, Data 4.9 (ATM), Based on Virata 6.3.0.9-full release (Jun 27 2000)" To find out your modem version string, simply telnet to the modem 'telnet 10.0.0.138'. The password is 'password'. Once you are logged in to the modem, type 'version'. It appears that modems of the SECOND kind do NOT work with linux. Try to have Bezeq replace this version with "ATUR2". If you try to connect with "ATUR3", you will probably get the error "Error Making Call" from pptp. The patched pptp allows you to create the VPN tunnel with the modem, but we have not been able to connect successfully with it yet. The only absolute solution we found so far, is to ask Bezeq replace your modem to the first kind. A quick check which modem you have is that the first modem has two RJ-45 (data) connectors on the back, and the second kind has only one. Examining windows and linux pppd session negotiations shows that there are some different options. It is possible that patching pppd to emulate the windows ppp software (send the exact same options) will allow us to use the second modem with linux as well, but no one has done this patch to pppd yet. Alcatel modems There are four Alcatel modem tppes: one for ISDN lines, two ethernet modems for analog lines, and one USB modem. The USB model was not tested with Linux yet. All three ethernet modems work with Linux. INTRODUCTION This introduction describes the mechanism and specifics of the windows installation of the ADSL service. Bezeq do not officially support linux (although it is rumored that they might, in the yet-to-be-determined future) and therefore can provide no clue about how to connect a Linux box. Digging in Bezeq installation and reading this introduction will help you make the conclusions needed when connecting your Linux box. We describe here the details of the Orckit equipment. If you have ALcatel gear and it looks a bit different, try to use intuition... (I did not have the privilege to use Alcatel ADSL ..). 1) The communication between the ADSL unit and the computer is done by ethernet NIC (a regular network card. Bezeq will supply one to you, for an additional charge, or you can buy and install it yourself. Installing a network card is not covered by this ADSL-HOWTO, but is covered extensively elsewhere. TODO: add pointer to installing a NIC documentation) and it uses the following setup: network 10.0.0.0 mask 255.0.0.0 host: 10.200.1.1 adsl: 10.0.0.138 no dns, no domain , no gateway. (i did not try to move the host to 10.0.0.x and increase the mask). 2) Bezeq will install a peace of (junk?) software that connects automatically to their ADSL portal and activates your browser to show the main page. From there you can surf to the service selection and connect to your ISP. This is the front end hiding the things that actually take place: 3) A connection is established by dialing (yes, dial up just like with a "regular" modem) using the private network mechanism (VPN). If you want to set this up yoursel
Re: Updated ADSL-HOWTO
On Mon, 29 Jan 2001, Lior David wrote: Ok, I went out and patched the pppd software exactly according to crisk's suggestions, and I even reordered the lcp options so that they will be sent in the exact order win2000 sends them. Unfortunately, none of this worked - same result, even though I compared the packet sent by Linux and win2000 - they look almost identical. If anyone wants the patched ppp for testing, please send me mail. My current conclusion is, unless I made a mistake with the patch(it's quite possible), that the problem is not with the ppp options. It might be a bug in the IP stack of the orckit modem which causes it to ignore the pptp packets sent by Linux... Please make the patched pppd and the Win2000 and modified Linux captures available to us (me) for testing. If the first LCP packet is identical, and we know that the PPTP packets work fine, then the only thing I can think of right now is an error in the processing of the higher level GRE (IPPROTO 47) packets. I will confirm this given a decent sniff. It's seems incredibly odd that the modem knows the caller uses Windows or Linux by any other means than the data it gets via the network. Identical network data == identical response, that's the reason we programmers get the big bucks. Another possibility is that the bug is -still- in the PPTP packets, something that causes the Orckit modem to stop processing information, therefore it won't respond to the PPP data that follows the PPTP packets. Mulix said the Windows PPTP and Linux PPTP (using his patched pptp) packets are identical. If they really are, then take this out of the equation. If the data is COMPLETELY identical, and it still doesn't work, then I'd try to match the packet timing. Beyond that.. who knows. And I'd definitely mail bomb Orckit's support folk for a fixed firmware, if it's flashable. If the newest version they sell doesn't work with customers, it -should- get them moving to fix it. -- crisk ._ [EMAIL PROTECTED] ._/-==\\\ _ |_.-`---^-._ Instructions for life: 3. Don't believe all you hear, spend all you have or sleep all you want. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Updated ADSL-HOWTO
On Thu, 1 Feb 2001, crisk wrote: On Mon, 29 Jan 2001, Lior David wrote: Ok, I went out and patched the pppd software exactly according to crisk's suggestions, and I even reordered the lcp options so that they will be sent in the exact order win2000 sends them. Unfortunately, none of this worked - same result, even though I compared the packet sent by Linux and win2000 - they look almost identical. If anyone wants the patched ppp for testing, please send me mail. My current conclusion is, unless I made a mistake with the patch(it's quite possible), that the problem is not with the ppp options. It might be a bug in the IP stack of the orckit modem which causes it to ignore the pptp packets sent by Linux... Please make the patched pppd and the Win2000 andmodified Linux captures available to us (me) for testing. If the first LCP packet is identical, and we know that the PPTP packets work fine, then the only thing I can think of right now is an error in the processing of the higher level GRE (IPPROTO 47) packets. I will confirm this given a decent sniff. The patched ppp software was placed by mulix at his site (I think it's http://www.pointer.co.il/~mulix) and can be downloaded from there. I will try to get you captures from both win2000 and Linux sessions tonight for testing. I didn't check that the packets are _completely_ identical - there might be small differences with the IP header (or maybe the ethernet framing - is it shown with any sniffer?), I will check it in more detail... Thanks, Lior It's seems incredibly odd that the modem knows the caller uses Windows or Linux by any other means than the data it gets via the network. Identical network data == identical response, that's the reason we programmers get the big bucks. Another possibility is that the bug is -still- in the PPTP packets, something that causes the Orckit modem to stop processing information, therefore it won't respond to the PPP data that follows the PPTP packets. Mulix said the Windows PPTP and Linux PPTP (using his patched pptp) packets are identical. If they really are, then take this out of the equation. If the data is COMPLETELY identical, and it still doesn't work, then I'd try to match the packet timing. Beyond that.. who knows. And I'd definitely mail bomb Orckit's support folk for a fixed firmware, if it's flashable. If the newest version they sell doesn't work with customers, it -should- get them moving to fix it. -- crisk ._ [EMAIL PROTECTED] ._/-==\\\ _ |_.-`---^-._ Instructions for life: 3. Don't believe all you hear, spend all you have or sleep all you want. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Updated ADSL-HOWTO
On Thu, 1 Feb 2001, crisk wrote: On Mon, 29 Jan 2001, Lior David wrote: Ok, I went out and patched the pppd software exactly according to crisk's suggestions, and I even reordered the lcp options so that they will be sent in the exact order win2000 sends them. Unfortunately, none of this worked - same result, even though I compared the packet sent by Linux and win2000 - they look almost identical. If anyone wants the patched ppp for testing, please send me mail. My current conclusion is, unless I made a mistake with the patch(it's quite possible), that the problem is not with the ppp options. It might be a bug in the IP stack of the orckit modem which causes it to ignore the pptp packets sent by Linux... My asumption is that the pptp channel is not actualy being opened. The point is that the ppp packets are actualy sent by the adsl modem to its ATM peer. this peer is the same for all modem types, so it should work the same. maybe by telneting to the adsl modem during a session can get some info about whats going there. Please make the patched pppd and the Win2000 and modified Linux captures available to us (me) for testing. If the first LCP packet is identical, and we know that the PPTP packets work fine, then the only thing I can think of right now is an error in the processing of the higher level GRE (IPPROTO 47) packets. I will confirm this given a decent sniff. It's seems incredibly odd that the modem knows the caller uses Windows or Linux by any other means than the data it gets via the network. Identical network data == identical response, that's the reason we programmers get the big bucks. Another possibility is that the bug is -still- in the PPTP packets, something that causes the Orckit modem to stop processing information, therefore it won't respond to the PPP data that follows the PPTP packets. Mulix said the Windows PPTP and Linux PPTP (using his patched pptp) packets are identical. If they really are, then take this out of the equation. If the data is COMPLETELY identical, and it still doesn't work, then I'd try to match the packet timing. Beyond that.. who knows. And I'd definitely mail bomb Orckit's support folk for a fixed firmware, if it's flashable. If the newest version they sell doesn't work with customers, it -should- get them moving to fix it. -- crisk ._ [EMAIL PROTECTED] ._/-==\\\ _ |_.-`---^-._ Instructions for life: 3. Don't believe all you hear, spend all you have or sleep all you want. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] Dani = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Updated ADSL-HOWTO
Ok, I went out and patched the pppd software exactly according to crisk's
suggestions, and I even reordered the lcp options so that they will be
sent in the exact order win2000 sends them. Unfortunately, none of this
worked - same result, even though I compared the packet sent by Linux and
win2000 - they look almost identical. If anyone wants the patched ppp for
testing, please send me mail.
My current conclusion is, unless I made a mistake with the patch(it's
quite possible), that the problem is not with the ppp options. It might be
a bug in the IP stack of the orckit modem which causes it to ignore the
pptp packets sent by Linux...
Thanks,
Lior
On Mon, 29 Jan 2001, crisk wrote:
On the ADSL note, I've read in today's Yediot Achronot that
"Microsoft and Orckit fixed the serious problems with Orckit's ADSL
equipment and Windows ME." They say a fix is available on Microsoft's
site... this might be relevant.
You guys mightwant to bug Orckit to fix the firmware on their lousy
modems, too. There's nothing wrong with the LCP options that pppd sends,
except that the Orckit modem might not understand 'asyncmap' (hey,
it's not on RFC1661, but nobody bothered either reading the IETF pppext
drafts or implementing standard unknown option rejection). I have
parsed this information from the captures (Windows vs. Linux) that mulix
sent me:
The options in the first LCP (id 0) packet sent by a Windows dialer
(ordered as they appear in the packet):
- Magic-Number (32-bit number)
- Protocol-Field-Compression on
- Address-and-Control-Field-Compression on
- Callback value 6 (meaning CBCP will determine callback)
- Multilink-MRRU (Max-Recieved-Reconstructed-Unit), value 0x064e (1614)
- Multilink-Endpoint-Descriminator (with a class 1 [locally
assigned] address 22 bytes long)
The linux pppd first LCP (id 1, unlike Windows' id 0):
(the lousy Orckit modem never replies to this LCP message)
- Asyncmap 0x
- Magic-Number (32-bit number)
- Protocol-Field-Compression on
- Address-and-Control-Field-Compression on
If I had to fix this, I'd first set the id of the first LCP packet pppd
sends to zero. This is exactly the kind of stupid bugs people would make
and never test for, and it takes about 2 seconds to rig pppd to use 0
(ie change line 708 in fsm.c from "f-reqid = ++f-id" to "f-reqid =
f-id++" or something like that)
If this fails, I'd get rid of the asyncmap as well ('pppd -am' should do
this). And if -that- failed, I'd add multilink, and finally, callback.
It seems odd to me that nobody fixed the pppd yet. I don't have ADSL,
but a good friend of mine does, and obviously not a few people on this
list. Surely there must be some protocolguru with interest of fixing
this.. reverting to Windows is not an option.
On Sun, 28 Jan 2001, mulix wrote:
Hi Lior,
attached to this email is an updated version of the ADSL howto, covering
what we know about the problem you ran into.In short, there are several
kinds of orckit ADSL modems, one of whom works with Linux in the default
configuration (pptp with the trivial patch) and one of whom requires a
patched pptp and a patched pppd to (maybe) work.
Lior David wrote:
Hello,
I have a problem connecting to the ADSL service from Linux. I have
tried everything I know and I simply can't get it to work. Maybe some
of the ADSL experts here will have an idea...
--
mulix
linux/reboot.h: #define LINUX_REBOOT_MAGIC1 0xfee1dead
._
[EMAIL PROTECTED] ._/-==\\\ _
|_.-`---^-._
Sexually tilted quote from STAR WARS:
7. You've got something jammed in here real good.
=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
Updated ADSL-HOWTO
Hi Lior, attached to this email is an updated version of the ADSL howto, covering what we know about the problem you ran into. In short, there are several kinds of orckit ADSL modems, one of whom works with Linux in the default configuration (pptp with the trivial patch) and one of whom requires a patched pptp and a patched pppd to (maybe) work. Lior David wrote: Hello, I have a problem connecting to the ADSL service from Linux. I have tried everything I know and I simply can't get it to work. Maybe some of the ADSL experts here will have an idea... -- mulix linux/reboot.h: #define LINUX_REBOOT_MAGIC1 0xfee1dead HOWTO-ADSL-BEZEQ Originally written by Dr. Daniel Arbel ([EMAIL PROTECTED]) Additions and clarifications by mulix [EMAIL PROTECTED] ver 1.0 Aug 2000 ver 1.0.1 Sep 2000 - corrections for pap authentication and stopping sessions. ver 1.0.2 Jan 2001 - changes after the beginning of commercial service. Ver 1.1 Jan 2001 - additions and clarifications by mulix added "note about different ADSL modems" added "where to get more help" (mulix) Ver 1.1.1 Jan 2001 - added note about pppd patch (mulix) DISCLAIMER: The info in this doc is based mostly on our own experiences. Use it at your own risk, and if you find any omissions or mistakes, please don't hesitate to let us know. INTRODUCTION This introduction describes the mechanism and specifics of the windows installation of the ADSL service. Bezeq do not officially support linux (although it is rumored that they might, in the yet-to-be-determined future) and therefore can provide no clue about how to connect a Linux box. Digging in Bezeq installation and reading this introduction will help you make the conclusions needed when connecting your Linux box. We describe here the details of the Orckit equipment. If you have ALcatel gear and it looks a bit different, try to use intuition... (I did not have the privilege to use Alcatel ADSL ..). 1) The communication between the ADSL unit and the computer is done by ethernet NIC (a regular network card. Bezeq will supply one to you, for an additional charge, or you can buy and install it yourself. Installing a network card is not covered by this ADSL-HOWTO, but is covered extensively elsewhere. TODO: add pointer to installing a NIC documentation) and it uses the following setup: network 10.0.0.0 mask 255.0.0.0 host: 10.200.1.1 adsl: 10.0.0.138 no dns, no domain , no gateway. (i did not try to move the host to 10.0.0.x and increase the mask). 2) Bezeq will install a peace of (junk?) software that connects automatically to their ADSL portal and activates your browser to show the main page. From there you can surf to the service selection and connect to your ISP. This is the front end hiding the things that actually take place: 3) A connection is established by dialing (yes, dial up just like with a "regular" modem) using the private network mechanism (VPN). If you want to set this up yourself, here are the steps: 1) Install ms virtual private network adapter (it might already be installed if Bezeq installed the ADSL in your computer). 2) Go to dial up networking and start the wizard to create a new connection. 3) For this connection, use Microsoft VPN adapter. 4) host name is "10.0.0.138 RELAY_PPP1". Don't write the quotes, and yes, it really is a space between '138' and 'RELAY'. 5) Once the connection icon is created, go to its properties and disable netbeui, ipx etc (these are various net protocols which you do not need for this type of connection) 6) Start the connection. the username is your userid@ISP (for guest access this will be guest@OXx where X is your chosen ISP with its first character in upercase (i.e. Actcom ) the letter after the '@' is NOT zero . Note that guest access is not free of charge, and in fact VERY expensive. For non guest access to actcom, the username is username@IActcom. 'username' is obviously your actcom user name, notice the upper case 'I' and 'A' and lower case 'ctcom'. 7) If you receive a connection and are able to use it, you may go on to Linux installation. If not, try to search in the registry (search for 'wow') whether some details have been changed by Bezeq (most likely to change are the username and ISP strings). LINUX INSTALLATION (finally ... -- You should have no problem installing a NIC for ADSL. Reduce the MTU to 1452 (run the command 'ifconfig eth0 10.200.1.1 netmask 255.255.255.0 mtu 1452'). Use a kernel with ppp support and latest pppd. The latest pppd version (currently 2.3.11) can be downloaded from ftp://cs.anu.edu.au/pub/software/ppp/ The equivalent of Microsoft VPN adapter is just the pptp program . get it from http://cag.lcs.mit.edu/~cananian/Projects/PPTP/ The current version is 1.02. Since pptp does not receive all the options as a command line
Re: Updated ADSL-HOWTO
Hello, mulix wrote: A quick check which modem you have is that the first modem has two RJ-45 (data) connectors on the back, and the second kind has only one. A tidbit of info: according to Bezeq's ADSL support (1-800-340340), the Orkit modem with two RJ45 jacks is called "ATUR2". On the other hand, the problematic single-jack version has "ATUR3" in its version string (but Bezeq's support didn't have any special name for it). So, ignoring the existence of a third type of Orckit modems, the current state of the art is: ATUR2 works with Linux, ATUR3 doesn't. Regards, Eran Tromer = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Updated ADSL-HOWTO
On the ADSL note, I've read in today's Yediot Achronot that
"Microsoft and Orckit fixed the serious problems with Orckit's ADSL
equipment and Windows ME." They say a fix is available on Microsoft's
site... this might be relevant.
You guys might want to bug Orckit to fix the firmware on their lousy
modems, too. There's nothing wrong with the LCP options that pppd sends,
except that the Orckit modem might not understand 'asyncmap' (hey,
it's not on RFC1661, but nobody bothered either reading the IETF pppext
drafts or implementing standard unknown option rejection). I have
parsed this information from the captures (Windows vs. Linux) that mulix
sent me:
The options in the first LCP (id 0) packet sent by a Windows dialer
(ordered as they appear in the packet):
- Magic-Number (32-bit number)
- Protocol-Field-Compression on
- Address-and-Control-Field-Compression on
- Callback value 6 (meaning CBCP will determine callback)
- Multilink-MRRU (Max-Recieved-Reconstructed-Unit), value 0x064e (1614)
- Multilink-Endpoint-Descriminator (with a class 1 [locally
assigned] address 22 bytes long)
The linux pppd first LCP (id 1, unlike Windows' id 0):
(the lousy Orckit modem never replies to this LCP message)
- Asyncmap 0x
- Magic-Number (32-bit number)
- Protocol-Field-Compression on
- Address-and-Control-Field-Compression on
If I had to fix this, I'd first set the id of the first LCP packet pppd
sends to zero. This is exactly the kind of stupid bugs people would make
and never test for, and it takes about 2 seconds to rig pppd to use 0
(ie change line 708 in fsm.c from "f-reqid = ++f-id" to "f-reqid =
f-id++" or something like that)
If this fails, I'd get rid of the asyncmap as well ('pppd -am' should do
this). And if -that- failed, I'd add multilink, and finally, callback.
It seems odd to me that nobody fixed the pppd yet. I don't have ADSL,
but a good friend of mine does, and obviously not a few people on this
list. Surely there must be some protocol guru with interest of fixing
this.. reverting to Windows is not an option.
On Sun, 28 Jan 2001, mulix wrote:
Hi Lior,
attached to this email is an updated version of the ADSL howto, covering
what we know about the problem you ran into. In short, there are several
kinds of orckit ADSL modems, one of whom works with Linux in the default
configuration (pptp with the trivial patch) and one of whom requires a
patched pptp and a patched pppd to (maybe) work.
Lior David wrote:
Hello,
I have a problem connecting to the ADSL service from Linux. I have
tried everything I know and I simply can't get it to work. Maybe some
of the ADSL experts here will have an idea...
--
mulix
linux/reboot.h: #define LINUX_REBOOT_MAGIC1 0xfee1dead
._
[EMAIL PROTECTED] ._/-==\\\ _
|_.-`---^-._
Sexually tilted quote from STAR WARS:
7. You've got something jammed in here real good.
=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
