-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/06/14 08:32, Sam Varshavchik wrote:
Ed Greshko writes:
> On 07/06/14 07:28, Sam Varshavchik wrote:
> > Ed Greshko writes:
> >
> >> > The server with dhcp, httpd, named, and privoxy does not have
NetworkManager installed. Both the WAN and the LAN ports are configured as static IPs.
> >>
> >> You may want to try NetworkManager and wait-online. WAN links can take time
to become active.
> >
> > NetworkManager does nothing for me, except to suck in another 16 packages it
depends on, that I don't need. The WAN link is a statically-routed IP traffic.
It's up as soon as the network interface brings up the link.
>
> Now that you re-read what you wrote I think misunderstood WAN to be a wireless
connection which would require a time to bring up the link with the AP. If you mean WAN
in the sense of a Wide Area Network, I wonder if there is a need for PPP negotiation.
I didn't say PPP either. My WAN is not some screwed up pseudo-Internet connection
that uses ppp over some godforsaken transport.
Of course I didn't say you said PPP. Some areas of the world still use PPP and it
works fine and dandy. I didn't want to assume anything since I don't know where
you're located.
Hilarity ensues.
Any plans to bugzilla your issue? It should be fun to follow.
- --
If you can't laugh at yourself, others will gladly oblige.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlO4m30ACgkQ4JnKjVbCBvr1IQCaA0zChyKCoBOVRs3edg7vx8J9
q9IAnR9cCazWCNvn2ArulOj1RoHKQx8j
=qHAg
-----END PGP SIGNATURE-----