Showing posts with label DD-WRT. Show all posts
Showing posts with label DD-WRT. Show all posts

Seagate FAT issue

This Seagate Freeagent Theater is plugged into the following wired network setups:

Going into a Netgear 16-port 100 megabit switch which is uplinked to a Time warner cable router.

The media is pulled from a DD-WRT OPTWARE equipped router running Samba version 3.5.11.

While playing a video file or DVD ISO across the network and the playback will stop. One of the following two things then happens:

A. Video stops for several seconds, stutters some, pauses again and then resumes normal playback. This may happen multiple times during a single media file. Each time playback is interrupted it takes around 10-30 seconds to resume playback.
OR
B. Video stops and then I get this error message
:Media is Removed.
Stop Playback[OK]

Once a time that I noticed FAT+ ip address dropped to none available. I have to reset FAT+ to regain the control of FAT+.
But from local PC, I still can ping and access SAMBA drive.

Possible solution:
  1. Disable torrent downloads, and/or heavy files transfers on the net.
  2. file related, most of the files that freeze up are mkv/avi file, rmvb filrs are OK.
  3. some suggested frame drops caused by imperfect sync between FAT+ and TV,The TV set is not highend model, .the suggestion of Motionflow/Cinemamode/Theater/24p mode on/off  did ring a bell when I test TV setting.
  4. Using composite Video/Audio connection instead HDMI, yet the info that I stump about pin 13 of HDMI cable issue, its worthy noted here."disabling pin 13 on the HDMI cable, see if that fixes the problem. Pin 13 9CEC communication)on the player is sending the wrong signal to HDMI devices."

[Edit]: This media removed message pop up again, before that I noticed there's stop warning sign appear on the left top corner 2 or 3 times. My transmission GUI  traffics were heavily loaded. It also drop FAT+ ip address, just simply power on/off through remote controller will not bring FAT+ unit back with its static IP. I have to unplug and plug in the power cord for it to connect to the network again.
Disable transmission traffic seems to be the temporary solutions for nohow. I will work on balance traffics load later.

Samba. Cannot delete files on network share

Its Samba share on my router-attached NTFS partition.
Keep deny my permission........
Through winscp, this  /opt/etc/smb.conf

"Browseable = yes
Writable = yes
read only = no"

