kern/138407: [gre] gre(4) interface does not
come up after reboot
spawk at acm.poly.edu
Fri Sep 4 19:35:27 UTC 2009
The other end is a machine that can't be rebooted for testing as
frequently so I can't check how it behaves. Its tunnel is up and
running. It's 7.1, though, so I don't even think it was a problem back
then. Anyway, the state of the remote GRE tunnel does not appear to have
any bearing on the problem. I have sniffed traffic from the 128.x
machine on an intermediate router and it does not send anything out to
the remote machine when I get the "ping: sendto: Network is down"
message. Interestingly (or not?), running tcpdump on the GRE interface
that doesn't have the RUNNING flag adds the RUNNING flag to it, and then
Remko Lodder wrote:
> I have multiple tunnels that work correctly that way. (6). Do you need
> to issue 'ifconfig gre0 up' on the other side before it starts
> working? or do you need to force
> it on the 128.x machine? (please try both).
> On Sep 4, 2009, at 6:51 PM, Boris Kochergin wrote:
>> ifconfig_gre0="inet 10.0.0.1 10.0.0.2 netmask 255.255.255.0 tunnel
>> 184.108.40.206 220.127.116.11 up"
>> ...in rc.conf still leaves gre0 unusable after the system comes up.
>> There are workarounds, but this seems like something that should be
More information about the freebsd-bugs