Tails should be usable by those stuck with dial-up Internet access. Recent events have shown that in some cases, dial-up might be the last option to reach the Internet when broadband operators have been shut down.
Next thing to do: make up our mind wrt. towards which one of the possible solutions we want to go: tails#6045 (closed).
- fix Debian bug #258064, but GNOME PPP looks dead upstream, so it might be an option to create a custom package handling resolvconf the way we want.
- find alternative ways to use WvDial or PPP.
Ideal solution: tails#5543 (closed)
NetworkManager (and ModemManager) have full support for mobile modems. But nothing for old school dial-up modems at the moment: see Integrated PPP support
Fallback option: provide GNOME PPP, a GUI front-end to old but trusty WvDial.
Here is a method to test dial-up PPP connections without resorting to a real modem and a real Internet provider available on the Plain Old Telephony System. It needs a system running Tails and another one (the gateway) running standard Debian. So this requires either two computers in the same LAN or runing Tails using virtualization.
Prepare the networking stack on the gateway:
# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # sysctl -w net.ipv4.ip_forward=1
In Tails, create
[Dialer Defaults] Baud = 115200 Init = ATZ Init2 = AT%R1 Phone = 192.168.1.2:6789 Username = test Password = test Carrier Check = off
Replace the IP address in
Phonewith the IP address of the other system.
In Tails, install the
In Tails, remove the default route to let room for the one provided by PPP:
# ip route del default
On the gateway run:
# pppd noauth local lock nodefaultroute persist debug nodetach 10.1.2.3:10.4.5.6 pty "nc -l 6789"
And fairly quickly (before
pppdtimes out), run on Tails:
$ sudo modemu -c 'ln -nsf %s /dev/modem ; wvdial -C .wvdial.conf'
Repeat the last two steps if the connection is broken at some point.
To ensure that PPPoE (broadband DSL) support is not broken by tweaks to PPP configuration files, here is a test procedure. This needs a standard Debian system (the gateway), and either a spare wired network card or using virtualization.
This reciepe uses
kvm, but could be easily adapted to other setups:
On the gateway, install the
On the gateway, create
debug noauth lcp-echo-interval 10 lcp-echo-failure 2 ms-dns 188.8.131.52 defaultroute noipdefault
Start KVM, adding those arguments:
-net nic,model=virtio -net tap,ifname=tails.
On the gateway, up this interface:
# ip link set tails up
On the gateway, start the PPPoE server:
# sudo pppoe-server -I tails -F -S test -m 1412
On Tails, you can now right-click the NetworkManager icon, and select Edit connections.... In the DSL tab, click Add. Service name should be set to
test. Other settings should not matter.
On Tails, left-click the NetworkManager icon and selection the newly created connection.
To debug, use
tcpdump, and look at
As WvDial (and thus GNOME PPP) is not integrated with NetworkManager in any
way, the hooks in
/etc/NetworkManager/dispatcher.d are not normally run upon
They will be after adding the following script as
#!/bin/sh run-parts --regex='^[a-z0-9-]+(\.sh)?$' /etc/NetworkManager/dispatcher.d --arg="$1" --arg="up"
But this will probably has the undesired effect of calling NetworkManager hooks twice when using PPPoE. This does not look like a real issue, but Tor is still restarted twice which is not nice.
Answer to this problem is fairly simple: when using WvDial with a good ol'
SPEED environment variable is defined when
runs. Let's simply use this to determine if we should run NetworkManager hooks
resolvconf, see Debian bug #258064.
- Clarify what groups must the user be part of to run wvdial /
gnome-ppp? We've been told on the
the answer was
dialout(which is already the case) and
dip(which is not).