Trouble with pppoe(4) on O3.7 RELEASE

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Trouble with pppoe(4) on O3.7 RELEASE

Damon McMahon
Greetings,

I'm having trouble getting pppoe(4) to establish a connection from my
OpenBSD 3.7 RELEASE (+ errata patches) box to my ISP through a Netgear
DG632 in bridge mode. I can successfully establish a connection using
pppoe(8) although it is a bit hit-and-miss. The in-kernel pppoe(4) is
not hit-and-miss, however, it's just miss.

I create and bring up the interface as follows:

% ifconfig pppoe0 pppoedev sis1
% spppcontrol pppoe0 myauthproto=pap
myauthname="[hidden email]" myauthkey="SECRET"
% ifconfig pppoe0 inet 0.0.0.0 0.0.0.1 0xffffffff
% route add default 0.0.0.1
add net default: gateway 0.0.0.1
% ifconfig pppoe0 up
% ifconfig pppoe0
pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492
        dev: sis1 state: session
        sid: 0xee5 PADI retries: 0 PADR retries: 0 time: 0:0:42
        inet6 fe80::209:5bff:fe04:576a%pppoe0 ->  prefixlen 64 scopeid 0x9
        inet 58.104.4.241 --> 0.0.0.1 netmask 0xff000000
% spppcontrol -v pppoe0
pppoe0: phase=network
        myauthproto=pap myauthname="[hidden email]"

Here's the dump of the PPPoE session:

13:25:51.275241 PPPoE-Discovery
        code Initiation, version 1, type 1, id 0x0000, length 12
        tag Service-Name, length 0
        tag Host-Uniq, length 4 \000P\221D
  0000: 1109 0000 000c 0101 0000 0103 0004 0050  ...............P
  0010: 91d0                                     .D

13:25:51.402226 PPPoE-Discovery
        code Offer, version 1, type 1, id 0x0000, length 49
        tag AC-Name, length 13 swy1-waymouth
        tag Host-Uniq, length 4 \000P\221D
        tag Service-Name, length 0
        tag AC-Cookie, length 16 \227C/\011\206~b \003\212C9CB\011TB'DC
  0000: 1107 0000 0031 0102 000d 7377 7931 2d77  .....1....swy1-w
  0010: 6179 6d6f 7574 6801 0300 0400 5091 d001  aymouth.....P.D.
  0020: 0100 0001 0400 1097 ef09 867e a603 8af9  ........C/..~b ..C9
  0030: dc42 0954 a7d0 c709 feaf 34              CB.TB'DC.__4

13:25:51.402400 PPPoE-Discovery
        code Request, version 1, type 1, id 0x0000, length 32
        tag Service-Name, length 0
        tag AC-Cookie, length 16 \227C/\011\206~b \003\212C9CB\011TB'DC
        tag Host-Uniq, length 4 \000P\221D
  0000: 1119 0000 0020 0101 0000 0104 0010 97ef  ..... .........C/
  0010: 0986 7ea6 038a f9dc 4209 54a7 d0c7 0103  ..~b ..C9CB.TB'DC..
  0020: 0004 0050 91d0                           ...P.D

13:25:51.577644 PPPoE-Discovery
        code Confirm, version 1, type 1, id 0x0ee5, length 49
        tag Service-Name, length 0
        tag Host-Uniq, length 4 \000P\221D
        tag AC-Name, length 13 swy1-waymouth
        tag AC-Cookie, length 16 \227C/\011\206~b \003\212C9CB\011TB'DC
  0000: 1165 0ee5 0031 0101 0000 0103 0004 0050  .e.C%.1.........P
  0010: 91d0 0102 000d 7377 7931 2d77 6179 6d6f  .D....swy1-waymo
  0020: 7574 6801 0400 1097 ef09 867e a603 8af9  uth.....C/..~b ..C9
  0030: dc42 0954 a7d0 c7f1 b6b7 32              CB.TB'DCC1B6B72

13:25:51.578224 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Request, Magic-Number=382655019
  0000: 1100 0ee5 000c c021 014a 000a 0506 16ce  ...C%..A!.J.....I
  0010: da2b                                     U+

13:25:51.592411 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 21
        LCP: Configure-Request, Max-Rx-Unit=1492, Auth-Prot CHAP/MD5, Magic-Numb
er=1952652495, Vendor-Ext
  0000: 1100 0ee5 0015 c021 01f7 0013 0104 05d4  ...C%..A!.C7.....O
  0010: 0305 c223 0505 0674 631c cf00 0000 0000  ..A#...tc.I.....
  0020: 0000 0000 0000 0000 0000 0000 0000 2f49  ............../I
  0030: 9bb7                                     .B7

