Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to add PPPOE configuration support or make it compatible #1344

Open
Cookiemon18 opened this issue Aug 18, 2023 · 2 comments
Open

Request to add PPPOE configuration support or make it compatible #1344

Cookiemon18 opened this issue Aug 18, 2023 · 2 comments

Comments

@Cookiemon18
Copy link

Cookiemon18 commented Aug 18, 2023

Hello, I am a yast user and I want to use yast to manage my network configuration. However, I found that yast does not support PPPOE configuration, or rather, if I configure PPPOE elsewhere, yast cannot use the network settings function to configure other network cards.

I hope that yast can add support for PPPOE configuration, or at least not let me completely lose the ability to use yast's network settings function to configure other network cards because of configuring PPPOE elsewhere. In this way, I can easily manage my network settings without worrying about conflicts with PPPOE.

My operating system is openSUSE Leap 15.5, and the version of yast is 4.5.25. I have provided some screenshots in the attachment to illustrate my situation.
图片

In addition, I need to declare that I use rp-pppoe to configure pppoe. This is the configuration information of my pppoe interface:

# /etc/sysconfig/network/ifcfg-ppp0
USERCTL=yes
BOOTPROTO=dialup
NAME=DSLppp0
DEVICE=ppp0
TYPE=xDSL
ONBOOT=yes
PIDFILE=/var/run/pppoe-adsl.pid
FIREWALL=NONE
PING=.
PPPOE_TIMEOUT=80
LCP_FAILURE=3
LCP_INTERVAL=20
CLAMPMSS=1412
CONNECT_POLL=6
CONNECT_TIMEOUT=60
DEFROUTE=yes
SYNCHRONOUS=no
ETH=eth8
PROVIDER=DSLppp0
[email protected]
PEERDNS=no
DEMAND=no
ZONE=public
@teclator
Copy link
Contributor

teclator commented Sep 11, 2023

It looks reasonable to me to at least identify the BOOTPROTO as a valid one although we do not support he dialup connections anymore, so we probably should skip that ones by not touching them, so, something to be evaluated.

Will move it to a bug with an "Enhancement" priority

@Cookiemon18
Copy link
Author

It looks reasonable to me to at least identify the BOOTPROTO as a valid one although we do not support he dialup connections anymore, so we probably should skip that ones by not touching them, so, something to be evaluated.

Will move it to a bug with an "Enhancement" priority

Thank you so much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants