|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [Plug] Two networking questions...
|
Martin DiViaio wrote:
>
> Ok, this is too weird. First, I've NEVER done this before (if you
> haven't figured that out all ready.) Please bear with me...
>
> When I ran ifconfig just now, I got the following:
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:142 errors:0 dropped:0 overruns:0 frame:0
> TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> eth0 Link encap:Ethernet HWaddr 00:80:C7:6A:69:BA
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:3 Base address:0x2e0
>
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:REMOVED P-t-P:REMOVED Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1006 Metric:1
> RX packets:92 errors:0 dropped:0 overruns:0 frame:0
> TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> If I am reading this right, both eth0 and ppp0 are running fine, well
> almost.
Not true:
ppp0 shows that the local address ant the remote address has been
removed. Thus in reality, pppd is running but it is ineffective.
Your ppp0 portion of ifconfig should show the locally assigned ip
address and the remote address as follows:
ppp0 Link encap:Point-to-Point Protocol
inet addr:207.106.60.5 P-t-P:207.106.60.1
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:12460 errors:0 dropped:0 overruns:0 frame:0
TX packets:6667 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
>
> netstat -rn gave me the following:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 10.65.48.12 0.0.0.0 255.255.255.255 UH 0 0 0
> ppp0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 192.168.0.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 10.65.48.12 0.0.0.0 UG 0 0 0
> ppp0
>
This shows that ppp0 is using the private network address and not the
assigned network address from your internet service provider. It should
look like:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
207.106.60.1 0.0.0.0 255.255.255.255 UH 0 0 0
ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
0.0.0.0 207.106.60.1 0.0.0.0 UG 0 0 0
ppp0
you see where the gateway and a destination are both on ppp0. These
addresses came from the dynamically assigned address from the isp.
Everytime I log in to netaxs, these addresses change. Also note that
the the ethernet network is also up and ready to receive connections
from the local network. This machine is the gateway for all of the
boxes on the local network, thus allowing all of the machines on the
local network connections to the internet through only one modem
connection.
> To ask something really silly, shouldn't the two entries for eth0 look
> something like ppp0? (i.e. destination and gateway reversed.)
>
> When I checked netcfg, it told me that the eth0 interface was active.
> When I get the computer I want to talk to working right I'll see.
> (Anyone know how to get network card drivers working under Win3.1? :)
>
> About the only think I can figure is that I accidentally pulled the
> ethernet pc card out when I was disconnecting the modem cable. When I
> re-inserted it pcmcia-cs automatically runs the network startup script.
> The really funny part is that up until then the network startup script
> always failed. :\
>
> (Sorry about the lenght of this...)
>
> Here are the /etc/resolv.conf and /etc/ppp/options files:
>
> /etc/resolv.conf
>
> search erols.com
> nameserver 207.172.3.8
> nameserver 207.172.3.9
> nameserver 207.172.3.10
> nameserver 207.172.3.11
>
> /etc/ppp/options
>
> -detach
> modem
> lock
> crtscts
> defaultroute
> asyncmap 0
> mtu 1006
> debug
> kdebug 7
There are a lot of items missing from this version of the ppp options
file. for instance there is no mention of where the modem device is, no
mention of the connect baud rate, no chatscript mentioned and other
stuff. I question why you have set the kernel debug level and the
debug. Why have you set the mtu to 1006? Also, do you have a
chatscript somewhere on your system and a shell script that calls the
chat chatscript?
I have set up a connection script that connects to netaxs as follows:
pppd /dev/ttyS0 57600 connect "/usr/sbin/chat -v -V -f
/etc/ppp/chatscript-966-7777" asyncmap 0 crtscts defaultroute modem mru
1500
BTW This is all on one single line.
notice that the command is pppd
with the following arguments:
serial device where your modem is
baud connection speed
connect takes a command for a argument
read man pppd for the meaning of the other options
read man chat for instructions for setting up a chatscript
I realize that I have mentioned a lot of items, but connecting to every
isp is different. Some have more prompts than what your distribution
calls for in their default dial up scripts. I would suggest that you
should first use minicom to see what prompts your isp asks for so you
can make an appropriate chatscript that includes your login password,
name, phonenumber and etc.
--
0 0 L & R Associates
" Home Page: http://www.netaxs.com/~ldc/
_______ooO ~ Ooo_______________________________________________
LeRoy D. Cressy /\_/\ ldc@netaxs.com
Computer Consulting ( o.o ) Phone (215) 535-4037
> ^ < Fax (215) 535-4285
_______________________________________________
Plug maillist - Plug@lists.nothinbut.net
http://lists.nothinbut.net/mail/listinfo/plug
|
|