On 2019-02-25, Markus Hennecke <markus-henne...@markus-hennecke.de> wrote:
> Am 25.02.2019 um 16:30 schrieb Thomas Huber:
>> Hi misc,
>>
>> i got the opportuniy to have 4 ADSL links to my rural site.
>> Two links have already been there and OpenBSD -stable running a APU2 is
>> shaping the traffic between this two links.
>>
>> But now I struggle with setting up the 3rd (pppoe2) link.
>> As far as I know I´ve to go through a vlan(4) with vnetid 7 and this seems
>> to be valid information
>> because the pppoe debug-logs are more extensive than when trying to connect
>> without the vlan between em0 and pppoe2:
>>
>> # cat /var/log/messages
>> [...]
>> Feb 25 10:14:49 router /bsd: pppoe2 (8864) state=3, session=0xa3 output ->
>> 88:a2:5e:1e:52:88, len=17
>> Feb 25 10:14:49 router /bsd: pppoe2: lcp input(req-sent): <conf-ack id=0x43
>> len=14
>> 05-06-d3-66-5d-a2-01-04-05-d4-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00>
>> Feb 25 10:14:49 router /bsd: pppoe2: lcp req-sent->ack-rcvd
>> Feb 25 10:14:50 router /bsd: pppoe2: lcp TO(ack-rcvd) rst_counter = 10
>> Feb 25 10:14:50 router /bsd: pppoe2: lcp ack-rcvd->req-sent
>> Feb 25 10:14:50 router /bsd: pppoe2: lcp output <conf-req id=0x44 len=14
>> 05-06-d3-66-5d-a2-01-04-05-d4>
>> Feb 25 10:14:50 router /bsd: pppoe2 (8864) state=3, session=0xa3 output ->
>> 88:a2:5e:1e:52:88, len=22
>> Feb 25 10:14:50 router /bsd: pppoe2: lcp input(req-sent): <conf-ack id=0x44
>> len=14
>> 05-06-d3-66-5d-a2-01-04-05-d4-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00>
>> Feb 25 10:14:50 router /bsd: pppoe2: lcp req-sent->ack-rcvd
>> Feb 25 10:14:51 router /bsd: pppoe2: lcp TO(ack-rcvd) rst_counter = 10
>> Feb 25 10:14:51 router /bsd: pppoe2: lcp ack-rcvd->req-sent
>> Feb 25 10:14:51 router /bsd: pppoe2: lcp output <conf-req id=0x45 len=14
>> 05-06-d3-66-5d-a2-01-04-05-d4>
>> Feb 25 10:14:51 router /bsd: pppoe2 (8864) state=3, session=0xa3 output ->
>> 88:a2:5e:1e:52:88, len=22
>> Feb 25 10:14:51 router /bsd: pppoe2: lcp input(req-sent): <conf-ack id=0x45
>> len=14
>> 05-06-d3-66-5d-a2-01-04-05-d4-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00>
>> Feb 25 10:14:51 router /bsd: pppoe2: lcp req-sent->ack-rcvd
>>
>> But to be honest I don´t know what this means and where to look furhter.
>> The ADSL modem is able to sync and a ISP-provided router-modem is also able
>> to establish connection.
>>
>> # cat /etc/hostname.pppoe2
>>
>> inet 0.0.0.0 255.255.255.255 NONE \
>> pppoedev vlan0 authproto pap \
>> authname 'xxx' authkey 'xxx'
>> dest 0.0.0.3
>> inet6 eui64
>> debug
>> up
>> !/sbin/route add default -ifp pppoe1 0.0.0.3
>> !/sbin/route add -inet6 default -ifp pppoe1 fe80::%pppoe2
>
> Why does it mention pppoe1 in the route add statements here? If I'm not
> mistaken these should be pppoe2.
>
>>
>> # cat /etc/hostname.vlan0
>>
>> inet 0.0.0.3 255.255.255.255 NONE descr VODDSL vlan 7 vlandev em0
>
> Why do you have 0.0.0.3 assigned to the vlan interface? My 6.4 router
> just has "vnetid 7 parent em0" + "up" in /etc/hostname.vlan7.
Yes you really don't want that.
>> # cat /etc/hostname.em0
>>
>> up
>>
>> Without understanding the internals of ADSL or PPPoE, I just copied this
>> configuration from the functional hostname.pppoe[0|1]
>> but this links work fine without the additional vlan(4). Guess this is
>> related to something ISP-thing called "BNG"
>> The reated ISP is Vodafone in Germany which is using the Telekom
>> infrastrcture just in case this is relevant.
>>
>> Anybody andy clue how to set this connection up correctly or where to look?
>> Thanks
>
>
One thing you can try is replacing this
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev vlan0 authproto pap \
authname 'xxx' authkey 'xxx'
dest 0.0.0.3
with this
inet 0.0.0.0 255.255.255.255 0.0.0.3 \
pppoedev vlan0 authproto pap \
authname 'xxx' authkey 'xxx'
(setting an inet address automatically brings up an interface - my
theory is that in the first case it may get too far in the negotiation
before 'dest XXX' is set).
If it doesn't help, please get a capture from tcpdump -nevvs1500 -i vlan0
and show the LCP/IPCP/IPV6CP bits there as well as the pppoe(4) debug output,
this gives a much more useful decode of the negotiation than you'll get from
the lcp-input and lcp-output lines.
