Re: System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP

Maybe another option to dhclient to have it poll the interface every 2-3 seconds to see if it has lost a link and if so, set the lease timer to be expired, and wait for it to come back and once it does, it will acquire a new address. ___ freebsd-net@freeb

Re: System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP

I work with an old version of AIX all day, there are no shortcuts :( On Thu, Jul 12, 2012 at 2:01 PM, Freddie Cash wrote: > On Thu, Jul 12, 2012 at 1:52 PM, Chris Benesch > wrote: > > Thats pretty standard for BSD and most Unixes. DHCP hands out leases > for a > > specifi

Re: System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP

Thats pretty standard for BSD and most Unixes. DHCP hands out leases for a specified period of time, so unless there is a reason to reset it, it wont. Windows does that, but it is designed more as a client / user facing OS whereas BSD is designed to run in the background silently serving you cont

Re: GIF tunnel doesnt like fragmented packets?

OMG I am so stupid gifconfig_gif0="192.168.0.2 64.62.134.130" << works gifconfig_gif0="198.168.0.2 64.62.134.130" << what it was before, doesnt work Sorry to waste everyones time ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman

GIF tunnel doesnt like fragmented packets?

So I'm trying to set up a tunnel with Hurricane Electric. Works great on OpenBSD BTW, took only a minute or two. So heres rc.conf ipv6_gateway_enable="YES" gif_interfaces="gif0" gifconfig_gif0="198.168.0.2 64.62.134.130" ipv6_network_interfaces="rl0 em0 gif0 lo0" ifconfig_gif0_ipv6="inet6 2001:4

Re: IPSec woes coming from OpenBSD to Free

http://copamadman.blogspot.com/2012/07/freebsd-90-how-to-set-up-ipsec-vpn.html ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: IPSec woes coming from OpenBSD to Free

Now that I have the rest of the system set up, I was going to write a blog to help out other users /admins. Some of the error messages have misleading symptoms to say the least LOL. Actually I still dont have IPV6 working, but I can address that in another thread.

Re: IPSec woes coming from OpenBSD to Free

I got it to work! There were some addresses in the SA file (ipsec.conf) that were wrong, ie 192.168 vs. 192.186 Helluva nice error message, I was looking for a literal sending error. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mail

Re: IPSec woes coming from OpenBSD to Free

Yeah the whole GIF interface thing seemed weird to me too. I'm in much the same situation I'm connecting to a Watchguard device, similar to the router I guess you are hooking to. I did get it to start trying to send, using the ping command. Never thought I had to kick start the data going to it

Re: IPSec woes coming from OpenBSD to Free

All things aside, I'm just trying to get it to work on FreeBSD thats all ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

IPSec woes coming from OpenBSD to Free

Hi all, Forgive me if I sound noobish, but I have been using OpenBSD for a long time and havent messed with FreeBSD in over 5 years. My situation overall is thus: I need to connect an internal network to my workplace over IPSec. It is currently working on OpenBSD, but after all the flack that c