I was going through some TCP windowing over a high speed WAN link, and thought it might be worth to post some info regarding this.

We do face a typical problem of having slow speed file transfer even if the dedicated pipe is capable of supporting it.

There are three factors which affects this…

1. TCP Window Size.
2. Round trip latency of the circuit.
3. Bandwidth of the circuit.

Maximum throughput you can get from a line with 10ms latency and a TCP window of 32KB can be calculated with…

32KB –> 32 x 1024 x 8 = 262144 Bits

262144 ÷ 0.01 = 26214400 bps = 26.2144 Mbps

Let’s say we have an OC-3 line, which is at 155 Mbps and a round trip latency of 10ms, and we need to calculate the TCP window size to maximize the throughput…

155.52 x 10⁶ = 155520000 bps

TCP_WINDOW = 155520000 x 0.01 = 1555200 Bits = 194400 Bytes = 189.84375 KB

Hope I got the calculation right

Multilink is a way of bundling more than one PPP WAN links and bundle them together into one logical interface. This is one of the method you can implement when you have a primary and secondary links in place and create a logical conduit where both links are present.

This method can be used to load balance data across the links and at the same time it will support redundancy when one one link fails.

I have tested this configuration on 2 of my 2500 Routers and I haven’t tested these on more recent IOS so some commands may vary. I will be checking them on a pair of 3845s/2691s on a later date and will add my findings to this post.

As you can see the Diagram, I am using R4 and R5 which are connected via Serial 0 and Serial 1 respectivly.

R4 Configuration

Multilink Interface
interface Multilink1
ip address 172.16.1.1 255.255.255.252
ppp multilink
ppp multilink links maximum 2
ppp multilink links minimum 1
ppp multilink group 1

Serial 0

interface Serial0
no ip address
encapsulation ppp
clock rate 64000
ppp multilink
ppp multilink group 1

Serial 1

interface Serial1
no ip address
encapsulation ppp
clock rate 64000
ppp multilink
ppp multilink group 1

As you can see, since this is a lab scenario, I have set the clock rate on the link. If you are setting this up on a WAN link, you don’t need to do this as the circuit provider would be setting this up for you.

Also another thing to watch out for is to create the Multilink interface first then move onto configuring the Serial interfaces. If you do the other way around, it will not allow you to set the multilink group as it is not present on the router (See the error message below).

R4(config-if)#ppp multi gr 1
% Cannot set multilink group. Interface Multilink1 does not exist

That is all to watch out for and you can see my R5 configuration below…

R5 Configuration

Multilink

interface Multilink1
ip address 172.16.1.2 255.255.255.252
ppp multilink
ppp multilink links maximum 2
ppp multilink links minimum 1
ppp multilink group 1

Serial 0

interface Serial0
no ip address
encapsulation ppp
ppp multilink
ppp multilink group 1

Serial 1

interface Serial1
no ip address
encapsulation ppp
ppp multilink
ppp multilink group 1

Here is how it should look…

R4#sh ip int br | i up
Multilink1    172.16.1.1    YES   manual  up  up
Serial0       unassigned    YES   manual  up  up
Serial1       unassigned    YES   manual  up  up

R5#sh ip int br | i up
Multilink1    172.16.1.2    YES   manual  up  up
Serial0       unassigned    YES   manual  up  up
Serial1       unassigned    YES   manual  up  up

R4#ping 172.16.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/44/52 ms
R4#

Now I will bring Serial 0 interface down and test the Multilink…

R4(config)#int se0
R4(config-if)#shut
R4(config-if)#

*Mar  1 01:19:41.123: %LINK-5-CHANGED: Interface Serial0, changed state to administratively down
*Mar  1 01:19:42.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down

R4(config-if)#do sh ip int br
Interface     IP-Address   OK?    Method  Status              Protocol
Ethernet0     unassigned   YES    NVRAM   administratively    down  down
Multilink1    172.16.1.1   YES    manual  up                  up
Serial0       unassigned   YES    manual  administratively    down  down
Serial1       unassigned   YES    manual  up                  up

R4(config-if)#do ping 172.16.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/36 ms
R4(config-if)#

As you can see, it works even when one interface is down…

Frame-Relay is one of the core concept of networking and nowadays it is one of the under appreciated part on modern networking.

I am just going to go over how to configure it using 4 Routers and one will act as a Frame-Relay cloud.

Before I go ahead and explain the configuration, You can see the below diagram which represents the physical topology.

As you can see, FRS is connected via…

Serial 1/1 to R1 Serial 1/0
Serial 1/2 to R2 Serial 1/0
Serial 1/3 to R3 Serial 1/0

Now we have got the physical topology clear, we will move onto Frame-Relay configuration and the DLCI assignment.

As you can see the DLCI configuration…

On R1 : DLCI 122 is connected to R2 and DLCI 123 is connected to R3
On R2 : DLCI 221 is connected to R1
On R3: DLCI 321 is connected to R3.

If you are configuring the DLCI then I would suggest you follow this method of numbering, Because from the DLCI Number, I can simply distinguish where the DLCI is connecting to…

