🚀 go-pugleaf

It's 04 Dec 97  11:05,
We'll return to todd@zeta.org.au and All's
discussion of PPP troubles

 to> Gday all. Well, after finally nailing a few hardware related problems,
 to> I have got my Linux machine going.
 to> It is working fine across my LAN. I can FTP & Telnet to the Linux box.
 to> I think SAMBA is even running, it must
 to> do that as a default. My problem is still it wont connect to the net.
 to> Below are all my config files. If there are more I need to post, let
 to> me know.
 to> Also, net-start wont run.
 to> This is what happens when i try and run net-start.

 to> [root@ozzy bin]# net-start
 to> bash: /usr/local/bin/net-start: No such file or directory
 to> [root@ozzy bin]# /usr/local/bin/net-start
 to> bash: /usr/local/bin/net-start: No such file or directory

What is net-start supposed to do?  I haven't seen this command.  On my
Linux box, network services are loaded in the rc scripts on startup and
for the PPP connection, I either use a default (configured using diald)
login to the Net, or I manually run a script to connect to the network
at work (all PPP scripts are "home grown", I trust them more that way :)
).

 to> [root@ozzy bin]# ifconfig
 to> lo        Link encap:Local Loopback
 to> inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
 to> UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
 to> RX packets:129 errors:0 dropped:0 overruns:0
 to> TX packets:129 errors:0 dropped:0 overruns:0

 to> eth0      Link encap:10Mbps Ethernet  HWaddr 00:00:E8:3A:17:0A
 to> inet addr:192.168.0.1  Bcast:192.168.0.255
 to> Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST  MTU:1500
 to> Metric:1 RX packets:1311 errors:0 dropped:0 overruns:0
 to> TX packets:1576 errors:0 dropped:0 overruns:0
 to> Interrupt:9 Base address:0x300

 to> ppp0      Link encap:Point-Point Protocol
 to> inet addr:203.2.228.248  P-t-P:203.15.68.20
 to> Mask:255.255.255.0
 to> UP POINTOPOINT RUNNING  MTU:1500  Metric:1
 to> RX packets:9 errors:1 dropped:1 overruns:0
 to> TX packets:10 errors:0 dropped:0 overruns:0

Loos like you have a network. :-)  Mine looks similar, except for having
an official IP address on eth0 and a phantom sl0 interface used by
diald. :-)

 to> [root@ozzy bin]# route -n
 to> Kernel IP routing table
 to> Destination     Gateway         Genmask         Flags Metric Ref
 to> Use Iface
 to> 203.15.68.20    0.0.0.0         255.255.255.255 UH    0      0
 to> 0 ppp0
 to> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
 to> 4 eth0
 to> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
 to> 3 lo
 to> 0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0
 to> 11 eth0

Your default route goes via your Ethernet?  Shouldn't it be going out
through the PPP link?  Try adding the "defaulteroute" option to your
pppd commandline.


 to> After Logging off.
-----------------------

Looks pretty normal, though I wouldn't have a default route pointing to
your Ethernet, unless it leads elsewhere.  My default route points to
the sl0 interface, and appears as though I'm still connected to the Net,
but this is because I'm using diald.  Without diald, I wouldn't have a
default route, which would be fine (if it's not on the LAN, it doesn't
exist! :) ).

 to> [root@ozzy ppp]# cat options
 to> lock


 to> Any help, greatly appreciated.

Try adding defaulteroute to your pppd commandline (or /etc/ppp/options
if you will only ever use one PPP connection), and remove your static
default route (which serves no useful purpose). If you do happen to have
multiple LAN segments (common in a company LAN), use specific static
routes to route to them, as you should know the address ranges and
gateways used on the LAN. Leave the default route pointing towards the
Internet. :-)

... 90% of PC problems are located between the keyboard and the chair.
--
| Fidonet:  Tony Langdon 3:632/367.2
| Internet: tlang@freeway.DIALix.oz.au
|
| Freeway Internet Gateway, Melbourne, Australia.  For information about
| our services and conditions of use, e-mail:
| info@freeway.DIALix.oz.au, to receive a copy of the FAQ.