13:25:51.592646 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 11
        LCP: Configure-Nak, Auth-Prot PAP, Vendor-Ext, Max-Rx-Unit=46848
  0000: 1100 0ee5 000b c021 03f7 0009 0305 c023  ...C%..A!.C7....A#
  0010: 05                                       .

13:25:51.592870 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Ack, Magic-Number=382655019, Vendor-Ext
  0000: 1100 0ee5 000c c021 024a 000a 0506 16ce  ...C%..A!.J.....I
  0010: da2b 0000 0000 0000 0000 0000 0000 0000  U+..............
  0020: 0000 0000 0000 0000 0000 0000 0000 8cf5  ...............o
  0030: 88bc                                     .B<

13:25:52.583842 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Request, Magic-Number=382655019, Vendor-Ext
  0000: 1100 0ee5 000c c021 014b 000a 0506 16ce  ...C%..A!.K.....I
  0010: da2b                                     U+

13:25:52.598964 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Ack, Magic-Number=382655019, Vendor-Ext
  0000: 1100 0ee5 000c c021 024b 000a 0506 16ce  ...C%..A!.K.....I
  0010: da2b 0000 0000 0000 0000 0000 0000 0000  U+..............
  0020: 0000 0000 0000 0000 0000 0000 0000 93e2  ...............C"
  0030: 783c                                     x<

13:25:53.593815 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Request, Magic-Number=382655019, Max-Rx-Unit
  0000: 1100 0ee5 000c c021 014c 000a 0506 16ce  ...C%..A!.L.....I
  0010: da2b                                     U+

13:25:53.608943 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Ack, Magic-Number=382655019, Vendor-Ext
  0000: 1100 0ee5 000c c021 024c 000a 0506 16ce  ...C%..A!.L.....I
  0010: da2b 0000 0000 0000 0000 0000 0000 0000  U+..............
  0020: 0000 0000 0000 0000 0000 0000 0000 4c8b  ..............L.
  0030: 4a08                                     J.

13:25:54.603837 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Request, Magic-Number=382655019
  0000: 1100 0ee5 000c c021 014d 000a 0506 16ce  ...C%..A!.M.....I
  0010: da2b                                     U+

13:25:54.619199 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        LCP: Configure-Ack, Magic-Number=382655019, Vendor-Ext
  0000: 1100 0ee5 000c c021 024d 000a 0506 16ce  ...C%..A!.M.....I
  0010: da2b 0000 0000 0000 0000 0000 0000 0000  U+..............
  0020: 0000 0000 0000 0000 0000 0000 0000 539c  ..............S.
  0030: ba88                                     B:.

13:25:54.683259 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 20
        LCP: Configure-Request, Max-Rx-Unit=1492, Auth-Prot PAP, Magic-Number=19
52652495, Vendor-Ext
  0000: 1100 0ee5 0014 c021 01f8 0012 0104 05d4  ...C%..A!.o.....O
  0010: 0304 c023 0506 7463 1ccf 0000 0000 0000  ..A#..tc.I......
  0020: 0000 0000 0000 0000 0000 0000 0000 f605  ..............C6.
  0030: 14c7                                     .C

13:25:54.683452 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 20
        LCP: Configure-Ack, Max-Rx-Unit=1492, Auth-Prot PAP, Magic-Number=195265
2495, Add-Ctrl-Field-Compr ACFC
  0000: 1100 0ee5 0014 c021 02f8 0012 0104 05d4  ...C%..A!.o.....O
  0010: 0304 c023 0506 7463 1ccf                 ..A#..tc.I

13:25:54.683804 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 40
        PAP: Authenticate-Request, Peer-Id=[hidden email],
