interface FIB

2009-11-27 Thread Igor Sysoev
Currently only packets generated during encapsulation can use
interface's FIB stored during interface creation:

setfib 1 ifconfig gif0 ...
setfib 1 ifconfig tun0 ...

is it possible to implement this feature for any interface:

setfib 1 ifconfig vlan0 ...

or

ifconfig vlan0 setfib 1 ...


-- 
Igor Sysoev
http://sysoev.ru/en/
___
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: ipw driver on FreeBSD 8.0

2009-11-27 Thread Guido Falsi
On Thu, Nov 26, 2009 at 09:31:58PM -0500, Chris wrote:
> Hello,
> 
> Months ago there was some chatter about the ipw driver (For Centrino Intel
> 2100 wireless) being broken in 8.0 but that was when 8.0 was still under the
> CURRENT branch. Can anyone tell me if it has been fixed? I'm having a heck
> of a time trying to get it to work with the new VAP stuff. Here's the thread
> I'm referring to:
> 
> http://old.nabble.com/wpa_supplicant-can%27t-associate-with-WPA2-AP-td22687633.html
> 
> I'm seeing exactly the same problem shown in the thread when trying to
> associate with a regular WPA access point.
> 
> Any info would be appreciated!

That was me having thet problem on my old laptop. Still using that same 
laptop(I'd like to buy the latest hardware for my home setup, but at
this time of the year I like spending my money to go to sky!).

I have not tried ipw driver anymore, I have "fixed" the problem by using
ndis. Works like a charm, so if you have this problem I suggest you do
the same. I have not seen any major commit to the ipw driver, so my take
is it is as it was then. Please correct me if I'm wrong.

Some time ago I also had a look at the driver source, but it really
requires some major knowledge of wlan protocols and device interface,
and I lack both.

BTW, at present my biggest problem with WiFi is the one described in PR
kern/139117: [lagg] + wlan boot timing (EBUSY).

I encountered it while trying to configure a wlan(with WPA2) failsafe
lagg with the cabled ethernet.

Any news on that front?

Sorry if I could not be of any more help and thanks for any answers to
my query.

P.S. I'm also CCing freebsd-net@, since the problems seems to be
appropriate there.

-- 
Guido Falsi 
___
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: interface FIB

2009-11-27 Thread Julian Elischer

Igor Sysoev wrote:

Currently only packets generated during encapsulation can use
interface's FIB stored during interface creation:

setfib 1 ifconfig gif0 ...
setfib 1 ifconfig tun0 ...


not sure if tun actually does this (in fac tit shouldn't)

but for gre and gif (and stf) these are tunnelling other things into 
IP and thus it makes sense to be able to connect a routing table with 
the generated envelopes.




is it possible to implement this feature for any interface:

setfib 1 ifconfig vlan0 ...

or

ifconfig vlan0 setfib 1 ...


these two things would mean differnt things.
and one of them wouldn't mean anything.

setfig 1 ifconfig vlan0 woudl mean "what" exactly?
VLAN tagging is an L2/L1 operation and FIBS have no effect on this.

as for ifconfig vlan0 setfib 1, or  ifconfig em0 setfib 1

this will (shortly) mean that incoming packets through this interface 
will be default be connected with fib 1 so the any return packets 
(resets, icmp etc.) will use FIB1 to go back to the sender.


That patch is in the works.






___
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"