For Example, we will take DLCI 122 (One Two Two ) I remember it as; From Router One 2 Two and the same goes for DLCI 321 (Three Two One) Router Three 2 One.

Here are the configuration on the FRS (Please see the first diagram for interface info…)

Serial 1/1

interface Serial1/1
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 64000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 122 interface Serial1/2 221
frame-relay route 123 interface Serial1/3 321

Serial 1/2

interface Serial1/2
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 64000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 221 interface Serial1/1 122

Serial 1/3

interface Serial1/3
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 64000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 321 interface Serial1/1 123

As you can see, if you are configuring Frame-Relay you should understand what every command does and I will be writing a more detailed post on Frame-Relay switching where all of these commands will be covered.

Now the FRS is set, we will go ahead and configure each interface of the routers R1, R2 and R3.

R1

interface Serial1/0
ip address 172.16.10.1 255.255.255.0
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
no fair-queue
frame-relay map ip 172.16.10.2 122 broadcast
frame-relay map ip 172.16.10.3 123 broadcast
no frame-relay inverse-arp

R2

interface Serial1/0
ip address 172.16.10.2 255.255.255.0
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
no fair-queue
frame-relay map ip 172.16.10.1 221 broadcast
frame-relay map ip 172.16.10.3 221 broadcast
no frame-relay inverse-arp

R3

interface Serial1/0
ip address 172.16.10.3 255.255.255.0
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
no fair-queue
frame-relay map ip 172.16.10.1 321 broadcast
frame-relay map ip 172.16.10.2 321 broadcast
no frame-relay inverse-arp

The most important commands are “Frame-Relay Map” on the Routers and the “Frame-Relay Route” command on the Frame switching router.

As you can see, I have the Broadcast option at the end of the “frame-relay map” command; It is there to allow routing packets such as RIP to be passed through the Frame network. Without this option, it will not allow IP traffic to be switch through frame network.

If you don’t get the DLCI mapping correct, you will not get the circuit to come “active”

You can check the Frame route by issuing the “show frame-relay route” command on FRS.

FRS#sh fr ro
Input Intf   Input Dlci   Output Intf   Output Dlci   Status
Serial1/1    122          Serial1/2     221           active
Serial1/1    123          Serial1/3     321           active
Serial1/2    221          Serial1/1     122           active
Serial1/3    321          Serial1/1     123           active
FRS#

And “show frame-relay map” on the Routers (R1, R2, R3)

R1#sh frame map
Serial1/0 (up): ip 172.16.10.2 dlci 122(0x7A,0x1CA0), static,
broadcast,
CISCO, status defined, active
Serial1/0 (up): ip 172.16.10.3 dlci 123(0x7B,0x1CB0), static,
broadcast,
CISCO, status defined, active

R2#sh frame map
Serial1/0 (up): ip 172.16.10.1 dlci 221(0xDD,0x34D0), static,
broadcast,
CISCO, status defined, active
Serial1/0 (up): ip 172.16.10.3 dlci 221(0xDD,0x34D0), static,
broadcast,
CISCO, status defined, active

R3#sh frame map
Serial1/0 (up): ip 172.16.10.1 dlci 321(0x141,0x5010), static,
broadcast,
CISCO, status defined, active
Serial1/0 (up): ip 172.16.10.2 dlci 321(0x141,0x5010), static,
broadcast,
CISCO, status defined, active

If it says “inactive” or “deleted”, I would first check the DLCI assignment and encapsulation and so forth…

And it is always nice to see the following message…

*Mar  1 00:00:21.005: %FR-5-DLCICHANGE: Interface Serial1/1 - DLCI 122 state changed to ACTIVE
*Mar  1 00:00:21.005: %FR-5-DLCICHANGE: Interface Serial1/1 - DLCI 123 state changed to ACTIVE
*Mar  1 00:00:21.098: %FR-5-DLCICHANGE: Interface Serial1/2 - DLCI 221 state changed to ACTIVE
*Mar  1 00:00:21.146: %FR-5-DLCICHANGE: Interface Serial1/3 - DLCI 321 state changed to ACTIVE

All broadcasts messages are dropped by the router when it receives on an interface. This specific command is enables the router to convert the broadcast messages distended for a specific destination into unicast. This interface level command needs to be applied on the interface which the broadcast receives from.

R1(config-if)#ip helper-address 10.10.10.10

Also there are other options where you point the address to a vrf etc…

The following broadcasts are forwarded by default…

TIME – Port 37
TACACS – Port 49
DNS – Port 53
BOOTP/DHCP Server – Port 67
BOOTP/DHCP Client – Port 68
TFTP – Port 69
NetBIOS Name Service – Port 137
NetBios Datagram Service – Port 138

Other protocols can be forwarded by using the following Global config commanding…

R1(config)#ip forward-protocol udp ?

Use the ? to see the supported protocols. You may use the following command to remove a specific protocol being forwarded…

R1(config)#no ip forward-protocol udp ?

There are many free TFTP server sortware out there, just install one.

First of all, make sure you have IP reachablity to the TFTP Server. You can do that via Ping…

