Siap2 nyoba pake WAP54G yang udah rusak ethernete :(



PostPosted: Wed Sep 27, 2006 10:17 am Post subject: Easy success on WAP54G v2 MDG2 Reply with quote
I installed the latest DD-WRT (v23 SP2) on two WAP54G's here, and had great success!

I made the mistake a while ago of buying WAP54G instead of the more powerful (and cheaper!) WRT54G. And they were selling WRT54G v4's by the pallet load back then, too, sigh.... I'm glad DD-WRT micro edition now works on WAP54G as well as the newer crippled WRT54G v5 and v6's.

Everything worked the first time :)

That is something that did NOT happen when running the original Linksys firmware (2.08)! What a headache that was to keep running. The things lost connection all the time.

Now, DD-WRT is rock solid. The micro generic version worked great.

Some instructions to clarify:

1) After doing the full factory reset of your original Linksys firmware, go to this "secret" webpage and make sure both are set to Disable. Click Apply and then Go Home. Otherwise, you'll get that stupid "You cannot downgrade the firmware" error. BTW, there is no need to rename .bin to .trx, as other pages suggested in the past. Flashing the .bin file worked just fine for me.

http://192.168.1.245/fw-conf.asp

2) After flashing with DD-WRT micro generic, the reset button no longer worked. I was able to do a factory reset from the web interface, and that seemed to work just as well.

3) Your MAC address will get corrupted after doing the upgrade. It will get changed to 00-90-4C-60-04-01. You can keep this if you want, but since I had 2 WAP54G's on my network, they needed to be different. So, I "cloned" the MAC address back to what I had originally!

4) On WAP54G, the LAN and wireless ports seem to be the same thing, and the WAN port does not exist. Changing the MAC address of the LAN also affects the wireless, and vice versa!

5) Since there's no WAN port, set WAN to disabled and firewall to off, and disable other stuff you can find that uses the WAN. Turn off DHCP server, set gateway to Router instead, disable routing, and so forth. This will also free up some memory, which will help your stability.

I also installed DD-WRT standard generic edition on a sweet WRT54G v4 that was up at my parent's house. Gave them some more range, and got my Dad interested in wireless stuff, by watching the live signal bars go back and forth. Now my Dad's moving the laptop around and trying to find the strongest spot that is still convenient :)

Thanks for this great firmware, I will definitely be donating....

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=5025&highlight=wap54g+radius

6.14 - How can I do equal-cost multipath routing?
Equal-cost multipath routing refers to having multiple routes in the routing table for the same network, such as the default route, 0.0.0.0/0. When the kernel is doing a route lookup to determine where to send packets destined to that network, it can choose from any of the equal-cost routes. In most scenarios, multipath routing is used to provide redundant uplink connections, e.g., redundant connections to the Internet.
The route(8) command is used to add/change/delete routes in the routing table.
The -mpath argument is used when adding multipath routes.

# route add -mpath default 10.130.128.1
# route add -mpath default 10.132.0.1
Verify the routes:
# netstat -rnf inet grep default
default 10.130.128.1 UGS 2 134 - fxp1
default 10.132.0.1 UGS 0 172 - fxp2

In this example we can see that one default route points to 10.130.128.1 which is accessible via the fxp1 interface, and the other points to 10.132.0.1 which is accessible via fxp2.
Since the mygate(5) file does not yet support multipath default routes, the above commands should be added to the bottom of the hostname.if(5) files for the fxp1 and fxp2 interfaces.
The /etc/mygate file should then be deleted.

/etc/hostname.fxp1
!route add -mpath default 10.130.128.1
/etc/hostname.fxp2
!route add -mpath default 10.132.0.1

Lastly, don't forget to activate the use of multipath routes by enabling the proper sysctl(3) variable.

# sysctl net.inet.ip.multipath=1
# sysctl net.inet6.ip6.multipath=1
Be sure to edit sysctl.conf(5) to make the changes permanent.
Now try a traceroute to different destinations. The kernel will load balance the traffic over each multipath route.

# traceroute -n 154.11.0.4
traceroute to 154.11.0.4 (154.11.0.4), 64 hops max, 60 byte packets
1 10.130.128.1 19.337 ms 18.194 ms 18.849 ms
2 154.11.95.170 17.642 ms 18.176 ms 17.731 ms
3 154.11.5.33 110.486 ms 19.478 ms 100.949 ms
4 154.11.0.4 32.772 ms 33.534 ms 32.835 ms

# traceroute -n 154.11.0.5
traceroute to 154.11.0.5 (154.11.0.5), 64 hops max, 60 byte packets
1 10.132.0.1 14.175 ms 14.503 ms 14.58 ms
2 154.11.95.38 13.664 ms 13.962 ms 13.445 ms
3 208.38.16.151 13.964 ms 13.347 ms 13.788 ms
4 154.11.0.5 30.177 ms 30.95 ms 30.593 ms

For more information about how the route is chosen, please refer to RFC2992, "Analysis of an Equal-Cost Multi-Path Algorithm".
It's worth noting that if an interface used by a multipath route goes down (i.e., loses carrier), the kernel will still try to forward packets using the route that points to that interface. This traffic will of course be blackholed and end up going nowhere. It's highly recommended to use ifstated(8) to check for unavailable interfaces and adjust the routing table accordingly.



source : http://www.openbsd.org/faq/faq6.html#Multipath

Perbandingan antara menggunakan kurang kurawal {} dan tidak.
Ternyata untuk website2 intenasional, kyak Yahoo dan temen deketnya tidak menyukai nat berdasarkan device.
Berdasarkan pengalaman, YM sama mail.yahoo jadi lelet dan kadang gk mau di buka klo natnya pake {}

contoh nat yg running well :

nat on $ext_if inet from -> $ext_ip
nat on $ext_if inet from -> $ext_ip
nat on $ext_if inet from -> $ext_ip
nat on
$ext_if inet from !$ext_if to -> $ext_rad

rdr on $int_if inet
proto tcp from to any port $redirect -> $proxy
rdr on $int_if inet
proto tcp from to any port $redirect -> $proxy

Junos 2300 Recovery Mode

Hit [Enter] to boot immediately, or space bar for command prompt.

ok boot -s
Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery

root@SURAKARTA> configure
Entering configuration mode
The configuration has been changed but not committed

[edit]
root@SURAKARTA# set system root-authentication plain-text-password
New password:
Retype new password:

[edit]
root@SURAKARTA# commit
commit complete

[edit]
root@SURAKARTA#
root@SURAKARTA# exit
Exiting configuration mode
root@SURAKARTA> quit

Reboot the system? [y/n]y


http://www.juniper.net/techpubs/software/junos/junos81/jweb81-user-guide/jN23F2A.html