Re: ng_ether and vlan interfaces

2011-02-15 Thread Nikolay Denev
On 15.02.2011, at 18:53, Arnaud Lacombe wrote: > Hi, > > On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: >> changing it to '_' might be accceptable, '.' is much like '/' in th >> filesystem. >> it is a separator. You can't have it in the name. >> a patch that converted . to _ would be

Re: ng_ether and vlan interfaces

2011-02-15 Thread Julian Elischer
On 2/15/11 8:53 AM, Arnaud Lacombe wrote: Hi, On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: changing it to '_' might be accceptable, '.' is much like '/' in th filesystem. it is a separator. You can't have it in the name. a patch that converted . to _ would be a nice idea. please e

Re: ng_ether and vlan interfaces

2011-02-15 Thread Arnaud Lacombe
Hi, On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: > changing it to '_' might be accceptable,  '.' is much like '/' in th > filesystem. > it is a separator. You can't have it in the name. > a patch that converted . to _ would be a nice idea. > please ensure that the man page is updated

Re: ng_ether and vlan interfaces

2011-02-15 Thread Julian Elischer
On 2/15/11 7:47 AM, Arnaud Lacombe wrote: Hi, On Tue, Feb 15, 2011 at 9:02 AM, Nikolay Denev wrote: Hi, When trying to use ng_ether with vlan interfaces using the naming sheme ${parent_if}.${vlan_tag} it produces the following warning : ng_ether_attach: can't name node ix0.512 And the

Re: ng_ether and vlan interfaces

2011-02-15 Thread Arnaud Lacombe
Hi, On Tue, Feb 15, 2011 at 9:02 AM, Nikolay Denev wrote: > Hi, > > When trying to use ng_ether with vlan interfaces using the naming sheme > ${parent_if}.${vlan_tag} > it produces the following warning : > >    ng_ether_attach: can't name node ix0.512 > > And the newly created netgraph node sta

ng_ether and vlan interfaces

2011-02-15 Thread Nikolay Denev
Hi, When trying to use ng_ether with vlan interfaces using the naming sheme ${parent_if}.${vlan_tag} it produces the following warning : ng_ether_attach: can't name node ix0.512 And the newly created netgraph node stays . This is due to the following check in sys/netgraph/ng_base.c:ng_name

Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...)

2011-02-15 Thread Monthadar Al Jaberi
here is a backtrace for the panic: panic: ieee80211_mesh_rt_add: adding self to the routing table KDB: enter: panic [ thread pid 0 tid 100030 ] Stopped at kdb_enter+0x50: lui at,0x804e db> bt Tracing pid 0 tid 100030 td 0xc08952f0 db_trace_thread+30 (?,?,?,?) ra 8009b510 sp c76275e8 sz 24

VRRP on VLANs: does it work?

2011-02-15 Thread Alex Povolotsky
Hello! I've run into strange problem: in non-promisc mode, two freevrrpds does not seems to see each others multicasts. Is it a bug or a feature? Alex. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net

[ieee80211_hwmp][panic] hwmp_recv_prep(...)

2011-02-15 Thread Monthadar Al Jaberi
Hej, I found that a panic can be generated when having a couple of ieee80211s nodes in a line topology with one of them being a ROOT node. A ping from ROOT in a newly started nodes causes a panic: panic: ieee80211_mesh_rt_add: adding self to the routing table KDB: enter: panic [ thread pid 0 tid 1