howto's

for DSM6 edit the file: /etc/samba/smb.conf,
for DSM5: /usr/syno/etc/smb.conf
add in [GENERAL] max xmit = 4096
to commit the changes, disable/enable samba from control panel/file services or reboot the nas.

also adjust the mss clamping on vpn traffic around the value 1300

oke, after u setup the vpn and you get it working:
enable telnet/ssh on synology box
login into synology
type ifconfig
you should see an pppx interface:

ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.1.44 P-t-P:192.168.1.99 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1396 Metric:1
RX packets:1819 errors:0 dropped:0 overruns:0 frame:0
TX packets:1372 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1694061 (1.6 MiB) TX bytes:236202 (230.6 KiB)

you need the P-t-P ip: in this case is 192.168.1.99

vi /etc/ppp/ip-up

add at the end of file:

#added for vpn routes
case "${IPREMOTE}" in
192.168.1.99)
ip ro add 1.2.3.4/24 dev ${IFNAME}
ip ro add 2.3.4.0/24 dev ${IFNAME}
;;
esac

restart vpn from control panel:
you should see already the new routes:

nas> ip route show
192.168.1.99 dev ppp0 src 192.168.1.44
|ip of vpn server| via |default gw| dev eth0 src |ip of syno|
|local subnet|/24 dev eth0
1.2.3.4/24 dev ppp0
2.3.4.0/24 dev ppp0
default via |gateway| dev eth0


Each and every zone file has a unique serial number and that serial number should increment with each subsequent revision

A serial number is traditionally in the format (YYYYMMDDSS) where SS the sequence number. For example, today is 6/24/2011, so the serial number in a zone file modfied today would be… 2011062400.

So let’s say that you pushed that zone today and when you went back to make an additional change, you accidentally added an additional number to your serials and instead of 2011062400 you ended up with 22011062400.

In order to get everything back in order you will need to manually reset the zone file’s serial number by setting it to the number below. Its highest number you can get using 32 bits.

4294967295

To to reset your serial number, update your zone file with the serial number listed above and push it out to the slaves. Then change your zone files serial number back to the correctserial number, which will be considered to be greater than the magic number above. Then push dns again.

Check your slave servers and verify the the zone file now has the correct serial.

Original article: http://www.fatmin.com/2011/01/bind-zone-file-serial-number-reset.html

whois -h filtergen.level3.net RIPE::ASXXXX

Hello again! I decided to stop making programming tutorials for a couple of days so in this tutorial you will learn how
to set up NAT Routing on Windows XP. Some of you know that some time ago I was working on a project in Visual Basic 6
that would do this thing. So, in Windows there is a tool that is used to manage network stuff like setting IP Addresses,
set up routing etc. This tool’s name is netsh (short for network shell). Using netsh you will need 2 NICs (Network
Interface Cards), one to connect to the public network(to the Internet) and the other to connect to the private
network(to other computers in LAN). So the network schema will look like this:

As we see, the machine that has 2 NICs will have routing enabled and will be the other client’s gateway. The clients
will connect to their gateway through a switch(if there will be only one client you can use a cross-over cable from
gateway’s private NIC to clients NIC).

Now HOW TO INSTALL IT?
First we open the Control Panel. If you are using the “Category View” to view icons first go to “Performance and
Maintenance” and then “Administrative Tools” otherwise go straight to the “Administrative Tools” then open
“Services”. On the list find “Routing and Remote Access”, double click on it and set the Startup type to
“Automatic” and click OK. Close the Services window and open the registry editor by going to Start > Run… and
typing “regedit” without the “ ”. Click OK and in the window expand to the following path: My Computer >
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip > Parameters. Now in the list you will see something
like “IPEnableRouter”. Double click on it and turn the value from 0 to 1. Now restart your computer.

You must know the names of your adapters you are using. For the tutorial we will use “Wireless Network Connection”
for the public NIC and “Local Area Connection” for the private NIC.

Now we open the command prompt and type the following command to install NAT:

Code:

netsh routing ip nat install

Now type the next command to add the public interface:

Code:

netsh routing ip nat add interface "Wireless Network Connection" full

And the last command to add the private interface:

Code:

netsh routing ip nat add interface "Local Area Connection" private

…and the installation is done!

What about the client’s IP addresses?
Oh yeah! Set an IP to the private NIC of the machine that is doing routing and the clients will use that IP as their
default gateway. The client’s IP addresses must be the same subnet as the gateways. Your public NIC’s IP doesn’t
need to be changed!

Heres an example of an IP configuration:

As you see the public NIC’s IP address on the routing machine is not the same subnet as the private NIC’s IP
address. So be careful, the mustn’t be!

I hope you will find this thread useful and save some money buying routers. If you want to set up a wireless router then
check the tutorials session later because I’ll be talking about creating ad-hoc wireless networks on Windows XP.

PS: I’m sorry if you don’t like my computers on the schemes, I’ve drawn them in Paint, lol

Best wishes,
Dren

Solution

This example will change the ethernet device with name dev12345 to eth0 and assumes eth0 currently does not exist.
Down the device before changing any files with the command # ifdown dev12345. Also remove the kernel module which is
referenced against this device in the /etc/modprobe.conf. In this example there is a line which has “alias dev12345
e1000“, so perform “#rmmod e1000“. It may also be necessary to run “#ifdown ” on any other network devices using this
kernel module. If this step is skipped it may be necessary to undo any file name changes including setting up the
ifcfg-dev12345 file as mentioned below.
Modify the file /etc/sysconfig/hwconf replacing ifcfg-dev12345 with ifcfg-eth0. If this file doesn’t exist ignore this
step as this file is simply a generated file from the Red Hat Enterprise Linux installation program:
class: NETWORK
bus: PCI
detached: 0
device: eth0
Modify the file /etc/modprobe.conf replacing ifcfg-dev12345 with ifcfg-eth0:
alias eth0 e1000
In the directory /etc/sysconfig/network-scripts/ rename the file ifcfg-dev12345 to ifcfg-eth0. Edit this file replacing
ifcfg-dev12345 with ifcfg-eth0:
DEVICE=eth0
If the system-config-network* tools were used, it may be necessary to remove any file referencing the old device in the
/etc/sysconfig/networking directory. ie.
# find /etc/sysconfig/networking -name ifcfg-dev12345
/etc/sysconfig/networking/profiles/default/ifcfg-dev12345
/etc/sysconfig/networking/devices/ifcfg-dev12345
# rm /etc/sysconfig/networking/profiles/default/ifcfg-dev12345
# rm /etc/sysconfig/networking/devices/ifcfg-dev12345
At this stage it is now possible to up eth0 with the command # ifup eth0.