Hi,

i'm working in an office, where right now there is an old DOS based computer with IPRoute (http://www.jacco2.dds.nl/isdn/ipr_ispa.html) running which connects our subnet to the internet. The subnet is part of a bigger network in our building providing just the internet for us. We are in no other way connected.

we now want to get rid of the old 486er pc and replace it with the draytek vigor 2820n. but i'm stuck in the configuration process.

this is how the actual config with iproute looks like:

packet en0 0x62 192.168.0.1/24
packet en1 0x63 192.168.180.253/24
nat en1 * * 192.168.180.253
route * en1 192.168.180.254 metric 1
rip en0

and this is the actual routing table:

Destination Interface: Router:
C 192.168.0.0/24 en0
C 192.168.180.0/24 en1
S default en1 192.168.180.254


i'm using wan2 with static IP adress. it says i am connected to the internet. but ping and whatsoever is not working... you got any hints, on how to configure the draytek?


thank you in advance.

regards mob

some infos about the iproute config:

route [] [metric ]
[preference ] [perm] [label ]

Adds a static route to the routing table. The "perm"
qualifier is required if packets are to be routed to
an interface that is not encapsulating IP (e.g. an
async interface running a script that will dial and
establish a SLIP link when packets are queued to the
interface).

If you are defining a default route then the
parameter should be "*" or "0.0.0.0/0".

The "label" parameter is for use with the "on packet *"
command.

nat

Appends a network address translation rule to the list
for the specified interface. This list is only checked
when a packet that does not match an existing connection
enters or leaves the router on a translated interface.
It is used to control connection establishment. It is
scanned linearly when a new connection is required.

The item specifies the protocols that should be
allowed to open a new connection. The following values
are recognized: "tcp", "udp", "icmp", "igmp", "ip-ip",
"esp" or "*" to match any recognized protocol.

The item specifies the internal machine
and/or port numbers that should be allowed access. On
outgoing connections, both the address and port can be
"*" to indicate any internal machine and/or port. On
incoming connections the address can only be "*" if the
external address is also "*" (this implies that the same
addresses must be used inside and out). The port number
on incoming connections can likewise only be "*" if the
external port number is the same (and this disables port
number translation).

The item specifies the address and/or
port numbers that should be used on the externally
visible network. The address and port must always be
fully specified unless they are the same internally and
externally. This is only useful for filtering traffic
based on established and approved connection information.
This can be useful because it provides a kind of dynamic
filtering that classic packet filtering can't do.

The following example commands allow for a single external
address, 192.0.2.1, and an internal network 192.168.0.0.
All outgoing connections from the internal network are
permitted, plus SMTP mail from the outside is delivered
to 192.168.0.5, and FTP connections from the outside are
delivered to 192.168.0.9, and pings can be responded to.
All other incoming connections will be dropped. Note that
the third line isn't strictly needed. It establishes that
outgoing FTP data connections from the internal FTP host
will use port 20 externally. This helps keep all sorts of
filtering and translating schemes that depend on this
behavior happy.

nat sl0 tcp 192.168.0.5:25 192.0.2.1:25
nat sl0 tcp 192.168.0.9:21 192.0.2.1:21
nat sl0 tcp *:20 192.0.2.1:20
nat sl0 icmp 192.0.2.1 192.0.2.1
nat sl0 * * 192.0.2.1


packet [broadcast ] [mtu ]

Configures a device interfaced by a packet driver for
use by the router. At present, only ethernet (class 1)
packet drivers are supported.

The example below configures a packet driver using the
standard software interrupt 0x60, and indicates that the
interface IP address is 192.168.1.254, and the network
mask is 255.255.255.0. By default the MTU is set to 1500
and 255.255.255.255 is used as the broadcast address.

packet en0 0x60 192.168.1.254/24


rip [default] [preference ] [quiet] [{v1,v2,off}]

Turns on/off RIP broadcasts on the specified interface. By
default, the entire routing table will be sent in version
1 responses. The "v2" qualifier causes RIP version 2
responses to be sent, but still broadcasts rather than
multicasts. The "default" qualifier causes only a default
route to be broadcast rather than the real routing table.
The "preference" option specifies the administrative
preference to be assigned to routes learned via RIP on this
interface. The "quiet" qualifier causes routes to be
learned but not distributed on this interface.

give wan2 a static ip of 192.168.180.253 (or whatever you have been assigned on that subnet)

Set up a static route on WAN 2 interface as destination 0.0.0.0 subnet mask 0.0.0.0 going to 192.168.180.254.

Set all clients to use the LAN ip of the router.

if this doesn't work can you post what ping message you get back? Destination host unreachable usually points to a routing problem.