Replies interspersed below. At 02:06 PM 1/26/03 -0500, Arcana wrote:
Yes, this would be better, for the reason you note. But it does not explain why the other approach fails. Even if it is an inefficient method, it should work.On Sunday 26 January 2003 13:24, Ray Olszewski wrote:> Third, your immediate problem is that when the connection goes down, your > keepalive script does not restart it. Nor does your executing the same > command (/etc/init.d/networking restart) from the command line. Since that > is the command to stop, then restart, all interfaces, this command should > work ... or at least it should do *something*. I suspect that, instead of using /etc/init.d/networking restart, I should probably just use 'ifup ppp0'. This means that I target the ppp interface specifically instead of bringing down the entire list of interfaces on the router (and killing, let's say, DHCP addresses).
Another thing I might be able to do is to NOT check if the connection is up orProbably not ... probably your log will just fill up with harmless error messages fro ifup... but the best way to find out is to try. But it also may not work ... see below.
down, but to run 'ifup ppp0' every fifteen minutes. Would there be adverse
effects in doing this?
> So ... please report this part in more detail than "but it didn't restartRight. What we need to see if the *abnormal* situation that is causing the problem. For example, if your ppp0 interface loses its configuration from the ISP end, but the Bering end does not bring the interface down, then it will still be present, still be detected by your keepalinve script ... so the script will not try to restart it. The same problem will present itself in your idea of just restarting the interface every 15 minutes.
> until the modem was powercycled". Use the SR FAQ to learn the set of
> diagnostics we want to see (in this case, run before and after you execute
> the command).
My Internet is up:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
30: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
30: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
inet 216.75.174.78 peer 64.39.160.16/32 scope global ppp0
I bring down internet with ifdown ppp0:
# ifdown ppp0
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
/var/log/syslog:
Jan 26 13:58:42 firewall pppd[31093]: Terminating on signal 15.
Jan 26 13:58:42 firewall pppd[31093]: Couldn't increase MTU to 1500.
Jan 26 13:58:42 firewall pppd[31093]: Couldn't increase MRU to 1500
Jan 26 13:58:42 firewall pppd[31093]: Connection terminated.
Jan 26 13:58:42 firewall pppd[31093]: Connect time 19.0 minutes.
Jan 26 13:58:42 firewall pppd[31093]: Sent 127644 bytes, received 91837 bytes.
Jan 26 13:58:42 firewall pppd[31093]: Doing disconnect
Jan 26 13:58:42 firewall pppd[31093]: Exit.
I type 'ifup ppp0' to bring the connection back up:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
31: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:f0:06:aa:a5 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:29:2c:98:b3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
31: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
inet 216.75.174.78 peer 64.39.160.16/32 scope global ppp0
Syslog:
Jan 26 14:01:09 firewall pppd[20638]: Plugin /usr/lib/pppd/pppoe.so loaded.
Jan 26 14:01:09 firewall pppd[20638]: PPPoE Plugin Initialized
Jan 26 14:01:09 firewall pppd[5955]: pppd 2.4.1 started by root, uid 0
Jan 26 14:01:09 firewall pppd[5955]: Sending PADI
Jan 26 14:01:09 firewall pppd[5955]: HOST_UNIQ successful match
Jan 26 14:01:09 firewall pppd[5955]: HOST_UNIQ successful match
Jan 26 14:01:09 firewall pppd[5955]: Got connection: ea9
Jan 26 14:01:09 firewall pppd[5955]: Connecting PPPoE socket:
00:90:1a:40:44:2c a90e eth0 0x807c260
Jan 26 14:01:09 firewall pppd[5955]: using channel 27
Jan 26 14:01:09 firewall pppd[5955]: Using interface ppp0
Jan 26 14:01:09 firewall pppd[5955]: Connect: ppp0 <--> eth0
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MTU to 1500.
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MRU to 1500
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MTU to 1500.
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MRU to 1500
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MTU to 1500.
Jan 26 14:01:09 firewall pppd[5955]: Couldn't increase MRU to 1500
Jan 26 14:01:10 firewall pppd[5955]: Cannot determine ethernet address for
proxy ARP
Jan 26 14:01:10 firewall pppd[5955]: local IP address 216.75.174.78
Jan 26 14:01:10 firewall pppd[5955]: remote IP address 64.39.160.16
This is what the "normal" situation for ppp0 going down and up looks like if I
do it on demand.
Without those diagnostics from an actual failure, all I can do is guess as to what is going on. But you might consider rewriting the keepalive script so that instead of checking if ppp0 is up, it checks if it is working (say, by pinging the other end of the PtP link). If it is not, then bring it down, then back up.
I still do not understand. The log you sent does not report any attempts (other than the initial one) to "bring up the interfaces". It reports that keepalive runs, but not that it tries to restart networking. Does keepalive itself stop running?> Also please clarify what you mean by "eventually the system stops trying". From the log output it seems that the system stops trying to bring up the interfaces.
Some ISPs want you to configure eth0 with a subnet-10 address, which is used for local communication between the router and the DSL modem. I've not used such a service myself, so I don't know the details ... but it appears from what you write that your specified setup does not require this extra step.> The problem may be in the details of how your PPPoE connection gets set up, > in particular how the rotuer communicates locally with the DSL modem. PPPoE > setup requirements imposed by ISPs vary a lot (who is your ISP, BTW? I know > PacBell uses the Enternet 300 Windows PPPoE client, or did bak when I > struggled with a PPPoE connection), and dealing with your problem may > require information on the details of your ISP's setup instructions (for > Windows). My modem is a GNet BB0050 modem. My ISP is Golden Triangle -- golden.net I did not receive any specific instructions for setup: it was basically, "Install the Enternet 300 software, add your username and password, and then connect." Is there any setup instructions that you were thinking of?
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
------------------------------------------------------------------------
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
