Hello. I have had 3 network outages this week, and everytime it
happened, I found that my freebsd8rc1 machine/router was unable to
communicate over the WAN interface even after the outages ended. A
reboot helps, but that's not an acceptable solution.
The symptoms are very weird: even though dh
s, I have found this to be successful in
restoring
network interfaces communication, without having to reboot.
Hope this helps.
On Sat, Nov 07, 2009 at 03:05:40PM +0100, umage thus spake:
Hello. I have had 3 network outages this week, and everytime it
happened, I found that my freebsd8rc1 machi
> 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 gatewa
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 thi
>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
Hi, I'm an ipfw user that finally got the opportunity to set up NAT on
an interface with a public IP. I was doing some multi-homing experiments
using ipfw fwd combined with outbound ipfw nat - and since I needed to
run both, and both immediately ended ipfw ruleset execution, I had to
turn off net.i
Some points:
1) I did use the handbook as reference, and my ruleset mimics the layout
used there.
2) Handbook uses divert natd, which I used until I switched to the
kernel nat approach.
3) I did not find any concrete examples of ipfw nat rule usage, so I'm
using them the old natd way.
I did s
I performed a kernel+world update of my freebsd router, RELENG_8 branch,
apparently from the version 6 months ago to current. I use ipfw and a
shell script that gets loaded at startup. I noticed after rebooting that
ipfw did not load two rules, both of type "divert natd". However, if I
run the scri
Hi there, a few months ago I inquired about an issue where using
ipfw+natd worked on 8.0 but produced errors in 8.1. After searching the
bugs database, I found multiple reports about it -
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/148137 and
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/148
