#debiants — Public Fediverse posts

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?

Hmmm going slightly troppo. I have bought a little four port fanless PC, nice-cheap-and-cheery, and installed #debian on it. The aim is to connect to my ISP (yless4u) using #PPPoE on enp4s0.

(the existing connection is through a vilo. Its only parameters are username and password. Somehow it makes sense of all the rest. Clever, but inscrutable)

pppoe-config produces a workable config, but, after the ppp0 comes up, all packets sent into it are filtered by the other end.

During debugging, I noticed that after the PAP/CHAP phase, the remote end sends a "VLAN 100" message back to me. I am *supposing* that it is saying ??? that I should ??? tag packets as #vlan 100 ??? before sending them down ppp0???
Is this in any way common/useful? Has anyone else seen this?

(The other idea, that vlan 100 might be required for authentication and setup seems not to work. Setting up emnp4s0.100 as vlan 100 and telling pppoe to use that interface instead of enp4s0 FAILS)

So, over to #mastodon #debiants. What is going on here? Am I barking up the wrong tree?