A "problem" exists with SuSE's installation
As many of you know, I've been struggling to get the Beast to reach the WWW via the Sony. There have been major impediments in reaching this goal. First is the fact that even though ip forwarding was set on the Sony, include the '1' stuff, it still wouldn't work. It seems that ipchains doesn't understand ipchains protocol, amazing as that may sound. The install on the Sony started with the default 2.2.18 kernel. I recompiled it to turn off sound (so that I could use the OSS sound) and to enable parport and ppa modules so that I could make the Zip100 drive work. Sound and the Zip drive work well. The ip config settings were default and never changed. ipchains and ipmasq were automatically installed by YaST2 when I installed 7.1 It's disconcerting that, for my hardware, it doesn't work. Well, I've run into YAP (Yet Another Problem). The Beast has an ATPIA CDROM drive, a PleXwriter 8/4/12. For the forth time I reinstalled 7.1 on the Beast. I did so for two reasons: 1) I wanted to install 'everything' and 2) from my readings of what it takes to get the CDRW to burn CDs I have to install the atpia-scsi emulation in the kernel. When I took a look at the /usr/src/linux symbolic link I found it pointing to the 2.4.0 kernel even though I had installed the 2.2.18 kernel. AND, in looking at the /lib/modules/2.2.18 directory I noticed another symbolic link in it that was NOT pointing to the 2.2.18 kernel but was cross-linked to the 2.4.0 kernel. THIS CAN'T BE RIGHT. Basically, when 7.1 installs on my old Sony it slides on like a silk purse (except of the ip forwarding thing). However, getting it to go onto the Beast has been a beast of a fight. It might be worth it to swap the ATPI CDROM for a scsi version and ditto for the Zip250. Another thing I found was that the USB is installed in the kernel even when I have disabled it in the BIOS. SuSE should honor the BIOS settings and not install any software for hardware that the BIOS has disabled. JLK
Jerry Kreps wrote: ...
Sound and the Zip drive work well. The ip config settings were default and never changed. ipchains and ipmasq were automatically installed by YaST2 when I installed 7.1
installed but not activcated (unless you say yes to personal-firewall when setting up a modem internet connection with yast2)
It's disconcerting that, for my hardware, it doesn't work.
I don't believe you. The network code has nothing whatsoever to do with any hardware. That's purely the device layer.
.... When I took a look at the /usr/src/linux symbolic link I found it pointing to the 2.4.0 kernel even though I had installed the 2.2.18 kernel. AND, in looking at the /lib/modules/2.2.18 directory I noticed another symbolic link in it that was NOT pointing to the 2.2.18 kernel but was cross-linked to the 2.4.0 kernel. THIS CAN'T BE RIGHT.
You installed 2.2.18 but 2.4 sources. Install 2.2.18 sources (package lx_sus22) instead.
Basically, when 7.1 installs on my old Sony it slides on like a silk purse (except of the ip forwarding thing). However, getting
What on earth do you need FORWARDING for on a notebook???? Do you use it as router for other machines??? A notebook?
it to go onto the Beast has been a beast of a fight. It might be worth it to swap the ATPI CDROM for a scsi version and ditto for the Zip250.
Another thing I found was that the USB is installed in the kernel even when I have disabled it in the BIOS. SuSE should honor the BIOS settings and not install any software for hardware that the BIOS has disabled.
The kernel code is always there of course, at least the small part that's not a module. What do you care? If it's disabled in the BIOS it won't do anything. If you're talking about usbmgr, well, set /etc/rc.config START_USB="no". But if it's disabled in the bios it won't do anything anyway.
On Sunday 18 March 2001 17:57, you wrote:
Jerry Kreps wrote: ....
Sound and the Zip drive work well. The ip config settings were default and never changed. ipchains and ipmasq were automatically installed by YaST2 when I installed 7.1
installed but not activcated (unless you say yes to personal-firewall when setting up a modem internet connection with yast2)
Someone on the list suggested using the SuSEFireWall to give the Beast the ability to send and recieve from the internet via the Sony. It didn't work for me, so I turned it off.
It's disconcerting that, for my hardware, it doesn't work.
I don't believe you.
What an ARROGANT statement! I can guarantee that a statement like that will turn an ardent supporter into a Mandrake user quicker than you can say 'I don't care". Do you think I am making this stuff up, or just lying? Or both? You can't imagine how angry your comment has made me. I am seeking help, not asking to be called a liar. If you think I don't understand Linux or SuSE well enough then enlighten me with better documentation. If it's not me then fix your software. But, UNDER NO CIRCUMSTANCES, will you ever get anything accomplished by calling a customer a liar.
The network code has nothing whatsoever to do with any hardware. That's purely the device layer.
.... When I took a look at the /usr/src/linux symbolic link I found it pointing to the 2.4.0 kernel even though I had installed the 2.2.18 kernel. AND, in looking at the /lib/modules/2.2.18 directory I noticed another symbolic link in it that was NOT pointing to the 2.2.18 kernel but was cross-linked to the 2.4.0 kernel. THIS CAN'T BE RIGHT.
You installed 2.2.18 but 2.4 sources. Install 2.2.18 sources (package lx_sus22) instead.
WRONG! I selected the "INSTALL EVERYTHING OPTION", and when I was asked which kernel to install, it offered two buttons and I could click either or both. I clicked the 2.2.18 button ONLY! I know of no way, using YaST2, of telling it to cross install the way it did. And if I only wanted the 2.2.18 why would I ever install the 2.4.0 sources. That would be a non-sequiter, even to me.
Basically, when 7.1 installs on my old Sony it slides on like a silk purse (except of the ip forwarding thing). However, getting
What on earth do you need FORWARDING for on a notebook???? Do you use it as router for other machines??? A notebook?
There you go, assuming again. Who says a Sony VAIO has to be a notebook? My Sony VAIO is a 1966 P166 **DESKTOP**. And to bring you up todate: I have a Cisco 675 router configured as a DHCP server connected to eth0 on the Sony. The Sony's eth0 is 192.168.200.2. I have added a second ethernet NIC to it and connected it, as eth1, 192.168.201.2, to a NetGear EN104 hub. The second PC, I call the "Beast", has an ethenet NIC connected to the EN104 hub too. The Beast's eth0 is 192.168.201.3. I've been trying to get the Beast to connect to the Internet through the Sony.
it to go onto the Beast has been a beast of a fight. It might be worth it to swap the ATPI CDROM for a scsi version and ditto for the Zip250.
Another thing I found was that the USB is installed in the kernel even when I have disabled it in the BIOS. SuSE should honor the BIOS settings and not install any software for hardware that the BIOS has disabled.
The kernel code is always there of course, at least the small part that's not a module. What do you care? If it's disabled in the BIOS it won't do anything. If you're talking about usbmgr, well, set /etc/rc.config START_USB="no". But if it's disabled in the bios it won't do anything anyway.
Well, for starters, I wouldn't care. But, I didn't turn the USB on in the first place. In fact, I had disabled USB in the BIOS and was suprised to see YaST2 attempt to install it anyway. And I did use the "Change the Configuration File" in YaST to turn it off. In fact, EVERYTHING I've done was/is by clicking buttons in YaST2 or running YaST. I wrote the original email to let SuSE know what happened: namely, when I selected the "Install Everything" option, and clicked the 2.2.18 kernel button, the result was that the 2.2.18 kernel was installed, the 2.4.0 source was installed, and the symbolic link, /lib/modules/2.2.18/block, points to the symbolic link /usr/src/linux and that link points to the 2.4.0 source tree. This situtation was made by the simle selection of installing everyting and selecting the 2.2.18 kernel. Oh, I did click on the 2.4 kernel button, but changed my mind and unclicked it, if that clue means anything. But, if you think I'm lying then never mind. I'll get out of your hair and go check out some other distros. Bye. JLK
Jerry Kreps wrote:
Someone on the list suggested using the SuSEFireWall to give the Beast the ability to send and recieve from the internet via the Sony. It didn't work for me, so I turned it off.
A firewall per definitionem doesn't _give_ you the ability to communicate but _limits_ it.
It's disconcerting that, for my hardware, it doesn't work.
I don't believe you.
What an ARROGANT statement! I can guarantee that a statement like that will turn an ardent supporter into a Mandrake user quicker than you can say 'I don't care". Do you think I am making this stuff up, or just lying? Or both?
No, I just don't think that your conclusion is correct. Something's wrong all right, but I don't believe it's what you say. I don't see any cause for your above accusation.
You can't imagine how angry your comment has made me. I am seeking
I indeed can't
help, not asking to be called a liar. If you think I don't understand
That is a very far reaching interpretation of a very innocent statement. I'll ignore how angry this makes ME for now and see if there's any substance in the rest of the mail. If I want to call someone a liar I _DO_ so, no need for any interpretations and reading between the lines like you did. The contents of MY statements is _IN_ the lines, not between them.
You installed 2.2.18 but 2.4 sources. Install 2.2.18 sources (package lx_sus22) instead.
WRONG! I selected the "INSTALL EVERYTHING OPTION", and when I was asked which kernel to install, it offered two buttons and I could click either or both. I clicked the 2.2.18 button ONLY!
Yes, but the sources are 2.4 as for the reason I already mentioned. When I said "you" I didn't meant to imply you were actively involved, but that this is what your system did. The sources don't have anything to do with what kernel's running, so just because you said yes to kernel 2.2.18 only doesn't give any hint about the source package actually installed.
I know of no way, using YaST2, of telling it to cross install the way it did. And if I only wanted the 2.2.18 why would I ever install the 2.4.0 sources. That would be a non-sequiter, even to me.
See reason given in email #1, which you overlooked while being angry for no reason.
What on earth do you need FORWARDING for on a notebook???? Do you use it as router for other machines??? A notebook?
There you go, assuming again. Who says a Sony VAIO has to be a notebook? My Sony VAIO is a 1966 P166 **DESKTOP**.
I didn't know they've that. I only know the notebooks next door.
And to bring you up todate: I have a Cisco 675 router configured as a DHCP server connected to eth0 on the Sony. The Sony's eth0 is 192.168.200.2. I have added a second ethernet NIC to it and connected it, as eth1, 192.168.201.2, to a NetGear EN104 hub. The second PC, I call the "Beast", has an ethenet NIC connected to the EN104 hub too. The Beast's eth0 is 192.168.201.3. I've been trying to get the Beast to connect to the Internet through the Sony.
/etc/rc.config.d/firewall.rc.config FW_DEV_WORLD="eth0" FW_DEV_INT="eth1" FW_ROUTE="yes" FW_MASQUERADE="yes" Should do it. You won't be able to use your cisco-dhcp server for anything, it seems... unless you make sure the requests (broadcasts) get through from the internal network.
In fact, EVERYTHING I've done was/is by clicking buttons in YaST2 or running YaST. I wrote the original email to let SuSE know what happened: namely, when I selected the "Install Everything" option, and clicked the 2.2.18 kernel button, the result was that the 2.2.18 kernel was installed, the 2.4.0 source was installed, and the symbolic link, /lib/modules/2.2.18/block, points to the symbolic link /usr/src/linux and that link points to the 2.4.0 source tree. This situtation was made by the simle selection of installing everyting and selecting the 2.2.18 kernel. Oh, I did click on the 2.4 kernel button, but changed my mind and unclicked it, if that clue means anything. But, if you think I'm lying then never mind. I'll get out of your hair and go check out some other distros.
Whatever.
Thanks Michael, Replacing the ipchains did it, along with putting a copy of my server's resolv.conf on my Beast. The Beast is now prowling the net! Thanks again, Jerry
participants (2)
-
Jerry Kreps -
Michael Hasenstein