Sounds like you are narrowing down the culprit(s). Also note that it could
possibly be a timing issue related to the order things start up. If
the NATD
is attempting to start before the interface has come up it will die.
/etc/rc.d/natd has no REQUIRE section, so it is indeed possible for it
to
On 9. 11. 2009 1:27, umage wrote:
When the connection goes down and comes back up it will take 5 minutes
before my FreeBSD gateway box checks the lease and decides if a
renewal is
in order. This is automatic. If I am sitting in front of my computer
and I
want to speed this up I issue
umage wrote:
[snip]
In my case the router does get the renewed ip, as I described earlier.
However, even after waiting 8+ hours, the system will not recover from
the outage properly (reason unknown). That's what this thread is all
about.
When I started the system today, I found that again it
When the connection goes down and comes back up it will take 5 minutes
before my FreeBSD gateway box checks the lease and decides if a
renewal is
in order. This is automatic. If I am sitting in front of my computer
and I
want to speed this up I issue /etc/rc.d/netif restart on the gateway
Have you tried restarting routing?
/etc/rc.d/routing restart
I have found the same symptoms with other outages and not performing the
above.
I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart.
Wtih using these commands, I have found this to be successful in restoring
network
On 7. 11. 2009 19:07, Jason wrote:
Have you tried restarting routing?
/etc/rc.d/routing restart
I have found the same symptoms with other outages and not performing the
above.
I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart.
Wtih using these commands, I have found this to
umage wrote:
On 7. 11. 2009 19:07, Jason wrote:
Have you tried restarting routing?
/etc/rc.d/routing restart
I have found the same symptoms with other outages and not performing the
above.
I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart.
[snip]
Thank you for the
