olsr

[Kevin Gerrard]

now that i have the vds and routables down i can now loose all static routes and use olsr

upon the attempt last night i got everything to work except my main gateway. the hna routes for the ap's all worked well that was a kick.

i uncommented the 0.0.0.0 0.0.0.0
in the config file for the main star router before the cisco router

even tried to put in x.x.x.1/25 for the gateway.

wont have a chance until tonight to play with this again but it is possible that it wouldnt work because of the overlap i had on my star while playing with the wds because of the ip overlap i had

ether0 x.x.x.2/24
ether1 192.168.100.1/24
ether2 192.168.101.1/24
wds1 x.x.x.129/25

like i said when i tried this last night i had that overlap, did that stop olsr from advertising the gateway hna?

and i will try again tonight

thanks again

[lonnie]

It could mess it up since overlaps like that really confuse automated systems. Try it when you have it corrected. maybe even wait a bit and use the new 1.3.23b that will be coming soon. I am applying it to most systems in my LAN right now and it seems to be solid.

[Kevin Gerrard]

no problem here since i wait until to night to try it, using 1.3.9 on most but i found a couple of 20b, will make all 1.3.9 for now and see what happens
not alot of people on it but the businesses during i want to run.

thanks again and will post back tonight late

[lonnie]

Please don't make them all 1.3.9. Just wait for the new 1.3.23b and make them all get the newest code. There have been a lot of fixes since 1.3.9

[Kevin Gerrard]

gotcha, will wait, but i would like to at least flash them with the same version. i need a break so i will find a bottle for the night!!! woot woooot

no problem here

and thanks for the reply, saved me more messups

[DrLove73]

If you want to use stable release, use 1.3.13(.1). That is the latest that surely works OK.

[lonnie]

No, you should wait for the 1.3.23b and get modern.

If you want to use stable release, use 1.3.13(.1). That is the latest that surely works OK.

[DrLove73]

He is using 1.3.9. as an fallback version. I suggested that he uses 1.3.13(.1) as an fallback version. I am using 1.3.22b on my own network, and I am very happy with it, and I will be trying 1.3.23b as soon as it gets out, but if anything goes wrong, I will be reverting to 1.3.13 so I can produce absolutely stable environment for my business.

[go.fast]

No, you should wait for the 1.3.23b and get modern.

I want to be futuristic

What version is that Lonnie?

[Kevin Gerrard]

thanks again, will be putting the 3.13 on tonight on that segment. will comment back later tonight,

[Kevin Gerrard]

the 1.3.13 appears to be working so far, all static routes are out, will leave it since these are really loyal customers. the vds appears to be good to.

if this is good and works the weekend will prolly do another leg monday night or tuesday night.

[DrLove73]

1.3.13 (1.3.13.1 for X86-PC branch) will apsolutely work, I can not remember any reported problem.

Hopefully, 1.3.23b will prove itself in the field without reported problems, and will be after week or two renamed to stable.

[Kevin Gerrard]

woke up this morning to phone calls, apparantly it quit, the vds for routables quit to. I put a static default gateway in the star server version and that repaired everything

i now have only one route in the system and it is the main gateway for the whole network. Still better than all the routes for now

just an update

[Kevin Gerrard]

possible i did that gateway wrong

all i did was uncomment the statement 0.0.0.0 0.0.0.0 for the gateway, olsr started and worked last night. this morning it didnt, put that static gateway in and it worked.

will try kicking the static out later to see if it keeps on working and for how long, im in a good position to play with this right now

thanks again

[lonnie]

1.3.23b
I want to be futuristic

What version is that Lonnie?

[Kevin Gerrard]

yessir

[Kevin Gerrard]

just for alls knowledge, I ran this 1.3.13 and it did well with only 2 towers

1 main star server edition

2 bh x4000 one on each tower

2 ap x4000 one on each tower with 3 sectionals

approximately 50 customers

worked well

added 3 more towers last night

exact same setup on these as those above, routes seem to come and go now, it i traceroute it shows awesome, and then like a link with water in a connector it will drop and come back randomly.

dont need a comment here, its not a problem at all, will be able to do it later easier now that i have a bit a the experience.

1.3.23.b wink GOTTIT THIS TIME LONNIE wink

[tog]

You're using 1.3.13 on all your systems you're using OLSR on?

What did you use for a config? Did you use my OLSR config as a template?
http://staros.tog.net/wiki/OLSR

That config shown in the wiki is the actual config I am using across my network with 30+ OLSR-speaking StarV3 systems and 264 routes being announced without any flapping.

[Kevin Gerrard]

i thought so tog, but i will double check it right now and reply back, its been doing okay, but if a route is not used it seems to delay a couple a secs before finding it.

and thegateway hna of 0.0.0.0 0.0.0.0 doesnt work, yes 1.3.13 and yes im not a pro at this, it wont hurt my feelings to point a finger at me

