I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
Just did fresh install of FC3 RC5 from DVD. LPD server printing still not working. This is kernel 649.
Gerry
Gerry Tool wrote:
Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
Just did fresh install of FC3 RC5 from DVD. LPD server printing still not working. This is kernel 649.
Gerry
On a tip from Steven Schwartz, I found that if I execute
/sbin/service iptables off
printing to the remote LPD server works.
Of course this is not a valid fix. Any ideas of a correct way to solve the problem?
Thanks.
Gerry Tool
On Sat, 30 Oct 2004 13:24:09 -0500, Gerry Tool gstool@earthlink.net wrote:
Gerry Tool wrote:
Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
Just did fresh install of FC3 RC5 from DVD. LPD server printing still not working. This is kernel 649.
Gerry
On a tip from Steven Schwartz, I found that if I execute
/sbin/service iptables off
printing to the remote LPD server works.
Of course this is not a valid fix. Any ideas of a correct way to solve the problem?
What level of the firewall did you select on the install. It might be a valid fix if you set the highest level :).
Stephen J. Smoogen wrote:
On Sat, 30 Oct 2004 13:24:09 -0500, Gerry Tool gstool@earthlink.net wrote:
Gerry Tool wrote:
Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
Just did fresh install of FC3 RC5 from DVD. LPD server printing still not working. This is kernel 649.
Gerry
On a tip from Steven Schwartz, I found that if I execute
/sbin/service iptables off
printing to the remote LPD server works.
Of course this is not a valid fix. Any ideas of a correct way to solve the problem?
What level of the firewall did you select on the install. It might be a valid fix if you set the highest level :).
I accepted the default. Steven Schwartz came up with a change to /etc/sysconfig/iptables that allows my print server to finally work. See the most recent comment in bugzilla #133064.
Gerry Tool
On Sat, 2004-10-30 at 14:48 -0500, Gerry Tool wrote:
Stephen J. Smoogen wrote:
On Sat, 30 Oct 2004 13:24:09 -0500, Gerry Tool gstool@earthlink.net wrote:
... snip ...
On a tip from Steven Schwartz, I found that if I execute
/sbin/service iptables off
Possibly you mean
# service iptables stop
and
# chkconfig iptables off
to keep it from coming back on the next reboot.
printing to the remote LPD server works.
Of course this is not a valid fix. Any ideas of a correct way to solve the problem?
What level of the firewall did you select on the install. It might be a valid fix if you set the highest level :).
I accepted the default. Steven Schwartz came up with a change to /etc/sysconfig/iptables that allows my print server to finally work. See the most recent comment in bugzilla #133064.
Setting eth0 as a trusted device (comment 33 in BZ 133064) is essentially the same as turning off the firewall if that is your only interface. Good firewall rules would be preferable, unless you REALLY trust your hardware firewall. Which begs the question - what is a good firewall tool for FC3? Have been unable to get firestarter to work. Compiles, but hangs when executed.
Phil
On Mon, 2004-11-01 at 22:38 -0500, Phil Schaffner wrote:
Setting eth0 as a trusted device (comment 33 in BZ 133064) is essentially the same as turning off the firewall if that is your only interface. Good firewall rules would be preferable, unless you REALLY trust your hardware firewall. Which begs the question - what is a good firewall tool for FC3? Have been unable to get firestarter to work. Compiles, but hangs when executed.
Shorewall (www.shorewall.net). Text files to hold configuration, so no cute GUI but you do get to access and modify it via SSH. Secure, reliable, easy to learn and use, very very powerful. 5-star tool. Well supported and documented, even.
Cheers,
Rodolfo J. Paiz wrote:
On Mon, 2004-11-01 at 22:38 -0500, Phil Schaffner wrote:
Setting eth0 as a trusted device (comment 33 in BZ 133064) is essentially the same as turning off the firewall if that is your only interface. Good firewall rules would be preferable, unless you REALLY trust your hardware firewall. Which begs the question - what is a good firewall tool for FC3? Have been unable to get firestarter to work. Compiles, but hangs when executed.
Shorewall (www.shorewall.net). Text files to hold configuration, so no cute GUI but you do get to access and modify it via SSH. Secure, reliable, easy to learn and use, very very powerful. 5-star tool. Well supported and documented, even.
Cheers,
Thanks to Phil for the comments and to Rodolfo for the link. I have decided to go the safe route and have ordered a copy of "Red Hat Linux Firewalls" by Bill McCarty. I will also try out shorewall.
Gerry
Hello, I have installed FC3 rc3 on my machine with the hardwares listed beloew :
Motherboard : ASUS A8V Deluxe CPU : AMD Athlon64 3500+ AGP card : ASUS ATI9200SE/TD Monitor : IIyama LCD AS4314UT RAM : 512MB Samsung DDR3200 Single Channel HDD : Seagate Barracuda 7200.7 160Gb
The installation run and terminate with no problems. But when I reboot the system to running for the first time, firstly it cannot recognise my monitor as it could with FC2 or FC3 test 3. Then I choose Generic LCD 17' and continue... All steps of first time setup are finished without problem, but then when the system starts loading, it hangs up and I see many lines with all colors on my screen.
I thinh that there's a problem with my monitor(which is not recognised) or with my AGP card because I can run FC2 smoothly.
So someone could tell me how to solve this problem?
Thank you all.
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
On Tue, 2004-11-02 at 10:15 -0600, Gerry Tool wrote:
Rodolfo J. Paiz wrote:
On Mon, 2004-11-01 at 22:38 -0500, Phil Schaffner wrote:
Setting eth0 as a trusted device (comment 33 in BZ 133064) is essentially the same as turning off the firewall if that is your only interface. Good firewall rules would be preferable, unless you REALLY trust your hardware firewall. Which begs the question - what is a good firewall tool for FC3? Have been unable to get firestarter to work. Compiles, but hangs when executed.
Shorewall (www.shorewall.net). Text files to hold configuration, so no cute GUI but you do get to access and modify it via SSH. Secure, reliable, easy to learn and use, very very powerful. 5-star tool. Well supported and documented, even.
Cheers,
Thanks to Phil for the comments and to Rodolfo for the link. I have decided to go the safe route and have ordered a copy of "Red Hat Linux Firewalls" by Bill McCarty. I will also try out shorewall.
Well, checked out shorewall and it does indeed seem powerful and thoroughly documented, but is overkill for my little home network requirements, plus must admit to having gotten used to the Firestarter cute GUI - a tough admission from an old command-line guy. Anyway, had another look around and found the new 1.0 beta release (Firestarter 0.9.9b3.2) with a .src.rpm. Had previously tried the one from Fedora.US. The rpm builds and seems to work (-: plus it has the cute penguin with the match ;^). Still don't see an option for the LPD port explicitly, but you can at least add services by name or port for individual hosts or networks. May be worth a look.
Phil
On Tue, 2004-11-02 at 23:53 -0500, Phil Schaffner wrote:
Well, checked out shorewall and it does indeed seem powerful and thoroughly documented, but is overkill for my little home network requirements, plus must admit to having gotten used to the Firestarter cute GUI - a tough admission from an old command-line guy.
You are more than welcome to keep Firestarter. No one tool is suitable for all tasks. However, should you desire to attempt Shorewall, let me offer (from memory, so not 100% guaranteed!) a quick-quick-start:
1. Create a "net" and a "loc" zone in zones file. Probably already there, not much to do. If not there, format is "net Net Internet" and "loc Local Local Zone".
2. Write "eth0 net" and "eth1 loc" lines in interfaces file. Check that eth0 is actually your outside interface, adjust to needs. For reference, since my Internet access (external) interface gets its address via DHCP, mine actually say:
net eth0 detect blacklist,dhcp loc eth1 detect
3. Check that "loc net ACCEPT" in in policy file if you want your local network unrestricted access to the Net (most common).
4. Add rules like "AllowSSH net fw" into the rules file.
5. Add "eth1" (your local interface) to the routestopped file.
6. If you want the local network on eth1 to access the Internet via eth0 using masquerading, add "eth0 eth1" to the masq file.
7. Remove the startup_disabled file.
8. /sbin/chkconfig shorewall on
9. /sbin/service shorewall start
That, and a little judicious reading of the docs inside each file, should have you up and running in less than 100 seconds if I haven't made any grievous mistakes. But even if I have, it's a good start to show what needs to be done to get the average home firewall up and running with Shorewall.
Cheers,
On Wed, 2004-11-03 at 00:18 -0600, Rodolfo J. Paiz wrote:
On Tue, 2004-11-02 at 23:53 -0500, Phil Schaffner wrote:
Well, checked out shorewall and it does indeed seem powerful and thoroughly documented, but is overkill for my little home network requirements, plus must admit to having gotten used to the Firestarter cute GUI - a tough admission from an old command-line guy.
You are more than welcome to keep Firestarter. No one tool is suitable for all tasks. However, should you desire to attempt Shorewall, let me offer (from memory, so not 100% guaranteed!) a quick-quick-start:
- Create a "net" and a "loc" zone in zones file. Probably already
there, not much to do. If not there, format is "net Net Internet" and "loc Local Local Zone".
- Write "eth0 net" and "eth1 loc" lines in interfaces file. Check that
eth0 is actually your outside interface, adjust to needs. For reference, since my Internet access (external) interface gets its address via DHCP, mine actually say:
net eth0 detect blacklist,dhcp loc eth1 detect ... snip ...
Very nice guide to augment quickstart docs. Will pass it on to the admin at work, and may help the OP; although looks like he may have the same single-Ethernet setup I have. For a simple end-user firewall to backup in case any bad guys get through the router, will stick with Firestarter, now that it works again.
Thanks for being so helpful.
Cheers, Phil
On Mon, 2004-01-11 at 22:53 -0600, Rodolfo J. Paiz wrote:
Shorewall (www.shorewall.net). Text files to hold configuration, so no cute GUI but you do get to access and modify it via SSH. Secure, reliable, easy to learn and use, very very powerful. 5-star tool. Well supported and documented, even.
In addition to SSH, you can do configuration via Web Interface that allows you to have a GUI for the configuration of the firewall post install.
I have been using it here with great success for quite some time now on an old P-II 266 w/128MB RAM (More than required) and a 2GB HD.
Robert.
On Friday 29 October 2004 08:23 pm, Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
For the Record,
I have also installed Fedora Core 3 and I am also having problems with network printing, the only difference that I am having is with connecting to a remote CUPS server on my local network. This seems to be a problem also when I had Fedora Core 2 installed as well. Ironically, when I had a different distribution of Linux on my server, the other computers could "see" the print server without having to set up printing through the KDE print manager. This bug needs to be worked out before the official release.
Jeff D. Yuille
Jeffrey D. Yuille wrote:
On Friday 29 October 2004 08:23 pm, Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
For the Record,
I have also installed Fedora Core 3 and I am also having problems withnetwork printing, the only difference that I am having is with connecting to a remote CUPS server on my local network. This seems to be a problem also when I had Fedora Core 2 installed as well. Ironically, when I had a different distribution of Linux on my server, the other computers could "see" the print server without having to set up printing through the KDE print manager. This bug needs to be worked out before the official release.
Jeff D. Yuille
It might be useful for you to add your comments to bugzilla #133064. That bug report has been reassigned to the kernel, and even though it is for remote LPD servers, the problem with remote CUPS servers may be from the same root cause.
Gerry
personally, telling system-config-securitylevel to open 631:udp made it possible for me to use printer service discovery...
Why isn't this listed in the "list" of ports in s-c-s?
lør, 30.10.2004 kl. 19.48 skrev Gerry Tool:
Jeffrey D. Yuille wrote:
On Friday 29 October 2004 08:23 pm, Gerry Tool wrote:
I have just done a fresh install of FC3, Release Candidate 3. Printing to a networked LPD server still will not work. This is a bug (#133064) that is assigned to the kernel. Telnet to the print server fails, but ping succeeds. FC2 telnets fine to the print server.
Gerry Tool
For the Record,
I have also installed Fedora Core 3 and I am also having problems withnetwork printing, the only difference that I am having is with connecting to a remote CUPS server on my local network. This seems to be a problem also when I had Fedora Core 2 installed as well. Ironically, when I had a different distribution of Linux on my server, the other computers could "see" the print server without having to set up printing through the KDE print manager. This bug needs to be worked out before the official release.
Jeff D. Yuille
It might be useful for you to add your comments to bugzilla #133064. That bug report has been reassigned to the kernel, and even though it is for remote LPD servers, the problem with remote CUPS servers may be from the same root cause.
Gerry
-
Gerry Tool -
Jeffrey D. Yuille -
Kyrre Ness Sjobak -
NGUYEN Dang-Truc -
Phil Schaffner -
Robert Couture -
Rodolfo J. Paiz -
Stephen John Smoogen