Your basic problem apparently is what you think it is -- the ppp connection from your ISP is not assigning a local Ip address. Why (and why this problem occurs on the LEAF system but not the Slack system) is not immediately apparent.
The problem shows in this section of the log entries you posted.
LEAF system --
Jul 13 09:26:14 firewall pppd[734]: sent [IPCP ConfAck id=0xdb <compress VJ 0f
00
> <addr 206.166.57.162>]
Jul 13 09:26:14 firewall pppd[734]: rcvd [IPCP ConfAck id=0x1 <addr
12.34.56.78>
<compress VJ 0f 01>]
Jul 13 09:26:14 firewall pppd[734]: Remote IP address changed to
206.166.57.162
Jul 13 09:26:14 firewall pppd[734]: sent [proto=0x21] 45 00 00 54 00 03 00 00
40
Slack system --
/lib/modules/2.4.18/kernel/drivers/net/ppp_deflate.o.gz will taint the kernel: non-GPL license - BSD without advertisement clause Jul 13 13:14:49 Intrepid insmod: See http://www.tux.org/lkml/#s1-18 for information about tainted modules Jul 13 13:14:49 Intrepid insmod: Module ppp_deflate loaded, with warnings Jul 13 13:14:52 Intrepid pppd[311]: local IP address 206.166.57.173 Jul 13 13:14:52 Intrepid pppd[311]: remote IP address 206.166.57.162
At 01:29 PM 7/13/2003 -0500, RS Peterson wrote:
Ray -- Thanks for your kind, helpful reply. I hope all this info is helpful.[details deleted]
Questions/responses --> embedded
On Saturday 12 July 2003 10:10 pm, [EMAIL PROTECTED] wrote: > Message: 2 > Date: Sat, 12 Jul 2003 13:14:23 -0700 > To: [EMAIL PROTECTED] > From: Ray Olszewski <[EMAIL PROTECTED]> > Subject: Re: [leaf-user] can only ping assigned IP > > The project name these days is LEAF, not LRP. I do note that EigerStein > plus Trevor's PPP dialup package is pretty old stuff, possibly tough to get > current support for.
This seemed to be the case, but no other versions seemed to be tailored for a serial modem dial-up connection (ppp0) <--> LAN (eth0). So, after many failed attempts with other LRP flavors (which had screen problems) I found Eiger to be at least bootable. Please, suggest a better, more robust approach with LEAF for ppp0 <--> eth0, if I should give up the present course with Eiger. Thanks.
> > As to your substantive problem, I see a couple of oddities in what you > posted. First, the pppd messages never report receiving a local IP address > > for ppp0, but do report this entry: > >Jul 12 10:31:31 firewall pppd[735]: Remote message: > >Jul 12 10:31:35 firewall pppd[735]: Remote IP address changed to > >206.166.57.162
Yes, I thought this odd also. Why am I not getting a "local IP address" sent/assigned to me? From my working SW9.0 dial-up, it always returns: Using interface ppp0 Connect: ppp0 <--> /dev/ttyS1 local IP address 206.166.57.178 remote IP address 206.166.57.162 I attributed the firewall box not doing this due to versions of pppd. Apparently, I should be getting this back. Yes? No?
> > Second, your routing table offers this oddity: > >206.166.57.162 dev ppp0 proto kernel scope link src 12.34.56.78 > > The "12.34.56.78" part suggests that you are not getting a proper local > address assigned to the interface. SInce both local and remote addresses > are usually logged by pppd, the two oddities are at least consistent. >
The "12.34.56.78" gets set in /etc/ppp/options. Thus: -------- name "rpeterson" /dev/ttyS1 38400 idle 180 debug #### DO NOT CHANGE THESE UNLESS YOU THINK YOU KNOW WHAT YOU ARE DOING #### connect '/usr/sbin/chat -v -f /etc/ppp/chatscript -r /tmp/connect.log' demand #persist passive asyncmap 0 #192.168.100.1:192.168.100.1 #0.0.0.0:10.10.10.10 12.34.56.78:12.34.56.79 ipcp-accept-local ipcp-accept-remote modem crtscts defaultroute noipdefault lock #noauth #holdoff 30 #mtu 576 #mru 576 -------------
I read in various docs that if the ISP sets the IP dynamically then any ole address will do as a dummy. This allows my firewall to dial-up and connect to my ISP when I issue a 'ping' request. I know I am connected, because I can 'ping 206.166.57.162' (which is the remote IP address assigned, found in /var/log/messages), but I cannot ping anywhere else: not the DNS servers (206.166.17.20), not known outside IPs, not outside site names. Nothing, only the remote IP address assigned: 206.166.57.162 answers. The outside pings fail silently with nothing returned to log files or to the screen. The modem "SO" blinks indicating my firewall box is sending, but nothing is coming back. Also (and this seems important) if I change /etc/ppp/options to something rational (ex: 192.168.100.1:192.168.100.1) (amoung others) then ALL pings fail; the system will NOT dial-out. The message returned says: PING 206.166.17.20 (206.166.17.20): 56 data bytes ping: send to: Operation not permitted ping: wrote 206.166.17.20 64 chars, ret=-1 ping: send to: Operation not permitted ping: wrote 206.166.17.20 64 chars, ret=-1 ping: send to: Operation not permitted ping: wrote 206.166.17.20 64 chars, ret=-1 ping: send to: Operation not permitted ping: wrote 206.166.17.20 64 chars, ret=-1 ping: send to: Operation not permitted ping: wrote 206.166.17.20 64 chars, ret=-1
--- 206.166.17.20 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss
tail /var/log/ppp.log shows 'pppd' exiting. Sorry I did not snag this message.
I must have the /etc/ppp/options address set to something bogus: 12.34.56.78.
Makes no sense to me.
> But this leaves me a bit puzzled about what IP address you are referring to > when you say you can ping "ONLY to the assigned IP my ISP gives me". Do you > really mean "12.34.56.78", or do you mean some other address (which implies > some error in what you reported to us)?
Again, I do not mean "12.34.56.78"; rather the remote IP address handed back to me from my ISP: 206.166.57.162 is the only IP I can ping when I get connected.
> > It might help if next time you included the output of "ip -v link show" so > we could see what interfaces are active and what packet counts they show.
see below
> > As to the pings, how do they fail? Do they fail silently,
yes, things are silent IF I use the bogus address in /etc/ppp/options.
>or do you get one > of the many possible error messages? Details count here for diagnosis. And > you mention ping'ing (unsuccessfully) addresses "including the DNS servers > or other IPs or names". What about the other end of the ppp0 link (in the > example you reported, 206.166.57.162)? Until you can ping the other end of > the link, you will not be able to ping anything past it.
Yes, I can ping successfully this address: 206.166.57.162 but only this address. All others fail, silently.
> > One thing you **might** want to try: change this line in /etc/network.conf > > > # External Address dynamically assigned > >EXTERN_DYNADDR=NO # - YES/NO > > to read YES.
Tried this. No avail.
> > If none of this causes you to spot the solution on your own, please post a > followup with this information (don't edit, please, and include the command > you enter, not a replacement header as you did this time) when the ppp0 > interface is up: > > output of "ip -v link show" > output of "ip route show" > the log output of "pppd" only after "chat" finishes logging
Run: 'ip link show' (switch -v not allowed): 1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: brg0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:fd:01:09:25:56 brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 52:54:40:21:30:31 brd ff:ff:ff:ff:ff:ff 5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 30 link/ppp
Run: 'ip route show': 206.166.57.162 dev ppp0 proto kernel scope link src 12.34.56.78 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.1 default via 206.166.57.162 dev ppp0
Lastly, 'tail /etc/ppp/ppp.log':
Jul 13 09:25:43 firewall pppd[734]: Starting link
Jul 13 09:25:44 firewall chat[807]: report (CONNECT)
Jul 13 09:25:44 firewall chat[807]: timeout set to 60 seconds
Jul 13 09:25:44 firewall chat[807]: abort on (BUSY)
Jul 13 09:25:44 firewall chat[807]: abort on (NO CARRIER)
Jul 13 09:25:44 firewall chat[807]: abort on (VOICE)
Jul 13 09:25:44 firewall chat[807]: abort on (NO DIALTONE)
Jul 13 09:25:44 firewall chat[807]: send (AT&F1^M)
Jul 13 09:25:44 firewall chat[807]: expect (OK)
Jul 13 09:25:44 firewall chat[807]: AT&F1^M^M
Jul 13 09:25:44 firewall chat[807]: OK
Jul 13 09:25:44 firewall chat[807]: -- got it
Jul 13 09:25:44 firewall chat[807]: send (ATDT16302325970^M)
Jul 13 09:25:44 firewall chat[807]: timeout set to 60 seconds
Jul 13 09:25:44 firewall chat[807]: expect (CONNECT)
Jul 13 09:25:44 firewall chat[807]: ^M
Jul 13 09:26:03 firewall chat[807]: ATDT16302325970^M^M
Jul 13 09:26:03 firewall chat[807]: CONNECT
Jul 13 09:26:03 firewall chat[807]: -- got it
Jul 13 09:26:03 firewall pppd[734]: Serial connection established.
Jul 13 09:26:04 firewall pppd[734]: Connect: ppp0 <--> /dev/ttyS1
Jul 13 09:26:04 firewall pppd[734]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magi
c 0x5bb182a8> <pcomp> <accomp>]
Jul 13 09:26:07 firewall pppd[734]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magi
c 0x5bb182a8> <pcomp> <accomp>]
Jul 13 09:26:08 firewall pppd[734]: rcvd [LCP ConfReq id=0xb8 <asyncmap
0xa0000>
<auth pap> <magic 0x8b087e0f> <pcomp> <accomp>]
Jul 13 09:26:08 firewall pppd[734]: sent [LCP ConfAck id=0xb8 <asyncmap
0xa0000>
<auth pap> <magic 0x8b087e0f> <pcomp> <accomp>]
Jul 13 09:26:10 firewall pppd[734]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magi
c 0x5bb182a8> <pcomp> <accomp>]
Jul 13 09:26:10 firewall pppd[734]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magi
c 0x5bb182a8> <pcomp> <accomp>]
Jul 13 09:26:10 firewall pppd[734]: sent [PAP AuthReq id=0x1 user="rpeterson"
pas
sword="gg2ljb"]
Jul 13 09:26:11 firewall pppd[734]: rcvd [PAP AuthAck id=0x1 ""]
Jul 13 09:26:11 firewall pppd[734]: Remote message:
Jul 13 09:26:11 firewall pppd[734]: sent [IPCP ConfReq id=0x1 <addr
12.34.56.78>
<compress VJ 0f 01>]
Jul 13 09:26:11 firewall pppd[734]: sent [CCP ConfReq id=0x1 <deflate 15>
<deflat
e(old#) 15> <bsd v1 15>]
Jul 13 09:26:11 firewall pppd[734]: rcvd [LCP ProtRej id=0xb9 80 fd 01 01 00
0f 1
a 04 78 00 18 04 78 00 15 03 2f]
Jul 13 09:26:11 firewall pppd[734]: rcvd [IPCP ConfReq id=0xda <compress VJ 0f
00
> <addr 206.166.57.162>]
Jul 13 09:26:11 firewall pppd[734]: sent [IPCP ConfAck id=0xda <compress VJ 0f
00
> <addr 206.166.57.162>]
Jul 13 09:26:14 firewall pppd[734]: sent [IPCP ConfReq id=0x1 <addr
12.34.56.78>
<compress VJ 0f 01>]
Jul 13 09:26:14 firewall pppd[734]: rcvd [IPCP ConfReq id=0xdb <compress VJ 0f
00
> <addr 206.166.57.162>]
Jul 13 09:26:14 firewall pppd[734]: sent [IPCP ConfAck id=0xdb <compress VJ 0f
00
> <addr 206.166.57.162>]
Jul 13 09:26:14 firewall pppd[734]: rcvd [IPCP ConfAck id=0x1 <addr
12.34.56.78>
<compress VJ 0f 01>]
Jul 13 09:26:14 firewall pppd[734]: Remote IP address changed to
206.166.57.162
Jul 13 09:26:14 firewall pppd[734]: sent [proto=0x21] 45 00 00 54 00 03 00 00
40
01 56 7c 0c 22 38 4e ce a6 11 14 08 00 7d 0b 25 03 00 00 97 25 11 3f c2 89 00
00
08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21
22
23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32
Jul 13 09:26:14 firewall pppd[734]: 33 34 35 36 37
> > Also provide the equivalent information for your Slackware system when it > is working. That might be the same commands or it might be > > output of "ifconfig -a" > output of "netstat -nr" > the same pppd output > Finally, from my working SW9.0 box, when connected: [EMAIL PROTECTED]:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:BA:50:FF:59 inet addr:192.168.100.3 Bcast:192.168.100.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 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:9 Base address:0xa800
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 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 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ppp0 Link encap:Point-to-Point Protocol
inet addr:206.166.57.173 P-t-P:206.166.57.162 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:4 errors:2 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:58 (58.0 b) TX bytes:95 (95.0 b)
[EMAIL PROTECTED]:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 206.166.57.162 0.0.0.0 255.255.255.255 UH 40 0 0 ppp0 192.168.100.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo 0.0.0.0 206.166.57.162 0.0.0.0 UG 40 0 0 ppp0
tail /var/log/messges: ((snip)) Jul 13 13:14:19 Intrepid chat[313]: expect (OK) Jul 13 13:14:19 Intrepid chat[313]: AT&FH0^M^M Jul 13 13:14:19 Intrepid chat[313]: OK Jul 13 13:14:19 Intrepid chat[313]: -- got it Jul 13 13:14:19 Intrepid chat[313]: send (atdt16302325970^M) Jul 13 13:14:20 Intrepid chat[313]: timeout set to 75 seconds Jul 13 13:14:20 Intrepid chat[313]: expect (CONNECT) Jul 13 13:14:20 Intrepid chat[313]: ^M Jul 13 13:14:41 Intrepid chat[313]: atdt16302325970^M^M Jul 13 13:14:41 Intrepid chat[313]: CONNECT Jul 13 13:14:41 Intrepid chat[313]: -- got it Jul 13 13:14:41 Intrepid pppd[311]: Serial connection established. Jul 13 13:14:41 Intrepid pppd[311]: Using interface ppp0 Jul 13 13:14:41 Intrepid pppd[311]: Connect: ppp0 <--> /dev/ttyS1 Jul 13 13:14:49 Intrepid kernel: PPP BSD Compression module registered Jul 13 13:14:49 Intrepid kernel: PPP Deflate Compression module registered Jul 13 13:14:49 Intrepid insmod: Warning: loading /lib/modules/2.4.18/kernel/drivers/net/ppp_deflate.o.gz will taint the kernel: non-GPL license - BSD without advertisement clause Jul 13 13:14:49 Intrepid insmod: See http://www.tux.org/lkml/#s1-18 for information about tainted modules Jul 13 13:14:49 Intrepid insmod: Module ppp_deflate loaded, with warnings Jul 13 13:14:52 Intrepid pppd[311]: local IP address 206.166.57.173 Jul 13 13:14:52 Intrepid pppd[311]: remote IP address 206.166.57.162
Hmmm, thought: should I try "stealing" the local IP address 206.166.57.173 that shows up on my SW9.0 box connection. This seems to always be this IP though I was never "given" an IP. Life is dynamic, isn't it?
You have been more than generous to help me. Here's hoping a safe harbor is close. Thanks, again. I look forward to your response, at your leisure. Go Well -- Bob Peterson
-- Robert S. Peterson 31 N Alfred, Elgin IL 60123 USA 847/697-6491 Compass Adjusting for Lake Michigan navigators since 1985 Physics @ Bartlett HS e-mail: rpeterson(at)enc.k12.il.us
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
