Network Card
Hi I have two lan cards em0 and rl0 on my system. is there a way to know on freebsd which is onboard or pci card ?. The issue is my system is located at remote location. Thanks and Regards Kaushal. ___ 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: Network Card
On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote: > Dear Kaushal, > > I have two lan cards em0 and rl0 on my system. is there a way to know on >> freebsd which is onboard or pci card ?. The issue is my system is located >> at >> remote location. >> > > perhaps lspci -v helps. > > or something like dmidecode (at linux, does not know the freebsd name), > then you can readout the mb-name. > > Kind regards, >Ingo Flaschberger > Hi Ingo I did pciconf -lv and ran dmidecode. I could not figure it out which one was onboard or pci ? Do you want me to paste the output of that commands Please suggest Thanks and Regards Kaushal ___ 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: Network Card
Dear Kaushal, I have two lan cards em0 and rl0 on my system. is there a way to know on freebsd which is onboard or pci card ?. The issue is my system is located at remote location. perhaps lspci -v helps. or something like dmidecode (at linux, does not know the freebsd name), then you can readout the mb-name. Kind regards, Ingo Flaschberger ___ 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: Network Card
On Tue, Apr 21, 2009 at 5:30 PM, ovi freebsd wrote: > Kaushal Shriyan wrote: > >> On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote: >> >> >> >>> Dear Kaushal, >>> >>> I have two lan cards em0 and rl0 on my system. is there a way to know on >>> >>> freebsd which is onboard or pci card ?. The issue is my system is located at remote location. >>> perhaps lspci -v helps. >>> >>> or something like dmidecode (at linux, does not know the freebsd name), >>> then you can readout the mb-name. >>> >>> Kind regards, >>> Ingo Flaschberger >>> >>> >>> >> >> Hi Ingo >> >> I did pciconf -lv and ran dmidecode. I could not figure it out which one >> was >> onboard or pci ? >> Do you want me to paste the output of that commands >> >> Please suggest >> >> Thanks and Regards >> >> Kaushal >> ___ >> 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" >> >> >> > It is possible to find you the manufacturer of the motherboard? If yes, it > would be easy to know which is onboard and which is on PCI since are > different network chipsets. > > Hi ovi so there is no such command line utility to get to know about that information on Free BSD ? Thanks and Regards Kaushal ___ 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: Network Card
Kaushal Shriyan wrote: On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote: Dear Kaushal, I have two lan cards em0 and rl0 on my system. is there a way to know on freebsd which is onboard or pci card ?. The issue is my system is located at remote location. perhaps lspci -v helps. or something like dmidecode (at linux, does not know the freebsd name), then you can readout the mb-name. Kind regards, Ingo Flaschberger Hi Ingo I did pciconf -lv and ran dmidecode. I could not figure it out which one was onboard or pci ? Do you want me to paste the output of that commands Please suggest Thanks and Regards Kaushal ___ 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" It is possible to find you the manufacturer of the motherboard? If yes, it would be easy to know which is onboard and which is on PCI since are different network chipsets. ___ 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: Network Card
Dear Kaushal, I did pciconf -lv and ran dmidecode. I could not figure it out which one was onboard or pci ? Do you want me to paste the output of that commands yes, please send me the output. Kind regards, Ingo Flaschberger ___ 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: Network Card
ovi freebsd wrote: Kaushal Shriyan wrote: On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote: Dear Kaushal, I have two lan cards em0 and rl0 on my system. is there a way to know on freebsd which is onboard or pci card ?. The issue is my system is located at remote location. perhaps lspci -v helps. or something like dmidecode (at linux, does not know the freebsd name), then you can readout the mb-name. Kind regards, Ingo Flaschberger Hi Ingo I did pciconf -lv and ran dmidecode. I could not figure it out which one was onboard or pci ? Do you want me to paste the output of that commands Please suggest Thanks and Regards Kaushal ___ 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" It is possible to find you the manufacturer of the motherboard? If yes, it would be easy to know which is onboard and which is on PCI since are different network chipsets. ___ 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" As an extension of this, what CPU is in the machine? I have never seen an AMD motherboard come with an onboard Intel controller. That is not to say that one doesn't exist, but that it is very rare. -Boris ___ 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: Network Card
--- On Tue, 4/21/09, Boris Kochergin wrote: > From: Boris Kochergin > Subject: Re: Network Card > To: "ovi freebsd" > Cc: freebsd-net@freebsd.org, "Kaushal Shriyan" , > "Ingo Flaschberger" > Date: Tuesday, April 21, 2009, 9:36 AM > ovi freebsd wrote: > > Kaushal Shriyan wrote: > >> On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger > wrote: > >> > >> > >>> Dear Kaushal, > >>> > >>> I have two lan cards em0 and rl0 on my > system. is there a way to know on > >>> > freebsd which is onboard or pci card ?. > The issue is my system is located > at > remote location. > > > >>> perhaps lspci -v helps. > >>> > >>> or something like dmidecode (at linux, does > not know the freebsd name), > >>> then you can readout the mb-name. > >>> > >>> Kind regards, > >>>Ingo Flaschberger > >>> > >>> > >> > >> Hi Ingo > >> > >> I did pciconf -lv and ran dmidecode. I could not > figure it out which one was > >> onboard or pci ? > >> Do you want me to paste the output of that > commands > >> > >> Please suggest > >> > >> Thanks and Regards > >> > >> Kaushal > >> ___ > >> 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" > >> > >> > > It is possible to find you the manufacturer of the > motherboard? If yes, it would be easy to know which is > onboard and which is on PCI since are different network > chipsets. > > > > ___ > > 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" > As an extension of this, what CPU is in the machine? I have > never seen an AMD motherboard come with an onboard Intel > controller. That is not to say that one doesn't exist, > but that it is very rare. > > -Boris On all of the MBs that I have, the slot NIC appears before the onboard ports in the pciconf -l listing. Its certainly not for sure. Barney ___ 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: Network Card
On Tue, 21 Apr 2009 16:37:29 +0530, Kaushal Shriyan wrote: KS> I have two lan cards em0 and rl0 on my system. is there a way to know on KS> freebsd which is onboard or pci card ?. The issue is my system is located at KS> remote location. KS> install from ports dmidecode, it can show mainboard name. Than read specification for this mainboard. -- Anton Yuzhaninov ___ 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"
CARP as a module; followup thoughts
Hello,
I've written a patch (against 8.0-CURRENT as of r191369) which makes
it possible to build, load, run, & unload CARP as a module, using the
GENERIC kernel. It can be obtained from:
http://firepipe.net/patches/carp-as-module-20090421.diff
Having written this patch, I have some thoughts. First of all, this
patch follows the same pattern of function pointers used by if_lagg,
if_vlan, ng_ether, bpf, and if_bridge. While it works, this approach
(along with that used by the other interfaces) is a hackish way to
implement the interfaces as kernel modules.
It appears that each one needs to have its hooks inserted at a
specific point in the packet processing. So it seems to me that a
better way to do this would be to implement a generic network protocol
interface and have everything that processes packets register its
hooks with that interface. Which if_* seems to do to an extent, but
not enough to meet the requirements of the above-mentioned network
protocols.
More to the point, netinet/in_proto.c & netinet6/in6_proto.c use
hardcoded protocol definition structures. Until this diff introduced
in{6,}_proto_{un,}register(), there was no way to define hooks for any
other protocols without hacking these files or compiling with
different options (like DEV_CARP).
I envision a struct ifnet_hooks array that includes hooks that can be
registered by any protocol for packet processing at any point,
including: pre-input, input, post-input, pre-output, output,
post-output, link state change, route, etc. Then each struct ifnet
would contain a list of these pointers, to be configured in a given
order depending on the administrator's needs. The interface would run
through the list for a given stage and run the protocol specific
function pointer to perform its processing at that stage.
Of course, that is probably a much too simplistic idea (there are a
lot of special cases it seems). And the reality is, there is already
something in FreeBSD that makes arbitrary packet processing hook order
possible - netgraph. So why is it FreeBSD allows these modules when
there are netgraph equivalents for all of them (currently, except
CARP)? More to the point, why isn't netgraph used for most (if not
all) packet processing?
Has anyone tried to build a kernel without INET? It's not pretty, and
demonstrates the biases the stack has towards IPv4 vs. other protocols
like IPv6. In other words, there's lots of code that looks like this:
#ifdef INET6
#endif
It would be nice if the stack didn't assume any particular protocol
base; making all protocols optional (except as explicitly defined by
direct dependency) seems a worthy goal.
I think it also might be useful to third party developers if they
didn't have to modify anything in the base kernel to insert a new
protocol in the stack.
I'm sure most of this sounds like rambling from a crazed lunatic or
something, but I'm also sure most who understand my patch agree that
it isn't the nicest of ways to make it possible to load carp (or any
other protocol) as a module.
Regards,
--Will.
___
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: kern/133902: [tun] Killing tun0 iface ssh tunnel causes Panic String: page fault
Old Synopsis: Killing tun0 iface ssh tunnel causes Panic String: page fault New Synopsis: [tun] Killing tun0 iface ssh tunnel causes Panic String: page fault Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 22 06:51:05 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=133902 ___ 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"
