Re: igb issues

2012-12-14 Thread Daniel Braniss 
Hi Jack,
> --20cf30780b4661e6f904d0bedadd
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Try putting the driver from 9.1 back onto 8.3 and see if you still
> see a problem. That will indicate if its in the driver or the stack/OS.
> If you have any question about doing this send me email.
> 
> Is NFS using UDP or TCP?
> 
> Regards,

short version: All is OK, sorry for the noise.

long version:
after sending off the message, I found a nic that I could plug into the box,
did that, and before switching to use the em card, I tried another run with
the igb, and surprice! all is ok, I will now have to go through logs to see 
what
happend, but my guess is that the switch this host was connected was under 
heavy
load, it has a cluster of HPCs.

thanks, have a nice weekend and season greatings!

danny
> 
> Jack
> 
> 
> On Thu, Dec 13, 2012 at 8:05 AM, Daniel Braniss  wrote:
> 
> > hi,
> > I'm trying out a 4way Dell PowerEdge C5125/AMD server with onboard
> > Intel(R) PRO/1000 Network Connection version - 2.3.1
> >
> > when running FreeBsd 8.3 (from sometime around Nov 2) all is ok.
> > with latest (at least Fridays') 9.1-PRERELEASE it's getting 'constipated'.
> >
> > It seems that NFS writes slowdown to a halt, and so I'm getting 'not
> > responding' errors.
> >
> > I am using the same kernel on different hosts with out any problems,
> > even with Intel(R) PRO/1000 Network Connection version - 2.3.4
> >
> > Any ideas?
> >
> > danny
> >
> >
> > ___
> > 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"
> >
> 
> --20cf30780b4661e6f904d0bedadd
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
> Try putting the driver from 9.1 back onto 8.3 and see if you stillsee =
> a problem. That will indicate if its in the driver or the stack/OS. iv>If you have any question about doing this send me email.
> Is NFS using UDP or TCP?Regards,=
> JackOn Th=
> u, Dec 13, 2012 at 8:05 AM, Daniel Braniss < "mailto:da...@cs.huji.ac.il"; target=3D"_blank">da...@cs.huji.ac.il><=
> /span> wrote:
>  x #ccc solid;padding-left:1ex">hi,
> I'm trying out a 4way Dell PowerEdge C5125/AMD server with onboard
> =A0 =A0 =A0 =A0 Intel(R) PRO/1000 Network Connection version - 2.3.1
> 
> when running FreeBsd 8.3 (from sometime around Nov 2) all is ok.
> with latest (at least Fridays') 9.1-PRERELEASE it's getting 'co=
> nstipated'.
> 
> It seems that NFS writes slowdown to a halt, and so I'm getting 'no=
> t
> responding' errors.
> 
> I am using the same kernel on different hosts with out any problems,
> even with Intel(R) PRO/1000 Network Connection version - 2.3.4
> 
> Any ideas?
> 
> danny
> 
> 
> ___
> mailto:freebsd-net@freebsd.org";>freebsd-net@freebsd.org mail=
> ing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net"; target=3D=
> "_blank">http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "mailto:freebsd-net-unsubs=
> cr...@freebsd.org">freebsd-net-unsubscr...@freebsd.org"
> 
> 
> --20cf30780b4661e6f904d0bedadd--


___
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: ng_ether naming

2012-12-14 Thread Andriy Gapon 
on 13/12/2012 20:57 Ermal Luçi said the following:
> 
> 
> 
> On Thu, Dec 13, 2012 at 5:25 PM, Andriy Gapon  > wrote:
> 
> on 13/12/2012 14:08 Alexander V. Chernikov said the following:
> > On 13.12.2012 15:46, Andriy Gapon wrote:
> >>
> >> ng_ether uses if_xname for naming its nodes.
> >> This could be troublesome for mapping interface names to their ng_ether
> companions
> >> in the face of interface renaming capability.  Especially given that 
> interface
> >> renaming and ng_ether _module_ loading may happen in an arbitrary 
> order.
> >>
> >> I am not sure how to solve this best.
> >>
> >> One possibility is to use if_dname+if_dunit combination for ng_ether
> naming.  This
> >> should be stable and available for querying.  This behavior should 
> also be
> >> backward compatible with ng_ether being compiled into kernel
> (if_dname+if_dunit ==
> >> if_xname before any renaming could occur).
> >>
> >> Another possibility is to do ng_ether renaming when its interface is 
> renamed.
> >> This seems nicer but appears to be more work and more intrusive, 
> because
> >> interfaces would have to know about their ng_ether nodes.
> >
> > Not exactly. You can register for ifnet_departure_event and 
> ifnet_arrival_event.
> >
> > Interface renaming is done via sending departure event with old name 
> and arrvial
> > event with new one.
> 
> Good to know.  Thank you!
> 
> 
> So which approach sounds better?
> Or maybe there is even a better one?
> 
> 
> The best is interface event handling.
> Just recopy the new name from if_xname and should be done.

There is one problem with the current code which would automatically apply to 
the
interface renaming handling.
ng_ether does not do any validation or "normalization" of if_xname and the name
can contain symbols which are prohibited in a netgraph name, such as '.' for 
example.
ng_name_node would fail and warning would be logged but a node would stay 
unnamed.
I am a bit reluctant to write "netgraph name escaping" code myself.  Perhaps it
already exists in some place?

-- 
Andriy Gapon
___
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: ng_ether naming

2012-12-14 Thread Nikolay Denev 
On Dec 14, 2012, at 7:02 PM, Andriy Gapon  wrote:

> on 13/12/2012 20:57 Ermal Luçi said the following:
>> 
>> 
>> 
>> On Thu, Dec 13, 2012 at 5:25 PM, Andriy Gapon > > wrote:
>> 
>>on 13/12/2012 14:08 Alexander V. Chernikov said the following:
>>> On 13.12.2012 15:46, Andriy Gapon wrote:
 
 ng_ether uses if_xname for naming its nodes.
 This could be troublesome for mapping interface names to their ng_ether
>>companions
 in the face of interface renaming capability.  Especially given that 
 interface
 renaming and ng_ether _module_ loading may happen in an arbitrary order.
 
 I am not sure how to solve this best.
 
 One possibility is to use if_dname+if_dunit combination for ng_ether
>>naming.  This
 should be stable and available for querying.  This behavior should also be
 backward compatible with ng_ether being compiled into kernel
>>(if_dname+if_dunit ==
 if_xname before any renaming could occur).
 
 Another possibility is to do ng_ether renaming when its interface is 
 renamed.
 This seems nicer but appears to be more work and more intrusive, because
 interfaces would have to know about their ng_ether nodes.
>>> 
>>> Not exactly. You can register for ifnet_departure_event and 
>>> ifnet_arrival_event.
>>> 
>>> Interface renaming is done via sending departure event with old name and 
>>> arrvial
>>> event with new one.
>> 
>>Good to know.  Thank you!
>> 
>> 
>>So which approach sounds better?
>>Or maybe there is even a better one?
>> 
>> 
>> The best is interface event handling.
>> Just recopy the new name from if_xname and should be done.
> 
> There is one problem with the current code which would automatically apply to 
> the
> interface renaming handling.
> ng_ether does not do any validation or "normalization" of if_xname and the 
> name
> can contain symbols which are prohibited in a netgraph name, such as '.' for 
> example.
> ng_name_node would fail and warning would be logged but a node would stay 
> unnamed.
> I am a bit reluctant to write "netgraph name escaping" code myself.  Perhaps 
> it
> already exists in some place?
> 
> -- 
> Andriy Gapon
> ___
> 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"


Hi,

Some time ago I had similar issue : 
http://lists.freebsd.org/pipermail/freebsd-net/2011-February/027982.html

The patch is also in : kern/154850

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

MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
Greetings,
 I attempted another BSD install on another piece of hardware the
other day. I'm evaluating a different ISP, and the gateway/router/modem
they provided, has 1 ether, which I currently use on my server, and 1
USB(3) port that I had intended to use with the new install. Problem I
ran into, was that BSD generates random (fake) MAC(3) addresses, when
utilizing the CDCE(4)/ue0. This worked just fine during the install.
But the modem "held" the MAC(3) generated during the install, and I
now have no idea how to tell BSD to use that MAC(3) when negotiating
with the modem. I had absolutely no difficulty assigning the MAC(3)
address when spinning up several "live" Linux distro(s) -- they provide
the following:
su
password: ***
ifconfig eth1 down
ifconfig eth0 hw ether ##:##:##:##:##:##
dhclient eth0
blah, blah, blah

And I'm connected.
Couldn't manage that with BSD. What must I do? Is it even possible?
If so, can it be assigned for use on a permanent basis?

Thank you for all your time, and consideration.

--Chris

___
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: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
> Greetings,
>  I attempted another BSD install on another piece of hardware the
> other day. I'm evaluating a different ISP, and the gateway/router/modem
> they provided, has 1 ether, which I currently use on my server, and 1
> USB(3) port that I had intended to use with the new install. Problem I
> ran into, was that BSD generates random (fake) MAC(3) addresses, when
> utilizing the CDCE(4)/ue0. This worked just fine during the install.
> But the modem "held" the MAC(3) generated during the install, and I
> now have no idea how to tell BSD to use that MAC(3) when negotiating
> with the modem. I had absolutely no difficulty assigning the MAC(3)
> address when spinning up several "live" Linux distro(s) -- they provide
> the following:
> su
> password: ***
> ifconfig eth1 down
> ifconfig eth0 hw ether ##:##:##:##:##:##
> dhclient eth0
> blah, blah, blah
EDIT
those _should_ have all read "eth1" in the session quoted above.
Sorry.
>
> And I'm connected.
> Couldn't manage that with BSD. What must I do? Is it even possible?
> If so, can it be assigned for use on a permanent basis?
>
> Thank you for all your time, and consideration.
>
> --Chris
>
> ___
> 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"
>

___
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: MAC cloning available like Linux has?

2012-12-14 Thread Adam Vande More 
On Fri, Dec 14, 2012 at 12:11 PM, Chris H  wrote:

> > Greetings,
> >  I attempted another BSD install on another piece of hardware the
> > other day. I'm evaluating a different ISP, and the gateway/router/modem
> > they provided, has 1 ether, which I currently use on my server, and 1
> > USB(3) port that I had intended to use with the new install. Problem I
> > ran into, was that BSD generates random (fake) MAC(3) addresses, when
> > utilizing the CDCE(4)/ue0. This worked just fine during the install.
> > But the modem "held" the MAC(3) generated during the install, and I
> > now have no idea how to tell BSD to use that MAC(3) when negotiating
> > with the modem. I had absolutely no difficulty assigning the MAC(3)
> > address when spinning up several "live" Linux distro(s) -- they provide
> > the following:
> > su
> > password: ***
> > ifconfig eth1 down
> > ifconfig eth0 hw ether ##:##:##:##:##:##
> > dhclient eth0
> > blah, blah, blah
> EDIT
> those _should_ have all read "eth1" in the session quoted above.
> Sorry.
> >
> > And I'm connected.
> > Couldn't manage that with BSD. What must I do? Is it even possible?
> > If so, can it be assigned for use on a permanent basis?
> >
> > Thank you for all your time, and consideration.
>
>
http://lmgtfy.com/?q=freebsd+change+mac+address

-- 
Adam Vande More
___
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: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
> On Fri, Dec 14, 2012 at 12:11 PM, Chris H  wrote:
>
>> > Greetings,
>> >  I attempted another BSD install on another piece of hardware the
>> > other day. I'm evaluating a different ISP, and the gateway/router/modem
>> > they provided, has 1 ether, which I currently use on my server, and 1
>> > USB(3) port that I had intended to use with the new install. Problem I
>> > ran into, was that BSD generates random (fake) MAC(3) addresses, when
>> > utilizing the CDCE(4)/ue0. This worked just fine during the install.
>> > But the modem "held" the MAC(3) generated during the install, and I
>> > now have no idea how to tell BSD to use that MAC(3) when negotiating
>> > with the modem. I had absolutely no difficulty assigning the MAC(3)
>> > address when spinning up several "live" Linux distro(s) -- they provide
>> > the following:
>> > su
>> > password: ***
>> > ifconfig eth1 down
>> > ifconfig eth0 hw ether ##:##:##:##:##:##
>> > dhclient eth0
>> > blah, blah, blah
>> EDIT
>> those _should_ have all read "eth1" in the session quoted above.
>> Sorry.
>> >
>> > And I'm connected.
>> > Couldn't manage that with BSD. What must I do? Is it even possible?
>> > If so, can it be assigned for use on a permanent basis?
>> >
>> > Thank you for all your time, and consideration.
>>
>>
> http://lmgtfy.com/?q=freebsd+change+mac+address

Further internet searches provided useless, incorrect information.
So, just for kicks, I spun up, and installed a copy PC-BSD-9.
The LXDE desktop provided a network applet that allowed to use
the hardware MAC(3), or one of my choosing. I chose my own.
But even that failed. So I attempted to use:

 # ifconfig ue0 ether ##:##:##:##:##:##
 # ifconfig ue0
ether ##:##:##:##:##:##
 # dhclient ue0
blah, blah, blah
 # ping yahoo.com
64 bytes from 98.138.253.109: icmp_seq=0 ttl=53 time=48.867 ms
64 bytes from 98.138.253.109: icmp_seq=1 ttl=53 time=51.118 ms
64 bytes from 98.138.253.109: icmp_seq=2 ttl=53 time=80.145 ms
64 bytes from 98.138.253.109: icmp_seq=3 ttl=53 time=48.964 ms

OK. So it is possible with BSD. Let's try to make it permanent!
adding any of the following attempts failed miserably:
ifconfig_ue0="ether ##:##:##:##:##:## DHCP"

ifconfig_ue0="DHCP"
ifconfig_ue0_alias0="ether ##:##:##:##:##:##"

So apparently it's not possible (for me) to accomplish this
with anything but Linux. Bummer, have used BSD exclusively
since the early 80's. Couldn't imagine having to use anything
else. :(


>
> --
> Adam Vande More
> ___
> 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"
>

___
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: MAC cloning available like Linux has?

2012-12-14 Thread Mateusz Guzik 
On Fri, Dec 14, 2012 at 02:46:33PM -0800, Chris H wrote:
> > On Fri, Dec 14, 2012 at 12:11 PM, Chris H  wrote:
> >
> >> > Greetings,
> >> >  I attempted another BSD install on another piece of hardware the
> >> > other day. I'm evaluating a different ISP, and the gateway/router/modem
> >> > they provided, has 1 ether, which I currently use on my server, and 1
> >> > USB(3) port that I had intended to use with the new install. Problem I
> >> > ran into, was that BSD generates random (fake) MAC(3) addresses, when
> >> > utilizing the CDCE(4)/ue0. This worked just fine during the install.
> >> > But the modem "held" the MAC(3) generated during the install, and I
> >> > now have no idea how to tell BSD to use that MAC(3) when negotiating
> >> > with the modem. I had absolutely no difficulty assigning the MAC(3)
> >> > address when spinning up several "live" Linux distro(s) -- they provide
> >> > the following:
> >> > su
> >> > password: ***
> >> > ifconfig eth1 down
> >> > ifconfig eth0 hw ether ##:##:##:##:##:##
> >> > dhclient eth0
> >> > blah, blah, blah
> >> EDIT
> >> those _should_ have all read "eth1" in the session quoted above.
> >> Sorry.
> >> >
> >> > And I'm connected.
> >> > Couldn't manage that with BSD. What must I do? Is it even possible?
> >> > If so, can it be assigned for use on a permanent basis?
> >> >
> >> > Thank you for all your time, and consideration.
> >>
> >>
> > http://lmgtfy.com/?q=freebsd+change+mac+address
> 
> Further internet searches provided useless, incorrect information.
> So, just for kicks, I spun up, and installed a copy PC-BSD-9.
> The LXDE desktop provided a network applet that allowed to use
> the hardware MAC(3), or one of my choosing. I chose my own.
> But even that failed. So I attempted to use:
> 
>  # ifconfig ue0 ether ##:##:##:##:##:##
>  # ifconfig ue0
> ether ##:##:##:##:##:##
>  # dhclient ue0
> blah, blah, blah
>  # ping yahoo.com
> 64 bytes from 98.138.253.109: icmp_seq=0 ttl=53 time=48.867 ms
> 64 bytes from 98.138.253.109: icmp_seq=1 ttl=53 time=51.118 ms
> 64 bytes from 98.138.253.109: icmp_seq=2 ttl=53 time=80.145 ms
> 64 bytes from 98.138.253.109: icmp_seq=3 ttl=53 time=48.964 ms
> 
> OK. So it is possible with BSD. Let's try to make it permanent!
> adding any of the following attempts failed miserably:
> ifconfig_ue0="ether ##:##:##:##:##:## DHCP"
> 
> ifconfig_ue0="DHCP"
> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
> 
> So apparently it's not possible (for me) to accomplish this
> with anything but Linux. Bummer, have used BSD exclusively
> since the early 80's. Couldn't imagine having to use anything
> else. :(
> 
> 

ifconfig_ue0="ether ##:##:##:##:##:##; DHCP"

-- 
Mateusz Guzik 
___
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: MAC cloning available like Linux has?

2012-12-14 Thread Freddie Cash 
On Fri, Dec 14, 2012 at 2:46 PM, Chris H  wrote:

> ifconfig_ue0="DHCP"
> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
>
> So apparently it's not possible (for me) to accomplish this
> with anything but Linux. Bummer, have used BSD exclusively
> since the early 80's. Couldn't imagine having to use anything
> else. :(
>

You're just not trying hard enough, or thinking logically enough.  ;)

ifconfig then dhclient works.  Yet you configure rc.conf to do dhclient
then ifconfig.  :)

Reverse your rc.conf entries to match what you did at the command prompt:

ifconfig_ue0="ether blah blah blah"
ifconfig_ue0_alias0="DHCP"

-- 
Freddie Cash
fjwc...@gmail.com
___
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: MAC cloning available like Linux has?

2012-12-14 Thread Glen Barber 
On Fri, Dec 14, 2012 at 02:46:33PM -0800, Chris H wrote:
> OK. So it is possible with BSD. Let's try to make it permanent!
> adding any of the following attempts failed miserably:
> ifconfig_ue0="ether ##:##:##:##:##:## DHCP"
> 
> ifconfig_ue0="DHCP"
> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
> 

Try this:

ifconfig_ue0="DHCP"
create_args_ue0="ether ##:##:##:##:##:##"

Glen



pgpHOSeuXeAIm.pgp
Description: PGP signature

Re: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
Greetings, and thank you for taking the time to respond...

> On Fri, Dec 14, 2012 at 02:46:33PM -0800, Chris H wrote:
>> > On Fri, Dec 14, 2012 at 12:11 PM, Chris H  wrote:
>> >
>> >> > Greetings,
>> >> >  I attempted another BSD install on another piece of hardware the
>> >> > other day. I'm evaluating a different ISP, and the gateway/router/modem
>> >> > they provided, has 1 ether, which I currently use on my server, and 1
>> >> > USB(3) port that I had intended to use with the new install. Problem I
>> >> > ran into, was that BSD generates random (fake) MAC(3) addresses, when
>> >> > utilizing the CDCE(4)/ue0. This worked just fine during the install.
>> >> > But the modem "held" the MAC(3) generated during the install, and I
>> >> > now have no idea how to tell BSD to use that MAC(3) when negotiating
>> >> > with the modem. I had absolutely no difficulty assigning the MAC(3)
>> >> > address when spinning up several "live" Linux distro(s) -- they provide
>> >> > the following:
>> >> > su
>> >> > password: ***
>> >> > ifconfig eth1 down
>> >> > ifconfig eth0 hw ether ##:##:##:##:##:##
>> >> > dhclient eth0
>> >> > blah, blah, blah
>> >> EDIT
>> >> those _should_ have all read "eth1" in the session quoted above.
>> >> Sorry.
>> >> >
>> >> > And I'm connected.
>> >> > Couldn't manage that with BSD. What must I do? Is it even possible?
>> >> > If so, can it be assigned for use on a permanent basis?
>> >> >
>> >> > Thank you for all your time, and consideration.
>> >>
>> >>
>> > http://lmgtfy.com/?q=freebsd+change+mac+address
>>
>> Further internet searches provided useless, incorrect information.
>> So, just for kicks, I spun up, and installed a copy PC-BSD-9.
>> The LXDE desktop provided a network applet that allowed to use
>> the hardware MAC(3), or one of my choosing. I chose my own.
>> But even that failed. So I attempted to use:
>>
>>  # ifconfig ue0 ether ##:##:##:##:##:##
>>  # ifconfig ue0
>> ether ##:##:##:##:##:##
>>  # dhclient ue0
>> blah, blah, blah
>>  # ping yahoo.com
>> 64 bytes from 98.138.253.109: icmp_seq=0 ttl=53 time=48.867 ms
>> 64 bytes from 98.138.253.109: icmp_seq=1 ttl=53 time=51.118 ms
>> 64 bytes from 98.138.253.109: icmp_seq=2 ttl=53 time=80.145 ms
>> 64 bytes from 98.138.253.109: icmp_seq=3 ttl=53 time=48.964 ms
>>
>> OK. So it is possible with BSD. Let's try to make it permanent!
>> adding any of the following attempts failed miserably:
>> ifconfig_ue0="ether ##:##:##:##:##:## DHCP"
>>
>> ifconfig_ue0="DHCP"
>> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
>>
>> So apparently it's not possible (for me) to accomplish this
>> with anything but Linux. Bummer, have used BSD exclusively
>> since the early 80's. Couldn't imagine having to use anything
>> else. :(
>>
>>
>
> ifconfig_ue0="ether ##:##:##:##:##:##; DHCP"

BRILLIANT!
If _only_ I had not overlooked that semicolon. :/

Thank you Mateusz Guzik! Greatly appreciated.

>
> --
> Mateusz Guzik 
>

___
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: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
> On Fri, Dec 14, 2012 at 2:46 PM, Chris H  wrote:
>
>> ifconfig_ue0="DHCP"
>> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
>>
>> So apparently it's not possible (for me) to accomplish this
>> with anything but Linux. Bummer, have used BSD exclusively
>> since the early 80's. Couldn't imagine having to use anything
>> else. :(
>>
>
> You're just not trying hard enough, or thinking logically enough.  ;)

Or _too_ hard -- making it harder than it really is. ;)
>
> ifconfig then dhclient works.  Yet you configure rc.conf to do dhclient
> then ifconfig.  :)

D'OH!

>
> Reverse your rc.conf entries to match what you did at the command prompt:
>
> ifconfig_ue0="ether blah blah blah"
> ifconfig_ue0_alias0="DHCP"

Thanks/1 That will _clearly_ work.

Thanks for Freddie, for taking the time to respond.

>
> --
> Freddie Cash
> fjwc...@gmail.com
>

___
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: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
> On Fri, Dec 14, 2012 at 02:46:33PM -0800, Chris H wrote:
>> OK. So it is possible with BSD. Let's try to make it permanent!
>> adding any of the following attempts failed miserably:
>> ifconfig_ue0="ether ##:##:##:##:##:## DHCP"
>>
>> ifconfig_ue0="DHCP"
>> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
>>
>
> Try this:
>
> ifconfig_ue0="DHCP"
> create_args_ue0="ether ##:##:##:##:##:##"

Excellent! I had never heard/seen the _args_ option for NIC's before.
Thank you!

--Chris

>
> Glen
>
>

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

LOR with ixgbe+lagg and panic with ixgbe related to an uninitialized stack variable

2012-12-14 Thread Garrett Cooper 
Hi,
Seeing the following LOR on CURRENT when scping files over two L3
lagged ixgbe interfaces:

lock order reversal:
 1st 0xfe000d15a118 ix0:rx(1) (ix0:rx(1)) @
/usr/src/sys/modules/ixgbe/../../dev/ixgbe/ixgbe.c:4353
 2nd 0xfe01334ada08 if_lagg rwlock (if_lagg rwlock) @
/usr/src/sys/modules/if_lagg/../../net/if_lagg.c:1276
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff8496fc5740
kdb_backtrace() at kdb_backtrace+0x39/frame 0xff8496fc57f0
witness_checkorder() at witness_checkorder+0xc00/frame 0xff8496fc5880
__rw_rlock() at __rw_rlock+0x98/frame 0xff8496fc5920
lagg_input() at lagg_input+0x38/frame 0xff8496fc5960
ether_nh_input() at ether_nh_input+0x171/frame 0xff8496fc5990
netisr_dispatch_src() at netisr_dispatch_src+0x90/frame 0xff8496fc5a00
tcp_lro_flush() at tcp_lro_flush+0x197/frame 0xff8496fc5a20
ixgbe_rxeof() at ixgbe_rxeof+0x5f2/frame 0xff8496fc5ad0
ixgbe_msix_que() at ixgbe_msix_que+0x9b/frame 0xff8496fc5b20
intr_event_execute_handlers() at
intr_event_execute_handlers+0x90/frame 0xff8496fc5b60
ithread_loop() at ithread_loop+0x161/frame 0xff8496fc5bb0
fork_exit() at fork_exit+0x84/frame 0xff8496fc5bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xff8496fc5bf0
--- trap 0, rip = 0, rsp = 0xff8496fc5cb0, rbp = 0 ---
lock order reversal:
 1st 0xfe000d15a118 ix0:rx(1) (ix0:rx(1)) @
/usr/src/sys/modules/ixgbe/../../dev/ixgbe/ixgbe.c:4353
 2nd 0xfe0133003da8 tcpinp (tcpinp) @ /usr/src/sys/netinet/in_pcb.c:1785
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff8496fc5570
kdb_backtrace() at kdb_backtrace+0x39/frame 0xff8496fc5620
witness_checkorder() at witness_checkorder+0xc00/frame 0xff8496fc56b0
_rw_wlock_cookie() at _rw_wlock_cookie+0x63/frame 0xff8496fc56f0
in_pcblookup_hash() at in_pcblookup_hash+0xba/frame 0xff8496fc5740
tcp_input() at tcp_input+0x60e/frame 0xff8496fc5870
ip_input() at ip_input+0xb2/frame 0xff8496fc58c0
netisr_dispatch_src() at netisr_dispatch_src+0x90/frame 0xff8496fc5930
ether_demux() at ether_demux+0x143/frame 0xff8496fc5960
ether_nh_input() at ether_nh_input+0x325/frame 0xff8496fc5990
netisr_dispatch_src() at netisr_dispatch_src+0x90/frame 0xff8496fc5a00
tcp_lro_flush() at tcp_lro_flush+0x197/frame 0xff8496fc5a20
ixgbe_rxeof() at ixgbe_rxeof+0x5f2/frame 0xff8496fc5ad0
ixgbe_msix_que() at ixgbe_msix_que+0x9b/frame 0xff8496fc5b20
intr_event_execute_handlers() at
intr_event_execute_handlers+0x90/frame 0xff8496fc5b60
ithread_loop() at ithread_loop+0x161/frame 0xff8496fc5bb0
fork_exit() at fork_exit+0x84/frame 0xff8496fc5bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xff8496fc5bf0
--- trap 0, rip = 0, rsp = 0xff8496fc5cb0, rbp = 0 ---

# uname -a
FreeBSD wf158.west.isilon.com 10.0-CURRENT FreeBSD 10.0-CURRENT #3
r+5a05236: Wed Dec 12 17:35:14 PST 2012
r...@wf158.west.isilon.com:/usr/obj/usr/src/sys/ISI-GENERIC  amd64

I ran into a panic under similar conditions with a slightly older
kernel (12/05):

Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex ix1:rx(0) (ix1:rx(0)) r = 0 (0xfe000d14e808)
locked @ /usr/src/sys/modules/ixgbe/../../dev/ixgbe/ixgbe.c:4353
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff849702d530
kdb_backtrace() at kdb_backtrace+0x39/frame 0xff849702d5e0
witness_warn() at witness_warn+0x4a3/frame 0xff849702d6a0
trap_pfault() at trap_pfault+0x5a/frame 0xff849702d750
trap() at trap+0x659/frame 0xff849702d960
calltrap() at calltrap+0x8/frame 0xff849702d960
--- trap 0xc, rip = 0x8185a82f, rsp = 0xff849702da20, rbp
= 0xff849702dad0 ---
ixgbe_rxeof() at ixgbe_rxeof+0x20f/frame 0xff849702dad0
ixgbe_msix_que() at ixgbe_msix_que+0x9b/frame 0xff849702db20
intr_event_execute_handlers() at
intr_event_execute_handlers+0x90/frame 0xff849702db60
ithread_loop() at ithread_loop+0x161/frame 0xff849702dbb0
fork_exit() at fork_exit+0x84/frame 0xff849702dbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xff849702dbf0
--- trap 0, rip = 0, rsp = 0xff849702dcb0, rbp = 0 ---


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x18
fault code  = supervisor write data, page not present
instruction pointer = 0x20:0x8185a82f
stack pointer   = 0x28:0xff849702da20
frame pointer   = 0x28:0xff849702dad0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
db> x/s version
version:FreeBSD 10.0-CURRENT #3 r+5a05236: Wed Dec 12 17:35:14
PST 2012\012
r...@wf158.west.isilon.com:/usr/obj/usr/src/sys/ISI-GENERIC\012
db> show alllocks
Process 1052 (syslogd) thread 0xfe000adfe000 (100180)
exc

Re: MAC cloning available like Linux has?

2012-12-14 Thread Chris H 
> On Fri, Dec 14, 2012 at 02:46:33PM -0800, Chris H wrote:
>> OK. So it is possible with BSD. Let's try to make it permanent!
>> adding any of the following attempts failed miserably:
>> ifconfig_ue0="ether ##:##:##:##:##:## DHCP"
>>
>> ifconfig_ue0="DHCP"
>> ifconfig_ue0_alias0="ether ##:##:##:##:##:##"
>>
Well, dfeeling "armed, and dangerous" with the new knowledge
gained from Mateusz Guzik, Freddie Cash, and Glen Barber,
I downloaded CD1 of RELENG_9, and installed it.
I attempted to use the suggestions previously provided.
However, they were either rejected, or quietly ignored. :(

with: ifconfig_ue0="ether ##:##:##:##:##:##; DHCP"
the ether isn't honored (ignored)

ifconfig_ue0="ether blah blah blah"
ifconfig_ue0_alias0="DHCP"
throws an error (but spins by too fast to catch)
/var/log/messages would probably reveal it.

ifconfig_ue0="DHCP"
create_args_ue0="ether ##:##:##:##:##:##"
create_args is simply ignored.

I don't get it. I've tried every imaginable incarnation I
could possibly conceive. Is it even possible? I had really
hoped to turn this into a gateway, and while Linux will
"clone" the MAC(3). I don't trust it (security wise).
Is Linux' DHCP more robust than BSD'?! Hard to imagine,
but I'm completely at a loss.

--Chris

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