How do I setup a DSL connection?

[daos]

Hi, I am a beginner when it comes to Linux. I wanted to try this distro but I can't find a GUI like in most other distros to set up my DSL connection.
I am using FossaPup64 9.5.
Can you help me please?
Thank you!

[rockedge]

There should be a "connect" icon on the desktop or in the menu under Setup that will open a GUI to set up a network connection

[daos]

That is true but i can't find how to make the DSL connection.

[FeodorF]

The network tool will use 'auto connect'.
Are you talking about wired or wireless internet access?

[daos]

I'm talking about making a wired connection.

The network tool will use 'auto connect'.

Auto connect to what?...DSL connection is not created.I need to make it manually on the PC itself because that's what a DSL connection means, there's no router that already has the dsl connection set up.

[FeodorF]

So you are using a digital subscriber line modem installed in a computer PCI slot.

[daos]

So you are using a digital subscriber line modem installed in a computer PCI slot.

No, I'm using a fibre optics FTTH device that is in bridge mode(not in router mode). Because it's not in router mode I need to set up the DSL connection with a user and password directly on my PC.

[rockedge]

Ok I think you can do it via the connection wizard via the analog modem selection. I am not 100% sure of it though.

(13).png (55.33 KiB) Viewed 576 times

[daos]

Ok I think you can do it via the connection wizard via the analog modem selection. I am not 100% sure of it though.

(13).png

I don't see there any DSL type of connection.

Can't it be something like this? but what are the Puppy Linux equivalent commands?

https://www.linuxbabe.com/ubuntu/create ... untu-16-04

[rockedge]

I was looking around and found this information https://oldforum.puppylinux.com/viewtopic.php?p=175853

I just tried this in a Bionic64-8.0 from a terminal and it looks promising:

Code: Select all

pppoe-setup

[williams2]

You can edit the file /etc/ppp/pppoe.conf to set your USER id.
ETH would probably be eth0 or eth1.

You need to setup the ethernet network first. Probably the network connection wizard in the menu can do that.
The network wizard might have dsl options, I don't know.

Then you can open a text terminal (click Console on the desktop) and type pppoe-start

It's easier to have an eth or wireless router configured to connect to dsl.

[wizard]

@daos

just a caution, connecting in bridge mode like you propose is gong to be a big security risk since it will give you a WAN address that is much easier to attack. One of the benefits of using a router is it provides you with NAt and a LAN address that is more secure.

wizard

[daos]

@daos

just a caution, connecting in bridge mode like you propose is gong to be a big security risk since it will give you a WAN address that is much easier to attack. One of the benefits of using a router is it provides you with NAt and a LAN address that is more secure.

wizard

I have the same DSL over PPPOE type of connection over fibre for 5 years. Not sure what you have in mind with the attacks scenario but until now I didn't have on windows 7/10 viruses/malware/ransomware in all those years(of course I use mostly trusted software)

You can edit the file /etc/ppp/pppoe.conf to set your USER id.
ETH would probably be eth0 or eth1.

You need to setup the ethernet network first. Probably the network connection wizard in the menu can do that.
The network wizard might have dsl options, I don't know.

Then you can open a text terminal (click Console on the desktop) and type pppoe-start

It's easier to have an eth or wireless router configured to connect to dsl.

Do you know if DNS will be properly configured and ISP will provide it automatically?

[williams2]

It's been a long time since I had a dsl connection.
Roaring Penguin had a gui and a cli interface.

I think the pppoe scripts use /etc/ppp/pppoe.conf
pppoe.conf has options for dns.
I think the defaults should give you dns from the isp, using dhcp.
pppoe-setup might be easier to use.

I don't remember if the ethernet network should be up or down before starting pppoe.
I seem to remember that it should be down (that is, you would need 2 eth cards if you want an eth network, 1 for pppoe and 1 for the network.)

You can use Cloudflare's dns server by putting nameserver 1.1.1.1 at the top of the file /etc/resolv.conf.head
You can create the file if it doesn't exist. That should work in any case, whether your isp's dns works or not.

[rerwin]

