[Asterisk-Users] hdlc setup routing question

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Mon Jun 7 21:24:28 MST 2004


On Monday 07 June 2004 17:22, Michael A Rowley wrote:
<snip>
> WAN IP’s   Far end (Gateway) 209.26.250.73
>                       Near end (local interface) 209.26.250.74
>                       Subnet mask 255.255.255.252
>                       Encapsulation Frame Relay
>                       Maintenance Protocol ANNEX D (ANSI)
>                       DLCI 44
> Ethernet IP on Router is 209.26.224.33  subnet mask 255.255.255.248
> Usable IP’s are 209.26.224.34  to 209.26.224.38
> DNS servers
>    Primary     138.210.81.3
>    Secondary  205.160.188.2
>
> So, I need pointopoint from 209.26.250.74 to 209.26.250.73...
>
> Now, 209.26.250.74 belongs to sprint... I can't use it... but it is
> being assigned to pvc0 to complete the point to point protocol for
> frame relay.
>
> 209.26.224.33 is the router IP address that sprint set up on my
> adtran. Thats fine.  So I need the ip address for my box to
> actually be 209.26.224.33 so that I can actually reach it... I
> tried the setup without 209.26.224.33, but I could not reach the
> box at all at 209.26.250.74.  It would respond to a ping, but could
> not ssh into it, or anything else.  My guess is that 209.26.250.74
> is protected by a firewall at sprint, and 209.26.224.33-38 (my ip
> addresses) are set up as DMZ's.
>
> With this setup, I can ssh 209.26.250.74, if 209.26.224.33 is set
> up, but not without it.....

The route(8) command is deprecated.  Don't use it.  What you should
be using instead is the "ip route" command:

# ip route add default via 209.26.250.74 src 209.26.224.33

This sets packets originating on your gateway machine to have the
source address of 209.25.224.33 even if the packets are going out the
interface with the 209.26.250.74 address.

-- 
Tilghman



More information about the asterisk-users mailing list