Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
It just occurred to me that you probably don't have static IP address assignments for your various networks. This might be a problem. The latest versions of pppd permit, if I read the documentation correctly, dynamic switching of IP addresses once the interface comes up. I've used this for the remote IP address, and it works, but I've never tried using it for the local IP address. If you have multiple demand daemons running, there's also the issue of what the default route should be. In my setup, the default route assignment is established by pppd, but I think it gets done when pppd starts up. It correctly switches to the current remote IP address after a connection is made, but without research I don't know what will happen with two pppd's running. The pppd program has a plethora of options, though, and hooks to execute scripts when an interface connects/disconnects. You'll have to experiment a bit, it now appears. - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |