Re: [e-smith-devinfo] RC1 PPPoE issues

2001-04-26 Thread Jack McCauley
AIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 31, 2001 7:38 AM Subject: [e-smith-devinfo] RC1 PPPoE issues > 1) when configured as "Server And Gateway" with PPPoE, > the default route still is wrong > now 0.0.0.0 on eth1, was 192.168.65.1 on eth1 with

RC2 PPPoE and NIC swap (was: RC1 PPPoE issues)

2001-04-26 Thread Michael Weinberger
I re-run some tests concering PPPoE and swapped NICs, with fresh installed RC2. Works great now, execept a minor issue: 1) configured as "Server&Gateway" with PPPoE and two different NICs installed (RTL8139 and Tulip) Result: default route was set probably now. All works fine 2) swapped RTL8139

Re: [e-smith-devinfo] RC2 PPPoE and NIC swap (was: RC1 PPPoE issues)

2001-04-26 Thread Gordon Rowell
On Thu, Feb 01, 2001 at 05:28:29PM +0100, Michael Weinberger <[EMAIL PROTECTED]> wrote: > [...] > 5) replaced the RTL8139 by the Tulip, having now the > initial hardware config. > Result: eth0 device is not configured, eth1 and pppoe works. > I found the "EthernetAssign" variable still set to val

Re: [e-smith-devinfo] RC1 PPPoE issues

2001-04-26 Thread Charlie Brady
On Thu, 1 Feb 2001, Jack McCauley wrote: > This is the route command output from the non-working 4.1rc1 installation. ... > The system also still starts the pppoe service after being reconfigured as a > server only. You should find that these issues are fixed in rc2. Charlie Brady

RC1 PPPoE issues

2001-04-26 Thread Michael Weinberger
1) when configured as "Server And Gateway" with PPPoE, the default route still is wrong now 0.0.0.0 on eth1, was 192.168.65.1 on eth1 with beta4 Is this the problem addressed by Jack McCauley? 2) after configuration is altered from "Server and Gateway" with PPPoE to "Server only" the pppoe servic

Re: [e-smith-devinfo] RC1 PPPoE issues

2001-04-26 Thread Gordon Rowell
On Wed, Jan 31, 2001 at 01:38:22PM +0100, Michael Weinberger <[EMAIL PROTECTED]> wrote: > 1) when configured as "Server And Gateway" with PPPoE, > the default route still is wrong > now 0.0.0.0 on eth1, was 192.168.65.1 on eth1 with beta4 > Is this the problem addressed by Jack McCauley? Related