ifconfig meshforward command bug

(set80211meshttl, val, d) static DECL_CMD_FUNC(set80211meshforward, val, d) { - set80211(s, IEEE80211_IOC_MESH_FWRD, atoi(val), 0, NULL); + set80211(s, IEEE80211_IOC_MESH_FWRD, d, 0, NULL); br, -- Monthadar Al Jaberi ___ freebsd-net@freebsd.org

Re: ifconfig meshforward command bug

n or off. Another one I found, static DECL_CMD_FUNC(set80211meshpeering, val, d) { - set80211(s, IEEE80211_IOC_MESH_AP, atoi(val), 0, NULL); + set80211(s, IEEE80211_IOC_MESH_AP, d, 0, NULL); I took a quick look and think this is last one > > > Adrian thn

Re: ifconfig meshforward command bug

set80211meshttl, val, d) { set80211(s, IEEE80211_IOC_MESH_TTL, atoi(val), 0, NULL); } br > > > adrian -- Monthadar Al Jaberi ___ 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: B.a.t.m.a.n.

all of them to have a preference. > ___ > 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" -- Monthadar Al Jaber

Re: B.a.t.m.a.n.

On Mon, May 14, 2012 at 3:02 PM, Ivo Vachkov wrote: > Hello all, > > On Mon, May 14, 2012 at 1:52 PM, Monthadar Al Jaberi > wrote: >> >> On Sun, May 13, 2012 at 2:49 PM, Ivan Voras wrote: >> > On 13 May 2012 06:46, Ivo Vachkov wrote: >> >> P

netstat -r do not show bridge0 as the interface for default route.

0:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: arge0 flags=143 ifmaxaddr 0 port 3 prio

problem setting up a mesh portal with a bridge to wired lan

this old post, http://lists.freebsd.org/pipermail/freebsd-net/2010-February/024538.html... but didnt help me. Thank you in advance! -- //Monthadar Al Jaberi ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freeb

Bridging mesh with wired not working?

member: wlan0 flags=143 ifmaxaddr 0 port 7 priority 128 path cost 370370 br, -- //Monthadar Al Jaberi ___ 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: Bridging mesh with wired not working?

rward(vap, m, mc); if (dir == IEEE80211_FC1_DIR_DSTODS) goto out; /* NB: fall thru to deliver mcast frames locally */ } ... } I am puzzeled... everyone says it works, did I miss something?! :P br, > > >

Re: Bridging mesh with wired not working?

when it is a proxy dest, and it did ping!!! but! if I change anything in how the mesh is set up it wont invalidate old values and thus stop working for proxy addresses :( > > > > Adrian br, > > On 1 December 2010 15:48, Monthadar Al Jaberi wrote: >> On Wed, Dec 1, 2010 a

capturing packet from wlan0 with netgraph?

stack RSPROs and connected them a big switch and a PC. Hope was I clear in my thoughts. Best regards, -- //Monthadar Al Jaberi ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to

How hard is it to write a dummy wireless driver? (wtap??)

IFQ_DEQUEUE(&ifp->if_snd, m) inside myath_start (stripped down version of ath_start) always returns null... I can share my code if you think it helps. thnx -- //Monthadar Al Jaberi ___ 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: capturing packet from wlan0 with netgraph?

looking at the crash, it certainly seems like in ip_input, the line >>     435         if (ip->ip_v != IPVERSION) { >> >> got a bad address for the ip pointer. >> >> The output of 'show registers' at the ddb prompt would be useful to >> debug further. >>

Re: capturing packet from wlan0 with netgraph?

Whatever is passing the packet to the IP layer should be re-aligning > things beforehand. > (eg, look at what the ethernet ipfw hook code does - if the ether type > is ipv4/ipv6, it actually realigns the packets before passing it back > up the stack.) > > > > Adrian > >

Bug in ieee80211_mesh.c code?

Hi, This line 1466 in ieee80211_mesh.c: frm += frm[2] + 2; When I look at the other modes it should be frm += frm[1] + 2; ?? br, -- //Monthadar Al Jaberi ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net

if_alloc() page fault, VirtualBox + VIMAGE

process = 1203 (ioctl) panic: from debugger cpuid = 0 Uptime: 21s Physical memory: 495 MB Dumping 55 MB: 40 24 8 Without VIMAGE option if_alloc returns fine, I thought if I dont create any VNETs the system should behave like normal... what is the problem? Best regards, -- //Monthadar Al

Re: if_alloc() page fault, VirtualBox + VIMAGE

On Tue, Feb 1, 2011 at 3:49 PM, John Baldwin wrote: > On Tuesday, February 01, 2011 9:38:16 am Monthadar Al Jaberi wrote: >> Hi, >> >> I am running FreeBSD Current (201010) as guest in VirtualBox on an >> Ubuntu 10.04. FreeBSD is compiled with VIMAGE option. >> &

80211s HWMP problem

1:67] discard PREP for 00:15:6d:67:21:67, wrong seqno 6 != 22 br -- //Monthadar Al Jaberi ___ 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: 80211s HWMP problem

n Thursday, February 10, 2011 11:06:41 Monthadar Al Jaberi wrote: >> Hej, wanna check if anyone encountered this problem: >> I setup 4 mesh nodes in a link topology ( 0 <-> 1 <-> 2 <-> 3) >> >> But I cant ping from 3 to 0, or 0 to 3, without first ping between >

Re: 80211s HWMP problem

On Thu, Feb 10, 2011 at 12:09 PM, Bernhard Schmidt wrote: > On Thursday, February 10, 2011 11:42:05 Monthadar Al Jaberi wrote: >> Okej, I run all four scenarios: >> >> 0->2 OK, but the first "ping -c 1" got lost >> 1->3 OK, >> 2->0 OK, >>

Re: 80211s HWMP problem

On Thu, Feb 10, 2011 at 12:17 PM, Monthadar Al Jaberi wrote: > On Thu, Feb 10, 2011 at 12:09 PM, Bernhard Schmidt > wrote: >> On Thursday, February 10, 2011 11:42:05 Monthadar Al Jaberi wrote: >>> Okej, I run all four scenarios: >>> >>> 0->2 OK, but

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

s & IEEE80211_MESHFLAGS_FWD)) return; -- //Monthadar Al Jaberi ___ 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: [ieee80211_hwmp][panic] hwmp_recv_prep(...)

:00 PM, Monthadar Al Jaberi wrote: > 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: ad

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

== bad idea), what legitimate-but-broken circumstances could > cause a node to hear its own announcement? > > > > Adrian > > > On 15 February 2011 07:00, Monthadar Al Jaberi wrote: >> Hej, >> >> I found that a panic can be generated when having a couple of

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

On Thu, Feb 17, 2011 at 1:30 AM, Adrian Chadd wrote: > On 16 February 2011 15:51, Monthadar Al Jaberi wrote: >> >> I think anytime the destination node sends a PREP to the originator >> node that is not a peering node (not in direct contact with) we would >> get th

Clarification request about mesh_parse_meshpeering_action()

, //Monthadar Al Jaberi ___ 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"