Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LINUX -- Ignore unavailable to you. Want to Upgrade?

To: SunSpot who wrote (2245)	4/14/2000 1:45:00 PM
From: Cheeky Kid	Read Replies (1) \| Respond to of 2615

I know someone using OpenBSD to make very secure firewalls. And you would be surprised who and what companies are using it as their firewall. I have been told that confidence is quite high, you can build a very secure firewall on an old 486 using OpenBSD that can compete with firewalls that are worth many thousands of dollars. I have heard that LOpht uses OpenBSD as their firewall too.

To: SunSpot who wrote (2245)	4/19/2000 4:20:00 AM
From: Gerald Walls	Read Replies (1) \| Respond to of 2615

Sunspot, and all. Maybe someone can help me here. I upgraded my 486 Linux machine from Red Hat 6.1 (with a kernel already upgraded to 2.2.14-1.1.0) to Red Hat 6.2 (kernel 2.2.14-5.0) because I figured it would be a quickie, minor upgrade and I'd have the latest software on my machine. There were some initial problems with the upgrade where it couldn't locate certain modules but that's been fixed by re-installing the upgrade. Now I'm banging my head on the wall trying to figure out how to get my PPP connection working again. I use diald and it continues to dial out and connect fine. The pap authentication succeeds and I'm logged in fine. However, trying to nslookup a site gives me "unknown host" and trying to ping a random IP address gives me "network unreachable". route -n (see below) shows that one of the eth0 entries is marked as the gateway and there's only one ppp0 entry. The ppp how-to says that this is a Bad Thing and that there should be two ppp0 entries, with one labeled "default". (In their example the "default" is also marked "UG" indicating gateway.) I've never in the past had an entry labeled "default", but I have always had either a ppp0 or a tap0 entry (depending on ppp being active) labeled "0.0.0.0" which I assume is the same thing. Someplace somewhere there's a script that setting up eth0 as the gateway and I can't find it. Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 192.168.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tap0 192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0 When I activate PPP the other tap0 line is replace by the proper ppp0 line but the 0.0.0.0 tap0 line just goes away instead of being replaced. I think this is because eth0 is already considered a gateway. Any pointers?