| View previous topic :: View next topic |
| Author |
Message |
evdo-wizard
EVDO Heavy User
Joined: 21 Apr 2007
Posts: 125
|
 Posted: Thu Jul 05, 2007 8:51 pm Post subject: |
 |
|
| Quote: | | any further progress on your end, wizard? |
yeah.. i'm still a bit stumped on how the interfaces should be set up. The normal OpenWrt firmware just has a WAN (wide area network) interface for internet, where it can be set up for static, dhcp, pppoe, pptp, etc according to your internet provider. I could just add a 3g option to the WAN interface, but instead I think I'll create a new interface called WWAN (wireless wide area network), so the WAN and WWAN interfaces can be set up independently. That would allow for failover, etc. So right now I'm just working that out.
| Quote: | Is there any way to create a usable signal strength indicator page in OpenWRT? "Poor", "Good", "Excellent" in the stock firmware is next to useless for positioning an antenna...
Just a suggestion.
RLW |
I agree that the poor, good, excellent signal ratings are next to useless which is why I'm not even trying to implement it right now. I'm pretty sure that the method that Linksys uses (as well as the other linux based routers) is similar to this. Using that method, the signal strength can only be read when the card is disconnected, which makes it pretty useless. Also, this method doesn't give a very accurate RSSI rating, which explains why the signal reading with the stock Linksys firmare is so unresponsive and simple.
There is one program that I know of for windows called USB Monitor (link) that would help reveal how the actual windows connection manager programs receive signal strength. I've experimented with this a little bit using the Sprint connection manager, and it seems that the card constantly sends signal strength readings through the secondary serial device, even while the card is connected. I'm not exactly sure how it all works, but I can tell you that it is possible to get this signal reading in Linux (this router), with some work. |
|
| Back to top |
|
 |
