On Tue, Dec 28, 2004 at 11:18:42PM -0600, Matthew Boehm wrote:
> Hey gang,
> I was successful in recompiling my 2.4.20 kernel to support HDLC. I was
> successful in hooking up our T1 line into the zap card. I was successful in
> being able to ping equipment on the other end of the T1. I was unsucc
> appears that your box isn't configured for NAT, so you want to brush up
> on iptables.
Ahhh. Didn't think about that. Makes sense now..if I send a packet to
the outside world how is it going to get back to the originator when the
originator is inside a 10.0.*.* network. I forgot that we have
> And your cheezy network image shows you have not exhibited good
> networking knowledge. You show an internet clod in the middle of a point
> to point T1.
That cloud pic only serves to show that there is a 30 mile gap between
the two endpoints.
> Why is it you have 10.0.0.2 as a IP on the ot
On Dec 29, 2004, at 12:18 AM, Matthew Boehm wrote:
Hey gang,
I was successful in recompiling my 2.4.20 kernel to support HDLC. I
was
successful in hooking up our T1 line into the zap card. I was
successful in
being able to ping equipment on the other end of the T1. I was
unsuccessful
in pinging
> Check with your ISP and make sure they have you set up correctly. I have
> had issues in the past with that.
What's funny is that I am the ISP. There is nothing between the two T1
endpoints.
> BTW, I can ping the above IP from my machine just fine, so the rest of
> the world sees your T1 as
Matthew Boehm wrote:
Hey gang,
I was successful in recompiling my 2.4.20 kernel to support HDLC. I was
successful in hooking up our T1 line into the zap card. I was successful in
being able to ping equipment on the other end of the T1. I was unsuccessful
in pinging the outside world from the other
On Tue, 2004-12-28 at 23:18 -0600, Matthew Boehm wrote:
> Hey gang,
> I was successful in recompiling my 2.4.20 kernel to support HDLC. I was
> successful in hooking up our T1 line into the zap card. I was successful in
> being able to ping equipment on the other end of the T1. I was unsuccessful
What can I use to find out why packets destined for the outside world (via
65.78.109.2) are not being routed?
Check with your ISP and make sure they have you set up correctly. I have
had issues in the past with that.
Fact is, if you can ping the far end, *and packets are returned*, then
the prob
Hey gang,
I was successful in recompiling my 2.4.20 kernel to support HDLC. I was
successful in hooking up our T1 line into the zap card. I was successful in
being able to ping equipment on the other end of the T1. I was unsuccessful
in pinging the outside world from the other end of the T1.
I've
