Not sure I understand what all you are doing here, but you need
your gateway to be on the same subnet as your main ip address.
Why do you assign 2 ip's to your pvc?
If ping's are allow, sometimes it helps to use traceroute to
see the path a packet is taking.
On Mon, 2004-06-07 at 15:21, Michael A Rowley wrote:> Hello All,
>
> I am battling a problem I don't know how to fix... Here is the
> scenario:
>
> Fractionated T1 with 1-6 channels voice, 21-24 channels data.
> Comes into a box with Digium T100P, splits off data channes with HDLC,
> to devicec pvc0,
> This works fine, but I have a routing problem getting to my machines!
>
> Here is the current set up...
>
> sethdlc hdlc0 fr lmi ansi
> sethdlc hdlc0 create 44
> ifconfig hdlc0 up
> ifconfig pvc0 xxx.xxx.250.74 netmask 255.255.255.252 pointopoint
> xxx.xxx.250.73
> ifconfig pvc0:0 xxx.xxx.244.33 netmask 255.255.255.248
>
> route add -default gw xxx.xxx.250.74 metric 1 pvc0
>
> Now, this works, but has some unexpected results.... For example,the
> xxx.xxx.250.74 ip belongs to the phone company, so when I try to use it
> to access my machine, I get no response.... unless I set up the
> alilas to xxx.xxx.244.33, then it works, but not if I access 244.33,
> only if I access 250.74 ???
>
> my routing tables look like this from route:
>
> host72.sprintne * 255.255.255.252 U 0 0 0
> pvc0
> host32.sprintne * 255.255.255.248 U 0 0 0
> pvc0
> 192.168.1.0 * 255.255.255.0 U 0 0 0
> eth0
> loopback asterisk 255.0.0.0 UG 0 0 0
> lo
> default host74.sprintne 0.0.0.0 UG 1 0 0
> pvc0
>
> and from ip route show
>
> xxx.xxx.250.72/30 dev pvc0 proto kernel scope link src xxx.xxx.250.74
> xxx.xxx.224.32/29 dev pvc0 proto kernel scope link src xxx.xxx.224.33
> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1
> 127.0.0.0/8 via 127.0.0.1 dev lo scope link
> default via xxx.xxx.250.74 dev pvc0 scope link metric 1
>
> what I want to be able to do is to ping xxx.xxx.224.33, and have that
> IP respond, then use the other IP addresses that I have avaliable as
> my internal server addresses (for the machines to connect to the
> internet), but until I figure out the routing, I am stuck here... When
> I trace route the xxx.xxx.224.33 address, I get a return of
> xxx.xxx.250.74, when I ping, I get xxx.xxx.250.74, etc.
>
> What I am wondering is if I should not have the system set up more like
> pvc0 ip xxx.xxx.250.74 pointopoint xxx.xxx.250.73
> eth0 ip xxx.xxx.224.33
> eth0:0 192.168.1.1 (for internal routing)
> with routing set up as
> default route xxx.xxx.224.33
> net route xxx.xxx.250.74 src xxx.xxx.244.33
>
> and I am completely baffeled why xxx.xxx.224.72 shows up on the routing
> at all....
>
> This is a wierd setup, and apparently is beyond me... Can anyone help
> me here?
>
> Michael.
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
--
respectfully, Joseph - (606) 477-2355 x140
------=============