Passwd=SECRET
  0000: 1100 0ee5 0028 c023 014e 0026 18XX XXXX  ...C%.(A#.N.&.myuser
  0010: XXXX XXXX XX40 XXXX XXXX XXXX XXXX 2e63  [hidden email]
  0020: 6f6d 2e61 7508 XXXX XXXX XXXX XXXX       om.au.SECRET

13:25:55.683841 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 40
        PAP: Authenticate-Request, Peer-Id=[hidden email], Passwd=42bt
mr58
  0000: 1100 0ee5 0028 c023 014f 0026 18XX XXXX  ...C%.(A#.O.&.myuser
  0010: XXXX XXXX XX40 XXXX XXXX XXXX XXXX 2e63  [hidden email]
  0020: 6f6d 2e61 7508 XXXX XXXX XXXX XXXX       om.au.SECRET

13:25:55.712727 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 7
        PAP: Authenticate-Ack
  0000: 1100 0ee5 0007 c023 024f 0005 0000 0000  ...C%..A#.O......
  0010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0020: 0000 0000 0000 0000 0000 0000 0000 197b  ...............{
  0030: dc18                                     C.

13:25:55.713074 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Request, IP-Address=0.0.0.0
  0000: 1100 0ee5 000c 8021 0150 000a 0306 0000  ...C%...!.P......
  0010: 0000                                     ..

13:25:55.720113 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Request, IP-Address=211.31.137.129
  0000: 1100 0ee5 000c 8021 01f6 000a 0306 d31f  ...C%...!.C6....O.
  0010: 8981 0000 0000 0000 0000 0000 0000 0000  ................
  0020: 0000 0000 0000 0000 0000 0000 0000 fee1  .............._C!
  0030: 306d                                     0m

13:25:55.720334 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Ack, IP-Address=211.31.137.129
  0000: 1100 0ee5 000c 8021 02f6 000a 0306 d31f  ...C%...!.C6....O.
  0010: 8981                                     ..

13:25:55.739813 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Nak, IP-Address=58.104.4.241
  0000: 1100 0ee5 000c 8021 0350 000a 0306 3a68  ...C%...!.P....:h
  0010: 04f1 0000 0000 0000 0000 0000 0000 0000  .C1..............
  0020: 0000 0000 0000 0000 0000 0000 0000 cd13  ..............I.
  0030: eae1                                     C*C!

13:25:55.739991 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Request, IP-Address=58.104.4.241
  0000: 1100 0ee5 000c 8021 0151 000a 0306 3a68  ...C%...!.Q....:h
  0010: 04f1                                     .C1

13:25:55.766690 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 12
        IPCP: Configure-Ack, IP-Address=58.104.4.241
  0000: 1100 0ee5 000c 8021 0251 000a 0306 3a68  ...C%...!.Q....:h
  0010: 04f1 0000 0000 0000 0000 0000 0000 0000  .C1..............
  0020: 0000 0000 0000 0000 0000 0000 0000 30f9  ..............0C9
  0030: 92ec                                     .C,

13:25:59.423836 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 10
        LCP: Echo-Request, Magic-Number=382655019
  0000: 1100 0ee5 000a c021 0952 0008 16ce da2b  ...C%..A!.R...IU+

13:25:59.450387 PPPoE-Session
        code Session, version 1, type 1, id 0x0ee5, length 10
        LCP: Echo-Reply, Magic-Number=1952652495
  0000: 1100 0ee5 000a c021 0a52 0008 7463 1ccf  ...C%..A!.R..tc.I
  0010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0020: 0000 0000 0000 0000 0000 0000 0000 dfee  ..............CC.
  0030: 5675                                     Vu

There are a series of LCP Echo-Request and Echo-Replies after this,
but nothing else.

Can anyone hazard a guess about the problem here? dmesg follows:

OpenBSD 3.7 (GENERIC) #0: Tue Jan 10 15:26:51 CST 2006
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 75 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8
cpu0: F00F bug workaround installed
real mem  = 41525248 (40552K)
avail mem = 30085120 (29380K)
using 532 buffers containing 2179072 bytes (2128K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 10/10/94, BIOS32 rev. 0 @ 0xf6f20
apm0 at bios0: Power Management spec V1.1
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000
pcibios0: PCI BIOS has 4 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82437FX" rev 0x02
pcib0 at pci0 dev 7 function 0 "Intel 82371FB ISA" rev 0x02
pciide0 at pci0 dev 7 function 1 "Intel 82371FB IDE" rev 0x02: DMA, channel 0 wi
red to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <ST51270A>
wd0: 32-sector PIO, LBA, 1223MB, 2504880 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <MITSUMI, CD-ROM FX400E !B, K04> SCSI0 5/cdrom rem
ovable
cd0(pciide0:1:1): using PIO mode 3
sis0 at pci0 dev 8 function 0 "NS DP83815 10/100" rev 0x00: DP83815D, irq 10, ad
dress 00:09:5b:04:57:6a
nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1
sis1 at pci0 dev 9 function 0 "NS DP83815 10/100" rev 0x00: DP83815D, irq 11, ad
dress 00:40:f4:6f:d4:d4
nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard
vga0 at isa0 port 0x3b0/48 iomem 0xa0000/131072
wsdisplay0 at vga0: console (80x25, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
isapnp0 at isa0 port 0x279: read port 0x203
"ESS ES1868 Plug and Play AudioD, ESS0000, , " at isapnp0 port 0x800/8 not confi
gured
ess0 at isapnp0 "ESS ES1868 Plug and Play AudioD, ESS1868, , " port 0x220/16,0x3
88/4,0x330/2 irq 5 drq 1,0: ESS Technology ES1868 [version 0x688b]
ess0: audio1 interrupting at irq 5
audio0 at ess0
opl0 at ess0: model OPL3
midi1 at opl0: <ESS Yamaha OPL3>
joy0 at isapnp0 "ESS ES1868 Plug and Play AudioD, ESS0001, , " port 0x201/1
"ESS ES1868 Plug and Play AudioD, ESS0002, , " at isapnp0 port 0x100/8,0x300/2 i
rq 0 resource conflict
biomask f345 netmask ff45 ttymask ffc7
pctr: 586-class performance counters and user-level cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
pppoe0: phase establish
pppoe0: phase network
pppoe0: phase terminate
pppoe0: phase dead

Reply | Threaded
Open this post in threaded view
|

Re: Trouble with pppoe(4) on O3.7 RELEASE

Damon McMahon
OK, before I get a deluge of well-meaning people on and off list
telling me I inadvertently revealed my ISP authentication details,
I've already realised this and they have now been changed *blushes a
very deep shade of purple* For those who have/were going to let me
know, thanks for the thought!!

On 10/02/06, Damon McMahon <[hidden email]> wrote:
> Greetings,
>
> I'm having trouble getting pppoe(4) to establish a connection from my
> OpenBSD 3.7 RELEASE (+ errata patches) box to my ISP through a Netgear
> DG632 in bridge mode. I can successfully establish a connection using
> pppoe(8) although it is a bit hit-and-miss. The in-kernel pppoe(4) is
> not hit-and-miss, however, it's just miss.

[SNIP]

Reply | Threaded
Open this post in threaded view
|

Re: Trouble with pppoe(4) on O3.7 RELEASE

Shane J Pearson
In reply to this post by Damon McMahon
Hi Damon,

On 2006.02.10, at 2:44 PM, Damon McMahon wrote:
> Greetings,
>
> I'm having trouble getting pppoe(4) to establish a connection from my
> OpenBSD 3.7 RELEASE (+ errata patches) box to my ISP through a Netgear
> DG632 in bridge mode. I can successfully establish a connection using
> pppoe(8) although it is a bit hit-and-miss. The in-kernel pppoe(4) is
> not hit-and-miss, however, it's just miss.

I use a DG632 in "MODEM" mode, which appears to allow a "half bridge"
mode. To this my Sun U10 OpenBSD firewall is attached, with hme0 as my
ext interface which sees all traffic destined to my public IP without
the DG632 doing NAT. I have the DG632 negotiating a PPPoA connection to
my ISP and then it just bridges the internet traffic to my U10. So my
OpenBSD firewall does not have to deal with PPPoE or PPPoA and I can
use an MTU of 1500.

This has been rock solid for 6 months or more.

The manual for the DG632 does not mention a "bridge mode" and also does
not mention "half bridge". In MODEM mode you can refrain from entering
your PPPoA/PPPoE username and password, etc and have the machine it is
attached to deal with those, or you can enter those details into the
MODEM and have it perform as a half-bridge.

Maybe this would be a solution for you? I'm really happy with the DG632
and have been considering buying another to keep as a spare, because
I've had trouble in the past with other DSL MODEM's which claimed to
support a half bridge mode.

Bye for now,


Shane J Pearson        shanejp netspace net au                       ->|

Reply | Threaded
Open this post in threaded view
|

Re: Trouble with pppoe(4) on O3.7 RELEASE

Can Erkin Acar
In reply to this post by Damon McMahon
On 10/02/06, Damon McMahon <[hidden email]> wrote:
> Greetings,
>
> I'm having trouble getting pppoe(4) to establish a connection from my
> OpenBSD 3.7 RELEASE (+ errata patches) box to my ISP through a Netgear
> DG632 in bridge mode. I can successfully establish a connection using
> pppoe(8) although it is a bit hit-and-miss. The in-kernel pppoe(4) is
> not hit-and-miss, however, it's just miss.

While it may not be related to your particular problem, please note that
there have been considerable changes to pppoe and sppp layer since 3.7
you should consider upgrading.

It looks from the trace like you have established a pppoe session. But
no traffic flows? Have you actually tried pinging some remote IP?

you may have problems with name resolution.
pppoe(4) does not negotiate DNS. you should enter a valid DNS resolver
address to /etc/resolv.conf manually.

also, from the trace, it looks like the peer asks for CHAP authentication
but then falls back to PAP, due to your settings. Using 'myauthproto=chap'
might help. Also it is strange that the peer offers an IP then NAK's it
and offers another one. You could try debugging this with your ISP.

if all fails, dumps from a successful pppoe(8) session might help.
please add '-e' switch to tcpdump. it helps identifying peers.

Can