Fox McCloud
EVDO Junkie
Joined: 02 Dec 2006
Posts: 599
|
| Posted: Thu Jul 05, 2007 10:04 pm Post subject: |
|
|
ok, great.
For now, I reverted back to the *gasp* old Linksys firmware. Why? for QoS implementation. The only downside to this, however, is that it appears the stock firmware has bad QoS....
and the OpenWRT QoS is about 10 times worse, unless I'm just not setting something up right. |
|
| Back to top |
|
|
CodinAndHaulin
EVDO User
Joined: 19 Jan 2007
Posts: 26
|
| Posted: Fri Jul 06, 2007 1:12 am Post subject: |
|
|
| Fox McCloud wrote: | ok, great.
For now, I reverted back to the *gasp* old Linksys firmware. Why? for QoS implementation. The only downside to this, however, is that it appears the stock firmware has bad QoS....
and the OpenWRT QoS is about 10 times worse, unless I'm just not setting something up right. |
Hope I can help. I've just spent a few hours with this new firmware trying to get QoS right for my ViaTalk VoIP adapter. It took a while, and some google-ing, but I finally found what works for me. It seemed no matter what rule I set up, the VoIP traffic was being classified as BULK. 
What I did was set up two rules as so (in file /etc/config/qos) (obviously, change the IP to the static IP of your VoIP adapter)
# Begin changes for VoIP
config classify
option target 'Express'
option dsthost '192.168.0.50'
config classify
option target 'Express'
option srchost '192.168.0.50'
# End changes for VoIP
Also, importantly, I commented out the following rule which was in the file as shipped with the firmware:
# RULES:
#config classify
# option target 'Bulk'
# option ipp2p 'all'
It seemed this rule was reclassifying all my VoIP traffic as Bulk.
Let me know if this helps. I used the Status, QoS menu on the OpenWRT interface to verify that the traffic was being classified the way I like.
...Still haven't figured out how to set up a DMZ...  |
|
| Back to top |
|
|
Fox McCloud
EVDO Junkie
Joined: 02 Dec 2006
Posts: 599
|
| Posted: Fri Jul 06, 2007 9:25 am Post subject: |
|
|
| CodinAndHaulin wrote: | | Fox McCloud wrote: | ok, great.
For now, I reverted back to the *gasp* old Linksys firmware. Why? for QoS implementation. The only downside to this, however, is that it appears the stock firmware has bad QoS....
and the OpenWRT QoS is about 10 times worse, unless I'm just not setting something up right. |
Hope I can help. I've just spent a few hours with this new firmware trying to get QoS right for my ViaTalk VoIP adapter. It took a while, and some google-ing, but I finally found what works for me. It seemed no matter what rule I set up, the VoIP traffic was being classified as BULK.
What I did was set up two rules as so (in file /etc/config/qos) (obviously, change the IP to the static IP of your VoIP adapter)
# Begin changes for VoIP
config classify
option target 'Express'
option dsthost '192.168.0.50'
config classify
option target 'Express'
option srchost '192.168.0.50'
# End changes for VoIP
Also, importantly, I commented out the following rule which was in the file as shipped with the firmware:
# RULES:
#config classify
# option target 'Bulk'
# option ipp2p 'all'
It seemed this rule was reclassifying all my VoIP traffic as Bulk.
Let me know if this helps. I used the Status, QoS menu on the OpenWRT interface to verify that the traffic was being classified the way I like.
...Still haven't figured out how to set up a DMZ... |
I might be switching back, afterall; Linksys's QoS implementation is not as bad as openWRT, but it's still really bad.
thanks for the information...though I don't have VoIP yet (do you have Viatalk+EVDO Revision A? If so, I have a few questions for you)....so I'm more interested in prioritizing my 2 gaming applications (ports 16567 and 17567). |
|
| Back to top |
|
|
evdo-wizard
EVDO Heavy User
Joined: 21 Apr 2007
Posts: 125
|
| Posted: Fri Jul 06, 2007 9:35 am Post subject: |
|
|
I don't know what version of X-Wrt (the routers web interface) is included with this firmware, but it's possible that it's an older version of X-Wrt which would explain the poor QoS webpage. You might try and upgrade X-Wrt, which you can on the routers main page (i think). Though if HeavlyArmdPokey made any changes to the webif, they will be erased when upgraded.
I have had a bit of experience with editing the webif pages.. and it's possible that I could improve the QoS page. After all, this is open source  . |
|
| Back to top |
|
|
Fox McCloud
EVDO Junkie
Joined: 02 Dec 2006
Posts: 599
|
| Posted: Fri Jul 06, 2007 10:26 am Post subject: |
|
|
| evdo-wizard wrote: | I don't know what version of X-Wrt (the routers web interface) is included with this firmware, but it's possible that it's an older version of X-Wrt which would explain the poor QoS webpage. You might try and upgrade X-Wrt, which you can on the routers main page (i think). Though if HeavlyArmdPokey made any changes to the webif, they will be erased when upgraded.
I have had a bit of experience with editing the webif pages.. and it's possible that I could improve the QoS page. After all, this is open source . |
basically, you could only set up ports and IP addresses (and select layer-7 and P2P) and label them as "bulk", "priority", "express", or "normal". It doesn't have MAC address priority, ethernet port priority, or anything like that; just IP addresses and ports. |
|
| Back to top |
|
|
HeavlyArmdPokey
EVDO Newbie
Joined: 25 Apr 2007
Posts: 9
|
| Posted: Fri Jul 06, 2007 10:39 pm Post subject: |
|
|
Alright, just letting you guys know I'm not dead; in fact, I am very much alive and making progress.
Version 0.2 of my OpenWRT firmware (which will be posted tomorrow, really) requires no configuration and boasts support for the disconnect/connect button and the beloved Blue Light.
From there, it will be a race to see who gets failover working first. May the best man win!  |
|
| Back to top |
|
|
Fox McCloud
EVDO Junkie
Joined: 02 Dec 2006
Posts: 599
|
| Posted: Sat Jul 07, 2007 12:37 am Post subject: |
|
|
| HeavlyArmdPokey wrote: | Alright, just letting you guys know I'm not dead; in fact, I am very much alive and making progress.
Version 0.2 of my OpenWRT firmware (which will be posted tomorrow, really) requires no configuration and boasts support for the disconnect/connect button and the beloved Blue Light.
From there, it will be a race to see who gets failover working first. May the best man win! |
Ahh the beloved blue light.....blueee..blueee....BLUEEEE!  Sorry, couldn't resist.
Anyway, although the blue light may seem trivial, I often use it as an indicator as to whether or not I've been disconnected....
So, auto-failover will be the big race, eh? What after that? Better QoS implementation?
Once again, thanks for submitting this firmware; it's truly awesome. |
|
| Back to top |
|
|
hustl3
EVDO User
Joined: 11 Oct 2006
Posts: 62
Location: Sunny Orlando, Florida
|
| Posted: Sat Jul 07, 2007 7:09 am Post subject: no disconnects yet |
|
|
I forgot about the blue light. hehe I havent had to look at my router since I installed this firmware and got it working per my own minor tweaks w00t! My downloads are avg 1Mbit and up avg is around 400kbit sweet!
thanks so much guys!
still having to updated dyndns manually though =\ |
|
| Back to top |
|
|
josw
EVDO User
Joined: 06 Feb 2007
Posts: 68
|
| Posted: Sat Jul 07, 2007 11:43 am Post subject: |
|
|
| HeavlyArmdPokey wrote: | Alright, just letting you guys know I'm not dead; in fact, I am very much alive and making progress.
Version 0.2 of my OpenWRT firmware (which will be posted tomorrow, really) requires no configuration and boasts support for the disconnect/connect button and the beloved Blue Light.
From there, it will be a race to see who gets failover working first. May the best man win! |
Thanks please let us know when you get the new firmware ready for download |
|
| Back to top |
|
|
evdo-wizard
EVDO Heavy User
Joined: 21 Apr 2007
Posts: 125
|
| Posted: Sat Jul 07, 2007 2:43 pm Post subject: |
|
|
| Quote: | | From there, it will be a race to see who gets failover working first. May the best man win! |
well while I don't mind a race.. I'll be posting all of the source code changes/additions somewhere, so that anyone can contribute to it. |
|
| Back to top |
|
|
HeavlyArmdPokey
EVDO Newbie
Joined: 25 Apr 2007
Posts: 9
|
| Posted: Sat Jul 07, 2007 6:48 pm Post subject: |
|
|
| Quote: | | well while I don't mind a race.. I'll be posting all of the source code changes/additions somewhere, so that anyone can contribute to it. |
Aye, I'll do that too, eventually. I just think a little friendly competition would be good for the project. Kicks it into gear. |
|
| Back to top |
|
|
joshuamcdo
EVDO User
Joined: 07 Jul 2007
Posts: 26
|
| Posted: Sat Jul 07, 2007 9:55 pm Post subject: Not to be a party pooper.. |
|
|
I have the WRT54G3G-ST, and before this firmware came along was about to toss my PX-500 and the WRT54G3G-ST in the trash. This firmware fixed a-lot of issues I was having.
However, today I am getting the following warning message.
touch: /etc/ppp/users.pptpd: No space left on device touch: /etc/ppp/users.pptp: No space left on device touch: /etc/ppp/peers.pptp: No space left on device grep: /etc/ppp/chap-secrets: No such file or directory rm: cannot remove '/etc/ppp/chap-secrets': No such file or directory '/etc/ppp/chap-secrets' exists chmod: /etc/ppp/chap-secrets: No such file or directory
I am not sure how this is or will be effecting me. The device is as of this moment in time, still working. Is there any way to fix this problem? I do not know enough about how this works to just start deleting things. Any advice / help would be appreciated.
Thanx in advance |
|
| Back to top |
|
|
evdo-wizard
EVDO Heavy User
Joined: 21 Apr 2007
Posts: 125
|
| Posted: Sat Jul 07, 2007 10:28 pm Post subject: |
|
|
@joshuamcdo
have you added any extra packages or features to your router (such as OpenVPN, etc.)? |
|
| Back to top |
|
|
joshuamcdo
EVDO User
Joined: 07 Jul 2007
Posts: 26
|
| Posted: Sun Jul 08, 2007 12:08 am Post subject: Re: Re: I hate to be a party pooper. |
|
|
| evdo-wizard wrote: | @joshuamcdo
@evdo-wizard
have you added any extra packages or features to your router (such as OpenVPN, etc.)? |
R
I actually did add open VPN, however, I need these packages to be able to VPN in. Hmmmm.. Is the source code available yet? I would like to take a look at what is being stored in the firmware a lil more in depth. The is a 7 meg tmp partition that isn't being used completely, any ideas why?
Thanx in advance. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Sprint Rev A USB: Compass 597
Sprint Rev A ExpressCard: Merlin EX720
Purchase an V740 Rev A ExpressCard
Sprint U727
CTR350 Router
CradlePoint PHS300
Purchase a MBR1000
Purchase an EVDO Booster Antenna
Purchase a LinkSys 3G Router
Purchase an EVDO Amplifier
Your Mac EVDO Experts
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
