Re: OpenBSD pppoe and Bell Fibe
Hi Stuart, You got it right off the bat. I removed mtu config, replaced NONE with 0.0.0.1 and removed the dest line. Booted up and voila, a workable WAN IP address using pppoe passthrough. It seems like the realtek card may be holding back performance as I'm only pulling in 800Mbps or perhaps it is the APU but I have doubts there. My comparison is using my laptop to test pppoe credentials and fully saturating the internet connection; as well as using the router that came with the ISP's service (Home Hub 4000). In any case, all is working and thank you very much for your help! Time to find an Intel 10Gb PCIe card. Brodey Dover On Sun, 20 Feb 2022 at 12:46, Stuart Henderson wrote: > I would recommend trying it like my example, there is a race condition > when you list the destination address separately. > > -- > Sent from a phone, apologies for poor formatting. > > > On 20 February 2022 16:50:35 Brodey Dover wrote: > >> You make a very good point about attaching the configuration :-). >> >> inet 0.0.0.0 255.255.255.255 NONE mtu 1500 >> pppoedev re0 authproto pap >> authname 'username' authkey 'password' up >> dest 0.0.0.1 >> !/sbin/route add default -ifp pppoe0 0.0.0.1 >> >> That should help. >> >> Thank you, >> >> >> >> On Sun, 20 Feb 2022 at 06:06, Stuart Henderson >> wrote: >> >>> On 2022-02-19, Brodey Dover wrote: >>> > Hello all, >>> > >>> > I've configured hostname.pppoe0 and hostname.re0 as per the pppoe >>> manpage >>> > for OpenBSD (I'm running 7) and I'm unable to successfully leverage >>> the >>> > Bell HomeHub 4000's pppoe passthrough. I've verified that passthrough >>> does >>> > work with my Windows 7 laptop, however, I just can't get pppoe to >>> move past >>> > the initialization stage. >>> >>> Might help to show your config. >>> >>> My typical config in hostname.pppoe0 is something like this >>> >>> inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap >>> authname "user@realm" authkey "password" up >>> >>> > The PADI gets sent, but ultimately it'll timeout. After adjusting to >>> the >>> > second config in the man page where mut1508 is set to the physical >>> device, >>> >>> That is a special case and is very unlikely to ever be _required_ by an >>> ISP and often won't work. Normally you're better off starting with the >>> default MTU to get things working initially, then try that later if >>> needed >>> as a refinement (but remember that it's there in case things stop working >>> later; sometimes internal changes in the ISP network will stop it from >>> working later).. >>> >>> > pppoe0: ipcp parse opt values: address 10.11.1.81 [not agreed] send >>> > conf-nak >>> >>> The other side proposed this address (possibly for the address of their >>> end of the connection?) and your side rejected it. >>> >>> -- >>> Please keep replies on the mailing list. >>> >>> >
Re: OpenBSD pppoe and Bell Fibe
I would recommend trying it like my example, there is a race condition when you list the destination address separately. -- Sent from a phone, apologies for poor formatting. On 20 February 2022 16:50:35 Brodey Dover wrote: You make a very good point about attaching the configuration :-). inet 0.0.0.0 255.255.255.255 NONE mtu 1500 pppoedev re0 authproto pap authname 'username' authkey 'password' up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 That should help. Thank you, On Sun, 20 Feb 2022 at 06:06, Stuart Henderson wrote: On 2022-02-19, Brodey Dover wrote: Hello all, I've configured hostname.pppoe0 and hostname.re0 as per the pppoe manpage for OpenBSD (I'm running 7) and I'm unable to successfully leverage the Bell HomeHub 4000's pppoe passthrough. I've verified that passthrough does work with my Windows 7 laptop, however, I just can't get pppoe to move past the initialization stage. Might help to show your config. My typical config in hostname.pppoe0 is something like this inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap authname "user@realm" authkey "password" up The PADI gets sent, but ultimately it'll timeout. After adjusting to the second config in the man page where mut1508 is set to the physical device, That is a special case and is very unlikely to ever be _required_ by an ISP and often won't work. Normally you're better off starting with the default MTU to get things working initially, then try that later if needed as a refinement (but remember that it's there in case things stop working later; sometimes internal changes in the ISP network will stop it from working later).. pppoe0: ipcp parse opt values: address 10.11.1.81 [not agreed] send conf-nak The other side proposed this address (possibly for the address of their end of the connection?) and your side rejected it. -- Please keep replies on the mailing list.
Re: OpenBSD pppoe and Bell Fibe
You make a very good point about attaching the configuration :-). inet 0.0.0.0 255.255.255.255 NONE mtu 1500 pppoedev re0 authproto pap authname 'username' authkey 'password' up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 That should help. Thank you, On Sun, 20 Feb 2022 at 06:06, Stuart Henderson wrote: > On 2022-02-19, Brodey Dover wrote: > > Hello all, > > > > I've configured hostname.pppoe0 and hostname.re0 as per the pppoe > manpage > > for OpenBSD (I'm running 7) and I'm unable to successfully leverage the > > Bell HomeHub 4000's pppoe passthrough. I've verified that passthrough > does > > work with my Windows 7 laptop, however, I just can't get pppoe to move > past > > the initialization stage. > > Might help to show your config. > > My typical config in hostname.pppoe0 is something like this > > inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap authname > "user@realm" authkey "password" up > > > The PADI gets sent, but ultimately it'll timeout. After adjusting to the > > second config in the man page where mut1508 is set to the physical > device, > > That is a special case and is very unlikely to ever be _required_ by an > ISP and often won't work. Normally you're better off starting with the > default MTU to get things working initially, then try that later if needed > as a refinement (but remember that it's there in case things stop working > later; sometimes internal changes in the ISP network will stop it from > working later).. > > > pppoe0: ipcp parse opt values: address 10.11.1.81 [not agreed] send > > conf-nak > > The other side proposed this address (possibly for the address of their > end of the connection?) and your side rejected it. > > -- > Please keep replies on the mailing list. > >
Re: OpenBSD pppoe and Bell Fibe
On 2022-02-19, Brodey Dover wrote: > Hello all, > > I've configured hostname.pppoe0 and hostname.re0 as per the pppoe manpage > for OpenBSD (I'm running 7) and I'm unable to successfully leverage the > Bell HomeHub 4000's pppoe passthrough. I've verified that passthrough does > work with my Windows 7 laptop, however, I just can't get pppoe to move past > the initialization stage. Might help to show your config. My typical config in hostname.pppoe0 is something like this inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap authname "user@realm" authkey "password" up > The PADI gets sent, but ultimately it'll timeout. After adjusting to the > second config in the man page where mut1508 is set to the physical device, That is a special case and is very unlikely to ever be _required_ by an ISP and often won't work. Normally you're better off starting with the default MTU to get things working initially, then try that later if needed as a refinement (but remember that it's there in case things stop working later; sometimes internal changes in the ISP network will stop it from working later).. > pppoe0: ipcp parse opt values: address 10.11.1.81 [not agreed] send > conf-nak The other side proposed this address (possibly for the address of their end of the connection?) and your side rejected it. -- Please keep replies on the mailing list.
OpenBSD pppoe and Bell Fibe
Hello all, I've configured hostname.pppoe0 and hostname.re0 as per the pppoe manpage for OpenBSD (I'm running 7) and I'm unable to successfully leverage the Bell HomeHub 4000's pppoe passthrough. I've verified that passthrough does work with my Windows 7 laptop, however, I just can't get pppoe to move past the initialization stage. The PADI gets sent, but ultimately it'll timeout. After adjusting to the second config in the man page where mut1508 is set to the physical device, things get a bit better but only after I manually invoke sh /etc/netstartbecause it seems after bootup there are only two PADI retries. Anyway, enabling debug and starting up netstart I will see pppoe0: ipcp input(starting):
Re: OpenBSD PPPOE
Andrey Korobkov writes: > Hello, > > I've already had the similar (same?) issue with PPPoE on OpenBSD 6.5 and > 6.6 when I tried to simply use the example from man pppoe(4). > > After looking through source code I thought it's like needed > configuration structs are not fully populated (missed dest value), as if > it were 2 different commands (inet 0.0.0.0… and dest 0.0.0.1), but looks > like it wants both address and dest being set during one single configuration > line (command). > > So I've just used slightly different config format, with both address and > source set in one single line: > > #cat /etc/hostname.pppoe0 > inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev cnmac0 authproto chap authname > ' authkey ' up > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > And it works very well for me! So I hope this would help you tooo. > > P.S. Also would be nice if anyone with knowledge of C language look once > more at this example from man pppoe(4) and verified it against current pppoe > initialization code… > > > best regards, > -- > Andrey Korobkov > Sorry, my mistake. I probably forgot word NONE in first config line. Just tested again and it worked even as in man pppoe(4) example. Sorry, -- Andrey Korobkov
Re: OpenBSD PPPOE
peterwkc writes: > Dear All, > > I would like to setup my openbsd as router. > /etc/hostname.fxp0 > up > > /etc/hostname.pppoe0 > pppoedev fxp0 authproto pap authname "" authkey "" up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > > Not able to get a connection. What wrong with it? > > > > -- > Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html > Hello, I've already had the similar (same?) issue with PPPoE on OpenBSD 6.5 and 6.6 when I tried to simply use the example from man pppoe(4). After looking through source code I thought it's like needed configuration structs are not fully populated (missed dest value), as if it were 2 different commands (inet 0.0.0.0… and dest 0.0.0.1), but looks like it wants both address and dest being set during one single configuration line (command). So I've just used slightly different config format, with both address and source set in one single line: #cat /etc/hostname.pppoe0 inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev cnmac0 authproto chap authname ' authkey ' up !/sbin/route add default -ifp pppoe0 0.0.0.1 And it works very well for me! So I hope this would help you tooo. P.S. Also would be nice if anyone with knowledge of C language look once more at this example from man pppoe(4) and verified it against current pppoe initialization code… best regards, -- Andrey Korobkov
Re: OpenBSD PPPOE
Hey, * /etc/hostname.vlan500 # hostname.vlan500 vnetid 835 parent parent fxp0 up * /etc/hostname.pppoe0 #hostname.pppoe0 inet 0.0.0.0 255.255.255.255 NONE \ pppoedev vlan500 authproto pap \ authname "" authkey "" up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 For debuging: ifconfig pppoe0 debug Kind regards, Sacha. Le 22/01/2020 à 02:49, Peter Wong a écrit : > Yes, my ISP operate pppoe with vlan. How to configure my fxp0 using vlan id > 500? > > > Regards, > -- > Peter Wong > 016-396 3326 > > > On Wed, Jan 22, 2020 at 6:10 AM Joe Cook wrote: > >> Hi, >> >> In my experience, PPPoE operates on a VLAN and not directly on an >> interface like fxp0. >> >> For my setup I had the ONT connect to interface em2. I ran the following: >> >> *doas tcpdump -i em2* >> >> In the output I found the following: >> >> *11:05:43.878079 802.1Q vid 10 pri 0 PPPoE-Session* >> >> This tells me that PPPoE is tagged with VLAN ID 10 (802.1Q vid 10). I had >> to create vlan10 and attach it to em2 then I could create pppoe0 and attach >> it to vlan10. >> >> >> I hope this helps. >> >> >> Joe >> On 21/01/2020 6:42 pm, peterwkc wrote: >> >> Dear All, >> >> I would like to setup my openbsd as router. >> /etc/hostname.fxp0 >> up >> >> /etc/hostname.pppoe0 >> pppoedev fxp0 authproto pap authname "" authkey "" up >> dest 0.0.0.1 >> !/sbin/route add default -ifp pppoe0 0.0.0.1 >> >> >> Not able to get a connection. What wrong with it? >> >> >> >> -- >> Sent from: >> http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html >> >>
Re: OpenBSD PPPOE
On Thu, Jan 23, 2020 at 05:59:20AM +0800, Peter Wong wrote: > The hostname.filename should follow vlan or vnetid? > > Regards, > -- > Peter Wong > 016-396 3326 Hi, In my router I have 3 vlans configured so far. I seem to have created the hostname.if arbitrarily after the vnetid (3, 4 and 7), like here: eta$ ls /etc/hostname.vlan* /etc/hostname.vlan3/etc/hostname.vlan7 /etc/hostname.vlan4/etc/hostname.vlan7.OLD The .OLD gets skipped by rc afaik and is just a remnant file. Regards, -peter
Re: OpenBSD PPPOE
The hostname.filename should follow vlan or vnetid? Regards, -- Peter Wong 016-396 3326 On Wed, Jan 22, 2020 at 2:35 PM Peter J. Philipp wrote: > On Wed, Jan 22, 2020 at 09:49:18AM +0800, Peter Wong wrote: > > Yes, my ISP operate pppoe with vlan. How to configure my fxp0 using vlan > id > > 500? > > > > > > Regards, > > -- > > Peter Wong > > 016-396 3326 > > Hi Peter Wong, > > My PPPoE router uses VLAN id #7 (IEEE 802.1q protocol), this is how I set > up > the vlan: > > eta$ more /etc/hostname.vlan7 > description "T-Online Internet" > vnetid 7 parent cnmac0 > up mtu 1508 > eta$ ifconfig vlan7 > vlan7: flags=8843 mtu 1508 > lladdr fc:ec:da:04:8d:68 > description: T-Online Internet > index 9 priority 0 llprio 3 > encap: vnetid 7 parent cnmac0 txprio packet rxprio outer > groups: vlan > media: Ethernet autoselect (1000baseT full-duplex) > status: active > > You may make your vlan similarly by setting vnetid to 500. And then > instead of > your fxp interface you'd use vlan. In my case it's vlan7. > > Hope that helps, > -peter >
Re: OpenBSD PPPOE
On Wed, Jan 22, 2020 at 09:49:18AM +0800, Peter Wong wrote: > Yes, my ISP operate pppoe with vlan. How to configure my fxp0 using vlan id > 500? > > > Regards, > -- > Peter Wong > 016-396 3326 Hi Peter Wong, My PPPoE router uses VLAN id #7 (IEEE 802.1q protocol), this is how I set up the vlan: eta$ more /etc/hostname.vlan7 description "T-Online Internet" vnetid 7 parent cnmac0 up mtu 1508 eta$ ifconfig vlan7 vlan7: flags=8843 mtu 1508 lladdr fc:ec:da:04:8d:68 description: T-Online Internet index 9 priority 0 llprio 3 encap: vnetid 7 parent cnmac0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex) status: active You may make your vlan similarly by setting vnetid to 500. And then instead of your fxp interface you'd use vlan. In my case it's vlan7. Hope that helps, -peter
Re: OpenBSD PPPOE
Yes, my ISP operate pppoe with vlan. How to configure my fxp0 using vlan id 500? Regards, -- Peter Wong 016-396 3326 On Wed, Jan 22, 2020 at 6:10 AM Joe Cook wrote: > Hi, > > In my experience, PPPoE operates on a VLAN and not directly on an > interface like fxp0. > > For my setup I had the ONT connect to interface em2. I ran the following: > > *doas tcpdump -i em2* > > In the output I found the following: > > *11:05:43.878079 802.1Q vid 10 pri 0 PPPoE-Session* > > This tells me that PPPoE is tagged with VLAN ID 10 (802.1Q vid 10). I had > to create vlan10 and attach it to em2 then I could create pppoe0 and attach > it to vlan10. > > > I hope this helps. > > > Joe > On 21/01/2020 6:42 pm, peterwkc wrote: > > Dear All, > > I would like to setup my openbsd as router. > /etc/hostname.fxp0 > up > > /etc/hostname.pppoe0 > pppoedev fxp0 authproto pap authname "" authkey "" up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > > Not able to get a connection. What wrong with it? > > > > -- > Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html > >
Re: OpenBSD PPPOE
On Mon, 20 Jan 2020 22:42:51 -0700, peterwkc wrote: > /etc/hostname.pppoe0 > pppoedev fxp0 authproto pap authname "" authkey "" up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > Not able to get a connection. What wrong with it? Try using authproto chap instead of pap and see if that makes a difference. I doubt there are many ISPs still using PAP with PPPoE due to its weaknesses so we may want to update the example in the manual page. - todd
Re: OpenBSD PPPOE
Can you provide me with some more information? Perhaps run dmesg or check /var/log/messages ? You may also want to reboot your PC and test ping to see where the network error lies. jrmu On Mon, Jan 20, 2020 at 10:42:51PM -0700, peterwkc wrote: > Dear All, > > I would like to setup my openbsd as router. > /etc/hostname.fxp0 > up > > /etc/hostname.pppoe0 > pppoedev fxp0 authproto pap authname "" authkey "" up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > > Not able to get a connection. What wrong with it? > > > > -- > Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html >
Re: OpenBSD PPPOE
$man pppoe or http://man.openbsd.org/pppoe
OpenBSD PPPOE
Dear All, I would like to setup my openbsd as router. /etc/hostname.fxp0 up /etc/hostname.pppoe0 pppoedev fxp0 authproto pap authname "" authkey "" up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 Not able to get a connection. What wrong with it? -- Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
