Be ERECT in less than 15 mins PRlCE: $ 2 / use visit our website --> goldslive.net - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello ! A basic question : There's a way to start a PPP connection like an ADSL connection always in the same interface (eg. ppp0 ) ? I have two adsl Links and I would like to start adsl1 always in ppp0 and the adsl2 always in the ppp1, otherwise when I reboot and the adsl1 fail to connect, the adsl2 start in ppp0 and my firewall rules screw up ! Regards. - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 6 Dec 2005, Cleiton Reis wrote: |Hello ! | | A basic question : | | There's a way to start a PPP connection like an ADSL connection |always in the same | interface (eg. ppp0 ) ? | | I have two adsl Links and I would like to start adsl1 always in ppp0 |and the adsl2 always in the ppp1, otherwise when I reboot and the |adsl1 fail to connect, the adsl2 start in ppp0 and my |firewall rules screw up ! Man pppd, see whether the option "unit <num>" is what you want. --- Clifford Kite - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Clifford Kite writes: > | I have two adsl Links and I would like to start adsl1 always in ppp0 > |and the adsl2 always in the ppp1, otherwise when I reboot and the > |adsl1 fail to connect, the adsl2 start in ppp0 and my > |firewall rules screw up ! > > Man pppd, see whether the option "unit <num>" is what you want. ... or use the /etc/ppp/ip-up script interface to rewrite the firewall rules on the fly. (Agreed; there needs to be a better way to deal with this issue.) -- -- James Carlson 42.703N 71.076W <carlsonj <at> workingcode.com> - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 6 Dec 2005, James Carlson wrote: > Clifford Kite writes: >> | I have two adsl Links and I would like to start adsl1 always in ppp0 >> |and the adsl2 always in the ppp1, otherwise when I reboot and the >> |adsl1 fail to connect, the adsl2 start in ppp0 and my >> |firewall rules screw up ! >> >> Man pppd, see whether the option "unit <num>" is what you want. > > ... or use the /etc/ppp/ip-up script interface to rewrite the firewall > rules on the fly. > > (Agreed; there needs to be a better way to deal with this issue.) > One of the real problems with linux appears to be the difficulty of associating a unit with a physical device. Thus with ethernet, it depends on which hardware device the system just happens to look at first which gets called eth0. The aliases established in /etc/modprobe.conf seem to be just ignored. Similarly with ppp, and everything else. This really needs a unified way of dealing with it. the unit option in pppd helps, but if for some reason that unit is unavailable, ppp simply grabs whatever anyway. To have to set up a script which determines which units are which and rewrites all references to the unit number is not only a kludge but is also extremely prone to bugs. That is not the way to go. -(Continue reading)
Bill Unruh writes: > One of the real problems with linux appears to be the difficulty of > associating a unit with a physical device. Thus with ethernet, it depends > on which hardware device the system just happens to look at first which > gets called eth0. OK, but it's also the case that pppd is *more* than just Linux. In fact, it predates Linux by quite a bit. So, I'd argue that the solution needs to work for other systems (BSD, Solaris) as well as Linux. > The aliases established in /etc/modprobe.conf seem to be > just ignored. Similarly with ppp, and everything else. This really > needs a unified way of dealing with it. the unit option in pppd helps, but > if for some reason that unit is unavailable, ppp simply grabs whatever > anyway. > > To have to set up a script which determines which units are which and > rewrites all references to the unit number is not only a kludge but is also > extremely prone to bugs. That is not the way to go. I agree that's kludgy. One of the bad parts of it is that the interface is established and enabled *before* the filters get applied, and that's almost certainly not what anyone concerned with security wants. But even if we could somehow nail down the meaning of "ppp0" and "ppp1" and so on, I think we'd be no better off than we are today for pppd. The problem I see is that a system with a number of links and a large number of peers (not just this simple configuration with two(Continue reading)
All recent versions of pppd have a filedescriptor leak -
pppd leaks a filedescriptor to the (serial/pty/whatever)
underlying device on each "redial".
The global `devfd' variable that holds this filedescriptor
is initialized to -1 at the start of the main loop, before
each redial.
The filedescriptor is opened in auth.c:link_required(),
calling the_channel->connect() routine.
Later, again in auth.c, in link_terminated() routine,
there's the following code:
/*
* Run disconnector script, if requested.
* XXX we may not be able to do this if the line has hung up!
*/
if (devfd >= 0 && the_channel->disconnect) {
the_channel->disconnect();
devfd = -1;
}
For a tty device, there's a tty.c:disconnect_tty() used as
the_channel->disconnect; but it does not *close* any files.
For that, there's the_channel->close field. Which is only
used in safe_fork() routine when running a child process...
Again, connect_tty() is used (from the_channel->connect())
to start new connection cycle, and that routine starts with
(Continue reading)
Be ERECT in less than 15 mins PRlCE: $ 2 / use visit our website --> juicesign.net - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Be ERECT in less than 15 mins PRlCE: $ 2 / use visit our website --> worldamoure.com - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
All can anybody telll me where to find some more information on how to setup a pppoe-server? Currently I'm using suse linux 9.3 as my server to dial in via a windows xp client (yeah I know). It hasn't been successfull for almost 2 weeks now. When I check with ethereal is see that the session gets confirmed, but it hangs at "PPP LC Configuration request", it seems that the server is not responding to this request. How can I solve this. My server has 2 networks cards: - eth0: 10.0.0.1 - eth1: 50.0.0.1 I start the pppoe-server with following command: $pppoe -C myacname -S myservice -I eth1 -L 50.0.0.1 -R 50.0.0.100 pppoe-server-options are set to: debug dump require-pap login lcp-echo-interval 10 lcp-echo-failure 2 I can not figure it out what could be wrong.(Continue reading)
RSS Feed5 | |
|---|---|
9 | |
12 | |
2 | |
6 | |
7 | |
4 | |
8 | |
1 | |
2 | |
24 | |
13 | |
44 | |
7 | |
10 | |
25 | |
18 | |
11 | |
12 | |
63 | |
34 | |
40 | |
36 | |
34 | |
23 | |
7 | |
21 | |
73 | |
25 | |
2 | |
13 | |
3 | |
21 | |
5 | |
6 | |
21 | |
4 | |
17 | |
10 | |
21 | |
8 | |
14 | |
43 | |
29 | |
66 | |
51 | |
16 | |
8 | |
16 | |
24 | |
9 | |
19 | |
7 | |
47 | |
14 | |
3 | |
6 | |
7 | |
5 | |
13 | |
3 | |
12 | |
31 | |
23 | |
21 | |
41 | |
8 | |
10 | |
18 | |
54 | |
27 | |
14 | |
19 | |
25 | |
15 | |
17 | |
36 | |
20 | |
7 | |
19 | |
35 | |
43 | |
36 | |
15 | |
43 | |
65 | |
44 | |
10 | |
36 | |
54 | |
19 | |
62 | |
36 | |
44 | |
31 | |
45 | |
42 | |
29 | |
26 | |
32 | |
63 | |
32 | |
42 | |
41 | |
34 | |
44 | |
54 | |
45 | |
158 | |
64 | |
61 | |
162 | |
74 | |
26 | |
54 | |
39 |