Then check whether TCP port 69 is open. Usually it is not the case, but when it comes to troubleshooting, it is the first thing to check after a succesful Ping test.

Jump onto the router you are going to do the IOS upgrade.

Make sure the IOS you are going to replace it with is compatible with your router & also you have the necessary Flash / RAM.

If your Flash is big enough to have more than two IOS images, then you can straight away go and download it from the TFTP Server.

If you are going to have two IOS images in flash, you need to specify the router which image to load on boot. It can be done via the following command…

boot system flash IMAGE_NAME_HERE

Example:
Router(config)#boot system flash c2691-adventerprisek9_ivs-mz.124-15.T9.bin
If the flash is not big enough to have both images, you need to delete the old image.

I usually use the command show flash: then delete the content via the command delete flash:

You can see an example here…

Router#show flash: all
-#- --length-- -----date/time------ path
1 32293924 Mar 1 1993 00:23:52 +00:00 c2691-adventerprisek9-mz.124-5a.bin
31739904 bytes available (32296960 bytes used)
Router#delete flash:
Delete filename []? c2691-adventerprisek9-mz.124-5a.bin
Delete flash:c2691-adventerprisek9-mz.124-5a.bin? [confirm]
Router#
Router#
Router#
Router#show flash:
No files on device
64036864 bytes available (0 bytes used)

Now copy the IOS image from the TFTP Server

Copy tftp: flash:

Example here…

Router#copy tftp: flash:
Address or name of remote host []? 192.168.1.100
Source filename []? c2691-adventerprisek9_ivs-mz.124-15.T9.bin
Destination filename [c2691-adventerprisek9_ivs-mz.124-15.T9.bin]?
Accessing tftp://192.168.1.100/c2691-adventerprisek9_ivs-mz.124-15.T9.bin...
Loading c2691-adventerprisek9_ivs-mz.124-15.T9.bin from 192.168.1.100 (via FastEthernet0/1): !!!!!!!!!!

Sometimes the router might ask you to erase Flash: but I usually do that…

Reload the router and it should be able to run the new IOS Image.

If you happen to have more than one IOS on Flash: You can hardcode which version of IOS to load with the global config command.

Router(config)#boot system flash c2691-adventerprisek9_ivs-mz.124-15.T9.bin

Sky Broadband is aimed for home users thus a few features like SSH (Port 22), VPN and other tunneling are disabled by the router (NETGEAR DG834GT) they provide. If you want to use these features, you have two choices…

• Use another Router
• Re-flash the firmware of the Sky Router (NETGEAR DG834GT)

Re-flashing the router is risky and I am sure it is against Sky’s Terms and Conditions, because as far as I’m aware, that router is a property of Sky. If you are thinking of doing it, then Good Luck!

Using another router is the smartest thing to do, But for you to use another router, you do need the Sky Username and Password.

This is how you get the Sky Username and Password…

Open up your browser and Copy and paste the following URL to the Address Bar. (Make sure its in one line, not two!)

http://192.168.0.1/setup.cgi?todo=ping_test&c4_IPAddr=%26/bin/grep+ppoa_+/tmp/nvram+%3E+/www/netgear.cfg

It will ask for Username and Password, use the follwoing unless you have changed your Router Login info, then use that.

Username:admin
Password: sky

You will get a page that reads “Usage: ping [OPTION]… host”

Now Copy and paste the following URL to the Web Browser’s Address Bar.

http://192.168.0.1/netgear.cfg

This will then download a config file, “netgear.cfg”

Open the file with wordpad or any other Text Editor.

You should see some text like this below :

pppoa_username=001122aabbcc@skydsl
pppoa_password=a0b1c2d4e5
pppoa_idle=0
pppoa_ipaddr=

That’s it, Use those above info with another router, and you should be able to connect to Sky Broadband.

Since Telewest does not use authentication, it can be a bit puzzling if you are going to share your broadband internet connection via a Router. I will be using a LinkSys WRT54GS as an example…

Before you do that, it is recommend doing the following…

• Turn off your modem and your Router for about 5 minutes so your PC MAC lease will expire so you can use your Router’s MAC

• If you are having MAC address issue, then you can get your Network Card’s MAC Address by going to

Start => type CMD type ipconfig /all

Write it down, login to the router and use the MAC Address Clone Feature. It’s a 12 Digit code, looks something like this 00-04-5B-89-21-7F

If a cable provider does not use Authentication method, the only way to make your router talk to the modem is via Automatic Configuration – DHCP.

It is also possible to do it via Static IP, BUT if you are on a dynamic IP, then the internet connection will not work when your ISP renews your IP.

If you are on a Static IP and the DNS / Default gateway does not change, then you can hook your modem directly to the PC, go to

Start => type CMD type ipconfig /all

Write down the values, and enter it in the Static IP setting.

This is how it is done if you are on a Dynamic IP.

Turn off your Modem, Reset your Router, and connect your modem and your PC to your router. Then select Automatic Configuration – DHCP Setting.

That’s it, with a bit of luck, you should have an active internet connection via the Router!