Fuzzy Fox wrote:
> Barry Treahy <[EMAIL PROTECTED]> wrote:
> >
> > Don't cring, but I'm using ipfw not ipchains and there is not
> > filtering occuring at this time, only masqing...
>
> I was just asking if you add/replace rules on the fly, for some reason.
> Sounds like you do not.
Nope, once the system boots, I leave it alone... Didn't want to break what was
working, if you know what I mean...
>
>
> > From the box, I can ping IP's on my LAN, going out eth1, but I can't
> > reach anything that would be masq'd going out eth0 when the system
> > fails!
>
> The masq box can't send anything out its own interface, directly?
> Ethernet card failure? Does "arp -an" show the mac address of your DSL
> modem? Does ifconfig down/up on eth0 reset the card and make it work
> again?
I will try both suggestions on the next occurance. Since the DSL circuit is at my
home, I can't do it from work when it fails and if I do it now while it is working,
I'm not sure it will do anything except disconnect me when I do the ifconfig down...
:-0
>
>
> > > > The ISP states they can ping my interface.
>
> That's odd, considering that your ethernet card appears to not be
> working. Can you log the packets using input rules, and show that you
> see the pings coming in your eth0, and the replies going out?
>
> Maybe they are pinging the "other" side of your point-to-point link.
> That only proves that things are working, up to the other side of the
> DSL.
Well, this is another story... US West had the ISP originally configure the DSL
equipment in bridging mode, yeach! Anyway, my ISP is installing two more circuits
over which number three will be configured as PPP and I'll be moved over to that when
its ready. A long-winded story to tell you that yes, they are actually pinging my
interface at this time.
>
>
> > Well, I'm on a SW distribution and it doesn't use the new C
> > libraries... The last time I attempted to upgrade to it, what is it
> > called GLIB2?, I choked my entire system...
>
> I'm on a 2.2 kernel with Slackware, using the old libc5 libraries. I
> still haven't made the jump to glibc. It's still not required... yet. :)
Oh, I must have misread the upgrade packages and requirements list before linuxhq
died... Ok, I'll take the just and give it a shot. Besides the kernel, any other
know routines or modules that I need to jump to keep masqing working? I believe I
remember seeing that in the FAQ, so if I don't hear back on this question, I'll
assume that I recalled correctly...
>
>
> > I know simple kernel reconfigs and builds go fast, but if I've got to
> > jump to 2.2.x, well, I'm not that good to do everything in an hour.
>
> You're right, there. It may be that it's flaky hardware, or a driver
> problem. Just spouting ideas, really.
I've had great success with 3C509 cards and can't say I've never had a failure... I
suppose it could be the board. I'll see about digging up a replacement if the other
suggestions yield no working solution.
Thanks
Barry
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
