HOWTO-ADSL-BEZEQ

Written by Dr. Daniel Arbel darbel@tx.technion.ac.il
ver 1.0 Aug. 2000
ver 1.0.1 Sep. 2000 - corrections for pap authentication and stoping sessions.

DISCLAIMER

INTRODUCTION

The introduction describes the mechanism of windows installation. The reason is that Bezeq technicians have NO idea about any other environment and can provide no clue about how to connect a Linux box. They will not describe the details of the connection in technical language because of lack of knowledge. Diging in Bezeq installation and reading this introduction will help you make the conclusions needed when connecting your Linux box.

I describe here the details of Orkit equipment. If you have ALcatel gear and it looks a bit different, try to use intuition... (I did not have the privelage to use Alcatel ADSL ..).

1. The communication between the ADSL unit and the comp. is done by ethernet NIC and it uses the following setup:
   network 10.0.0.0 mask 255.0.0.0 host: 1200.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 encrease the mask).
2. bezeq will install a peace of (junk?) s/w that connects automatically to their ADSL portal and activating 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. connection is done by dialing (yes, dial up just like with a modem) using the private network mechanism. the equivivalent dial setup is as follows:
   1. install ms private network adapter (this is done when Bezeq install ADSL in your pc).
   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
   5. once the connection icon is created, go to its properties and disable netbeui, ipx etc (not so important)
   6. start the connection. the username is guest@OXxxxxx where Xxxxx is your chosen ISP with it first character in upercase (i.e. Actcom ) (the letter after the '@' is NOT zero).
   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) weather some details have been changes by Bezeq (most likely to change are the username and hostname of the VPN endpoint).

LINUX INSTALLATION (finaly) ...

You should have no problem in installing a NIC for ADSL. Reduce the MTU to 1452 (ifconfig eth0 10.200.1.1/8 mtu 1452 )
use a kernel with ppp support and latest pppd (in my mandrake 7.1 , kernel 2.2.17 the version is 2.3.11).

the equivivalent of Microsoft VPN adapter is just the pptp .. get it 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 parameter, you have to enter the RELAY_PPP1 (see the introduction) into the source file (is anyone out there willing to enhance this pptp s/w ?) : change line 212 in pptp_ctrl.c to:

	hton16(PPTP_WINDOW), 0, 0, 0, {"RELAY_PPP1"}, {0}

The authentication method is forced by the server. In order to cover both optons (pap and chap) create 2 identical files:
edit /etc/ppp/chap-secrets and /etc/ppp/pap-secrets to include proper lines like:
"guest@OActcom" "10.0.0.138 RELAY_PPP1" "Bezeq"

and finaly, start a call:

./pptp 10.0.0.138 debug user guest@OActcom remotename "10.0.0.138 RELAY_PPP1" defaultroute netmask 255.0.0.0 mtu 1452 noauth

If everything goes well you should be connected, and your networking will look something like that:

# netstat -r -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.200.1.1      0.0.0.0         255.255.255.255 UH        0 0          0 eth0
213.8.120.1     0.0.0.0         255.255.255.255 UH        0 0          0 ppp0
10.0.0.0        0.0.0.0         255.0.0.0       U         0 0          0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         213.8.120.1     0.0.0.0         UG        0 0          0 ppp0
# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:BF:0E:F6:A8
          inet addr:10.200.1.1  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1452  Metric:1
          RX packets:51825 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56376 errors:0 dropped:0 overruns:0 carrier:0
          collisions:109 txqueuelen:100
          Interrupt:9 Base address:0xb000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:61 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:213.8.120.98  P-t-P:213.8.120.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1452  Metric:1
          RX packets:49753 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26973 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10



Stoping a session should be done as follows:


down the ppp0:

   ifconfig ppp0 down
kill the pptp process:

    killall pptp


Document HTML-ized by Tzafrir 
Cohen