[Leaf-user] Looking for alternate 3c59x module for 3c905c
Hello Simon, (Or should I say Salut'?) 'Problems with 905c's'. Interesting comment. I just went out a got a couple of 3c905c's and they don't work with Dach's 3c59x module. Works with LRP 2.9.8 3c59x, and also no prob with Red Hat 7.2 3c59x. Posted question on Vortex list, and received the reply below. Does anyone have the 3c905 from 3com compiled for Dachstein? http://support.3com.com/infodeli/tools/nic/linuxdownloads.htm Maybe that would work. Or other suggestion? Thanks, Boyd On Sun, 10 Mar 2002, Boyd Kelly wrote: I am trying to load the 3c59x module for two 3c905CX TXNM cards in a dachstein LRP (Kernel 2.2.19). The module seems to load ok. Mar 10 22:14:19 kernel: 3c59x.c:v0.99Rb 8/8/2000 Donald Becker, [EMAIL PROTECTED] The CX cards need a longer time to reset the Rx part. I don't know (and don't have time to check now) if the 0.99Rb driver has this fix. A newer driver should work. -- Bogdan Costescu IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868 E-mail: [EMAIL PROTECTED] -Original Message- From: Simon Bolduc [mailto:[EMAIL PROTECTED]] Sent: Wed 06/03/2002 5:06 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Subject: Re: [Leaf-user] Problem with 3c59x.o on Dachstein disk Nah - the 59x module supports the 90x series of cards - altho I have had problems with it and 905c's previously... S From: Stephen Lee [EMAIL PROTECTED] To: Leaf-user [EMAIL PROTECTED] Subject: Re: [Leaf-user] Problem with 3c59x.o on Dachstein disk Date: 06 Mar 2002 16:44:49 -0800 Hi, Maybe I'm missing something here but don't you want to load the 3c90x module? Stephen On Tue, 2002-03-05 at 10:56, Simon Bolduc wrote: I'm not sure whether the 905c's are supported by this driver - I do know that 905c's are quite different from 905b's - and did require different drivers when I was using certain dists. Have you uncommented the pci-scan module? S From: Boyd Kelly [EMAIL PROTECTED] To: Charles Steinkuehler [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: [Leaf-user] Problem with 3c59x.o on Dachstein disk Date: Tue, 5 Mar 2002 10:18:31 -0800 Hi, I have a 3c905C card. When I try to insmod 3c59x, i get error: Unresolved symbol acpi_wake, acpi_set_pwr_state, pci_drv_unregister, pci_drv_register. Tried to download a copy dated dec 1 from devel/cstein/files/kernels/Dachstein-small/modules/net with same result. Any other possibilities? Thanks Boyd ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user y§î±êæj)b b²ÒÞiû¬z¹b²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²Ê.Ç¢¸ ë+-³ùb²Ø§~åy§î±ê
RE: [Leaf-user] General routing question. Securemote
Thanks Richard Charles for comments and links. I should provide a bit of insight here. Dealing with technical and political issues. (really too bad!) Office secretary doesn't get along with IT dept of company b, and there seems to have been a real lack of cooperation although according to management this guy (on their board of directors) is supposed to have access to their intranet. I think that there may be a reluctance to reconfigure their firewall (as link suggests) as the IT guy there seems so uncooperative. I did do some research and figured that this is going to require some testing and troubleshooting, and I don't know whether they are using encapsulated FWZ or not. Also, I am not an employee of company a, but just do work for them so I can't be on site for any extended time. So I will try to prepare a diskette as per instructions in links below to see if it will work, but I also want to have a plan b. ie jump around the firewall for that one route if that might work as well. Still open to suggestions. Thanks, Boyd PS. I'll also be working on both pptp and ipsec for my own dachstein. -Original Message- From: Richard Doyle [mailto:[EMAIL PROTECTED]] Sent: Thu 07/03/2002 7:08 PM To: Boyd Kelly; [EMAIL PROTECTED] Cc: Subject: RE: [Leaf-user] Dachstein migration successful! - General routing question. FWIW, a quick check on google for securemote linux nat turned up http://www.phoneboy.com/faq/0372.html and http://www.phoneboy.com/faq/0141.html. -Richard Got my ip aliasing/forwarding and all working on dachstein. Very happy about that. Great piece of work! Now for an interesting problem: One guy behind my leaf firewall needs a securemote (Checkpoint) connection to company b. He has a Win2k workstation. As I understand from searching the newsgroups, this isn't possible with Linux, although I would love to be corrected on that one. So I am looking for some opinions on a solution. Could I just do some routing magic on the win2k workstation to bypass the leaf router only for that securemote ip address? For something like that to work would the workstation need a second nic? Or can I just plug all the Internet/Leaf wires into the same switch, and then give computer 3 a default gateway of 208.x.x.1 for the address in question? Any security issues? [Internet] | eth0 208.x.x.13 | LEAF Box (DF 208.x.x.1) | | eth1 192.168.1.254 | --- | | Computer 2Computer 3 (needs to use securemote client) (192.168.1.2) (192.168.1.3) Thanks very much, Boyd ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Þiû¬z¹X§X¬´·~ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣù^iû¬z
RE: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein
Thanks Sudhir, Started with INTERN_SERVER1 and sorks fine now. BK -Original Message- From: barwals [mailto:[EMAIL PROTECTED]] Sent: March 7, 2002 12:18 AM To: [EMAIL PROTECTED] Subject: Re: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein Dear Body, Please do not start with INTERN_SERVER0 instead start with INTERN_SERVER1. I hope you will not get any error. I was also getting the same error but after changing 0 (zero) to 1. And I didnot got any error. Thanks. Sudhir Boyd Kelly wrote: Hello, Making good progress on my Dachstein migration, but just had a hiccup with forwarding. The uncommented line (well they all would) from below gives me an error when starting the network: IP filters: portfw: Invalid protocol specified. The INTERN_SERVER section (not indexed) works ok, but I have too many entries. Those shown below are just some of what I have to do. As usual any help is very much appreciated. Boyd # Advanced settings: parameters passed directly to portfw and autofw # Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R 192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R $PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80 #INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443 #INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800 #INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900 #INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53 #INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list) Dachstein
Hi, I take it back. When starting with INTERN_SERVER1, if I do an ipmasqadm portfw -l -n, then the entries I expect are not there. I suspect that starting at '1' just doesn't load anything at all. Thanks, BK -Original Message- From: Boyd Kelly Sent: Thu 07/03/2002 7:27 AM To: barwals; [EMAIL PROTECTED] Cc: Subject: RE: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein Thanks Sudhir, Started with INTERN_SERVER1 and sorks fine now. BK -Original Message- From: barwals [mailto:[EMAIL PROTECTED]] Sent: March 7, 2002 12:18 AM To: [EMAIL PROTECTED] Subject: Re: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein Dear Body, Please do not start with INTERN_SERVER0 instead start with INTERN_SERVER1. I hope you will not get any error. I was also getting the same error but after changing 0 (zero) to 1. And I didnot got any error. Thanks. Sudhir Boyd Kelly wrote: Hello, Making good progress on my Dachstein migration, but just had a hiccup with forwarding. The uncommented line (well they all would) from below gives me an error when starting the network: IP filters: portfw: Invalid protocol specified. The INTERN_SERVER section (not indexed) works ok, but I have too many entries. Those shown below are just some of what I have to do. As usual any help is very much appreciated. Boyd # Advanced settings: parameters passed directly to portfw and autofw # Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R 192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R $PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80 #INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443 #INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800 #INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900 #INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53 #INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Þiû¬z¹X§X¬´·~ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣù^iû¬z
RE: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list) Dachstein
Thanks Charles.
I am probably missing something, but as per below this is what happens if I start at
zero.
The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw: Invalid
protocol specified.
I do realize I can use the non indexed section as well.
Thanks for any help.
-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]]
Sent: Thu 07/03/2002 11:37 AM
To: Boyd Kelly; barwals; [EMAIL PROTECTED]
Cc:
Subject: Re: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list)
Dachstein
I take it back.
When starting with INTERN_SERVER1, if I do an ipmasqadm portfw -l -n, then
the entries I expect are not there. I suspect that starting at '1' just
doesn't load anything at all.
This is what I would expect to happen...indexed lists start with zero, and
continue to the first missing number. If the zero entry is missing, no
other variables will be processes.
snip
Making good progress on my Dachstein migration, but just had a hiccup
with forwarding. The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw: Invalid
protocol specified.
The INTERN_SERVER section (not indexed) works ok, but I have too many
entries. Those shown below are just some of what I have to do.
# Advanced settings: parameters passed directly to portfw and autofw #
Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR
RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R
192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R
$PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80
#INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443
#INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800
#INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900
#INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53
#INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53
Looking through the scripts, the comments above are incorrect. From the
actual procedure doing the port-forwarding:
# A function to portforward services, setup to be called by walk_list
# $1 = Name of environment variable to use for arguments
# Arguments as they should appear in the environment variable:
# protocol Laddr Lport Raddr [ Rport [ preference ] ]
port_forward () {
So...Remove the -a, -P, -L, and -R fields from your INTERN_SERVER entries,
start with INTERN_SERVER0, and everything should work properly.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
Þiû¬z¹X§X¬´·~ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣù^iû¬z
[Leaf-user] Dachstein migration successful! - General routing question.
Got my ip aliasing/forwarding and all working on dachstein. Very happy about that. Great piece of work! Now for an interesting problem: One guy behind my leaf firewall needs a securemote (Checkpoint) connection to company b. He has a Win2k workstation. As I understand from searching the newsgroups, this isn't possible with Linux, although I would love to be corrected on that one. So I am looking for some opinions on a solution. Could I just do some routing magic on the win2k workstation to bypass the leaf router only for that securemote ip address? For something like that to work would the workstation need a second nic? Or can I just plug all the Internet/Leaf wires into the same switch, and then give computer 3 a default gateway of 208.x.x.1 for the address in question? Any security issues? [Internet] | eth0 208.x.x.13 | LEAF Box (DF 208.x.x.1) | | eth1 192.168.1.254 | --- | | Computer 2Computer 3 (needs to use securemote client) (192.168.1.2) (192.168.1.3) Thanks very much, Boyd ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Problem with 3c59x.o on Dachstein disk
A quick look at the modules for dachstein, oxygen and lrp 2.9.8 don't have any 3c90x module available. I remember finding one somewhere, but found that the 3c59x works. Why does 3com have such a confusing numbering system for their products anyways? 905; 509; 59x?. Cheers and have a good one. BK -Original Message- From: Jeff Newmiller [mailto:[EMAIL PROTECTED]] Sent: March 6, 2002 5:06 PM To: Stephen Lee Cc: Leaf-user Subject: Re: [Leaf-user] Problem with 3c59x.o on Dachstein disk On 6 Mar 2002, Stephen Lee wrote: Hi, Maybe I'm missing something here but don't you want to load the 3c90x module? That is one option. Newer (than what I don't know exactly) versions of 3c59x are supposed to support the 3C905C NIC, but I haven't used any of them personally. 3c59x is Becker's, and 3c905c is 3Com's. http://www.scyld.com/network/vortex.html On Tue, 2002-03-05 at 10:56, Simon Bolduc wrote: I'm not sure whether the 905c's are supported by this driver - I do know that 905c's are quite different from 905b's - and did require different drivers when I was using certain dists. Have you uncommented the pci-scan module? S From: Boyd Kelly [EMAIL PROTECTED] To: Charles Steinkuehler [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: [Leaf-user] Problem with 3c59x.o on Dachstein disk Date: Tue, 5 Mar 2002 10:18:31 -0800 Hi, I have a 3c905C card. When I try to insmod 3c59x, i get error: Unresolved symbol acpi_wake, acpi_set_pwr_state, pci_drv_unregister, pci_drv_register. Tried to download a copy dated dec 1 from devel/cstein/files/kernels/Dachstein-small/modules/net with same result. Any other possibilities? Thanks Boyd ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user --- Jeff NewmillerThe . . Go Live... DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein
Hello, Making good progress on my Dachstein migration, but just had a hiccup with forwarding. The uncommented line (well they all would) from below gives me an error when starting the network: IP filters: portfw: Invalid protocol specified. The INTERN_SERVER section (not indexed) works ok, but I have too many entries. Those shown below are just some of what I have to do. As usual any help is very much appreciated. Boyd # Advanced settings: parameters passed directly to portfw and autofw # Indexed list: ipmasqadm portfw options #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R 192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R $PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80 #INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443 #INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800 #INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900 #INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53 #INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Ip aliasing
Hi Scott and others, I'm still looking at Oxygen and Dachstein. Oxygen looks really good but it's setup didn't work well for me, and have only just looked at dachstein. But let me explain what I have been doing till now. I have a 2.9.8 LRP and I have 3 ip addresses bound to my external interface. I just added this to network.conf and it works great: IF0_IFNAME=eth0 IF0_IPADDR=208.x.x.197 IF0_NETMASK=255.255.254.0 IF0_BROADCAST=208.181.73.255 IF0_IP_SPOOF=YES IF1_IFNAME=eth1 IF1_IPADDR=192.168.73.1 IF1_NETMASK=255.255.255.0 IF1_BROADCAST=192.168.73.255 IF1_IP_SPOOF=YES IF2_IFNAME=eth0:0 IF2_IPADDR=208.x.x.196 IF2_NETMASK=$IF0_NETMASK IF2_BROADCAST=$IF0_BROADCAST IF2_IP_SPOOF=YES IF3_IFNAME=eth0:1 ... Then I call my own firewall script from network_direct.conf using ipchains and also forward to three boxes behind. Since I run a couple of mail servers, the flexibility of NAT is very practical. Looking at dachstein network.conf, I think I might be a able to accomplish the same without my script, but I am willing to work with or without it. In any case though I am not sure how to go about the 3 ip's on eth0 in dachstein. Once I get that going I can start on the pptp stuff. Any suggestions much appreciated. Thanks, Boyd -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED]] Sent: March 4, 2002 6:18 PM To: Boyd Kelly Subject: RE: [Leaf-user] forwarding Protocal 47(gre) on Eigerstein LRP Boyd: Heya. You may be right: Oxygen is a great platform, but Dachstein is a better out-of-the-box solution. -Scott On Mon, 4 Mar 2002, Boyd Kelly wrote: Thanks Scott, I've been fiddling around with the Oxygen version today. Seems like the Dachstein will be a better bet for what I want to do. Will try it out tomorrow. Boyd -Original Message- From: Scott C. Best [mailto:[EMAIL PROTECTED]] Sent: March 4, 2002 10:42 AM To: Lonnie Cumberland Cc: [EMAIL PROTECTED]; Boyd Kelly Subject: Re: [Leaf-user] forwarding Protocal 47(gre) on Eigerstein LRP Lonnie, Boyd: Ah, serendipity. :) One email, two answers... To get a PPTP-based VPN client working from behind a LEAF/LRP disk, you need to do four things (none of which is to search the email archives, though that works too ;): 1. Be sure to be using a VPN enabled kernel. Dachstein has this by default. Earlier stuff, including 2.9.8, doesn't. See Charles' page for the kernels. If you install a new one, *always* install with it the associated modules. 2. Load the PPTP masq module: uncomment its line in /etc/modules, backup, reboot. 3. Goof the firewall rules to allow protocol 47 and port 1723 in. 4. Use the ipfwd utility (ships by default) to forward the GRE (protocol 47) packets across the firewall. As you'd expect, steps 3 4 are done for you automagically using the echoWall package. Hope this helps! -Scott On Sun, 3 Mar 2002, Lonnie Cumberland wrote: Hello, Could you please tell me how to prot forward this protocal 47 on my Eigerstein LRP box? I know how to forward regular ports coming in to a server behind the firewall, but I do not know about htis protocal 47 (gre) Thanks, Lonnie ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Problem with 3c59x.o on Dachstein disk
Hi, I have a 3c905C card When I try to insmod 3c59x, i get error: Unresolved symbol acpi_wake, acpi_set_pwr_state, pci_drv_unregister, pci_drv_register Tried to download a copy dated dec 1 from devel/cstein/files/kernels/Dachstein-small/modules/net with same result Any other possibilities? Thanks Boyd y§î±êæj)b b²ÒÞiû¬z¹b²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²ÊÇ¢¸ ë+-³ùb²Ø§~åy§î±ê