@daos
About 5 years ago I added to Frisbee the capabilities to connect to mobile (cellular) and DSL systems. The latter uses the "roaring penguin" package but sets things up using its own GUI, under the "Telephone Networks" tab.

I am unable to test the DSL part but have seen no complaints about it -- nor any confirmations that it actually works. But I may have some helpful information for you before you try it or use the pppoe-setup and pppoe-start commands.

First, some background: There has been a recurring conflict between links related to DNS resolution that can prevent connection. The fix has been applied repeatedly but subsequently lost during updates of roaring penguin -- and is currently absent from the fossapups.

I am attaching a script to apply the fix, for use before attempting to connect to a DSL service: rp_connect_resolv_fix. Click on it to unzip it, set its execute permission, then click on it to run it.

Note that I know little about DSL beyond what I found in roaring penguin's pppoe-setup and from the old forum.

I gather that you can run pppoe-setup and then pppoe-start to get a connection, but have no personal experience using them.

I am very curious to know whether Frisbee's PPPoE or the pppoe- commands work for you -- after you run the fix script.

Richard

-----

Just so you know what the "fix" script does, it changes pppoe-connect:

Code: Select all

# Jigger DNS if required...
if test "$DNSTYPE" = "SERVER" ; then
    # Sorry, dude...
    rm -f /etc/resolv.conf
    ln -s /etc/ppp/resolv.conf /etc/resolv.conf
elif test "$DNSTYPE" = "SPECIFY" ; then
    # Sorry, dude...
    rm -f /etc/resolv.conf
    echo "nameserver $DNS1" > /etc/resolv.conf
    if test -n "$DNS2" ; then
	echo "nameserver $DNS2" >> /etc/resolv.conf
    fi
fi

to:

Code: Select all

# Jigger DNS if required...
if test "$DNSTYPE" = "SERVER" ; then
    # Sorry, dude...
#BK    rm -f /etc/resolv.conf
#BK    ln -s /etc/ppp/resolv.conf /etc/resolv.conf
    : #BK
elif test "$DNSTYPE" = "SPECIFY" ; then
    # Sorry, dude...
#BK    rm -f /etc/resolv.conf
    echo "nameserver $DNS1" > /etc/resolv.conf
    if test -n "$DNS2" ; then
	echo "nameserver $DNS2" >> /etc/resolv.conf
    fi
fi

[williams2]

@rerwin AFAIK, /etc/ppp/resolv.conf is a symlink to /etc/resolv.conf (the actual config file)
because the dialup (analog telephone modem) connection needs it.

But when Roaring Penguin gets set up, /etc/resolv.conf becomes a symlink to /etc/ppp/resolv.conf (the actual config file)

If /etc/ppp/resolv.conf is a symlink and Roaring Penguin is initilized, you end up with /etc/ppp/resolv.conf and /etc/resolv.conf symlinked to each other, which will not work.
So, for RP to work, /etc/ppp/resolv.conf needs to be an actual file, and /etc/resolv.conf needs to be a symlink.

And to use dialup, /etc/ppp/resolv.conf needs to be a symlink to text file /etc/resolv.conf
or dialup won't work.

See /etc/ppp/README.txt

[rerwin]

If /etc/ppp/resolv.conf is a symlink and Roaring Penguin is initilized, you end up with /etc/ppp/resolv.conf and /etc/resolv.conf symlinked to each other, which will not work.
So, for RP to work, /etc/ppp/resolv.conf needs to be an actual file, and /etc/resolv.conf needs to be a symlink.

And to use dialup, /etc/ppp/resolv.conf needs to be a symlink to text file /etc/resolv.conf
or dialup won't work.

You describe the problem exactly but not the best solution. This problem is what I referred to above:

There has been a recurring conflict between links related to DNS resolution that can prevent connection. The fix has been applied repeatedly but subsequently lost during updates of roaring penguin -- and is currently absent from the fossapups.

The solution is to retain Barry's original fix, which the above-attached package implements. Yes, it may be considered "ugly", because it requires updating each new version of "RP". However, since the RP package is included as a .pet, someone makes the effort to convert the released .deb package to a .pet. If the conversion process were to include a "pinstall.sh" script to make the changes (described above), that could always be included to make the patch during .pet installation.