| View previous topic :: View next topic |
| Author |
Message |
n8evdo EVDO Fledgling
Joined: 03 Oct 2007 Posts: 22 Location: West Michigan
|
Posted: Mon Apr 28, 2008 10:48 am Post subject: |
|
|
| Has anyone been able to fix the port forward (not working) issue? |
|
| Back to top |
|
 |
rcoker6493 EVDO Newbie
Joined: 23 Feb 2008 Posts: 2
|
Posted: Tue May 13, 2008 7:56 pm Post subject: What tool is used to run the hardcore NVRAM erase |
|
|
| Rangerw wrote: | Think the Linksys firms must have left some junk laying around.
Flashed my original router to the stock 2.00.9 and did a reset to factory stats then upgraded to r75 and did a hardcore NVRAM erase (mtd -r erase nvram) (not for the faint of heart, can permently brick you) and then rebooted the router, set the network settings, unplugged the router, inserted the card and adapter and pluged the power in and it's back like old times.
I haven't up'ed to r82 yet but I'd bet the farm it will be ok with no ppp0 errors now that the NVRAM is clean. |
Was wondering what tool was use to run the commands for the hardcore delete. My router is running at r82 with all the edits. For some reason the router is running sluggish and I believe that the NVRAM has junk remaining from old flashes. Assistance would be appreciated. |
|
| Back to top |
|
 |
daverup EVDO User
Joined: 07 Dec 2007 Posts: 41
|
Posted: Wed May 14, 2008 5:08 am Post subject: |
|
|
If you are using Alltel, it's probably not your router that is sluggish.
Alltel is deploying a caching proxy server that is slowing things down.
The commands for the NVRAM cleanup are run after using ssh to get to the router command line. Those commands are a few pages back in this thread I think. |
|
| Back to top |
|
 |
jfarris EVDO Junkie
Joined: 10 May 2007 Posts: 182
|
Posted: Thu May 15, 2008 9:26 am Post subject: |
|
|
Ranger or anyone that has programmed on this firmware:
You can choose what service you connect through, but is the file with the connection information based on what carrier you choose accessible? I have some connection strings in my 3g-generic.chat file that have helped with connectivity and performance, but I want to make sure that I'm not conflicting with any Alltel strings that may be pre-programmed.
Thanks in advance. |
|
| Back to top |
|
 |
n8evdo EVDO Fledgling
Joined: 03 Oct 2007 Posts: 22 Location: West Michigan
|
Posted: Fri May 16, 2008 7:57 am Post subject: |
|
|
| Can someone that has v82 of this firmware running let me know if the port forward option actually works? |
|
| Back to top |
|
 |
Rangerw EVDO Junkie
Joined: 29 Oct 2006 Posts: 218 Location: Orange Texas
|
Posted: Tue Jun 03, 2008 7:57 pm Post subject: |
|
|
Working on the port forwarding and believe it's because
'iptables' only listens to WAN which is vlan1 and it ignores WWAN which is ppp0.
Experimenting with the init.d firewall script to see what I can screw up. But a ppp0 forward rule my help.
Been inactive since been on the KR1/USB 720 last month, but new month so moved back to the 54g3g/V740 and got to poking around in it again. _________________ A simple man. |
|
| Back to top |
|
 |
claudioc EVDO Newbie
Joined: 03 Jun 2008 Posts: 1
|
Posted: Tue Jun 03, 2008 9:23 pm Post subject: Diff listings? |
|
|
Hello. Great job with this, but is it possible for you to show a list of the diffs from the sources in the standard distribution so this can be replicated for other variants?
TIA,
Claudio |
|
| Back to top |
|
 |
DBoone EVDO Newbie
Joined: 04 Jun 2008 Posts: 1
|
Posted: Wed Jun 04, 2008 5:08 pm Post subject: |
|
|
| Rangerw wrote: | Working on the port forwarding and believe it's because
'iptables' only listens to WAN which is vlan1 and it ignores WWAN which is ppp0.
Experimenting with the init.d firewall script to see what I can screw up. But a ppp0 forward rule my help.
Been inactive since been on the KR1/USB 720 last month, but new month so moved back to the 54g3g/V740 and got to poking around in it again. |
Add these two lines, and I believe you should be good to go.
iptables -A FORWARD -i ppp0 -j forwarding_wan
iptables -t nat -A PREROUTING -i ppp0 -j prerouting_wan |
|
| Back to top |
|
 |
