Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
muc.lists.freebsd.stable
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion How to bind a route to a network adapter and not IP
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
sth...@nethelp.no  
View profile  
 More options Jun 17 2012, 5:10 pm
Newsgroups: mpc.lists.freebsd.stable, muc.lists.freebsd.stable
From: sth...@nethelp.no
Date: Sun, 17 Jun 2012 23:10:49 +0200 (CEST)
Local: Sun, Jun 17 2012 5:10 pm
Subject: Re: How to bind a route to a network adapter and not IP
Print | View thread | Show original | Report this message | Find messages by this author

> > I loose packets because I use a WLAN adapter. Sometimes the link is down for
> > various reasons, and then the routes start changing for manually created
> > routes, and I want to prevent that.

> well that is certainly not a reason for changing routes

> I have the feeling you are not explaining good enough what really is
> going on and it may help sending your configurations and an example of
> routes and IP addresses before and after this route change

Why is this so hard to understand? "Link down" leads to "static route
is deleted". This is standard FreeBSD behavior, and has been this way
for as long as I can remember (btw, I believe this behavior is from
the original BSD, not FreeBSD specific).

You can show this by having a static default route pointing to an
address on an Ethernet interface which has link. And then pulling the
TP cable from the Ethernet interface. Observe that the default route
is automatically removed.

My claim is that this behavior is reasonable *but* I'd like the route
restored when the link comes back up again. This is standard Cisco /
Juniper behavior - but *not* standard FreeBSD behavior.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
_______________________________________________
freebsd-sta...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google