i can't get ppp running

Nikos Vassiliadis nvass at teledomenet.gr
Wed Aug 29 00:15:30 PDT 2007


On Tuesday 28 August 2007 19:25, deeptech71 at gmail.com wrote:
> Nikos Vassiliadis wrote:
> > On Tuesday 28 August 2007 13:48, deeptech71 at gmail.com wrote:
> >> What does configuring the modem in bridging mode means?
> >>
> >> =====================================================================
> >>= =========================    ppp.conf   
> >> =============================
> >> =====================================================================
> >>=
> >>
> >> default:
> >>   set device PPPoE:rl0
> >>   set MTU 1492
> >>   set MRU 1492
> >>   set crtscts off
> >>   set speed sync
> >>   #set timeout 0
> >>   #set redial 0 0
> >>   enable lqr
> >>   #disable deflate
> >>   #disable pred1
> >>   #disable vjcomp
> >>   #disable acfcomp
> >>   #disable protocomp
> >>   set log Phase tun LCP IPCP CCP Warning Error Alert
> >>   set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0
> >>   add default HISADDR
> >>   #enable proxy
> >>   #nat enable yes
> >>   #nat log yes
> >>   #nat same_ports yes
> >>   #nat unregistered_only yes
> >>   #nat deny_incoming yes
> >> dsl:
> >>   set login
> >>   set authname q123 at qwerty.comg
> >>   set authkey asd12345
> >
> > This configuration file has several irrelevant settings.
> > Try the one below, it's from here:
> > /usr/share/examples/ppp/ppp.conf.sample
> > I just added "set authname" & "set authkey",
> > changed the NIC's name and removed the service name.
> >
> > pppoe:
> >  set authname "your_username"
> >  set authkey "your_password"
> >  set device PPPoE:rl0
> >  enable lqr echo
> >  set cd 5
> >  set dial
> >  set login
> >  set redial 0 0
> >
> > [snip]
> >
> >> =====================================================================
> >>= =======================    sysctl.conf   
> >> ============================
> >> =====================================================================
> >>=
> >>
> >> net.link.ether.bridge.config=rl0:0,ed0:0
> >> net.link.ether.bridge.ipfw=1
> >> net.link.ether.bridge.enable=1
> >> net.inet.ip.forwarding=1
> >
> > This has nothing to do with modem bridging mode.
> > This bridges your two ethernet segments. Disable it if
> > that's not what you want.
> >
> >> =====================================================================
> >>= =========================    ppp.log   
> >> ==============================
> >> =====================================================================
> >>=
> >>
> >> Aug 28 03:58:21 cp ppp[786]: Phase: Using interface: tun0
> >> Aug 28 03:58:21 cp ppp[786]: Phase: deflink: Created in closed state
> >> Aug 28 03:58:21 cp ppp[786]: tun0: Phase: PPP Started (interactive
> >> mode). Aug 28 03:58:22 cp ppp[801]: Phase: Using interface: tun1
> >> Aug 28 03:58:22 cp ppp[801]: Phase: deflink: Created in closed state
> >> Aug 28 03:58:22 cp ppp[802]: tun1: Phase: PPP Started (auto mode).
> >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: bundle: Establish
> >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: closed -> opening
> >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: Connected!
> >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: opening -> dial
> >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: dial -> carrier
> >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Disconnected!
> >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: carrier -> hangup
> >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Connect time: 5
> >> secs: 0 octets in, 0 octets out
> >
> > ^^^^^^^^^^^^^^^^^^
> > Zero octets in and zero octets out. Is your modem in bridging mode?
> > It may be called rfc1483. Enable it.
> >
> > check what goes on with tcpdump:
> > root:0:/# tcpdump -nli rl0
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> > decode listening on rl0, link-type EN10MB (Ethernet), capture size 96
> > bytes 14:34:54.863275 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name]
> > 14:34:56.862997 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name]
> > 14:34:59.969272 PPPoE PADI [Host-Uniq 0xC00CFAC3] [Service-Name]
> >
> > This is not what you should see, you should see PADO and the rest.
> > If that's what you see, your modem is probably not in bridging mode.
> >
> > [snip]
> >
> > Hope this helps
> >
> > Nikos
>
> I've tried your ppp.conf with the same results. Also, articles
> explicitly told me not to use "set dial".

"set dial" may be irrelevant. It may be used to set dial script
to "", e.g. to erase a previously set dial script, which is correct
since you don't need a dial script for PPPoE. Anyway, it doesn't
hurt.

> The tcpdump test displays PADI! OK, so not in bridging more?

No, PADI is your request for initiating a PPPoE connection.
You should see an offer(PADO). Something like this:
09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq 0x0400000007000000]
09:18:01.731345 PPPoE PADI [Service-Name] [Host-Uniq 0x0400000007000000]
09:18:01.731694 PPPoE PADO [AC-Name "iris.teledomenet.gr"] [Service-Name] [Service-Name "*"] [Host-Uniq 0x0400000007000000] [AC-Cookie 0x80DEECC3]
09:18:01.731772 PPPoE PADR [Service-Name] [Host-Uniq 0x0400000008000000] [AC-Cookie 0x80DEECC3]
09:18:01.731786 PPPoE PADS [ses 0x46] [AC-Name "iris.teledomenet.gr"] [Service-Name] [Host-Uniq 0x0400000008000000] [AC-Cookie 0x80DEECC3]
09:18:01.732322 PPPoE  [ses 0x46] LCP, Conf-Request (0x01), id 22, length 18
09:18:01.736886 PPPoE  [ses 0x46] LCP, Conf-Request (0x01), id 0, length 19
09:18:01.737145 PPPoE  [ses 0x46] LCP, Conf-Reject (0x04), id 0, length 9
09:18:01.747045 PPPoE  [ses 0x46] LCP, Conf-Reject (0x04), id 22, length 8

> The modem is a Dialcom ADSL Bridge 1600, which sound like some bridge,
> duh. I've searched for information about this product, there is no
> support for it. Dialcom sells these things to ISPs only I think. There's
> supposed to be a web interface to it, but I couldn't get in there yet.

Well, it's not optional to check the modem's settings:)
The two settings you have to configure for bridging are:
1) enable bridging:)
2) correct virtual circuit, you have to use correct VPI/VCI.
   You should get this from your ISP.

Perhaps your modem has DHCP. Try "dhclient rl0". If you do get
an address on your rl0, then do a "route -n get default" and
try to connect to the gateway using a web browser.

I would also set the modem to factory defaults. At least
then you will know some settings. Most modems have a little
button which can be pressed using a pin. I understood that
you did get the modem second-hand.

My hungarian is not very good these days. But you can see IP addresses etc
http://oldradio.tesla.hu/szetszedtem/039adslmodemek/004dialcom/dialcom.htm

> One important thing. FreeBSD is a good piece of software. If a hardware
> router can establish a PPPoE connection, why can't FreeBSD do the same
> thing? What does my hardware router have what FreeBSD doesn't?

Because your modem is probably not configured correctly. FreeBSD sends
requests, but doesn't get any answers back. FreeBSD is widely tested
with PPPoE, both in server and client environments.

HTH

Nikos


More information about the freebsd-questions mailing list