reply back in a bit

thanks again yall

[tog]

I haven't seen any delays like you just described. I have routes that are unused (192.168.x.x private management networks) for very long periods of time and I never see any delay on my initial communication. I just tracerouted a private network that's attached to a radio that's not even in use right now (0 clients connected) and the trace was completely instant. No traffic would have been passed to or from that private network for the last few weeks until just now.

Perhaps you're thinking of arp resolution which takes a few extra ms if you haven't communicated with that device in the last 10 minutes and its arp entry expired.

I haven't had any issues with the 0.0.0.0 0.0.0.0 Hna4 announcement. I remove the default gateway from all my OLSR systems and all is fine.

You can confirm the presence of the default route in your other systems via the OLSR web interface on the "Routes" tab. This lists only routes that have been learned via OLSR.

[DrLove73]

Wasn't there some additional setup/code to force OLSR? to act like it is point-to-point (or directly connected?) so it would not lose routes? I do not have time to search now, but tog surely knows what I am talking about and will know if I remembered correctly.

[Kevin Gerrard]

after fightin for a bit i think it is okay on 1.3.13

i found 3 radios in the middle 1.3.9 my fault, and was to arrogant to check it i guess

still swapping stuff around will reply after i get the network split

two weeks before we get the real upgrade

t3, ds3, 0c3 whatever it is not sure there is a diff

right now 3 t1 lines and half the network on sprint
and 3 t1 lines with the rest on at&t

fiber hook up two weeks and it all comes back together again

something else i noticed through all this is that 5.8 ghz links dont like the fresnel zone

makes links very noisey, good signals but noisey


will reply back after i do some more checking on all this, and i appreciate yalls comments very much. Its me and my pardner only in this business and we do everything from billing to climbing so we are time strapped.

Kevin

[Kevin Gerrard]

and even the gateway hna is working

kevin

[David L. Vrablic]

Hey Kevin,
It takes guts to admit you might be a bit arrogant and just might have overlooked something..
I wouldn't expect anything less from a Texan!

OlSR is dancing around a bit.
Tog prodded Tony to push it back to a working revision because some SP Damn thing wasn't working right .
I don't understand all I know about it but I just wipe out the default script and load the simplified template that Tog posted on his WIKI.
I then make sure the first port assignment is the one used for the back haul path.
It sure looks funny when there isn't anything in the default gateway.
==============
Hey guys Kevin needs a new handle "How about the one gun kid?"
Or Sundancer or sumpen like that?:p
I got it "KactisKev"

[Kevin Gerrard]

the complete split is off again for another day, when it is split, hopefully tomorrow, i am going to load tog's script and give it a try. thought the wiki and the default script were the same.

more arragonce eh?

bwahahahahahahahaaaa

it wouldnt have anything to do with the different wars would it, i am still dropping two links that seem to be the only three wp188's, the metro's and xscale's seem to be doing the routing thing right.

and this is just playing right now, but i will know more tomorrow night

and yes the routing tables are tough to get use too

like i said we have two wars each tower, 15 towers, trap set now we need customers

bwahhaa, they will come

[Kevin Gerrard]

well i got to do what i wanted and nothing worked, was to tired to play with it, not blaming the software, like i said i had a rough day and reading starboxes and configuring was not gonna happen.

i put it all to static, olsr still seems to lose a link ( not olsr though i am 90 percent sure that my problem with these towers losing the link is the 5.8 link is to low. will be raising it after this upgrade of trunk lines, prolly next week first part, they have great signals on the links but quality unstable, will fix)

so i do believe the olsr is working well in 1.3.13

i couldnt get the vds to work though after i added the other towers.

had hell, i couldnt even get the dadgum vds links to show active, figured it was something stupid and will tackle that again in the morning, it was fine before so i got the what did i do attitude here.

i am going to do this with olsr, vds on the main star for the routable ips using ics dhcp or can i put a static ip in the router and it will work to, right? (This is the only question i got)

climbing, configuring, meeting at 3 and lunch with someone at noon. kinda hard to keep the mind on just the tower configs

oh well, its just another hill!!!

[DrLove73]

Be aware that Master VDS with support for lots of connections for Server edition Lonnie talked about last 7 days is not supported it 1.3.13 (MASTER side is not, client should be the same).

[lonnie]

Even VDS is much improved in the newer releases. The driver is improved. 1.3.23b is pretty much ready and Tony will do the final build and get it uploaded to me.

[Kevin Gerrard]

awesome, i have it working with 1.3.13 but have only got one vds client, seems ok, there is an issue but i can wait.

after two weeks of temp t1's (that we was supposed to have in Nov. til the fiber got here) they are turning on the fiber today so i will be ready to put my time to the new version

when yall realease it im throwing it at all towers and clients
woot

will see probs if any

and thanks again for yalls help