chmod a -R option to make it recursively change permissions on all files/sub-directories.
chmod -R 777 ./data-folder/*
Changing the permissions of the directory is not what you need to do. You need to change the permissions of the SHARE. Think of the share as a layer inbetween the directory and the remote user. The user sees the permissions of the SHARE not the directory. The share only has access to the folder as far as the directory permissions let it.

So if the directory is rwx, the share can do whatever it wants. If the directory is r-x, then the share can at best be r-x, but it can aslo be r-- or --x or ---, but it can never be rwx or -w-, or anything with a write.

These two statements are not so. The Samba server in no way grants or denies permissions for the file system. Samba only authenticates the users access to the share. All authorization is done through the FS permissions. File creation can be controlled Samba with create and dir masks. In my Samba setup I force a common group (smbusers) even if it is a guest (I named smbguest). It's even possible to limit the authenticated users ability to delete files, but this is done using the Linux "sticky bit", not Samba. 

Samba can control the permissions of the share. The path to a Samba share can have a mode of 777 (rwxrwxrwx) but the share definition can limit the share to be read only.

It's just like in Windows if you disable "Simple file sharing" then for each folder you see a Share tab and a Security tab. The Security tab controls the permissions of the folder on the local system while the Share tab controls the effective permissions of a remote user. The Share permissions can be as lenient but no more lenient then the permissions set by the Security tab.

The same goes for Samba. The directory permissions are just the limiting factor. If the OP wants to control the share permissions through the filesystem permissions, then he should enable full read-write access through the share and adjust the filesystem accordingly. What seems to be the case though, is that the default permissions for the Samba share are read-only.

still with smb.conf. You need to change the fmask and dmask of the files that are created. You should want something like read-write for files and read-write-execute for folders. (6 and 7 respectively) Keep in mind that when talking about file permissions, "mask" is the opposite of what you want to take place (so 1 and 0 respectively)

quote the smb.conf man page, "The access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system. The server does not grant more access than the host system grants."

Through webgio 192.168.1.1:901 restarted samba daemons after changing the file settings.

“partition X does not end on cylinder boundary”

I had stump into this issue and alarmed for a while.
Since modern systems use LBA (Logical Block Addressing) instead of CHS (Cylinder/Head/Sector) to address disk drives, as long as there's no overlap between each partition, its fine to have such warning.

The settings saved on this computer does not match the requirements for the network

have a new router installed, my network connection show a bid red x sign on my router's SSID.
following the advice from MS, I removed all of my previous remember router's setting and disable password of my router, then doing research on possible wireless station, I got my router back.

This issue usually occurs on wireless network connections. I suggest that you turn off any security feature of wireless by following the steps below.
1.     Click Start and access Control Panel.
2.     Double-click on Network Connections
3.     Right click on the wireless adapter and select Properties.
4.     Choose Wireless Networks, click on your wireless network name and choose properties.
5.      Under Network Authentication choose Open to turn off the wireless security.
6.     Please try to connect. 
If the issue persists, I suggest that you delete the connection, and recreate the wireless network connections. The following website may help you on creating the wireless connection.
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
If the issue persists, I suggest that you reinstall the wireless adapter driver, and re-create the connection again.
 Remove the adapter driver
========================
1. Click Start. In the Start Search box type "devmgmt.msc" and press Enter.
2. Expand "Network Adapters", double-click on the entry of the wireless network device.
3. Click the tab "Driver", click "Uninstall".
4. Click Start. In the Start Search box type "appwiz.cpl" and press Enter.
5. Remove the entries related to the wireless network adapter.
Then reinstall the driver with your driver CD of from the manufacturer website. After installing, re-create the connection. 
Also access the link and try to follow the steps to troubleshoot network related issues on Vista computer:

DD-WRT telnet to : caused host connection lost

telnet, winscp, putty to DD-wrt caused host connection lost.
with invalid password end up login error, yet right password will cause host connection lost.
reboot router enable telnet,winscp,putty.

Reflash ASUS WL500GP V2 with DD-WRT

dd-wrt:192.168.1.1 255.255.255.0
wl500gp v2 192.168.1.2
255.255.255.0
wireless dhcp 192.168.1.135 255.255.255.0
ethernet dhcp
192.168.1.3 255.255.255.0
RJ45 cable connect pc to wl500gp-v2 lan1, wl500gp v2 wan to dd-wrt lan
ping 192.168.1.1 ok
brower 192.168.1.1 ok
ping 192.168.1.2 ok
brower 192.168.1.2 ok
ping google.com ok
WL-500gP V2's subnet ID and the subnet ID in WAN are the same

solution: instead plugging into router2 wan port, connect router1 lan an port to router2 lan port.

Installation

Connect to the router 2 @ http://192.168.1.1
disconnect this router from the main one or create a static ARP entry.
Open the Setup ; Basic Setup tab
WAN Connection Type : Disabled( ??could I assigned a static IP for it)
Local IP Address: 192.168.1.2 (i.e. different from primary router and out of DHCP pool)
Subnet Mask: 255.255.255.0 (i.e. same as primary router)
DHCP Server: Disable (also uncheck DNSmasq options)
(Recommended) Gateway/Local DNS: IP address of primary router (many things will fail without this)
(Optional) Assign WAN Port to Switch (visible only with WAN Connection Type set to disabled): Enable this if you want to use WAN port as a switch port
(Optional) NTP Client: Enable/Disable (if Enabled, specify Gateway/Local DNS above)
Save
Open the Setup ; Advanced Routing tab
(Optional) Change operating mode to: Router
Save
Open the Wireless ; Basic Settings tab
Wireless Network Name (SSID): YourNetworkNameHere
(Optional) Sensitivity Range: The max distance (in meters) to clients x2
Save
Open the Wireless ; Wireless Security tab
Note: Security is optional, but recommended! Clients must support whatever mode you select here.
(Recommended) Security Mode: WPA2
(Recommended) WPA Algorithm: AES
(Recommended) WPA Shared Key: ;8 characters
Save
Open the Services ; Services tab
(Optional) DNSMasq: Disable
(Optional) ttraff Daemon: Disable
Save
Open the Security ; Firewall tab
Uncheck all boxes except Filter Multicast
Save
Disable SPI firewall
Save
Open the Administration ; Management tab
(Recommended) Info Site Passw
ord Protection: Enable
Under routing select disabled
Apply Settings and connect Ethernet cable to main router via LAN-to-LAN uplink*

Notes:
To connect the WAP to the main router, you can probably use either a patch cable, straight-thru, or a crossover cable. Most DD-WRT capable devices can do auto-sensing so the cable type doesn't usually matter.
You can connect the WAP to the main router via LAN-to-WAN so long as you have assigned the WAN port to switch (see step 3).
There were three basic configuration changes you made to set up your router as a wireless access point.
Turn Off DHCP
If you did not turn off DHCP, when you plug your router into the network (after configuration), your WAP may provide IP addresses to clients on the wired network, and this may be inappropriate. Tracking down problems caused by multiple DHCP servers can be time-consuming and difficult.
Because its so important, it is worth repeating: Turn off DHCP before you continue!
Set the IP address of the LAN Interface
Immediately after turning off DHCP, while your PC still has the IP address the WAP gave you, set the LAN interface of the WAP to the IP address you want it to use, eg. if host router is 192.168.1.1, give WAP an IP of 192.168.1.2. Alternatively, you can use the instructions below to set the WAPs IP address via DHCP.
If you cannot connect to the WAP in order to set the LAN interface's IP address, it is probably because your computer no longer has an IP address on the same subnet. To get past this issue, simply set your computer's IP address and subnet to 192.168.1.8 and 255.255.255.0 respectively. (This assumes you are still using the default settings. If not, change the IP address and subnet as appropriate) You should now be able to point your browser at 192.168.1.1 (again assuming default settings).
LAN Uplink
There are two ways to connect your WAP to the LAN. You can either Uplink through one of the router's LAN ports, or use the WAN port that is normally connected to the cable/DSL modem.
LAN Uplink Through LAN Port
To complete the link between the two routers, connect a LAN port on the central router, to a LAN port on Linksys router (to be used as your WAP). You may need a crossover cable to do this, although many modern routers have an automatic polarity sensing. To test this, connect a standard ethernet cable between the two routers. If the LAN light comes on, the router has automatically switched the polarity and a crossover cable is not required.
LAN Uplink Through WAN Port
If you use your DD-WRT router as a WAP only, you may use your DD-WRT router's WAN port to connect it to your existing LAN. To do this, you need to disable the Internet Connection and "Assign WAN Port to Switch".
Normally, the router does Layer 3 IP routing. but by "Assigning WAN Port to Switch," your DD-WRT router will bypass that functionality and just pass on the Layer 2 ethernet packets from your wired network to the wireless network and vice versa.
Alternatively, if you have a router that supports assigning the WAN port to the switch:
Setup ; Basic Setup ; Internet Connection Type ; Connection Type = Disabled
Setup ; Basic Setup ; Network Setup ; WAN Port ; Assign WAN Port to Switch
you can connect the WAN port as your uplink to your main router. All this really buys you is an extra port (4 available instead of 3), but why not?
Roaming access

If you are installing additional Access Points to cover a broader area with Wi-Fi access, it is possible to allow clients to roam freely between them. The common method is to use the same SSID and Security settings on each access point.
Use a different channel on each AP. e.g. if you are in the US and installed two access points, use channels #1 and #11. Or if three access points, then use channels #1, #6, and #11 (setting the channels at least 5 apart should help keep interference between APs to a minimum). If you have a residential gateway with wireless turned on, and just one AP, then the same applies: each gets a different channel.
When using multiple Access Points, each one should be connected by LAN to LAN uplink as described above. They can even be attached to different switches within the same organization.
How To Use DHCP to Set the WAP's IP Address

Note: This step is optional. It is not required to set the WAP's IP address via DHCP. It can be made static, as shown above.
It is not possible to set the LAN interface to get its IP address via DHCP using the web configuration interface. You can, however, set your startup script to obtain an IP address.
Simply set your IP address to:
udhcpc -i br0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -H test-wrt-wireless
hostname `nslookup \`ifconfig br0 | grep 'inet addr' |cut -f 2 -d ':'\` | grep 'Name:' | awk '{print $2;}' | cut -f 1 -d '.'`
if test `hostname` != `nvram get wan_hostname`; then
     nvram set wan_hostname=`hostname`;
     nvram set router_name=`hostname`;
     nvram commit;
fi
Only the first line is required if you don't want your WAP to set its name based on the IP address it gets. However, if you want to save a configuration file which will apply to several WAPs, that can be a handy feature.
It seems that in some cases, the /tmp/udhcpc link doesn't exist. in that case, prepend:
ln -s /sbin/rc /tmp/udhcpc
to your startup script.
[edit]Related Forum links

Secure remote management for a WAPInstallation

Connect to the router 2 @ http://192.168.1.1
disconnect this router from the main one or create a static ARP entry.
Open the Setup ; Basic Setup tab
WAN Connection Type : Disabled
Local IP Address: 192.168.1.2 (i.e. different from primary router and out of DHCP pool)
Subnet Mask: 255.255.255.0 (i.e. same as primary router)
DHCP Server: Disable (also uncheck DNSmasq options)
(Recommended) Gateway/Local DNS: IP address of primary router (many things will fail without this)
(Optional) Assign WAN Port to Switch (visible only with WAN Connection Type set to disabled): Enable this if you want to use WAN port as a switch port
(Optional) NTP Client: Enable/Disable (if Enabled, specify Gateway/Local DNS above)
Save
Open the Setup ; Advanced Routing tab
(Optional) Change operating mode to: Router
Save
Open the Wireless -> Basic Settings tab
Wireless Network Name (SSID): YourNetworkNameHere
(Optional) Sensitivity Range: The max distance (in meters) to clients x2
Save
Open the Wireless ; Wireless Security tab
Note: Security is optional, but recommended! Clients must support whatever mode you select here.
(Recommended) Security Mode: WPA2
(Recommended) WPA Algorithm: AES
(Recommended) WPA Shared Key: >8 characters
Save
Open the Services ; Services tab
(Optional) DNSMasq: Disable
(Optional) ttraff Daemon: Disable
Save
Open the Security ; Firewall tab
Uncheck all boxes except Filter Multicast
Save
Disable SPI firewall
Save
Open the Administration ; Management tab
(Recommended) Info Site Passw
ord Protection: Enable
Under routing select disabled
Apply Settings and connect Ethernet cable to main router via LAN-to-LAN uplink*

Notes:
To connect the WAP to the main router, you can probably use either a patch cable, straight-thru, or a crossover cable. Most DD-WRT capable devices can do auto-sensing so the cable type doesn't usually matter.
You can connect the WAP to the main router via LAN-to-WAN so long as you have assigned the WAN port to switch (see step 3).
[edit]Review

There were three basic configuration changes you made to set up your router as a wireless access point.
[edit]Turn Off DHCP
If you did not turn off DHCP, when you plug your router into the network (after configuration), your WAP may provide IP addresses to clients on the wired network, and this may be inappropriate. Tracking down problems caused by multiple DHCP servers can be time-consuming and difficult.
Because its so important, it is worth repeating: Turn off DHCP before you continue!
[edit]Set the IP address of the LAN Interface
Immediately after turning off DHCP, while your PC still has the IP address the WAP gave you, set the LAN interface of the WAP to the IP address you want it to use, eg. if host router is 192.168.1.1, give WAP an IP of 192.168.1.2. Alternatively, you can use the instructions below to set the WAPs IP address via DHCP.
If you cannot connect to the WAP in order to set the LAN interface's IP address, it is probably because your computer no longer has an IP address on the same subnet. To get past this issue, simply set your computer's IP address and subnet to 192.168.1.8 and 255.255.255.0 respectively. (This assumes you are still using the default settings. If not, change the IP address and subnet as appropriate) You should now be able to point your browser at 192.168.1.1 (again assuming default settings).
[edit]LAN Uplink
There are two ways to connect your WAP to the LAN. You can either Uplink through one of the router's LAN ports, or use the WAN port that is normally connected to the cable/DSL modem.
[edit]LAN Uplink Through LAN Port
To complete the link between the two routers, connect a LAN port on the central router, to a LAN port on Linksys router (to be used as your WAP). You may need a crossover cable to do this, although many modern routers have an automatic polarity sensing. To test this, connect a standard ethernet cable between the two routers. If the LAN light comes on, the router has automatically switched the polarity and a crossover cable is not required.
[edit]LAN Uplink Through WAN Port
If you use your DD-WRT router as a WAP only, you may use your DD-WRT router's WAN port to connect it to your existing LAN. To do this, you need to disable the Internet Connection and "Assign WAN Port to Switch".
Normally, the router does Layer 3 IP routing. but by "Assigning WAN Port to Switch," your DD-WRT router will bypass that functionality and just pass on the Layer 2 ethernet packets from your wired network to the wireless network and vice versa.
Alternatively, if you have a router that supports assigning the WAN port to the switch:
Setup -> Basic Setup -> Internet Connection Type -> Connection Type = Disabled
Setup -> Basic Setup -> Network Setup -> WAN Port -> Assign WAN Port to Switch
you can connect the WAN port as your uplink to your main router. All this really buys you is an extra port (4 available instead of 3), but why not?
[edit]Roaming access

If you are installing additional Access Points to cover a broader area with Wi-Fi access, it is possible to allow clients to roam freely between them. The common method is to use the same SSID and Security settings on each access point.
Use a different channel on each AP. e.g. if you are in the US and installed two access points, use channels #1 and #11. Or if three access points, then use channels #1, #6, and #11 (setting the channels at least 5 apart should help keep interference between APs to a minimum). If you have a residential gateway with wireless turned on, and just one AP, then the same applies: each gets a different channel.
When using multiple Access Points, each one should be connected by LAN to LAN uplink as described above. They can even be attached to different switches within the same organization.
[edit]How To Use DHCP to Set the WAP's IP Address

Note: This step is optional. It is not required to set the WAP's IP address via DHCP. It can be made static, as shown above.
It is not possible to set the LAN interface to get its IP address via DHCP using the web configuration interface. You can, however, set your startup script to obtain an IP address.
Simply set your IP address to:
udhcpc -i br0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -H test-wrt-wireless
hostname `nslookup \`ifconfig br0 | grep 'inet addr' |cut -f 2 -d ':'\` | grep 'Name:' | awk '{print $2;}' | cut -f 1 -d '.'`
if test `hostname` != `nvram get wan_hostname`; then
     nvram set wan_hostname=`hostname`;
     nvram set router_name=`hostname`;
     nvram commit;
fi
Only the first line is required if you don't want your WAP to set its name based on the IP address it gets. However, if you want to save a configuration file which will apply to several WAPs, that can be a handy feature.
It seems that in some cases, the /tmp/udhcpc link doesn't exist. in that case, prepend:
ln -s /sbin/rc /tmp/udhcpc
to your startup script.
[edit]Related Forum links

Secure remote management for a WAP

Brick my WL500GP v2

WL-500gP V2's subnet ID and the subnet ID in WAN are the same.

reflashing my wl500gpv2 with all versions of firmware images from http://support.asus.com/download/ but unfortunately could not login to no one of them with default user/pass admin/admin to web interface. Also tried some standard combinations root/admin root/root root/password ..

Recovery!!:
-----------
1. pull power cable and wait 20 seconds
2. keep button pressed and connect power cable: power led should flash
3. ping 192.168.1.1 should reply else redo steps 1 and 2
4. run Asus Firmware restoration tool, select firmware file (e.g. wg01080109_WL500g_EN.trx) and press upload.
After some seconds press the Abort button or wait until it says "Upload fails! Please check the connection"
5. from a dos box or linux console run: tftp -i 192.168.1.1 put wg01080109_WL500g_EN.trx
6. tftp returns something like: "Transfer successful: 3731456 bytes in 2 seconds, 1865728 bytes/s" if it doesn't redo steps 1-5 (sometimes I needed three or four times before it worked)
7. after ca. 80 seconds your Asus should reboot

I did this procedure with
1. wl500g-clear-nvram.trx
2. wl500g-recover.trx
Then I could flash any firmware and the device was alive again.....