Rangerw EVDO Junkie
Joined: 29 Oct 2006 Posts: 218 Location: Orange Texas
|
Posted: Thu Jun 05, 2008 11:08 pm Post subject: |
|
|
| DBoone wrote: |
Add these two lines, and I believe you should be good to go.
iptables -A FORWARD -i ppp0 -j forwarding_wan
iptables -t nat -A PREROUTING -i ppp0 -j prerouting_wan |
That seems to do it! Many thanks to you DBoone.
Look to next post for directions for those that need help. _________________ A simple man. |
|
| Back to top |
|
 |
Rangerw EVDO Junkie
Joined: 29 Oct 2006 Posts: 218 Location: Orange Texas
|
Posted: Thu Jun 05, 2008 11:34 pm Post subject: |
|
|
As DBoone directed, add the two lines to the S35firewall file using the File Editor. The file is located at: /etc/init.d/s35firewall Click the 'paper/pencil' icon on the right side to enter edit mode.
iptables -A FORWARD -i ppp0 -j forwarding_wan add to the
"### FORWARDING" area: when added should be similar to this:
### FORWARDING
### (connections routed through the router)
# base case
iptables -P FORWARD DROP
iptables -A FORWARD -m state --state INVALID -j DROP
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
#
# insert accept rule or to jump to new accept-check table here
#
iptables -A FORWARD -j forwarding_rule
iptables -A FORWARD -i $WAN -j forwarding_wan
iptables -A FORWARD -i ppp0 -j forwarding_wan
------
iptables -t nat -A PREROUTING -i ppp0 -j prerouting_wan add to the ### MASQ area, example below:
### MASQ
iptables -t nat -A PREROUTING -m state --state NEW -j NEW
iptables -t nat -A PREROUTING -j prerouting_rule
iptables -t nat -A PREROUTING -i $WAN -j prerouting_wan
iptables -t nat -A PREROUTING -i ppp0 -j prerouting_wan
iptables -t nat -A POSTROUTING -j postrouting_rule
iptables -t nat -A POSTROUTING -o $WAN -j MASQUERADE
Then click Save Changes and then Apply changes and reboot the router.
I prefer to modify /etc/config/firewall with my forwarding rules, example of Remote Desktop forwarding:
forward:dport=3389:192.168.1.121:3389
(192.168.1.121 is my target PC IP)
Make sure the PC your forwarding to is listed in the Hosts area and getting a static IP via MAC address (also in host Area):
Static IP addresses (for DHCP)
00:00:00:00 --> IP address you want assigned to the target PC
(00:00:00:00 = Please use the actual MAC address of the target computers NIC/Wireless card.)
Host NamesIP
IP address you assigned to the target PC ---> Name of the Target PC
In DNSMASQ make sure 'Read Ethers' is checked. _________________ A simple man. |
|
| Back to top |
|
 |
Rangerw EVDO Junkie
Joined: 29 Oct 2006 Posts: 218 Location: Orange Texas
|
Posted: Sat Jun 14, 2008 9:12 pm Post subject: |
|
|
I posty this through my WRT54G3G-ST with X-OpenWrt Kamikaze 7.09 with Linux 2.4.34 #5 Kernal withn a VZW V740 Express card.
It's not pretty yet since I had to us the config files since the Network setup page (webif user inface) is not useable for US EVDO (3G) Cards, at least what I could gather.
There is no Mobile Network status page and using the PPPoE staus page to connect and Disconnect. I also have murdered ifup scripts and chatscripts to get a connection but it seems to work fine.
But good news is that port forwarding works, there is a working Firewall log and a Bandwidth monitor interface to moniter useage. It seems to also be better with system resources cpu and file system usuage.
I'll see what I can do to have a usuable Network setup page and Mobile Satus page and compile a workable image, but gonna take awhile since I'm learning as I go. _________________ A simple man. |
|
| Back to top |
|
 |
dojesus EVDO Fledgling
Joined: 31 Oct 2007 Posts: 13
|
Posted: Thu Jun 26, 2008 9:02 pm Post subject: |
|
|
Sweet! Looking forward to giving it a whirl.
Give us a heads up when it's ready. |
|
| Back to top |
|
 |
|