thanks but no - pppd with the 'demand' option sets up a virtual interface that is 'up'
But you can easily see that, because the configured IP adress is a private or invalid (depends on pppd and the configuration, on my gateway it'a a 192.168.) one, while it surely isn't once a connection is established. So checking the ifconfig output, conviniently done using Net::Ifconfig::Wrapper, check the ip-adress for validity/privateness and your done.
regards,
tomte
Hlade's Law:
If you have a difficult task, give it to a lazy person --
they will find an easier way to do it.
| [reply] |
huh? really? i assigned private IPs to those virtual interfaces anyhow, so i wouldn't have noticed...but wouldn't assigning a private IP (with a route to it) to the virtual interface not destroy the whol reason for actually having that virtual interface?
i mean - how would the packets that are supposed to go out on that link know how to go that link?
thanks, though - i'll look for some documentaion for that...
| [reply] |