Re: [Leaf-user] Re: Dachstein PPPoE don't know
In addition, once you get your modules loaded (as seen by ip addr showing eth0 and eth1 in addition to ppp0 and lo), there were some less than straightforward settings (at least for me) in the network.conf file (1-Network settings, 1-Network Configuration). IF_AUTO="eth1" ... IF_LIST="$IF_AUTO" ... EXTERNAL_IF="ppp0" <-- note: NOT eth0, you need "virtual" device ppp0 _over_ hardware device eth0 ... EXTERN_DHCP=NO ... EXTERN_DYNADDR=NO ... EXTERN_IP=DYNAMIC Of course, your mileage may vary. The biggest problem for me was the EXTERN_IF not being set to the virtual device. dbc. On Mon, 14 Jan 2002, Kenneth Hadley wrote: > definatly no modules loaded for your NIC's since you would see some messages > about them right before > > > Jan 13 18:43:24 firewall kernel: CSLIP: code copyright 1989 Regents of the > > University of California > > Jan 13 18:43:24 firewall kernel: PPP: version 2.3.7 (demand dialling) > > Jan 13 18:43:24 firewall kernel: PPP line discipline registered. > > Jan 13 18:43:24 firewall kernel: PPP Deflate Compression module registered > > Have you tried uncommenting "pci-scan" and "tulip" in /etc/modules? .im > not sure if this is the proper module for your LinkSys cards but its worth a > shot > > -Kenneth Hadley > > > > - Original Message - > From: "John Atkeison" <[EMAIL PROTECTED]> > To: "Kenneth Hadley" <[EMAIL PROTECTED]> > Cc: "[LEAF-user]" <[EMAIL PROTECTED]>; "John Atkeison" > <[EMAIL PROTECTED]> > Sent: Sunday, January 13, 2002 7:33 PM > Subject: Re: [Leaf-user] Re: Dachstein PPPoE don't know > > > > I am on [Leaf-user] but I cannot post direcly because of the postmaster > > account restriction- more on that in a separate email. > > > > The NICs are > > Linksys LNE100TX (v5.1) > > Linksys LNE100TX (v2) > > > > And- > > #ip addr > > 1: lo: MTU 3924 qdisc noque > > 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 global lo > > 1336: ppp0: mtu 1500 qdisc noop qlen 10 > > link/ppp > > > > From network.conf: > > eth0_IPADDR=1.1.1.2 > > eth0_MASKLEN=30 > > eth0_BROADCAST=+ > > eth0_DEFAULT_GW=1.1.1.1 > > eth0_IP_KRNL_LOGMARTIANS=YES > > eth0_IP_SHARED_MEDIA=NO > > eth0_BRIDGE=NO > > eth0_PROXY_ARP=NO > > eth0_FAIRQ=NO > > > > ### > > eth1_IPADDR=192.168.1.254 > > eth1_MASKLEN=24 > > eth1_BROADCAST=+ > > eth1_IP_SPOOF=YES > > eth1_IP_KRNL_LOGMARTIANS=YES > > eth1_IP_SHARED_MEDIA=NO > > eth1_BRIDGE=NO > > eth1_PROXY_ARP=NO > > eth1_FAIRQ=NO > > ### > > Heres messages: > > Jan 13 18:43:24 firewall syslogd 1.3-3#31.slink1: restart. > > Jan 13 18:43:24 firewall kernel: klogd 1.3-3#31.slink1, log source = > > /proc/kmsg started. > > Jan 13 18:43:24 firewall kernel: Cannot find map file. > > Jan 13 18:43:24 firewall kernel: Loaded 58 symbols from 14 modules. > > Jan 13 18:43:24 firewall kernel: Linux version 2.2.19-3-LEAF (root@debian) > > (gcc version 2.7.2.3) #1 Sat Dec 1 12:15:05 CST 2001 > > Jan 13 18:43:24 firewall kernel: BIOS-provided physical RAM map: > > Jan 13 18:43:24 firewall kernel: BIOS-e820: 0009fc00 @ (usable) > > Jan 13 18:43:24 firewall kernel: BIOS-e820: 0400 @ 0009fc00 (usable) > > Jan 13 18:43:24 firewall kernel: BIOS-e820: 05f0 @ 0010 (usable) > > Jan 13 18:43:24 firewall kernel: Detected 133638 kHz processor. > > Jan 13 18:43:24 firewall kernel: Console: colour VGA+ 80x25 > > Jan 13 18:43:24 firewall kernel: Calibrating delay loop... 266.24 BogoMIPS > > Jan 13 18:43:24 firewall kernel: Memory: 95180k/98304k available (732k > > kernel code, 416k reserved, 1232k data, 44k init) > > Jan 13 18:43:24 firewall kernel: Dentry hash table entries: 16384 (order > 5, > > 128k) > > Jan 13 18:43:24 firewall kernel: Buffer cache hash table entries: 131072 > > (order 7, 512k) > > Jan 13 18:43:24 firewall kernel: Page cache hash table entries: 32768 > > (order 5, 128k) > > Jan 13 18:43:24 firewall kernel: CPU: Intel Pentium 75 - 200 stepping 0c > > Jan 13 18:43:24 firewall kernel: Checking 386/387 coupling... OK, FPU > using > > exception 16 error reporting. > > Jan 13 18:43:24 firewall kernel: Checking 'hlt' instruction... OK. > > Jan 13 18:43:24 firewall kernel: Intel Pentium with F0 0F bug - workaround > > enabled. > > Jan 13 18:43:24 firewall kernel: POSIX conformance testing by UNIFIX > > Jan 13 18:43:24 firewall kernel:
Re: [Leaf-user] Re: Dachstein PPPoE don't know
definatly no modules loaded for your NIC's since you would see some messages about them right before > Jan 13 18:43:24 firewall kernel: CSLIP: code copyright 1989 Regents of the > University of California > Jan 13 18:43:24 firewall kernel: PPP: version 2.3.7 (demand dialling) > Jan 13 18:43:24 firewall kernel: PPP line discipline registered. > Jan 13 18:43:24 firewall kernel: PPP Deflate Compression module registered Have you tried uncommenting "pci-scan" and "tulip" in /etc/modules? .im not sure if this is the proper module for your LinkSys cards but its worth a shot -Kenneth Hadley - Original Message - From: "John Atkeison" <[EMAIL PROTECTED]> To: "Kenneth Hadley" <[EMAIL PROTECTED]> Cc: "[LEAF-user]" <[EMAIL PROTECTED]>; "John Atkeison" <[EMAIL PROTECTED]> Sent: Sunday, January 13, 2002 7:33 PM Subject: Re: [Leaf-user] Re: Dachstein PPPoE don't know > I am on [Leaf-user] but I cannot post direcly because of the postmaster > account restriction- more on that in a separate email. > > The NICs are > Linksys LNE100TX (v5.1) > Linksys LNE100TX (v2) > > And- > #ip addr > 1: lo: MTU 3924 qdisc noque > 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 global lo > 1336: ppp0: mtu 1500 qdisc noop qlen 10 > link/ppp > > From network.conf: > eth0_IPADDR=1.1.1.2 > eth0_MASKLEN=30 > eth0_BROADCAST=+ > eth0_DEFAULT_GW=1.1.1.1 > eth0_IP_KRNL_LOGMARTIANS=YES > eth0_IP_SHARED_MEDIA=NO > eth0_BRIDGE=NO > eth0_PROXY_ARP=NO > eth0_FAIRQ=NO > > ### > eth1_IPADDR=192.168.1.254 > eth1_MASKLEN=24 > eth1_BROADCAST=+ > eth1_IP_SPOOF=YES > eth1_IP_KRNL_LOGMARTIANS=YES > eth1_IP_SHARED_MEDIA=NO > eth1_BRIDGE=NO > eth1_PROXY_ARP=NO > eth1_FAIRQ=NO > ### > Heres messages: > Jan 13 18:43:24 firewall syslogd 1.3-3#31.slink1: restart. > Jan 13 18:43:24 firewall kernel: klogd 1.3-3#31.slink1, log source = > /proc/kmsg started. > Jan 13 18:43:24 firewall kernel: Cannot find map file. > Jan 13 18:43:24 firewall kernel: Loaded 58 symbols from 14 modules. > Jan 13 18:43:24 firewall kernel: Linux version 2.2.19-3-LEAF (root@debian) > (gcc version 2.7.2.3) #1 Sat Dec 1 12:15:05 CST 2001 > Jan 13 18:43:24 firewall kernel: BIOS-provided physical RAM map: > Jan 13 18:43:24 firewall kernel: BIOS-e820: 0009fc00 @ (usable) > Jan 13 18:43:24 firewall kernel: BIOS-e820: 0400 @ 0009fc00 (usable) > Jan 13 18:43:24 firewall kernel: BIOS-e820: 05f0 @ 0010 (usable) > Jan 13 18:43:24 firewall kernel: Detected 133638 kHz processor. > Jan 13 18:43:24 firewall kernel: Console: colour VGA+ 80x25 > Jan 13 18:43:24 firewall kernel: Calibrating delay loop... 266.24 BogoMIPS > Jan 13 18:43:24 firewall kernel: Memory: 95180k/98304k available (732k > kernel code, 416k reserved, 1232k data, 44k init) > Jan 13 18:43:24 firewall kernel: Dentry hash table entries: 16384 (order 5, > 128k) > Jan 13 18:43:24 firewall kernel: Buffer cache hash table entries: 131072 > (order 7, 512k) > Jan 13 18:43:24 firewall kernel: Page cache hash table entries: 32768 > (order 5, 128k) > Jan 13 18:43:24 firewall kernel: CPU: Intel Pentium 75 - 200 stepping 0c > Jan 13 18:43:24 firewall kernel: Checking 386/387 coupling... OK, FPU using > exception 16 error reporting. > Jan 13 18:43:24 firewall kernel: Checking 'hlt' instruction... OK. > Jan 13 18:43:24 firewall kernel: Intel Pentium with F0 0F bug - workaround > enabled. > Jan 13 18:43:24 firewall kernel: POSIX conformance testing by UNIFIX > Jan 13 18:43:24 firewall kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb620 > Jan 13 18:43:24 firewall kernel: PCI: Using configuration type 1 > Jan 13 18:43:24 firewall kernel: PCI: Probing PCI hardware > Jan 13 18:43:24 firewall kernel: Linux NET4.0 for Linux 2.2 > Jan 13 18:43:24 firewall kernel: Based upon Swansea University Computer > Society NET3.039 > Jan 13 18:43:24 firewall kernel: NET4: Unix domain sockets 1.0 for Linux > NET4.0. > Jan 13 18:43:24 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0 > Jan 13 18:43:24 firewall kernel: IP Protocols: ICMP, UDP, TCP > Jan 13 18:43:24 firewall kernel: TCP: Hash tables configured (ehash 131072 > bhash 65536) > Jan 13 18:43:24 firewall kernel: Initializing RT netlink socket > Jan 13 18:43:24 firewall kernel: Starting kswapd v 1.5 > Jan 13 18:43:24 firewall kernel: Software Watchdog Timer: 0.05, timer > margin: 60 sec > Jan 13 18:43:24 firewall kernel: Real Time Clock Driver v1.09 > Jan 13 18:43:24 firewall kernel: RAM disk driver initialized: 16 RAM disks > of 6144K size > Jan 13 18:43:24 firewall kernel: Floppy drive(s): fd0 is 1.44M > Jan 13 18:43:24 firew
[Leaf-user] Re: Dachstein PPPoE don't know
>From what I can understand it looks like you dont have your NICs loaded correctly.. Im not sure which module would be needed since you didnt say what LinkSys NIC model you have.. Also, what is the output from the command "ip addr" ? And do make sure you a subscribed to the leaf-user mailing list at sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/leaf-user ) since Im not always able to respond to emails sent to my personal email accounts but other folks on the LEAF mailing list might be able to help -Kenneth Hadley - Original Message - From: "John Atkeison" <[EMAIL PROTECTED]> To: "Kenneth Hadley" <[EMAIL PROTECTED]> Cc: "LEAF-user" <[EMAIL PROTECTED]> Sent: Sunday, January 13, 2002 6:28 PM Subject: Dachstein PPPoE don't know > I am so far behind the curve that I don't know where to start. 8-} I have > a Dachstein floppy firewall on my DSL (Speakeasy static IP) at my office, > and have _that_one_ mostly figured out. > > I've been futzing with 1.02 floppy pppoe dachstein for my home Verizon DSL > connection for a couple weeks off & on in my spare time, with little > success. I am afraid that I do not know enuf to ask intelligent questions, > so I will describe a bit of my setup and se what y'all have to point me to. > (Refs to docs are fine- I am trying to educate myself so I can set this up > for a non-profit client of mine, so I _do_ need to actually know what I am > doing, sooner or later! 8-)) > > The DSL works fine from my Win98 box. That connection uses WinPoET; its > documentation is not terribly informative. > The messages generated by the PPPoE dachstein are different enuf from the > one at the office that I am not sure how to interpret them. I have taken > the Verizon-supplied cable from the Win98 box and tried it in both NICs > (with reboots). > > In messages, this appears > Bringing up adsl link: > .registered device ppp0 > pppoe uses obsolete (PF_INET,SOCK_PACKET) > ..TIMED OUT > I also get the request to "add a subnet for eth1 (0.0.0.0)" but I thought > that might actually be a driver issue, based on what I saw in past posts on > this list (my local archives go back to June 09, 2001). > The firewall box is a P133 and I bought 2 Linksys NICs for this. Dumb > question: I don't have to have TWO tuplip.o drivers do I?? > > When it is up, there's this: > #adsl-start > ..TIMED OUT > #adsl-status > Link is down -- couldn't find interface corresponding to pid 3473 > > OK- now tell me what I _really_ need to tell ya! 8-)) > TIA > John > John Atkeison > [EMAIL PROTECTED] > (302) 888-1979 > (610) 952-2727 > CLIMATE ACTION THEATRE > The mission of Climate Action Theatre (CAT) is to educate the public about > global climate change through science-based dramatic presentations to > groups. CAT encourages audiences to take action to arrest global climate > change. To volunteer in ANY capacity, email [EMAIL PROTECTED] or call (610) > 952-2727. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
