Re: [Asterisk-Users] hdlc setup routing question
Hey Vasyl, Yup, this is exactly what I have... :) the hdlc stuff works great... It is the routing of the network that is driving me nuts since the set up that Sprint gave me was: 209.26.25074 pointopoint 209.26.250.73, adtran router 209.26.224.33, usable IP's as you said, 209.26.224.34/29, I wanted to match this setup as much as possible But I can't seem to figure out how to set the system up that way with asterisk... It is a firewall, and routing problem. Complex, and I think just beyond me. I can hit the server at 209.26.250.74 with ssh, and I guess I will have to live with that. If sprint gets pissed cause I am hitting 'their' IP, I will deal with it at that time... Thanks for the help... M On Monday, June 7, 2004, at 10:28 PM, Vasyl Rublyov wrote: Michael, I see that you configurataion is FR, and your router (with t100p) should have 209.26.250.74 and P2P end shoud be 209.26.250.74. Usually they are both belongs to ISP (in this case to Sprint), but your Ethernet end is 209.26.224.34/29. Michael Rowley MD FP
Re: [Asterisk-Users] hdlc setup routing question
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 00 pvc0 host32.sprintne * 255.255.255.248 U 0 00 pvc0 192.168.1.0 * 255.255.255.0 U 0 00 eth0 loopbackasterisk255.0.0.0 UG0 00 lo default host74.sprintne 0.0.0.0 UG1 00 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 [EMAIL PROTECTED] 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 --= ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] hdlc setup routing question
Ok, I guess I wasn't clear enough I keep doing that Here is what I recieved from sprint... Linecode B8ZS Format ESF Timing from Network If you are having any Internet issues call and report this circuit ID to (800) 603-8044 option 4, option 3, option1. Circuit ID (FRAME) 60.YGFS.576125.UFLG Order Number N495625 WAN IPs 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 IPs 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. M On Monday, June 7, 2004, at 03:51 PM, Joseph wrote: 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. Michael Rowley MD FP
Re: [Asterisk-Users] hdlc setup routing question
Michael,
I see that you configurataion is FR, and your router (with t100p)
should have 209.26.250.74 and P2P end shoud be 209.26.250.74.
Usually they are both belongs to ISP (in this case to Sprint), but your
Ethernet end is 209.26.224.34/29.
Hope this will work for you;
MODE=fr
LOCAL_IPADDR=209.26.250.74
REMOTE_IPADDR=209.26.250.73
NETWORK=209.26.250.72
NETMASK=255.255.255.252
GATEWAY=209.26.250.73
# FR
FR_LMI=ansi
FR_PVC=pvc0
FR_DLC=44
/sbin/modprobe zaptel
/sbin/modprobe wct1xxp
/sbin/modprobe hdlc
/sbin/ztcfg -vvv
sethdlc-1.15 ${DEVICE} ${MODE} lmi ${FR_LMI}
sethdlc ${DEVICE} create ${FR_DLC}
ifconfig ${DEVICE} up
ifconfig ${FR_PVC} ${LOCAL_IPADDR} pointopoint ${REMOTE_IPADDR}
route add -net ${NETWORK} netmask ${NETMASK} ${FR_PVC}
route add default gw ${GATEWAY} metric 1 ${FR_PVC}
# 209.26.224.33 belongs to your eth0 device.
ifconfig eth0 209.26.224.33 netmask 255.255.255.248
route add -net 209.26.224.32 netmask 255.255.255.248 dev eth0
=== /etc/zaptel.conf should be like this:
loadzone = us
defaultzone=us
span=1,1,0,esf,b8zs
nethdlc=21-24
.
also check /proc/sys/net/ipv4/ip_forward - it should be 1
Michael A Rowley wrote:
Ok, I guess I wasn't clear enough I keep doing
that Here is
what I recieved from sprint...
Linecode B8ZS
Format ESF
Timing from Network
If you
are having any Internet issues call and report this circuit ID to
(800) 603-8044 option 4, option 3, option1.
Circuit ID
(FRAME) 60.YGFS.576125.UFLG
Order Number N495625
WAN IPs 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 IPs 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.
M
On Monday, June 7, 2004, at 03:51 PM, Joseph wrote:
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.
Michael Rowley MD
FP
--
Thanks and regards,
Vasyl Rublyov
Re: [Asterisk-Users] hdlc setup routing question
On Monday 07 June 2004 17:22, Michael A Rowley wrote: snip WAN IPs 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 IPs 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 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
