I've found the problem and here is my testing:
I pluged the DSL line to one of the LAN port (as a WAN) and I could have internet now! Don't know why~ But at least I could use the LAN as WAN finally. Still hope someone could fix it though~
I don't know this exact case, but usually if you connect the WAN cable to one of the LAN ports, the device functions as a simple switch, with no routing/NAT etc. at all. Maybe this is why your problem is solved. How many clients are connected to the box?
Does not work for me, as it says local nameserver (192.168.2.1) is different than default gateway (192.168.1.1). I use RT-N13U as repeater and it has to be in different subnet.
Because i remove one line from it, it use netstat for geting the gateway (netstat is not available in fw).
You may edit "my" script by vi ang change GATEWAY= ...
Joined: 07 May 2010 Posts: 384 Location: Surgut, Western Siberia
Posted: Sat Jun 26, 2010 8:29 Post subject:
gouryella wrote:
Because i remove one line from it, it use netstat for geting the gateway (netstat is not available in fw).
You may edit "my" script by vi ang change GATEWAY= ...
Thanks for the tip now ftp works fine but not samba\swat. May be there's something else to be edited? Also I dont completly understand why should I remove samba's startup script (rm /opt/etc/init.d/S80samba)
Joined: 06 Mar 2010 Posts: 107 Location: Plzeň, CZE
Posted: Sat Jun 26, 2010 9:49 Post subject:
nihilo666 wrote:
gouryella wrote:
Because i remove one line from it, it use netstat for geting the gateway (netstat is not available in fw).
You may edit "my" script by vi ang change GATEWAY= ...
Thanks for the tip now ftp works fine but not samba\swat. May be there's something else to be edited? Also I dont completly understand why should I remove samba's startup script (rm /opt/etc/init.d/S80samba)
Samba, vsftpd, tftpd, swat start from xinetd (in some smb cases could be problem but im using this for ages on wl-500gP too)
Debug by:
Joined: 06 Mar 2010 Posts: 107 Location: Plzeň, CZE
Posted: Sat Jun 26, 2010 17:13 Post subject:
nihilo666 wrote:
I think the reason is you have not folder /opt/bin/busybox
And I thing that swap cannot be posible with the r14594 firmware.
Code:
root@dd-wrt:~# mkswap /dev/discs/disc0/part2
Setting up swapspace version 1, size = 65798144 bytes
root@dd-wrt:~# swapon /dev/discs/disc0/part2
swapon: /dev/discs/disc0/part2: Function not implemented
I think the reason is you have not folder /opt/bin/busybox
And I thing that swap cannot be posible with the r14594 firmware.
Code:
root@dd-wrt:~# mkswap /dev/discs/disc0/part2
Setting up swapspace version 1, size = 65798144 bytes
root@dd-wrt:~# swapon /dev/discs/disc0/part2
swapon: /dev/discs/disc0/part2: Function not implemented
I've found the problem and here is my testing:
I pluged the DSL line to one of the LAN port (as a WAN) and I could have internet now! Don't know why~ But at least I could use the LAN as WAN finally. Still hope someone could fix it though~
I don't know this exact case, but usually if you connect the WAN cable to one of the LAN ports, the device functions as a simple switch, with no routing/NAT etc. at all. Maybe this is why your problem is solved. How many clients are connected to the box?
Thanks! But My situation is that only one Lan port(specific one) becomes Wan port not all can, so probably not becomes a switch. Also, FYI, I only have a client connecting to the box.
Thanks! But My situation is that only one Lan port(specific one) becomes Wan port not all can, so probably not becomes a switch. Also, FYI, I only have a client connecting to the box.
If the client's IP address is from the 192.168.x.x pool, then the router is actually routing.
BTW, has anybody figured out how to get the swapfile working?
