Re: demand dialing



On Sat, 04 Aug 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <k3afo4-0du.ln1@xxxxxxxxxxxxxxxxx>, Hactar wrote:

Moe Trin <ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Why does it have to be a pointy-clicky?

I guess it doesn't, if the end user never has to touch it. I just had
this idealized view of this distro as "for newbies, so everything's done
in a GUI". I guess not...

Actually, even with a GUI, most of the "system" stuff, such as your boot
scripts that wake the system up, are exactly that - scripts. A GUI is a
needless complication at that point.

This is a one-time shot, and needs only to add a line to the boot scripts.

I don't see a file /etc/.../*local* in Ubuntu 5.10; is there one (or a
work-alike) in 7.04?

Standards are wonderful thing;
everyone should have one of his very own

Are you using 'upstart' or the more traditional SysVinit?

How exactly are you trying to do this?

% ping foo.com
Host unreachable. <-- instant

OK - if you looked at your routing table you would have seen no existing
default route, I suspect you hadn't restarted pppd into the demand mode,
which creates a route using (checks man page... checks README.... checks
Changes-2.3) 10.112.112.112. (Just a comment, I'm no longer using demand
mode, as the cable and phone companies finally pulled their fingers out
and got wide-band available where I live. If I make a mistake here,
hopefully the other responder [Clifford Kite] will correct me.)

Doesn't have to be root, since pppd is SUID root, right? I mean, I ran
pppd as me (no sudo) and it worked.

pppd is not SUID by default - that's a distribution "improvement". The
reason I was specifying getting it running as root (the default mode) is
that normally trying to do things as a user runs into problems. The
script will be run at boot as root, so the extra hoops aren't needed.

The first line is used to tell a 2.2.x or later kernel that the system
will have dynamic IP addresses, while the second line runs the dialin
script.

This is an example of Linux being user-hostile. Not that I'm
complaining...

This is actually a standard thing in *nix - which was designed from
scratch for a multi-user mode. This means you don't want the users
effecting _other_ users. That's why bringing the networking up/down,
or mounting/unmounting disks and the like is not a "user" task. Face
it, most users don't think about other users who could be using a
resource that they're finished with.

Is there a way to disregard _all_ packets that aren't a reply?
Except I'll need a way in to fix things...

Ubuntu... I'm pretty sure it has the "standard" LBL version of tcpdump,
and yes you can set things that way. Top of the head, I'd suggest
something like

active-filter port 135 and port 139 and port 445

which if memory serves will cause packets in both directions to those
ports to be ignored. Hopefully, Clifford will notice this and make
any corrections, as he did a lot more work with the filters than I
had to.

As for needing a way to fix things, I'm assuming you're meaning coming
in over the Internet (SSH), which the above active-filter line would
have no effect upon. There will be plenty of other ways things can go
boom, but this isn't one of them.

Might as well combine the followup. In your other reply, you
wrote:"

Hactar <ebenZEROONE@xxxxxxxxxxx> wrote:

I don't see a file /etc/.../*local* in Ubuntu 5.10; is there one
(or a work-alike) in 7.04?

There is an /etc/rc.local, which is called from /etc/init.d/rc.local,
which is linked to /etc/rc?.d/S99rc.local .

That sounds good

But I'll try again and see if my futzing around changed things.

Does now. Probably copying the lines pppd puts in /etc/resolv.conf
and adding them to it when the link _isn't_ up did it.

Above

echo -n 1 > /proc/sys/net/ipv4/ip_dynaddr

Just for kicks, what happens if you don't have the first line? The
link will come up, but may not work?

That's my understanding, but as mentioned I haven't used this in a
while. You'll have to remember that this (ANU) ppp daemon is written
for more than just Linux, so the Linux specific stuff isn't as well
covered. But look at the paragraph in the man page before the section
labeled "MULTILINK" (roughly line 1450 to 1467 depending on the version
of pppd you are using, and assuming an 80 character wide screen).

Old guy
.



Relevant Pages

  • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
    ... thus the creation of the port on the node. ... Download the Windows Server 2003 resource kit and add prnadmin.dll to the ... Do you actually think I would post these scripts if it didnt work? ... In your response include the commands you used. ...
    (microsoft.public.windows.server.clustering)
  • Re: firewall script in /etc/ppp/ip-up.d
    ... > after the ppp0 interface comes up. ... manpage on pppd(8) and look for the section on ip-up. ... Your scripts should be able to use these values directly instead of trying to ...
    (comp.os.linux.misc)
  • Linux ppp + MegaPOP dialup change = mrru related LCP timeout
    ... until last month when my Linux box could no ... longer establish a ppp connection. ... pppd version 2.4.1, upgrading to 2.4.3 did not help. ... sending it implements the PPP Multilink Protocol. ...
    (comp.os.linux.networking)
  • PPPD Connect Using Broadband Connection (problem)
    ... I have to use SUSE linux 7.3 because im using linux for Kylix ... My situation is that I am trying to connect my home linux system to a remote ... The remote office is using Microsoft RAS server, hence I need pppd ... acknowledging the connection parameters I was using were correct. ...
    (comp.os.linux.networking)
  • Re: How to set up dial-up on debian after a wrong pppoe config
    ... I used pppd on RH7.2 also on another machine. ... with linux it is always something over my experience. ... seem like I have always have to upgrade to get what I am looking for, ... that addresses exactly how things work so you can remedy problems is ...
    (comp.os.linux.networking)