Re: Adobe announces 64-bit Flash plugin for Linux (Alpha verson)
On Wed, 2008-11-19 at 15:26 -0800, Wolfgang S. Rupprecht wrote: > "Patrick O'Callaghan" <[EMAIL PROTECTED]> writes: > > http://labs.adobe.com/technologies/flashplayer10/ > > See also http://linux.slashdot.org/linux/08/11/17/168212.shtml > > They have no rpm and their instructions suck, but the plugin itself > seems to be ok. I've been using it for a few days. > > Here is what I did to install it so that all the users could have > access: > > yum erase flash-plugin.i386 nspluginwrapper.x86_64 nspluginwrapper.i386 It's not necessary to remove nspluginwrapper, which is used for other stuff besides Flash. Just don't configure it for the flash plugin. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
Simon Slater wrote: > > ACCEPT tcp -- anywhere anywheretcp > spt:nicname state NEW,ESTABLISHED > ACCEPT udp -- anywhere anywhereudp > spt:nicname state NEW,ESTABLISHED > spt=source port You want the destination port. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
[EMAIL PROTECTED] wrote: Sorry, what means about the sentence ? The last line of the script that I suggested to you was: passwd -- "$1" That line would be more secure if it were specific about where "passwd" should be: /usr/bin/passwd -- "$1" -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
On Thu, 2008-11-20 at 11:25 +1100, Simon Slater wrote: > > On Thu, 2008-11-20 at 07:25 +0800, Ed Greshko wrote: > > Simon Slater wrote: > > > On Thu, 2008-11-20 at 06:43 +0800, Ed Greshko wrote: > > > > > >>> I suppose the config file is the first place to look, but what > > >>> > > >> is the > > >> > > >>> relevant section? Couldn't see anything relevant in bugzilla. I'm > > >>> using F8 if that makes a difference. > > >>> > > >>> > > >>> > > >> Q1 Are all whois requests timing out or just this one? e.g. whois > > >> cnn.com works? fails? > > >> > > >> > > > [EMAIL PROTECTED] ~]$ whois cnn.com > > > [Querying whois.verisign-grs.com] > > > [Unable to connect to remote host] > > > [EMAIL PROTECTED] ~]$ > > > All for the past while, Ed, but not sure when it started. > > > > > >> Q2 Have you tried something like wireshark or tcpdump and filtered > > >> on > > >> port 43 (whois port)? > > >> > > >> > > > Nothing at all on wireshark port 43 TCP nor UDP. So the request is not > > > being sent at all? > > > > > Right... Not going out at all Something with your firewall setup? > > > I think I got the iptables syntax wrong on that try. Someone's just > dropped in. I'll post back soon with the results. > Back again. I made changes to the iptables rules but still no joy. The changes must not be correct because in the logs are: Nov 20 13:59:14 ipex kernel: [IPTABLES DROP] : IN= OUT=ppp0 SRC=59.101.172.32 DST=192.149.252.44 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=6278 DF PROTO=TCP SPT=40743 DPT=43 WINDOW=5840 RES=0x00 SYN URGP=0 Nov 20 13:59:17 ipex kernel: [IPTABLES DROP] : IN= OUT=ppp0 SRC=59.101.172.32 DST=192.149.252.44 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=6279 DF PROTO=TCP SPT=40743 DPT=43 WINDOW=5840 RES=0x00 SYN URGP=0 Nov 20 13:59:26 ipex kernel: [IPTABLES DROP] : IN= OUT=ppp0 SRC=59.101.172.32 DST=199.43.0.144 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=46068 DF PROTO=TCP SPT=50299 DPT=43 WINDOW=5840 RES=0x00 SYN URGP=0 Nov 20 13:59:29 ipex kernel: [IPTABLES DROP] : IN= OUT=ppp0 SRC=59.101.172.32 DST=199.43.0.144 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=46069 DF PROTO=TCP SPT=50299 DPT=43 WINDOW=5840 RES=0x00 SYN URGP=0 Nov 20 13:59:33 ipex kernel: [IPTABLES DROP] : IN= OUT=ppp0 SRC=59.101.172.32 DST=199.7.51.74 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=46927 DF PROTO=TCP SPT=44984 DPT=43 WINDOW=5840 RES=0x00 SYN URGP=0 The additions to the iptable rules are in the snipped listing below. What did I do wrong? [EMAIL PROTECTED] ~]# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhereicmp echo-reply ACCEPT icmp -- anywhere anywhereicmp destination-unreachable ACCEPT tcp -- anywhere anywheremultiport sports http,https state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywheremultiport dports http,https state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywheretcp spt:domain state ESTABLISHED ACCEPT udp -- anywhere anywhereudp spt:domain state ESTABLISHED ACCEPT tcp -- anywhere anywheremultiport sports smtp,pop3,nntp state ESTABLISHED ACCEPT tcp -- anywhere anywheretcp dpt:smtp state ESTABLISHED ACCEPT tcp -- anywhere anywheretcp dpt:nicname state ESTABLISHED ACCEPT udp -- anywhere anywhereudp dpt:nicname state ESTABLISHED Chain FORWARD (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywheretcp dpt:nicname ACCEPT udp -- anywhere anywhereudp dpt:nicname LOG_DROP all -- anywhere anywhere Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT tcp -- anywhere anywheretcp spt:nicname state NEW,ESTABLISHED ACCEPT udp -- anywhere anywhereudp spt:nicname state NEW,ESTABLISHED ACCEPT tcp -- anywhere anywheretcp dpt:ftp state NEW,ESTABLISHED ACCEPT tcp -- anywhere anywheretcp dpt:ftp-data state NEW,ESTABLISHED ACCEPT tcp -- anywhere anywheretcp spts:1024:65535 dpts:1024:65535 state NEW,RELATED,ESTABLISHED ACCEPT all -- anywhere 192.168.0.0/24 ACCEPT udp -- default 255.255.255.255 udp spt:bootps dpt:bootpc ACCEPT all -- ipex.local 192.168.0.0/24 LOG_DROP all -- anywhere anywhere Chain LOG_ACCEPT (8 references) target prot opt source destination LOGall -- anywhere anywhereLOG level warning prefix `[IPTABLES ACCEPT] : ' ACCEPT all -- anyw
Re: Moving Fedora 9 Hard Disk To Another System
On Wed, Nov 19, 2008 at 6:08 PM, Mikkel L. Ellertson <[EMAIL PROTECTED]> wrote: > What is more likely is that the motherboard is using a different > hard drive controller. The new controller requires a different > module from the original one. So you have to build a new initrd for > that system. This was covered in detail on the list a while back. Do you have a date reference? I'd like to take a look at the thread. thanks ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Moving Fedora 9 Hard Disk To Another System
On Wed, Nov 19, 2008 at 6:08 PM, Mikkel L. Ellertson <[EMAIL PROTECTED]> wrote: > What is more likely is that the motherboard is using a different > hard drive controller. The new controller requires a different > module from the original one. So you have to build a new initrd for > that system. This was covered in detail on the list a while back. Do you have a date reference? I'd like to take a look at the thread. thanks ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Network Card Naming Issue
On Wed, 19 Nov 2008 19:05:54 -0600 "Mikkel L. Ellertson" <[EMAIL PROTECTED]> wrote: > Take a look at /etc/udev/rules.d/70-persistent-net.rules Yep. It happens to other hardware as well. I replaced a dead DVD drive and spent quite a while tracking down why it came up as /dev/sr1 instead of /dev/sr0 (similar persistent .rules file with different name). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Moving Fedora 9 Hard Disk To Another System
Manish Kathuria wrote: > For a large installation of Fedora 9 we are cloning an updated system > on identical hard disks and then using that hard disk on other > systems. Most of the systems are either Pentium 4 or Core Duo > processor based and are capable of running the same kernel (i686) The > minor problems being faced include difference in network card drivers > requiring reconfiguration . However in certain cases, though we are > able to successfully boot Fedora 9 on a system using a cloned hard > disk but if the same hard disk is moved to another system having a > different motherboard, the system boot process comes to a halt after a > few steps as it is not able to locate the file systems on the hard > disk. The GRUB screen is displayed indicating that the MBR is being > read properly. Can there be a likelihood of the disk geometry being > interpreted in different manner leading to non recognition of > filesystems ? I would appreciate any tips or suggestions. > What is more likely is that the motherboard is using a different hard drive controller. The new controller requires a different module from the original one. So you have to build a new initrd for that system. This was covered in detail on the list a while back. Depending on the other hardware, you may have to run kudzu, or you may have to delete some or all of the /etc/udev/rules.d/??-persistent*.rules files. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
Michael Schwendt wrote: Hence let the script run /usr/bin/passwd at the bottom, which is exactly what you want. Hello, Sorry, what means about the sentence ? Thanks ! Edward. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
getting /lib/ld-linux.so.2 on a 64-bit f10 preview install?
long story short: x86-64 f10 preview install on AMD64 laptop. install coldfire cross-compile toolchain, which immediately fails looking for /lib/ld-linux.so.2, which it obviously won't find since the system has /lib64/ld-2.9.so (along with various symlinks). solution? rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Network Card Naming Issue
On Thu, Nov 20, 2008 at 6:35 AM, Mikkel L. Ellertson <[EMAIL PROTECTED]> wrote: > Manish Kathuria wrote: >> Hi, >> >> I have experienced a strange issue in Fedora 9 while replacing >> ethernet cards. Whenever a network card is replaced in Fedora 9, many >> times the new NIC takes a new logical interface name instead of taking >> the original interface name. For example, if a network card eth0 is >> removed from a Fedora 9 system and is replaced by another network >> card, the new card appears as eth1 or eth2 instead of eth0. This >> happens even if the cards are having the same chipset (and therefore >> the driver). What could be the reason for this behaviour ? It leads >> to a number of problems like modification in scripts, etc. I have >> never observed this in the earlier distributions. >> > Take a look at /etc/udev/rules.d/70-persistent-net.rules > > Mikkel > -- > I think that could be the reason. Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Network Card Naming Issue
On Thu, Nov 20, 2008 at 6:37 AM, Tim <[EMAIL PROTECTED]> wrote: > On Thu, 2008-11-20 at 06:15 +0530, Manish Kathuria wrote: >> Whenever a network card is replaced in Fedora 9, many times the new >> NIC takes a new logical interface name instead of taking the original >> interface name. For example, if a network card eth0 is removed from a >> Fedora 9 system and is replaced by another network card, the new card >> appears as eth1 or eth2 instead of eth0. > > Do you have an eth0 configuration file that has a HWADDR= line in it, > with the MAC of your old ethernet card after the equals sign? If so, > then it's holding eth0 for that card, even if that card isn't still in > the box. Remove the line, or set it to the MAC of your new card. > > See: /etc/sysconfig/networking/devices/ifcfg-eth0 > > -- > [EMAIL PROTECTED] ~]$ uname -r > 2.6.27.5-37.fc9.i686 Had already removed the offending line but it made no difference. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Moving Fedora 9 Hard Disk To Another System
For a large installation of Fedora 9 we are cloning an updated system on identical hard disks and then using that hard disk on other systems. Most of the systems are either Pentium 4 or Core Duo processor based and are capable of running the same kernel (i686) The minor problems being faced include difference in network card drivers requiring reconfiguration . However in certain cases, though we are able to successfully boot Fedora 9 on a system using a cloned hard disk but if the same hard disk is moved to another system having a different motherboard, the system boot process comes to a halt after a few steps as it is not able to locate the file systems on the hard disk. The GRUB screen is displayed indicating that the MBR is being read properly. Can there be a likelihood of the disk geometry being interpreted in different manner leading to non recognition of filesystems ? I would appreciate any tips or suggestions. Thanks, -- Manish Kathuria -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
Steve West wrote: > > What else does the ACPI service do? > It depends on your system. The power button is captured and processed by default by acpid, but there are other packages that add more rules for other ACPI events. You can also add your own rules. Take a look in /etc/acpi/events to see what events are being processed. You may also want to take a look at /etc/acpi/actions. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
Aaron Konstam wrote: >> Yes, you need acpid running for the power switch to work. It does >> not run during run level 1 by default. Run level 1 is normally >> reserved for fixing problems on the system, as it outs it in the >> single user mode, with root as the user. Only the minimum services >> necessary are started. >> > I agreee with the above but this raises the question what would running > halt do? > Running halt or shutdown works the same as it does in any other run level. There is just less for shutdown to actually shut down. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Network Card Naming Issue
On Thu, 2008-11-20 at 06:15 +0530, Manish Kathuria wrote: > Whenever a network card is replaced in Fedora 9, many times the new > NIC takes a new logical interface name instead of taking the original > interface name. For example, if a network card eth0 is removed from a > Fedora 9 system and is replaced by another network card, the new card > appears as eth1 or eth2 instead of eth0. Do you have an eth0 configuration file that has a HWADDR= line in it, with the MAC of your old ethernet card after the equals sign? If so, then it's holding eth0 for that card, even if that card isn't still in the box. Remove the line, or set it to the MAC of your new card. See: /etc/sysconfig/networking/devices/ifcfg-eth0 -- [EMAIL PROTECTED] ~]$ uname -r 2.6.27.5-37.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Need to control loading of usb-storage
Jean Francois Martinez wrote: > Unfortunetely the usb-storage string appers nowhere in /etc or in > the hal directories under /usr > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Network Card Naming Issue
Manish Kathuria wrote: > Hi, > > I have experienced a strange issue in Fedora 9 while replacing > ethernet cards. Whenever a network card is replaced in Fedora 9, many > times the new NIC takes a new logical interface name instead of taking > the original interface name. For example, if a network card eth0 is > removed from a Fedora 9 system and is replaced by another network > card, the new card appears as eth1 or eth2 instead of eth0. This > happens even if the cards are having the same chipset (and therefore > the driver). What could be the reason for this behaviour ? It leads > to a number of problems like modification in scripts, etc. I have > never observed this in the earlier distributions. > Take a look at /etc/udev/rules.d/70-persistent-net.rules Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Network Card Naming Issue
Hi, I have experienced a strange issue in Fedora 9 while replacing ethernet cards. Whenever a network card is replaced in Fedora 9, many times the new NIC takes a new logical interface name instead of taking the original interface name. For example, if a network card eth0 is removed from a Fedora 9 system and is replaced by another network card, the new card appears as eth1 or eth2 instead of eth0. This happens even if the cards are having the same chipset (and therefore the driver). What could be the reason for this behaviour ? It leads to a number of problems like modification in scripts, etc. I have never observed this in the earlier distributions. Thanks, -- Manish -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
On Thu, 2008-11-20 at 07:25 +0800, Ed Greshko wrote: > Simon Slater wrote: > > On Thu, 2008-11-20 at 06:43 +0800, Ed Greshko wrote: > > > >>> I suppose the config file is the first place to look, but what > >>> > >> is the > >> > >>> relevant section? Couldn't see anything relevant in bugzilla. I'm > >>> using F8 if that makes a difference. > >>> > >>> > >>> > >> Q1 Are all whois requests timing out or just this one? e.g. whois > >> cnn.com works? fails? > >> > >> > > [EMAIL PROTECTED] ~]$ whois cnn.com > > [Querying whois.verisign-grs.com] > > [Unable to connect to remote host] > > [EMAIL PROTECTED] ~]$ > > All for the past while, Ed, but not sure when it started. > > > >> Q2 Have you tried something like wireshark or tcpdump and filtered > >> on > >> port 43 (whois port)? > >> > >> > > Nothing at all on wireshark port 43 TCP nor UDP. So the request is not > > being sent at all? > > > Right... Not going out at all Something with your firewall setup? > I think I got the iptables syntax wrong on that try. Someone's just dropped in. I'll post back soon with the results. -- Hooroo, Simon Registered Linux User #463789. Be counted at: http://counter.li.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
Steve West wrote: What else does ACPI do besides the power switch. Take a look at the files in /etc/acpi/events/ and see. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
No snat rule in effect! Was the rule you provided in your original post verbatim? Because it had 'a' instead of the public address. In fact the rule seemed overly specific in other ways too. Here is what I have for a snat rule where the public (Internet) interface is eth1 (substitute your public ip address for a.b.c.d: -A POSTROUTING -o eth1 -j SNAT --to-source a.b.c.d Resulting in (again substituted a.b.c.d for the real public address): Chain POSTROUTING (policy ACCEPT 36819 packets, 4482K bytes) pkts bytes target prot opt in out source destination 39065 2513K SNAT all -- * eth10.0.0.0/0 0.0.0.0/0 to:a.b.c.d If your rule is correct, then you need to activate your iptables file rules by: service iptables restart Chris pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination -- "A society grows great when old men plant trees whose shade they know they shall never sit in" - Greek Proverb -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
On Wed, 2008-11-19 at 15:28 -0800, Antonio Olivares wrote: > > > --- On Wed, 11/19/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote: > > > From: Christopher K. Johnson <[EMAIL PROTECTED]> > > Subject: Re: set up NAT (network address translation) on local server > > To: "Community assistance, encouragement, and advice for using Fedora." > > > > Date: Wednesday, November 19, 2008, 2:57 PM > > What does this command produce? (shows whether your snat > > rule is implemented correctly) > > iptables -vnL -t nat > > > > And this one? (tells if ip forwarding is on) > > cat /proc/sys/net/ipv4/ip_forward > > > > Chris > > > > -- "A society grows great when old men plant trees > > whose shade they know > > they shall never sit in" - Greek Proverb > > > > -- fedora-list mailing list > > > [EMAIL PROTECTED] ~]$ su - > Password: > [EMAIL PROTECTED] ~]# iptables -vnL -t nat > Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > > Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > > Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > [EMAIL PROTECTED] ~]# cat /proc/sys/net/ipv4/ip_forward > 1 This is your Linux router? No way... Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
Antonio Olivares wrote: --- On Wed, 11/19/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote: From: Christopher K. Johnson <[EMAIL PROTECTED]> Subject: Re: set up NAT (network address translation) on local server To: "Community assistance, encouragement, and advice for using Fedora." Date: Wednesday, November 19, 2008, 2:57 PM What does this command produce? (shows whether your snat rule is implemented correctly) iptables -vnL -t nat And this one? (tells if ip forwarding is on) cat /proc/sys/net/ipv4/ip_forward Chris -- "A society grows great when old men plant trees whose shade they know they shall never sit in" - Greek Proverb -- fedora-list mailing list [EMAIL PROTECTED] ~]$ su - Password: [EMAIL PROTECTED] ~]# iptables -vnL -t nat Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination [EMAIL PROTECTED] ~]# cat /proc/sys/net/ipv4/ip_forward 1 [EMAIL PROTECTED] ~]# Try modprobe iptable_nat iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE and make sure the host itself can ping the targets you are trying. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade to 64-bit F10
On Wed, Nov 19, 2008 at 02:55:37PM -0800, Wolfgang S. Rupprecht wrote: > > Dave Feustel <[EMAIL PROTECTED]> writes: > > I have been running 64-bit OpenBSD, FreeBSD, and SUSE 11 for a while > > now. I expect that I will have no more problems with 64-bit F10 than > > I've had with the other 64-bit systems (which is to say, essentially > > none except for Maxima(caused by CLISP not working in 64-bit mode), so I > > am eager to take advantage of the extra (and bigger) registers available > > in 64-bit F10. > > I switched to fc4/64-bit (I think) from netbsd/64-bit and > openbsd/64-bit for the better apm support on the laptop, but I didn't > notice any great changes in how userland behaved. The BSD's seemed to > handle large address space programs a bit better when they started > swapping, but it wasn't enough of a problem to force me back. We are > talking about a program with a 13 gig working set and 4 gigs dram, but > with very good locality of reference. > > I'm surprised that clisp hasn't been hacked to run on Linux/64-bit. > Back when I cared about such things folks were always drooling over > large sparse address spaces and how it was going to help all sorts of > aspects of creating lisp objects. I'm surprised to see that now that > it is available nobody seems to care enough to actually make the code > work. 64-bit CLISP works on some platforms. Last I checked, OpenBSD did not have 64-bit CLISP. I think I remember that FreeBSD and SUSE11 do. I think to some degree it's a question of manpower and other resources. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
--- On Wed, 11/19/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote: > From: Christopher K. Johnson <[EMAIL PROTECTED]> > Subject: Re: set up NAT (network address translation) on local server > To: "Community assistance, encouragement, and advice for using Fedora." > > Date: Wednesday, November 19, 2008, 2:57 PM > What does this command produce? (shows whether your snat > rule is implemented correctly) > iptables -vnL -t nat > > And this one? (tells if ip forwarding is on) > cat /proc/sys/net/ipv4/ip_forward > > Chris > > -- "A society grows great when old men plant trees > whose shade they know > they shall never sit in" - Greek Proverb > > -- fedora-list mailing list [EMAIL PROTECTED] ~]$ su - Password: [EMAIL PROTECTED] ~]# iptables -vnL -t nat Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination [EMAIL PROTECTED] ~]# cat /proc/sys/net/ipv4/ip_forward 1 [EMAIL PROTECTED] ~]# Regards, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Adobe announces 64-bit Flash plugin for Linux (Alpha verson)
"Patrick O'Callaghan" <[EMAIL PROTECTED]> writes: > http://labs.adobe.com/technologies/flashplayer10/ > See also http://linux.slashdot.org/linux/08/11/17/168212.shtml They have no rpm and their instructions suck, but the plugin itself seems to be ok. I've been using it for a few days. Here is what I did to install it so that all the users could have access: yum erase flash-plugin.i386 nspluginwrapper.x86_64 nspluginwrapper.i386 cd /tmp wget http://download.macromedia.com/pub/labs/flashplayer10/libflashplayer-10.0.d20.7.linux-x86_64.so.tar.gz tar -xvzf libflashplayer-10.0.d20.7.linux-x86_64.so.tar.gz cp libflashplayer.so /usr/lib64/mozilla/plugins/libflashplayer.so -wolfgang -- Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only) You may need to config 6to4 to see the above pages. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
Simon Slater wrote: > On Thu, 2008-11-20 at 06:43 +0800, Ed Greshko wrote: > >>> I suppose the config file is the first place to look, but what >>> >> is the >> >>> relevant section? Couldn't see anything relevant in bugzilla. I'm >>> using F8 if that makes a difference. >>> >>> >>> >> Q1 Are all whois requests timing out or just this one? e.g. whois >> cnn.com works? fails? >> >> > [EMAIL PROTECTED] ~]$ whois cnn.com > [Querying whois.verisign-grs.com] > [Unable to connect to remote host] > [EMAIL PROTECTED] ~]$ > All for the past while, Ed, but not sure when it started. > >> Q2 Have you tried something like wireshark or tcpdump and filtered >> on >> port 43 (whois port)? >> >> > Nothing at all on wireshark port 43 TCP nor UDP. So the request is not > being sent at all? > Right... Not going out at all Something with your firewall setup? -- It's been a business doing pleasure with you. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
On Thu, 2008-11-20 at 06:43 +0800, Ed Greshko wrote: > > I suppose the config file is the first place to look, but what > is the > > relevant section? Couldn't see anything relevant in bugzilla. I'm > > using F8 if that makes a difference. > > > > > Q1 Are all whois requests timing out or just this one? e.g. whois > cnn.com works? fails? > [EMAIL PROTECTED] ~]$ whois cnn.com [Querying whois.verisign-grs.com] [Unable to connect to remote host] [EMAIL PROTECTED] ~]$ All for the past while, Ed, but not sure when it started. > Q2 Have you tried something like wireshark or tcpdump and filtered > on > port 43 (whois port)? > Nothing at all on wireshark port 43 TCP nor UDP. So the request is not being sent at all? -- Regards, Simon Slater Registered Linux User #463789. Be counted at: http://counter.li.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
On Wed, 2008-11-19 at 15:13 -0800, Antonio Olivares wrote: > --- On Wed, 11/19/08, Craig White <[EMAIL PROTECTED]> wrote: > > C:\Documents and Settings\6355-win2000>ping 209.131.36.158 > > Pinging 209.131.36.158 with 32 bytes of data: > > Reply from 192.168.0.1: Destination host unreachable. > Reply from 192.168.0.1: Destination host unreachable. > Reply from 192.168.0.1: Destination host unreachable. > Reply from 192.168.0.1: Destination host unreachable. > > Ping statistics for 209.131.36.158: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Documents and Settings\6355-win2000>ping www.yahoo.com > Unknown host www.yahoo.com. > > C:\Documents and Settings\6355-win2000> > > > > The problem is still at routing then :( > > Thanks for helping. Which rules should I try out? normally, to detect a routing problem, you would run traceroute command (on windows it's tracert) but of course it will only go so far before it starts showing breaks which would seem to be your Linux firewall/router. So it would be most useful to give us the output of the commands as asked for by Chris Johnson. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
--- On Wed, 11/19/08, Craig White <[EMAIL PROTECTED]> wrote: > From: Craig White <[EMAIL PROTECTED]> > Subject: Re: set up NAT (network address translation) on local server > To: [EMAIL PROTECTED], "Community assistance, encouragement, and advice for > using Fedora." > Date: Wednesday, November 19, 2008, 2:20 PM > On Wed, 2008-11-19 at 13:09 -0800, Antonio Olivares wrote: > > --- On Wed, 11/19/08, Antonio Olivares > <[EMAIL PROTECTED]> wrote: > > > > > From: Antonio Olivares > <[EMAIL PROTECTED]> > > > Subject: set up NAT (network address translation) > on local server > > > To: fedora-list@redhat.com > > > Date: Wednesday, November 19, 2008, 12:59 PM > > > Dear all, > > > > > > Starting new thread to clear up the other one: > > > Re: Make a DHCP server using Fedora - Help > > > > > > After going through the steps outlined and the > guidance > > > provided by great individuals that participate in > this list > > > :) > > > > > > /* Done now added eth1 to DHCPARGS */ > > > [EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd > > > DHCPDARGS=eth1 > > > > > > > > > I need a little bit of help in setting up NAT. I > can use > > > the system-config-firewall or I can try using > webmin or from > > > command line, I feel I can achieve the goal. > > > > > > How should I begin? > > > > > > I had done this before, but because of other > problems > > > between the devices and my errors, it did not > work :( > > > > > > # Forward all packets from eth1 (internal > network) to eth0 > > > (the public internet) > > > iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT > > > # Forward packets that are part of existing and > related > > > connections from eth0 to eth1 > > > iptables -A FORWARD -i eth0 -o eth1 -m state > --state > > > ESTABLISHED,RELATED -j ACCEPT > > > # Enable SNAT functionality on eth0. a.b.c.d are > generally > > > the ip of the eth0 > > > iptables -A POSTROUTING -t nat -s 192.168.1.0/24 > -o eth0 -j > > > SNAT --to-source a > > > > > > Thank you for helping, > > > > > > Regards, > > > > > > Antonio > > > > > > > > > > > > > > > -- > > Sorry to reply to my own thread, but some might ask if > I did the following and here's what I have done. > > > > Did this part : > > > > [EMAIL PROTECTED] ~]$ su - > > Password: > > [EMAIL PROTECTED] ~]# service dhcpd restart > > Starting dhcpd: > [ OK ] > > [EMAIL PROTECTED] ~]# tail -f /var/log/messages > > > Nov 19 15:00:02 localhost dhcpd: Copyright 2004-2007 > Internet Systems Consortium. > > > Nov 19 15:00:02 localhost dhcpd: All rights reserved. > > > Nov 19 15:00:02 localhost dhcpd: For info, please > visit http://www.isc.org/sw/dhcp/ > > > Nov 19 15:00:02 localhost dhcpd: Not searching LDAP > since ldap-server, ldap-port and ldap-base-dn were not > specified in the config file > > Nov 19 15:00:02 localhost dhcpd: Wrote 2 leases to > leases file. > > Nov 19 15:00:02 localhost dhcpd: Listening on > LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 > > > Nov 19 15:00:02 localhost dhcpd: Sending on > LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 > > > Nov 19 15:00:02 localhost dhcpd: Sending on > Socket/fallback/fallback-net > > Nov 19 15:00:06 localhost dhcpd: DHCPREQUEST for > 192.168.0.3 from 00:11:2f:35:88:2e via eth1 > > > Nov 19 15:00:06 localhost dhcpd: DHCPACK on > 192.168.0.3 to 00:11:2f:35:88:2e via eth1 > > > Nov 19 15:00:22 localhost dhcpd: DHCPDISCOVER from > 00:d0:b7:c1:09:58 via eth1 > > Nov 19 15:00:23 localhost dhcpd: DHCPOFFER on > 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > > Nov 19 15:00:23 localhost dhcpd: DHCPREQUEST for > 192.168.0.2 (192.168.0.1) from 00:d0:b7:c1:09:58 > (6355-hthhzebqqx) via eth1 > > > Nov 19 15:00:23 localhost dhcpd: DHCPACK on > 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > > Nov 19 15:00:33 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > > Nov 19 15:00:33 localhost dhcpd: DHCPACK to > 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 > > > Nov 19 15:00:37 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > > Nov 19 15:00:37 localhost dhcpd: DHCPACK to > 192.168.0.2 (00:d0:b7:c1:09
Re: set up NAT (network address translation) on local server
What does this command produce? (shows whether your snat rule is implemented correctly) iptables -vnL -t nat And this one? (tells if ip forwarding is on) cat /proc/sys/net/ipv4/ip_forward Chris -- "A society grows great when old men plant trees whose shade they know they shall never sit in" - Greek Proverb -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade to 64-bit F10
Dave Feustel <[EMAIL PROTECTED]> writes: > I have been running 64-bit OpenBSD, FreeBSD, and SUSE 11 for a while > now. I expect that I will have no more problems with 64-bit F10 than > I've had with the other 64-bit systems (which is to say, essentially > none except for Maxima(caused by CLISP not working in 64-bit mode), so I > am eager to take advantage of the extra (and bigger) registers available > in 64-bit F10. I switched to fc4/64-bit (I think) from netbsd/64-bit and openbsd/64-bit for the better apm support on the laptop, but I didn't notice any great changes in how userland behaved. The BSD's seemed to handle large address space programs a bit better when they started swapping, but it wasn't enough of a problem to force me back. We are talking about a program with a 13 gig working set and 4 gigs dram, but with very good locality of reference. I'm surprised that clisp hasn't been hacked to run on Linux/64-bit. Back when I cared about such things folks were always drooling over large sparse address spaces and how it was going to help all sorts of aspects of creating lisp objects. I'm surprised to see that now that it is available nobody seems to care enough to actually make the code work. -wolfgang -- Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only) You may need to config 6to4 to see the above pages. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Whois - unable to connect.
Simon Slater wrote: > G'day all. > I'm having trouble with whois timing out. Here is a sample: > > [EMAIL PROTECTED] ~]# whois -vv 199.43.0.144 > [Debug: Cache = On] > [Debug: Force lookup = No] > [Debug: Force host = (None)] > [Debug: Force port = (None)] > [Debug: Config file name = /etc/jwhois.conf] > [Debug: Follow redirections = Yes] > [Debug: Display redirections = No] > [Debug: Whois-servers.net service support = Yes] > [Debug: Whois-servers domain = whois-servers.net] > [Debug: Raw query = No] > [Debug: Rwhois display = (None)] > [Debug: Rwhois limit = (None)] > [Debug: Force rwhois = No] > [Querying whois.arin.net] > [Unable to connect to remote host] > [EMAIL PROTECTED] ~]# ping whois.arin.net > PING whois.arin.net (199.43.0.144) 56(84) bytes of data. > 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=1 ttl=230 time=382 > ms > 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=2 ttl=230 time=366 > ms > 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=3 ttl=230 time=419 > ms > > --- whois.arin.net ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 1998ms > rtt min/avg/max/mdev = 366.589/389.819/419.889/22.290 ms > [EMAIL PROTECTED] ~]# > > I suppose the config file is the first place to look, but what is the > relevant section? Couldn't see anything relevant in bugzilla. I'm > using F8 if that makes a difference. > > Q1 Are all whois requests timing out or just this one? e.g. whois cnn.com works? fails? Q2 Have you tried something like wireshark or tcpdump and filtered on port 43 (whois port)? -- I like work; it fascinates me; I can sit and look at it for hours. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Whois - unable to connect.
G'day all. I'm having trouble with whois timing out. Here is a sample: [EMAIL PROTECTED] ~]# whois -vv 199.43.0.144 [Debug: Cache = On] [Debug: Force lookup = No] [Debug: Force host = (None)] [Debug: Force port = (None)] [Debug: Config file name = /etc/jwhois.conf] [Debug: Follow redirections = Yes] [Debug: Display redirections = No] [Debug: Whois-servers.net service support = Yes] [Debug: Whois-servers domain = whois-servers.net] [Debug: Raw query = No] [Debug: Rwhois display = (None)] [Debug: Rwhois limit = (None)] [Debug: Force rwhois = No] [Querying whois.arin.net] [Unable to connect to remote host] [EMAIL PROTECTED] ~]# ping whois.arin.net PING whois.arin.net (199.43.0.144) 56(84) bytes of data. 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=1 ttl=230 time=382 ms 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=2 ttl=230 time=366 ms 64 bytes from whois.arin.net (199.43.0.144): icmp_seq=3 ttl=230 time=419 ms --- whois.arin.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 366.589/389.819/419.889/22.290 ms [EMAIL PROTECTED] ~]# I suppose the config file is the first place to look, but what is the relevant section? Couldn't see anything relevant in bugzilla. I'm using F8 if that makes a difference. -- Regards, Simon Slater Registered Linux User #463789. Be counted at: http://counter.li.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
On Wed, 2008-11-19 at 13:09 -0800, Antonio Olivares wrote: > --- On Wed, 11/19/08, Antonio Olivares <[EMAIL PROTECTED]> wrote: > > > From: Antonio Olivares <[EMAIL PROTECTED]> > > Subject: set up NAT (network address translation) on local server > > To: fedora-list@redhat.com > > Date: Wednesday, November 19, 2008, 12:59 PM > > Dear all, > > > > Starting new thread to clear up the other one: > > Re: Make a DHCP server using Fedora - Help > > > > After going through the steps outlined and the guidance > > provided by great individuals that participate in this list > > :) > > > > /* Done now added eth1 to DHCPARGS */ > > [EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd > > DHCPDARGS=eth1 > > > > > > I need a little bit of help in setting up NAT. I can use > > the system-config-firewall or I can try using webmin or from > > command line, I feel I can achieve the goal. > > > > How should I begin? > > > > I had done this before, but because of other problems > > between the devices and my errors, it did not work :( > > > > # Forward all packets from eth1 (internal network) to eth0 > > (the public internet) > > iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT > > # Forward packets that are part of existing and related > > connections from eth0 to eth1 > > iptables -A FORWARD -i eth0 -o eth1 -m state --state > > ESTABLISHED,RELATED -j ACCEPT > > # Enable SNAT functionality on eth0. a.b.c.d are generally > > the ip of the eth0 > > iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j > > SNAT --to-source a > > > > Thank you for helping, > > > > Regards, > > > > Antonio > > > > > > > > > > -- > Sorry to reply to my own thread, but some might ask if I did the following > and here's what I have done. > > Did this part : > > [EMAIL PROTECTED] ~]$ su - > Password: > [EMAIL PROTECTED] ~]# service dhcpd restart > Starting dhcpd:[ OK ] > [EMAIL PROTECTED] ~]# tail -f /var/log/messages > Nov 19 15:00:02 localhost dhcpd: Copyright 2004-2007 Internet Systems > Consortium. > > Nov 19 15:00:02 localhost dhcpd: All rights reserved. > > Nov 19 15:00:02 localhost dhcpd: For info, please visit > http://www.isc.org/sw/dhcp/ > > Nov 19 15:00:02 localhost dhcpd: Not searching LDAP since ldap-server, > ldap-port and ldap-base-dn were not specified in the config file > > Nov 19 15:00:02 localhost dhcpd: Wrote 2 leases to leases file. > > Nov 19 15:00:02 localhost dhcpd: Listening on > LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 > > Nov 19 15:00:02 localhost dhcpd: Sending on > LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 > > Nov 19 15:00:02 localhost dhcpd: Sending on Socket/fallback/fallback-net > > Nov 19 15:00:06 localhost dhcpd: DHCPREQUEST for 192.168.0.3 from > 00:11:2f:35:88:2e via eth1 > > Nov 19 15:00:06 localhost dhcpd: DHCPACK on 192.168.0.3 to 00:11:2f:35:88:2e > via eth1 > > Nov 19 15:00:22 localhost dhcpd: DHCPDISCOVER from 00:d0:b7:c1:09:58 via eth1 > > Nov 19 15:00:23 localhost dhcpd: DHCPOFFER on 192.168.0.2 to > 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > Nov 19 15:00:23 localhost dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) > from 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > Nov 19 15:00:23 localhost dhcpd: DHCPACK on 192.168.0.2 to 00:d0:b7:c1:09:58 > (6355-hthhzebqqx) via eth1 > > Nov 19 15:00:33 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 > > Nov 19 15:00:33 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) > via eth1 > > Nov 19 15:00:37 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 > > Nov 19 15:00:37 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) > via eth1 > > >From one of the machines I get : > > [EMAIL PROTECTED] ~]$ cat /media/STAPLES\ UFD/computer1.txt > > Windows 2000 IP Configuration > > Host Name . . . . . . . . . . . . : 6355-hthhzebqqx > Primary DNS Suffix . . . . . . . : > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No
Re: I love yum (usually)
Fred Silsbee wrote: yum update Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kmod-nvidia.i686 0:173.14.15-1.fc9.6 set to be updated --> Processing Dependency: kmod-nvidia-2.6.27.5-41.fc9.i686 = 173.14.15-1.fc9.6 for package: kmod-nvidia ---> Package faad2-libs.i386 1:2.6.1-6.fc9 set to be updated --> Running transaction check ---> Package kmod-nvidia-2.6.27.5-41.fc9.i686.i686 0:173.14.15-1.fc9.6 set to be updated --> Processing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 for package: kmod-nvidia-2.6.27.5-41.fc9.i686 --> Finished Dependency Resolution kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 from rpmfusion-nonfree-updates has depsolving problems --> Missing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 is needed by package kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 (rpmfusion-nonfree-updates) Error: Missing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 is needed by package kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 (rpmfusion-nonfree-updates) Looks like your rpmfusion mirror is more up-to-date than your updates-newkey mirror. Give it time, or use a different fedora mirror. -- Kevin J. Cummings [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Registered Linux User #1232 (http://counter.li.org) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
I love yum (usually)
yum update Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kmod-nvidia.i686 0:173.14.15-1.fc9.6 set to be updated --> Processing Dependency: kmod-nvidia-2.6.27.5-41.fc9.i686 = 173.14.15-1.fc9.6 for package: kmod-nvidia ---> Package faad2-libs.i386 1:2.6.1-6.fc9 set to be updated --> Running transaction check ---> Package kmod-nvidia-2.6.27.5-41.fc9.i686.i686 0:173.14.15-1.fc9.6 set to be updated --> Processing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 for package: kmod-nvidia-2.6.27.5-41.fc9.i686 --> Finished Dependency Resolution kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 from rpmfusion-nonfree-updates has depsolving problems --> Missing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 is needed by package kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 (rpmfusion-nonfree-updates) Error: Missing Dependency: kernel-uname-r = 2.6.27.5-41.fc9.i686 is needed by package kmod-nvidia-2.6.27.5-41.fc9.i686-173.14.15-1.fc9.6.i686 (rpmfusion-nonfree-updates) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: set up NAT (network address translation) on local server
--- On Wed, 11/19/08, Antonio Olivares <[EMAIL PROTECTED]> wrote: > From: Antonio Olivares <[EMAIL PROTECTED]> > Subject: set up NAT (network address translation) on local server > To: fedora-list@redhat.com > Date: Wednesday, November 19, 2008, 12:59 PM > Dear all, > > Starting new thread to clear up the other one: > Re: Make a DHCP server using Fedora - Help > > After going through the steps outlined and the guidance > provided by great individuals that participate in this list > :) > > /* Done now added eth1 to DHCPARGS */ > [EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd > DHCPDARGS=eth1 > > > I need a little bit of help in setting up NAT. I can use > the system-config-firewall or I can try using webmin or from > command line, I feel I can achieve the goal. > > How should I begin? > > I had done this before, but because of other problems > between the devices and my errors, it did not work :( > > # Forward all packets from eth1 (internal network) to eth0 > (the public internet) > iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT > # Forward packets that are part of existing and related > connections from eth0 to eth1 > iptables -A FORWARD -i eth0 -o eth1 -m state --state > ESTABLISHED,RELATED -j ACCEPT > # Enable SNAT functionality on eth0. a.b.c.d are generally > the ip of the eth0 > iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j > SNAT --to-source a > > Thank you for helping, > > Regards, > > Antonio > > > > > -- Sorry to reply to my own thread, but some might ask if I did the following and here's what I have done. Did this part : [EMAIL PROTECTED] ~]$ su - Password: [EMAIL PROTECTED] ~]# service dhcpd restart Starting dhcpd:[ OK ] [EMAIL PROTECTED] ~]# tail -f /var/log/messages Nov 19 15:00:02 localhost dhcpd: Copyright 2004-2007 Internet Systems Consortium. Nov 19 15:00:02 localhost dhcpd: All rights reserved. Nov 19 15:00:02 localhost dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Nov 19 15:00:02 localhost dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file Nov 19 15:00:02 localhost dhcpd: Wrote 2 leases to leases file. Nov 19 15:00:02 localhost dhcpd: Listening on LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 Nov 19 15:00:02 localhost dhcpd: Sending on LPF/eth1/00:60:97:c5:2a:c3/192.168.0.0/24 Nov 19 15:00:02 localhost dhcpd: Sending on Socket/fallback/fallback-net Nov 19 15:00:06 localhost dhcpd: DHCPREQUEST for 192.168.0.3 from 00:11:2f:35:88:2e via eth1 Nov 19 15:00:06 localhost dhcpd: DHCPACK on 192.168.0.3 to 00:11:2f:35:88:2e via eth1 Nov 19 15:00:22 localhost dhcpd: DHCPDISCOVER from 00:d0:b7:c1:09:58 via eth1 Nov 19 15:00:23 localhost dhcpd: DHCPOFFER on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 15:00:23 localhost dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 15:00:23 localhost dhcpd: DHCPACK on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 15:00:33 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 15:00:33 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 15:00:37 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 15:00:37 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 >From one of the machines I get : [EMAIL PROTECTED] ~]$ cat /media/STAPLES\ UFD/computer1.txt Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : 6355-hthhzebqqx Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN onMotherboard Physical Address. . . . . . . . . : 00-D0-B7-C1-09-58 DHCP Enabled. . . . . . . . . . . : Yes Autocon
set up NAT (network address translation) on local server
Dear all, Starting new thread to clear up the other one: Re: Make a DHCP server using Fedora - Help After going through the steps outlined and the guidance provided by great individuals that participate in this list :) /* Done now added eth1 to DHCPARGS */ [EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd DHCPDARGS=eth1 I need a little bit of help in setting up NAT. I can use the system-config-firewall or I can try using webmin or from command line, I feel I can achieve the goal. How should I begin? I had done this before, but because of other problems between the devices and my errors, it did not work :( # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a Thank you for helping, Regards, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Jackd Problems -- alsa_pcm: xrun of at least 1227061150613.504 msecs
On Wed, Nov 19, 2008 at 1:28 AM, Jonathan Ryshpan <[EMAIL PROTECTED]>wrote: > In the past I've never had any problems running jackd. Now I'm getting > a very large number of messages reading: > alsa_pcm: xrun of at least 1227061150613.504 msecs > I'm running F9 on an x86_64 system with all updates installed. > Pulseaudio is not running. Jackd is started via qjackctl. No past > problems with audio beyond the usual conflicts between pulseaudio and > firefox. > > Questions: > (1) What exactly does this message mean? An "xrun" is a buffer under- > or over-run -- but what does the time interval represent? > > (2) Whatever the time interval means, it looks rather large. > 1227061150613.504 msec is many days (or maybe years if msec means > millisec and not microsec) This looks like a misconfiguration of some > kind or a missing component. Any idea what it might be? > > The solution depends on your card (I have an Intel onboard card). But this material may give you an idea on what you can try: http://people.atrpms.net/~pcavalcanti/alsa-1.0.15rc2_snd-hda-intel.html#jack -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
HOW the "H" do you get the Mic working in FC8
FC8/KDE I have gone into Alsamixer selected MIC, enabled, Mic 1 is selected, what else must I do to get MIC working. In Kmix all settings are enabled for MIC . The Mic is the most Frustrating thing to get working in the sound system. How do you run Pulse to check Mic Settings. The MIC is also a problem FC10, submitted messages to Fedora-test and filed bug report, no body can help. Anyhow back to FC 8 Mic problems. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: CD boot problem -
Bob Goodwin wrote: I have a collection of used parts built into what I want to be an F-9 computer. I'm trying to boot from the Fedora 9 Live CD but no matter how I set the bios setup it doesn't boot. The CD drive is recognized, the light on the drive blinks while booting but it keeps telling me to insert a system disk? I have a 40G hard drive CS connected to primary master and the CD drive connected to secondary master also set Cable Select with appropriate cables [I believe]. Does this seem like a proper setup? I NEVER trust cable select. Use the master and slave hard jumpers on the drives. In your case (with them on separate IDE buses), set them both to master. The motherboard is ASUS P4B533-E with a P-4 processor. The 40 gig hard drive already has F9 on it but it had been set up on a failed motherboard with an AMD µprocessor on it. So I am dead in the water until I can read the CD. Are you sure the CD is bootable? If you stuff it into another machine and look at it, you should see a bunch of files on it, not a single file. If you see a single file, you burned the CD wrong. Oh, and you're sure it's a CD and not a DVD you're trying to put into a CD drive? Most F9 media is DVD (except for the live CDs). -- - Rick Stevens, Systems Engineer [EMAIL PROTECTED] - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - "I was contemplating the immortal words of Socrates when he said, - - 'I drank what?'" -- Val Kilmer in "Real Genius"- -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
Original Message Subject: Re: good cordless mouse? From: Dr. Michael J. Chudobiak <[EMAIL PROTECTED]> To: Michael Cronenworth <[EMAIL PROTECTED]> CC: "Community assistance, encouragement, and advice for using Fedora." Date: 11/19/2008 01:59 PM Thanks for the tip! There is a linux program that will set the eprom in the MX Revolution (http://goron.de/~froese/revoco). Running: ./reveco free did the trick for me. The wheel now scrolls and middle-clicks for me, without any xorg.conf tweaks. - Mike Sweet... you've made my day as well. Thanks for the link. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
CD boot problem -
I have a collection of used parts built into what I want to be an F-9 computer. I'm trying to boot from the Fedora 9 Live CD but no matter how I set the bios setup it doesn't boot. The CD drive is recognized, the light on the drive blinks while booting but it keeps telling me to insert a system disk? I have a 40G hard drive CS connected to primary master and the CD drive connected to secondary master also set Cable Select with appropriate cables [I believe]. Does this seem like a proper setup? The motherboard is ASUS P4B533-E with a P-4 processor. The 40 gig hard drive already has F9 on it but it had been set up on a failed motherboard with an AMD µprocessor on it. So I am dead in the water until I can read the CD. Any help appreciated. Bob -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Need to control loading of usb-storage
Unfortunetely the usb-storage string appers nowhere in /etc or in the hal directories under /usr On Tue, 2008-11-18 at 17:36 -0600, Mikkel L. Ellertson wrote: > Jean Francois Martinez wrote: > > My problem is: > > > > I need to find a way to tell Linux not to load the usb-storage module > > when a certain peripheral, whose signature I know, is inserted. For > > now the only way I have found is putting usb-storage in the blacklist > > but this means module doesn't load when I plug my usb key or my external > > hard drive so I look for something finer grained > > > > Details > > > > I own a cell phones who has USB connector and can be accessed either as > > an MTP device or as a mass storage one but the latter works if, and only > > if, it has an additional memory card inserted (presently I have none). > > The phone prompts for the mode at connect time but no matter what I > > select the usb-storage loads itself, unsuccessfully tries to put the > > phone in storage mode (normal behavior since the phone has no external > > memory card) and after a minute or two, gives up, unloads itself and > > removes the peripheral from the list of present USB devices. In other > > words even after the usb-storage module has unloaded I cannot use the > > phone in mtp mode. > > > > Regards > > > > JFM > > > Take a look at HAL - it can do fine control of what is mounted. (But > don't ask me to write it for you - I am not that good yet.) I guess > you could write a udev rule that prevents the SCSI devices needed by > HAL to mount the drive. This rule would have to run before > 40-redhat.rules. The string usb-storage appears nowhere be it under /etc or /usr/share/hal so I am still puzzled about how to control the loading of the driver. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
Yes, the middle mouse wheel functions. The back and forward buttons work in Firefox as well. However, I believe Logitech sets the default logic for something else. I cheated and used Windows to configure the mouse to my liking, so that may have something to do with it. It seems the mouse has an EPROM that only the Windows driver can set. Stuff like the motor on the middle wheel can be adjusted through the Windows driver, and it is retained for as long as you have the mouse on (OS independent). Thanks for the tip! There is a linux program that will set the eprom in the MX Revolution (http://goron.de/~froese/revoco). Running: ./reveco free did the trick for me. The wheel now scrolls and middle-clicks for me, without any xorg.conf tweaks. - Mike -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Konqueror development on Fedora
Is there any kind of tutorial for konqueror development on Fedora? Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
Original Message Subject: Re: good cordless mouse? From: Dr. Michael J. Chudobiak <[EMAIL PROTECTED]> To: Community assistance, encouragement, and advice for using Fedora. CC: [EMAIL PROTECTED] Date: 11/19/2008 10:26 AM Does the middle wheel both scroll and click for you? It scrolls for me, but I can't middle-click a link in firefox to open in a new tab, or to paste text. - Mike Yes, the middle mouse wheel functions. The back and forward buttons work in Firefox as well. However, I believe Logitech sets the default logic for something else. I cheated and used Windows to configure the mouse to my liking, so that may have something to do with it. It seems the mouse has an EPROM that only the Windows driver can set. Stuff like the motor on the middle wheel can be adjusted through the Windows driver, and it is retained for as long as you have the mouse on (OS independent). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
sftp hangs but used to work on fc8 not on fc9, using ssh secure shell for windows 2.1.0
FC9 - 2.6.27.5-37.fc9.i686 #1 SMP Wed Nov 12 18:56:28 EST 2008 i686 i686 i386 GNU/Linux SSH Secure Shell - 2.1.0 for windows xp I am already login with SSH and a command shell running ok. When I click on sftp FC9 sends this message to: /var/log/secure subsystem request for sftp and then hangs. This used to work on all previous Fedora cores. If I use sftp from another computer it works OK. -- This is an email sent via The Fedora Community Portal https://fcp.surfsite.org https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=304854&topic_id=64059&forum=10#forumpost304854 If you think, this is spam, please report this to [EMAIL PROTECTED] and/or blame [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
Michael Cronenworth wrote: I'm using the MX Revolution right now. All buttons work except for the side scroll wheel. I have no special xorg.conf settings. Are you using the evdev driver? If not, try it. Does the middle wheel both scroll and click for you? It scrolls for me, but I can't middle-click a link in firefox to open in a new tab, or to paste text. - Mike -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
> The advice to add: > net.ipv4.ip_forward = 1 > to /etc/sysctl.conf only takes effect after the next > reboot. If you want to change this on the fly you can: > echo 1 > /proc/sys/net/ipv4/ip_forward > [EMAIL PROTECTED] ~]# cat /etc/sysctl.conf # Kernel sysctl configuration file for Red Hat Linux # # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 1 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 # Controls the System Request debugging functionality of the kernel kernel.sysrq = 0 # Controls whether core dumps will append the PID to the core filename. # Useful for debugging multi-threaded applications. kernel.core_uses_pid = 1 > > it says iptables and has this part: > > # Forward all packets from eth1 (internal network) to > eth0 (the public internet) > > iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT > > # Forward packets that are part of existing and > related connections from eth0 to eth1 > > iptables -A FORWARD -i eth0 -o eth1 -m state --state > ESTABLISHED,RELATED -j ACCEPT > > # Enable SNAT functionality on eth0. a.b.c.d are > generally the ip of the eth0 > > iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o > eth0 -j SNAT --to-source a. > > > > I added everything here except last line "Enable > SNAT", I do not know what that means, I know it is > close. I can ping the host machine, it gets an ip, it gets > DNS, and all, but cannot surf :( > > Anywhere you send packets needs some way to get the > response back to the sender. One way to do this is to plan > things so all of your private subnets are unique and add > routes toward the gateway interfaces for everything else. > Another way is to NAT the source address as it goes out the > already-known interface. That way the rest of the world > does not need to know about your new private subnet. As a > packet goes out, the source address of the client will be > replaced with the address of the forwarding interface and > the host performing this will maintain a table of > connections to do the reverse mapping as the reply packets > come back. If you tcpdump your eth0 interface now, > you'll probably see packets being forwarded out but > nothing coming back because the rest of the net/world > doesn't know the route back. When you add the SNAT, it > will look like the host machine itself to the rest of the > world. The argument to -s is the range of original > addresses to replace, -o is the outbound interface, and > --to-source is the IP of the outbound interface on the host. > > -- Les Mikesell >[EMAIL PROTECTED] The rest of the local network does not have to know about this one, but I have not done this before, I have tried but not succeeded, now I know that I am close, but not there yet. Just need a few more hints/advice and it will work :) This appears to have been removed, the rules to forward using iptables :( [EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT [EMAIL PROTECTED] ~]# Thank you very much for trying to help. Now there's also ip6tables, but I do not want to go there yet :( Regards, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
Original Message Subject: good cordless mouse? From: Dr. Michael J. Chudobiak <[EMAIL PROTECTED]> To: Community assistance, encouragement, and advice for using Fedora. Date: 11/19/2008 08:28 AM Can someone recommend a good, in-production, hassle-free cordless mouse with a middle-clickable scroll wheel? I would rather not mess with xorg.conf, and I can't seem to get the Logitech MX Revolution to "just work" (i.e. middle click doesn't work). My older MX Lasers work great, but they doesn't seem to be available any more. - Mike I'm using the MX Revolution right now. All buttons work except for the side scroll wheel. I have no special xorg.conf settings. Are you using the evdev driver? If not, try it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
> After this breakthrough I also found out or not sure here? > is that iptables are forwarding packets to eth1 > > upon reading another page: > http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html > > it says iptables and has this part: > > # Forward all packets from eth1 (internal network) to eth0 > (the public internet) > iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT > # Forward packets that are part of existing and related > connections from eth0 to eth1 > iptables -A FORWARD -i eth0 -o eth1 -m state --state > ESTABLISHED,RELATED -j ACCEPT > # Enable SNAT functionality on eth0. a.b.c.d are generally > the ip of the eth0 > iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j > SNAT --to-source a. > > Then it recommends visiting the other page which was > referenced before. > > I will probably get to this machine tomorrow or on Monday. > I hope that I can get this working and with advice from the > list I believe it can get done. > > Regards, > > Antonio > -- I see that the forwarding is not there anymore :( See here: [EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT I can try using system-config-firewall to allow it or how do I do it, I added it manually and then ran iptables-save, but it is not there anymore :( Thank you all for your help, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: --- On Wed, 11/19/08, Les Mikesell <[EMAIL PROTECTED]> wrote: From: Les Mikesell <[EMAIL PROTECTED]> Subject: Re: Make a DHCP server using Fedora - Help To: [EMAIL PROTECTED], "Community assistance, encouragement, and advice for using Fedora." Date: Wednesday, November 19, 2008, 5:55 AM Antonio Olivares wrote: No, there is DNS, and they are the same as the host machine. It might be another little thing, maybe the packet forwarding or Iptables stuff? Thank you very much for your guidance :) It is much closer than before. You have to deal with routing and NAT somewhere. You might avoid it if you run a nameserver and squid proxy on the host and configure the clients to use the proxy. Otherwise you need the host to route the packets if you have a NAT gateway elsewhere, or to route and NAT if nothing but the host knows about this subnet. -- Les Mikesell [EMAIL PROTECTED] I added the following and saved them iptables-save upon reading another page: http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html The advice to add: net.ipv4.ip_forward = 1 to /etc/sysctl.conf only takes effect after the next reboot. If you want to change this on the fly you can: echo 1 > /proc/sys/net/ipv4/ip_forward it says iptables and has this part: # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a. I added everything here except last line "Enable SNAT", I do not know what that means, I know it is close. I can ping the host machine, it gets an ip, it gets DNS, and all, but cannot surf :( Anywhere you send packets needs some way to get the response back to the sender. One way to do this is to plan things so all of your private subnets are unique and add routes toward the gateway interfaces for everything else. Another way is to NAT the source address as it goes out the already-known interface. That way the rest of the world does not need to know about your new private subnet. As a packet goes out, the source address of the client will be replaced with the address of the forwarding interface and the host performing this will maintain a table of connections to do the reverse mapping as the reply packets come back. If you tcpdump your eth0 interface now, you'll probably see packets being forwarded out but nothing coming back because the rest of the net/world doesn't know the route back. When you add the SNAT, it will look like the host machine itself to the rest of the world. The argument to -s is the range of original addresses to replace, -o is the outbound interface, and --to-source is the IP of the outbound interface on the host. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: good cordless mouse?
On Wed, 19 Nov 2008 09:28:51 -0500 "Dr. Michael J. Chudobiak" <[EMAIL PROTECTED]> wrote: > Can someone recommend a good, in-production, hassle-free cordless mouse > with a middle-clickable scroll wheel? I just bought a Microsoft Wireless Optical Mouse 2000 last week and it "just works" on Fedora 9. All I did to set it up was to plug the receiver into the computer and put the (included) batteries into the mouse. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com DRY CLEANER BUSINESS FOR SALE ~ http://www.canadadrycleanerforsale.com -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
Steve West wrote: > When I run my service in init 1 there is no shutdown response to the > power off button. What service handles the shutdown of the power off > switch? ACPID? > > Steve > Yes, you need acpid running for the power switch to work. It does not run during run level 1 by default. Run level 1 is normally reserved for fixing problems on the system, as it outs it in the single user mode, with root as the user. Only the minimum services necessary are started. What else does the ACPI service do? I agreee with the above but this raises the question what would running halt do? What else does ACPI do besides the power switch. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Wed, 11/19/08, Les Mikesell <[EMAIL PROTECTED]> wrote: > From: Les Mikesell <[EMAIL PROTECTED]> > Subject: Re: Make a DHCP server using Fedora - Help > To: [EMAIL PROTECTED], "Community assistance, encouragement, and advice for > using Fedora." > Date: Wednesday, November 19, 2008, 5:55 AM > Antonio Olivares wrote: > > > > No, there is DNS, and they are the same as the host > machine. It might be another little thing, maybe the packet > forwarding or Iptables stuff? > > > > Thank you very much for your guidance :) > > It is much closer than before. > > > > You have to deal with routing and NAT somewhere. You might > avoid it if you run a nameserver and squid proxy on the host > and configure the clients to use the proxy. Otherwise you > need the host to route the packets if you have a NAT gateway > elsewhere, or to route and NAT if nothing but the host knows > about this subnet. > > -- Les Mikesell >[EMAIL PROTECTED] I added the following and saved them iptables-save upon reading another page: http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html it says iptables and has this part: # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a. I added everything here except last line "Enable SNAT", I do not know what that means, I know it is close. I can ping the host machine, it gets an ip, it gets DNS, and all, but cannot surf :( Thanks, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
On Wed, 2008-11-19 at 04:47 -0500, Steve West wrote: > Steve West wrote: > > When I run my service in init 1 there is no shutdown response to the > > power off button. What service handles the shutdown of the power off > > switch? ACPID? > > > > Steve > > > Yes, you need acpid running for the power switch to work. It does > not run during run level 1 by default. Run level 1 is normally > reserved for fixing problems on the system, as it outs it in the > single user mode, with root as the user. Only the minimum services > necessary are started. > > What else does the ACPI service do? > I agreee with the above but this raises the question what would running halt do? -- === "I may be synthetic, but I'm not stupid" -- the artificial person, from _Aliens_ === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
On Wed, 19 Nov 2008 19:14:43 +0800, [EMAIL PROTECTED] wrote:
> Michael Schwendt wrote:
>
> >On Wed, 19 Nov 2008 12:52:30 +0800, edwardspl wrote:
> >
> >
> >
> >>Dear All,
> >>
> >>For /usr/bin/upasswd :
> >>
> >>#!/bin/sh
> >>
> >># Validate that a username was given as an argument
> >>[ -n "$1" ] || {
> >>echo "Use: upasswd " >&2
> >>exit 64
> >>}
> >>
> >># Validate that the username wasn't "root"
> >>[ "$1" != "root" ] || {
> >>echo "Can't set the root user's password" >&2
> >>exit 77
> >>}
> >>
> >># Use -- to make sure that the "username" given wasn't just
> >># a switch that passwd would interpret.
> >># THIS ONLY WORKS ON GNU SYSTEMS.
> >>passwd -- "$1"
> >>
> >>For visudo :
> >>SYSADM MH = (ALL) /usr/bin/upasswd
> >>
> >>
> >
> >Even if you rely on sudo's default environment variables restrictions and
> >safety checks, prefer absolute paths when executing tools like
> >/usr/bin/passwd
> >
> >
> Hello,
>
> Sorry, I don't quite understanding what is your means...
>
> Thanks !
>
> Edward.
You've been on Fedora [or Red Hat Linux] related mailing-lists before, a
long time ago. It isn't news that you try to build a lot from tarballs
instead of using prebuilt/preconfigured rpms which are part of the
distribution. Asking questions is okay. Still you ought to show that
you're interested in trying to read the documentation that comes together
with the software you want to use. In this case "man sudo sudoers". These
manuals contain security related notes, which you really ought to read if
you want to give users sudo access.
What I mean with my comments on preferring absolute paths is that in the
wrapper-script /usr/bin/upasswd (the name you've chosen for it) you ought
to run "/usr/bin/passwd" at the bottom, not just "passwd". By running
"passwd" within PATH you rely on security features in sudo to prevent a
user from modifying $PATH and running an arbitrary program named "passwd"
with superuser privileges. That program could be anything, especially
since it is being passed with "$1" without any helpful safety-checks.
Even if you think that sudo does not make that possible (read about
SECURE_PATH and the env_* features I've mentioned), a change in the
configuration, in the defaults (or when using selfbuilt software) may open
the attack vector. Hence let the script run /usr/bin/passwd at the bottom,
which is exactly what you want.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Google Droid Fonts
David Hláčik wrote: > Hello guys, > > i have created a rpm package of Google Droid Fonts for F10 . (Inspired by > specfile from liberation-font ) > > The Droid family of fonts consists of Droid Sans, Droid Sans Mono >: and Droid Serif. Each contains extensive character set >: coverage including Western Europe, Eastern/Central Europe, >: Baltic, > Cyrillic, >: Greek and Turkish support. The Droid Sans regular font also >: includes support for Simplified and Traditional Chinese, > Japanese >: and Korean support for the GB2312, Big 5, JIS 0208 and KSC >: 5601 character sets respectively. > > RPM is available here : http://david.hlacik.eu/fedora/boss/ > > I am using it as a default font for my Gnome Desktop. > > My question is, what should i do , if i want this package to make an > official to Fedora? Join Fedora! http://fedoraproject.org/wiki/PackageMaintainers/Join Or lobby an existing contributor to do the maintainance/work for you. :) -- Rex -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
good cordless mouse?
Can someone recommend a good, in-production, hassle-free cordless mouse with a middle-clickable scroll wheel? I would rather not mess with xorg.conf, and I can't seem to get the Logitech MX Revolution to "just work" (i.e. middle click doesn't work). My older MX Lasers work great, but they doesn't seem to be available any more. - Mike -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Google Droid Fonts
You can read more about Droid Family at http://damieng.com/blog/2007/11/14/droid-font-family-courtesy-of-google-ascender Thanks, D. On Wed, Nov 19, 2008 at 15:18, David Hláčik <[EMAIL PROTECTED]> wrote: > > Hello guys, > > i have created a rpm package of Google Droid Fonts for F10 . (Inspired by > specfile from liberation-font ) > > The Droid family of fonts consists of Droid Sans, Droid Sans Mono >: and Droid Serif. Each contains extensive character set coverage >: including Western Europe, Eastern/Central Europe, Baltic, > Cyrillic, >: Greek and Turkish support. The Droid Sans regular font also >: includes support for Simplified and Traditional Chinese, Japanese >: and Korean support for the GB2312, Big 5, JIS 0208 and KSC 5601 >: character sets respectively. > > RPM is available here : http://david.hlacik.eu/fedora/boss/ > > I am using it as a default font for my Gnome Desktop. > > My question is, what should i do , if i want this package to make an official > to Fedora? > > Thanks! > > D. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Google Droid Fonts
Hello guys, i have created a rpm package of Google Droid Fonts for F10 . (Inspired by specfile from liberation-font ) The Droid family of fonts consists of Droid Sans, Droid Sans Mono : and Droid Serif. Each contains extensive character set coverage : including Western Europe, Eastern/Central Europe, Baltic, Cyrillic, : Greek and Turkish support. The Droid Sans regular font also : includes support for Simplified and Traditional Chinese, Japanese : and Korean support for the GB2312, Big 5, JIS 0208 and KSC 5601 : character sets respectively. RPM is available here : http://david.hlacik.eu/fedora/boss/ I am using it as a default font for my Gnome Desktop. My question is, what should i do , if i want this package to make an official to Fedora? Thanks! D. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Custom gdm theme
On Tue, 2008-11-18 at 18:14 +, Iarly Selbir wrote: > Thanks for you reply Gilboa, so... don't there's another way to do > it? > > > Thanks again. > > Reggards, > > -- > iarly Selbir ( Ski0s ) > No as far as I know... Sorry. Hopefully themed GDM will land in F11. - Gilboa -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: BTW, I am getting DHCP requests from other machines in the school network :( I only want the network for my own machines in the classroom not the others. Here's what I am getting Nov 19 07:14:27 localhost dhcpd: DHCPDISCOVER from 00:50:2c:a2:23:28 via eth0: network 10.154.19.0/24: no free leases Nov 19 07:14:27 localhost dhcpd: DHCPREQUEST for 10.154.19.248 (10.154.16.130) from 00:50:2c:a2:23:28 via eth0: unknown lease 10.154.19.248. Nov 19 07:18:50 localhost ntpd[2082]: synchronized to 72.249.76.84, stratum 2 Nov 19 07:24:25 localhost dhcpd: DHCPREQUEST for 10.154.19.94 from 00:40:f4:ea:ee:d3 via eth0: unknown lease 10.154.19.94. Nov 19 07:25:34 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 19 07:25:34 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 19 07:25:37 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 19 07:25:37 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 19 07:26:51 localhost dhcpd: DHCPREQUEST for 10.154.19.133 from 00:0c:f1:76:fc:68 via eth0: unknown lease 10.154.19.133. Nov 19 07:27:25 localhost dhcpd: DHCPINFORM from 10.154.19.165 via eth0 Nov 19 07:27:25 localhost dhcpd: DHCPACK to 10.154.19.165 (00:08:74:2e:70:e7) via eth0 Nov 19 07:27:28 localhost dhcpd: DHCPINFORM from 10.154.19.165 via eth0 Nov 19 07:27:28 localhost dhcpd: DHCPACK to 10.154.19.165 (00:08:74:2e:70:e7) via eth0 Nov 19 07:30:08 localhost dhcpd: DHCPINFORM from 10.154.19.63 via eth0 Nov 19 07:30:08 localhost dhcpd: DHCPACK to 10.154.19.63 (00:12:3f:31:8d:b4) via eth0 Nov 19 07:30:11 localhost dhcpd: DHCPINFORM from 10.154.19.63 via eth0 Nov 19 07:30:11 localhost dhcpd: DHCPACK to 10.154.19.63 (00:12:3f:31:8d:b4) via eth0 Nov 19 07:32:38 localhost dhcpd: DHCPINFORM from 10.154.19.133 via eth0 Nov 19 07:32:38 localhost dhcpd: DHCPACK to 10.154.19.133 (00:0c:f1:76:fc:68) via eth0 Nov 19 07:33:57 localhost dhcpd: DHCPDISCOVER from 00:08:a1:0f:53:35 via eth0: network 10.154.19.0/24: no free leases Nov 19 07:33:57 localhost dhcpd: DHCPREQUEST for 10.154.19.91 (10.154.16.130) from 00:08:a1:0f:53:35 via eth0: unknown lease 10.154.19.91. Nov 19 07:34:13 localhost dhcpd: DHCPINFORM from 10.154.19.91 via eth0 Nov 19 07:34:13 localhost dhcpd: DHCPACK to 10.154.19.91 (00:08:a1:0f:53:35) via eth0 Nov 19 07:34:16 localhost dhcpd: DHCPINFORM from 10.154.19.91 via eth0 Nov 19 07:34:16 localhost dhcpd: DHCPACK to 10.154.19.91 (00:08:a1:0f:53:35) via eth0 Thank you very much again for helping out. Your client subnet should be physically isolated from rest of the building's network. That is, the host should have one interface on the main net and another connected to a separate switch where your dhcp clients connect. You will break the rest of the main network if you connect your dhcp-serving interface there. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: No, there is DNS, and they are the same as the host machine. It might be another little thing, maybe the packet forwarding or Iptables stuff? Thank you very much for your guidance :) It is much closer than before. You have to deal with routing and NAT somewhere. You might avoid it if you run a nameserver and squid proxy on the host and configure the clients to use the proxy. Otherwise you need the host to route the packets if you have a NAT gateway elsewhere, or to route and NAT if nothing but the host knows about this subnet. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Wed, 11/19/08, Antonio Olivares <[EMAIL PROTECTED]> wrote: > From: Antonio Olivares <[EMAIL PROTECTED]> > Subject: Re: Make a DHCP server using Fedora - Help > To: fedora-list@redhat.com, [EMAIL PROTECTED] > Date: Wednesday, November 19, 2008, 5:24 AM > --- On Tue, 11/18/08, Marko Vojinovic > <[EMAIL PROTECTED]> wrote: > > > From: Marko Vojinovic <[EMAIL PROTECTED]> > > Subject: Re: Make a DHCP server using Fedora - Help > > To: fedora-list@redhat.com > > Cc: [EMAIL PROTECTED] > > Date: Tuesday, November 18, 2008, 3:14 PM > > On Monday 17 November 2008 18:49, Marko Vojinovic > wrote: > > > > I also wonder if I should have a ifcfg-eth1 > file > > in > > > > > > > > /etc/sysconfig/network-scripts/ > > > > > > Yes, definitely. The > "system-config-network" > > gui should create it for you. > > > Open it, and see if eth1 is listed in the Devices > tab. > > If not, click New > > > to create it (follow the wizard). Then click Edit > to > > edit its > > > configuration: > > > > > > In the General tab: > > > * Activate the device when computer starts --- > should > > be the only checked > > > option, everything else should be *unchecked* > > > * Activate the static IP settings: > > > * Address: 192.168.0.1 > > > * Subnet mask: 255.255.255.0 > > > * Gateway: leave empty for now > > > > > > In the Hardware Device tab: > > > * Hardware: eth1 > > > * Device alias --- unchecked > > > * Bind to MAC --- checked > > > * Hit the "probe" button and make sure > the > > MAC is 00:60:97:C5:2A:C3 (don't > > > type it yourself, the button should fill it for > you). > > > > > > Click OK to close the window and return to the > main > > one. In the File menu > > > choose Save to save the new configuration. Close > the > > gui. > > > > > > Go to /etc/sysconfig/network-scripts/ and verify > that > > there exists an > > > ifcfg-eth1 file, with the contents like the > following: > > > > > > TYPE=Ethernet > > > DNS1=10.154.16.130 > > > DEVICE=eth1 > > > BOOTPROTO=none > > > NETMASK=255.255.255.0 > > > IPADDR=192.168.0.1 > > > DNS2=10.128.0.4 > > > ONBOOT=yes > > > USERCTL=no > > > PEERDNS=yes > > > IPV6INIT=no > > > NM_CONTROLLED=no > > > > > > If this is ok, do a "service network > > restart" followed by the "service > > > dhcpd restart". Post the output of > > "ifconfig" and "tail -f > > > /var/log/messages". > > > > > > This should do it (hopefully), if you have no > > hardware/driver problems > > > with the eth1 card. > > > > > > Also, verify that the cable is connected into > eth1, > > that the led light is > > > on, that the corresponding light on the switch is > also > > on, etc. In other > > > words, make sure that the hardware part of the > setup > > is ok. > > > > > > HTH, :-) > > > Marko > > > > Did you manage to do what I described? > > Yes, It is very close to working. The machines get an IP, > get DNS, but cannot browse. Thank you for your guidance, > and patience. > > Nov 19 07:02:23 localhost dhcpd: DHCPDISCOVER from > 00:d0:b7:c1:09:58 via eth1 > Nov 19 07:02:24 localhost dhcpd: DHCPOFFER on 192.168.0.2 > to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > Nov 19 07:02:24 localhost dhcpd: DHCPREQUEST for > 192.168.0.2 (192.168.0.1) from 00:d0:b7:c1:09:58 > (6355-hthhzebqqx) via eth1 > > Nov 19 07:02:24 localhost dhcpd: DHCPACK on 192.168.0.2 to > 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 > > Nov 19 07:02:26 localhost dhcpd: DHCPDISCOVER from > 00:11:2f:35:88:2e via eth1 > Nov 19 07:02:27 localhost dhcpd: DHCPOFFER on 192.168.0.3 > to 00:11:2f:35:88:2e via eth1 > > Nov 19 07:02:27 localhost dhcpd: DHCPREQUEST for > 192.168.0.3 (192.168.0.1) from 00:11:2f:35:88:2e via eth1 > > Nov 19 07:02:27 localhost dhcpd: DHCPACK on 192.168.0.3 to > 00:11:2f:35:88:2e via eth1 > > Nov 19 07:03:16 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > Nov 19 07:03:16 localhost dhcpd: DHCPACK to 192.168.0.2 > (00:d0:b7:c1:09:58) via eth1 > > Nov 19 07:03:21 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > Nov 19 07:03:21 localhost dhcpd: DHCPACK to 192.168.0.2 > (00:d0:b7:c1:09:58) via eth1 > > Nov 19 07:04:53 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > Nov 19 07:04:53 localhost dhcpd: DHCPACK to 192.168.0.2 > (00:d0:b7:c1:09:58) via eth1 > > Nov 19 07:04:57 localhost dhcpd: DHCPINFORM from > 192.168.0.2 via eth1 > Nov 19 07:04:57 localhost dhcpd: DHCPACK to 192.168.0.2 > (00:d0:
Re: Make a DHCP server using Fedora - Help
--- On Tue, 11/18/08, Marko Vojinovic <[EMAIL PROTECTED]> wrote: > From: Marko Vojinovic <[EMAIL PROTECTED]> > Subject: Re: Make a DHCP server using Fedora - Help > To: fedora-list@redhat.com > Cc: [EMAIL PROTECTED] > Date: Tuesday, November 18, 2008, 3:14 PM > On Monday 17 November 2008 18:49, Marko Vojinovic wrote: > > > I also wonder if I should have a ifcfg-eth1 file > in > > > > > > /etc/sysconfig/network-scripts/ > > > > Yes, definitely. The "system-config-network" > gui should create it for you. > > Open it, and see if eth1 is listed in the Devices tab. > If not, click New > > to create it (follow the wizard). Then click Edit to > edit its > > configuration: > > > > In the General tab: > > * Activate the device when computer starts --- should > be the only checked > > option, everything else should be *unchecked* > > * Activate the static IP settings: > > * Address: 192.168.0.1 > > * Subnet mask: 255.255.255.0 > > * Gateway: leave empty for now > > > > In the Hardware Device tab: > > * Hardware: eth1 > > * Device alias --- unchecked > > * Bind to MAC --- checked > > * Hit the "probe" button and make sure the > MAC is 00:60:97:C5:2A:C3 (don't > > type it yourself, the button should fill it for you). > > > > Click OK to close the window and return to the main > one. In the File menu > > choose Save to save the new configuration. Close the > gui. > > > > Go to /etc/sysconfig/network-scripts/ and verify that > there exists an > > ifcfg-eth1 file, with the contents like the following: > > > > TYPE=Ethernet > > DNS1=10.154.16.130 > > DEVICE=eth1 > > BOOTPROTO=none > > NETMASK=255.255.255.0 > > IPADDR=192.168.0.1 > > DNS2=10.128.0.4 > > ONBOOT=yes > > USERCTL=no > > PEERDNS=yes > > IPV6INIT=no > > NM_CONTROLLED=no > > > > If this is ok, do a "service network > restart" followed by the "service > > dhcpd restart". Post the output of > "ifconfig" and "tail -f > > /var/log/messages". > > > > This should do it (hopefully), if you have no > hardware/driver problems > > with the eth1 card. > > > > Also, verify that the cable is connected into eth1, > that the led light is > > on, that the corresponding light on the switch is also > on, etc. In other > > words, make sure that the hardware part of the setup > is ok. > > > > HTH, :-) > > Marko > > Did you manage to do what I described? Yes, It is very close to working. The machines get an IP, get DNS, but cannot browse. Thank you for your guidance, and patience. Nov 19 07:02:23 localhost dhcpd: DHCPDISCOVER from 00:d0:b7:c1:09:58 via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPOFFER on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPACK on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:26 localhost dhcpd: DHCPDISCOVER from 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPOFFER on 192.168.0.3 to 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPREQUEST for 192.168.0.3 (192.168.0.1) from 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPACK on 192.168.0.3 to 00:11:2f:35:88:2e via eth1 Nov 19 07:03:16 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:03:16 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:03:21 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:03:21 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:04:53 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:04:53 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:04:57 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:04:57 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Regards, Antonio > > :-) > Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Wed, 11/19/08, Antonio Olivares <[EMAIL PROTECTED]> wrote: > From: Antonio Olivares <[EMAIL PROTECTED]> > Subject: Re: Make a DHCP server using Fedora - Help > To: [EMAIL PROTECTED] > Cc: fedora-list@redhat.com > Date: Wednesday, November 19, 2008, 5:06 AM > --- On Mon, 11/17/08, Marko Vojinovic > <[EMAIL PROTECTED]> wrote: > > > From: Marko Vojinovic <[EMAIL PROTECTED]> > > Subject: Re: Make a DHCP server using Fedora - Help > > To: [EMAIL PROTECTED], fedora-list@redhat.com > > Cc: [EMAIL PROTECTED] > > Date: Monday, November 17, 2008, 10:49 AM > > Ok, it seems we are getting somewhere. :-) > > > > > Nov 17 07:27:07 localhost dhcpd: Wrote 0 leases > to > > leases file. > > > Nov 17 07:27:07 localhost dhcpd: Listening on > > > LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 > > > Nov 17 07:27:07 localhost dhcpd: Sending on > > > LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 > > > Nov 17 07:27:07 localhost dhcpd: Sending on > > Socket/fallback/fallback-net > > > Nov 17 07:31:06 localhost dhcpd: DHCPINFORM from > > 10.154.19.25 via eth0 > > > Nov 17 07:31:06 localhost dhcpd: DHCPACK to > > 10.154.19.25 > > > (00:19:b9:10:16:92) via eth0 > > > > This is normal, dhcpd is active and running, listens > to all > > devices and > > "does nothing" on eth0, as configured. The > eth1 > > is a problem, but not > > related to dhcpd. > > > > > [EMAIL PROTECTED] ~]# dhcpd -f > > > > There is no need to start it explicitly. The > "service > > dhcpd restart" > > should be enough. > > > > > [EMAIL PROTECTED] ~]# cat /etc/sysconfig/dhcpd > > > DHCPDARGS= > > > > This is ok. > > > > > [EMAIL PROTECTED] ~]# ls > > /etc/sysconfig/network-scripts/ifcfg-eth* -l > > > -rw-r--r-- 3 root root 130 2007-04-03 12:36 > > > /etc/sysconfig/network-scripts/ifcfg-eth0 > > > > I see. There is no ifcfg-eth1. > > > > > [EMAIL PROTECTED] ~]# ifconfig -a > > > eth1 Link encap:Ethernet HWaddr > > 00:60:97:C5:2A:C3 > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:0 errors:0 dropped:0 > overruns:0 > > frame:0 > > > TX packets:0 errors:0 dropped:0 > overruns:0 > > carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > Interrupt:18 Base address:0xdf00 > > > > And this tells it all. The eth1 is not configured and > > running. > > > > > I also wonder if I should have a ifcfg-eth1 file > in > > > > > > /etc/sysconfig/network-scripts/ > > > > Yes, definitely. The "system-config-network" > gui > > should create it for you. > > Open it, and see if eth1 is listed in the Devices tab. > If > > not, click New > > to create it (follow the wizard). Then click Edit to > edit > > its > > configuration: > > > > In the General tab: > > * Activate the device when computer starts --- should > be > > the only checked > > option, everything else should be *unchecked* > > * Activate the static IP settings: > > * Address: 192.168.0.1 > > * Subnet mask: 255.255.255.0 > > * Gateway: leave empty for now > > > > In the Hardware Device tab: > > * Hardware: eth1 > > * Device alias --- unchecked > > * Bind to MAC --- checked > > * Hit the "probe" button and make sure the > MAC is > > 00:60:97:C5:2A:C3 (don't > > type it yourself, the button should fill it for you). > > > > Click OK to close the window and return to the main > one. In > > the File menu > > choose Save to save the new configuration. Close the > gui. > > > > Go to /etc/sysconfig/network-scripts/ and verify that > there > > exists an > > ifcfg-eth1 file, with the contents like the following: > > > > TYPE=Ethernet > > DNS1=10.154.16.130 > > DEVICE=eth1 > > BOOTPROTO=none > > NETMASK=255.255.255.0 > > IPADDR=192.168.0.1 > > DNS2=10.128.0.4 > > ONBOOT=yes > > USERCTL=no > > PEERDNS=yes > > IPV6INIT=no > > NM_CONTROLLED=no > > > > If this is ok, do a "service network > restart" > > followed by the "service > > dhcpd restart". Post the output of > > "ifconfig" and "tail -f > > /var/log/messages". > > > > This should do it (hopefully), if you have no > > hardware/driver problems > > with the eth1 card. > > > > Also, verify that the cable is connected into eth1, > that > > the led light is > > on, that the corresponding light on the switch is also > on, > > etc. In other > > words, make sure that the hardware part of the setup > is ok. > > > > HTH, :-) > > Marko > > I am making the changes and I am seeing new things :) > > [EMAIL PROTECTED] ~]# cat > /etc/sysconfig/network-scripts/ifcfg-eth1 > # Ethernet controller: 3Com Corporation 3c905 100BaseTX > [Boomerang] > DEVICE=eth1 > > HWADDR=00:60:97:c5:2a:c3 > > > BOOTPROTO=none > IPADDR=192.168.0.1 > ONBOOT=yes > USERCTL=no > PEERDNS=yes > IPV6INIT=no > NM_CONTROLLED=no > TYPE=Ethernet > [EMAIL PROTECTED] ~]# ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF > inet a
Re: Make a DHCP server using Fedora - Help
On Monday 17 November 2008 18:49, Marko Vojinovic wrote: > > I also wonder if I should have a ifcfg-eth1 file in > > > > /etc/sysconfig/network-scripts/ > > Yes, definitely. The "system-config-network" gui should create it for you. > Open it, and see if eth1 is listed in the Devices tab. If not, click New > to create it (follow the wizard). Then click Edit to edit its > configuration: > > In the General tab: > * Activate the device when computer starts --- should be the only checked > option, everything else should be *unchecked* > * Activate the static IP settings: > * Address: 192.168.0.1 > * Subnet mask: 255.255.255.0 > * Gateway: leave empty for now > > In the Hardware Device tab: > * Hardware: eth1 > * Device alias --- unchecked > * Bind to MAC --- checked > * Hit the "probe" button and make sure the MAC is 00:60:97:C5:2A:C3 (don't > type it yourself, the button should fill it for you). > > Click OK to close the window and return to the main one. In the File menu > choose Save to save the new configuration. Close the gui. > > Go to /etc/sysconfig/network-scripts/ and verify that there exists an > ifcfg-eth1 file, with the contents like the following: > > TYPE=Ethernet > DNS1=10.154.16.130 > DEVICE=eth1 > BOOTPROTO=none > NETMASK=255.255.255.0 > IPADDR=192.168.0.1 > DNS2=10.128.0.4 > ONBOOT=yes > USERCTL=no > PEERDNS=yes > IPV6INIT=no > NM_CONTROLLED=no > > If this is ok, do a "service network restart" followed by the "service > dhcpd restart". Post the output of "ifconfig" and "tail -f > /var/log/messages". > > This should do it (hopefully), if you have no hardware/driver problems > with the eth1 card. > > Also, verify that the cable is connected into eth1, that the led light is > on, that the corresponding light on the switch is also on, etc. In other > words, make sure that the hardware part of the setup is ok. > > HTH, :-) > Marko Did you manage to do what I described? :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Mon, 11/17/08, Marko Vojinovic <[EMAIL PROTECTED]> wrote: > From: Marko Vojinovic <[EMAIL PROTECTED]> > Subject: Re: Make a DHCP server using Fedora - Help > To: [EMAIL PROTECTED], fedora-list@redhat.com > Cc: [EMAIL PROTECTED] > Date: Monday, November 17, 2008, 10:49 AM > Ok, it seems we are getting somewhere. :-) > > > Nov 17 07:27:07 localhost dhcpd: Wrote 0 leases to > leases file. > > Nov 17 07:27:07 localhost dhcpd: Listening on > > LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 > > Nov 17 07:27:07 localhost dhcpd: Sending on > > LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 > > Nov 17 07:27:07 localhost dhcpd: Sending on > Socket/fallback/fallback-net > > Nov 17 07:31:06 localhost dhcpd: DHCPINFORM from > 10.154.19.25 via eth0 > > Nov 17 07:31:06 localhost dhcpd: DHCPACK to > 10.154.19.25 > > (00:19:b9:10:16:92) via eth0 > > This is normal, dhcpd is active and running, listens to all > devices and > "does nothing" on eth0, as configured. The eth1 > is a problem, but not > related to dhcpd. > > > [EMAIL PROTECTED] ~]# dhcpd -f > > There is no need to start it explicitly. The "service > dhcpd restart" > should be enough. > > > [EMAIL PROTECTED] ~]# cat /etc/sysconfig/dhcpd > > DHCPDARGS= > > This is ok. > > > [EMAIL PROTECTED] ~]# ls > /etc/sysconfig/network-scripts/ifcfg-eth* -l > > -rw-r--r-- 3 root root 130 2007-04-03 12:36 > > /etc/sysconfig/network-scripts/ifcfg-eth0 > > I see. There is no ifcfg-eth1. > > > [EMAIL PROTECTED] ~]# ifconfig -a > > eth1 Link encap:Ethernet HWaddr > 00:60:97:C5:2A:C3 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 > frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 > carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > Interrupt:18 Base address:0xdf00 > > And this tells it all. The eth1 is not configured and > running. > > > I also wonder if I should have a ifcfg-eth1 file in > > > > /etc/sysconfig/network-scripts/ > > Yes, definitely. The "system-config-network" gui > should create it for you. > Open it, and see if eth1 is listed in the Devices tab. If > not, click New > to create it (follow the wizard). Then click Edit to edit > its > configuration: > > In the General tab: > * Activate the device when computer starts --- should be > the only checked > option, everything else should be *unchecked* > * Activate the static IP settings: > * Address: 192.168.0.1 > * Subnet mask: 255.255.255.0 > * Gateway: leave empty for now > > In the Hardware Device tab: > * Hardware: eth1 > * Device alias --- unchecked > * Bind to MAC --- checked > * Hit the "probe" button and make sure the MAC is > 00:60:97:C5:2A:C3 (don't > type it yourself, the button should fill it for you). > > Click OK to close the window and return to the main one. In > the File menu > choose Save to save the new configuration. Close the gui. > > Go to /etc/sysconfig/network-scripts/ and verify that there > exists an > ifcfg-eth1 file, with the contents like the following: > > TYPE=Ethernet > DNS1=10.154.16.130 > DEVICE=eth1 > BOOTPROTO=none > NETMASK=255.255.255.0 > IPADDR=192.168.0.1 > DNS2=10.128.0.4 > ONBOOT=yes > USERCTL=no > PEERDNS=yes > IPV6INIT=no > NM_CONTROLLED=no > > If this is ok, do a "service network restart" > followed by the "service > dhcpd restart". Post the output of > "ifconfig" and "tail -f > /var/log/messages". > > This should do it (hopefully), if you have no > hardware/driver problems > with the eth1 card. > > Also, verify that the cable is connected into eth1, that > the led light is > on, that the corresponding light on the switch is also on, > etc. In other > words, make sure that the hardware part of the setup is ok. > > HTH, :-) > Marko I am making the changes and I am seeing new things :) [EMAIL PROTECTED] ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] DEVICE=eth1 HWADDR=00:60:97:c5:2a:c3 BOOTPROTO=none IPADDR=192.168.0.1 ONBOOT=yes USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=no TYPE=Ethernet [EMAIL PROTECTED] ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF inet addr:10.154.19.210 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::20e:a6ff:fe42:59af/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2535 errors:0 dropped:0 overruns:0 frame:0 TX packets:1985 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1074701 (1.0 MiB) TX bytes:401481 (392.0 KiB) Interrupt:22 Base address:0x6000 eth1 Link encap:Ether
Re: Lost audio on headphones (F9)
Hi Tim, On Tue, Nov 18, 2008 at 19:15, Tim <[EMAIL PROTECTED]> wrote: > On Tue, 2008-11-18 at 15:26 -0200, Andre Costa wrote: > > my desktop computer has one of those front headphones connectors, and > > it always worked (always = since Fedora8), playing the same audio that > > goes to the front speakers. I tried it today and it doesn't work > > anymore, > > Open up the volume controls and see if there's a separate volume control > just for the headphones. You might have to wallow through the > preferences to add more controls. Thks for the tip, but I had already done that. There's a chekcbox for headphone, which is checked. I also tried playing with every track volume level that seemed reasonable, but it did not work. (if anyone can provide more info on any specific settings that would affect headphone sound, that'd be great...) > > my guess is that some of the recent updates might have changed > > something on audio config > > > You might look through /var/log/yum.log to see what's been recently > updated, and see if they're a likely cause. > I took a look, but thet fact is that I can't precise when it stopped working, so the timeframe could be long... =( Thks anyway for your help. Regards, Andre -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
Michael Schwendt wrote: It depends on your sudo/sudoers configuration. You can read more about it in the manuals. Look out for setenv, env_, SECURE_PATH (and related settings). Hello, So, which config / env / default setting that we may need to know ( notice ) ? Many thanks ! Edward. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
Michael Schwendt wrote:
On Wed, 19 Nov 2008 17:17:40 +0800, [EMAIL PROTECTED] wrote:
Michael Schwendt wrote:
n Tue, 18 Nov 2008 08:36:56 -0800, Gordon Messmer wrote:
asswd-wrapper:
#!/bin/sh
# Validate that a username was given as an argument
[ -n "$1" ] || {
echo "Use: passwd-wrapper " >&2
exit 64
}
# Validate that the username wasn't "root"
[ "$1" != "root" ] || {
echo "Can't set the root user's password" >&2
exit 77
}
# Use -- to make sure that the "username" given wasn't just
# a switch that passwd would interpret.
# THIS ONLY WORKS ON GNU SYSTEMS.
passwd -- "$1"
Don't let users run this via sudo unless you execute tools with
absolute path --> /usr/bin/passwd
Hello,
Do you means there is some problem / security with this shell scripts ?
It depends on your sudo/sudoers configuration. You can read more about it
in the manuals. Look out for setenv, env_, SECURE_PATH (and related
settings).
Just the following rules :
SYSADM MH = (ALL)/usr/bin/passwd-wrapper
<>BUT, only some of special user who can running some of cmd via sudo...
eg: System Admin ( manager ) and Support Term...
<>It's general advise not to open an attack vector via $PATH when
trying to
impose restrictions on what those special users may run. Today your sudo
configuration may not permit that, but you wouldn't be the first one to
switch from sudo to setuid or to alter your sudo config in harmful ways.
I think the system admin config the sudo only for some special user (
eg: system support term ) for the Server Maintance...
So, NOT many user he/she can running with sudo, right ?
Thanks !
Edward.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
Michael Schwendt wrote:
>On Wed, 19 Nov 2008 12:52:30 +0800, edwardspl wrote:
>
>
>
>>Dear All,
>>
>>For /usr/bin/upasswd :
>>
>>#!/bin/sh
>>
>># Validate that a username was given as an argument
>>[ -n "$1" ] || {
>>echo "Use: upasswd " >&2
>>exit 64
>>}
>>
>># Validate that the username wasn't "root"
>>[ "$1" != "root" ] || {
>>echo "Can't set the root user's password" >&2
>>exit 77
>>}
>>
>># Use -- to make sure that the "username" given wasn't just
>># a switch that passwd would interpret.
>># THIS ONLY WORKS ON GNU SYSTEMS.
>>passwd -- "$1"
>>
>>For visudo :
>>SYSADM MH = (ALL) /usr/bin/upasswd
>>
>>
>
>Even if you rely on sudo's default environment variables restrictions and
>safety checks, prefer absolute paths when executing tools like
>/usr/bin/passwd
>
>
Hello,
Sorry, I don't quite understanding what is your means...
Thanks !
Edward.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No Shutdown Service in Init 1
Steve West wrote: When I run my service in init 1 there is no shutdown response to the power off button. What service handles the shutdown of the power off switch? ACPID? Steve Yes, you need acpid running for the power switch to work. It does not run during run level 1 by default. Run level 1 is normally reserved for fixing problems on the system, as it outs it in the single user mode, with root as the user. Only the minimum services necessary are started. What else does the ACPI service do? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IBM 19K5544 Intel Pro/100 Ethernet Adapter
I'm pretty sure that that card is a 64bit PCI card. The card that I have is kinda triangular shaped, and the connector is divided into three parts. One of them longer and the two equally small pieces, the second being the 64bit portion. In a 32bit slot, not all of the card would fit into the slot. The 64bit portion of the connector would be hanging out past the slot. This might explain why the card wouldn't be recognized when you check `lspci` and dmesg. -- This is an email sent via The Fedora Community Portal https://fcp.surfsite.org https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=304778&topic_id=63402&forum=10#forumpost304778 If you think, this is spam, please report this to [EMAIL PROTECTED] and/or blame [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
On Wed, 19 Nov 2008 17:17:40 +0800, [EMAIL PROTECTED] wrote:
> Michael Schwendt wrote:
>
> >On Tue, 18 Nov 2008 08:36:56 -0800, Gordon Messmer wrote:
> >
> >
> >
> >>passwd-wrapper:
> >>#!/bin/sh
> >>
> >># Validate that a username was given as an argument
> >>[ -n "$1" ] || {
> >>echo "Use: passwd-wrapper " >&2
> >>exit 64
> >>}
> >>
> >># Validate that the username wasn't "root"
> >>[ "$1" != "root" ] || {
> >>echo "Can't set the root user's password" >&2
> >>exit 77
> >>}
> >>
> >># Use -- to make sure that the "username" given wasn't just
> >># a switch that passwd would interpret.
> >># THIS ONLY WORKS ON GNU SYSTEMS.
> >>passwd -- "$1"
> >>
> >>
> >
> >Don't let users run this via sudo unless you execute tools with
> >absolute path --> /usr/bin/passwd
> >
> >
> >
> Hello,
>
> Do you means there is some problem / security with this shell scripts ?
It depends on your sudo/sudoers configuration. You can read more about it
in the manuals. Look out for setenv, env_, SECURE_PATH (and related
settings).
> BUT, only some of special user who can running some of cmd via sudo...
> eg: System Admin ( manager ) and Support Term...
It's general advise not to open an attack vector via $PATH when trying to
impose restrictions on what those special users may run. Today your sudo
configuration may not permit that, but you wouldn't be the first one to
switch from sudo to setuid or to alter your sudo config in harmful ways.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
On Wed, 19 Nov 2008 12:52:30 +0800, edwardspl wrote:
> Dear All,
>
> For /usr/bin/upasswd :
>
> #!/bin/sh
>
> # Validate that a username was given as an argument
> [ -n "$1" ] || {
> echo "Use: upasswd " >&2
> exit 64
> }
>
> # Validate that the username wasn't "root"
> [ "$1" != "root" ] || {
> echo "Can't set the root user's password" >&2
> exit 77
> }
>
> # Use -- to make sure that the "username" given wasn't just
> # a switch that passwd would interpret.
> # THIS ONLY WORKS ON GNU SYSTEMS.
> passwd -- "$1"
>
> For visudo :
> SYSADM MH = (ALL) /usr/bin/upasswd
Even if you rely on sudo's default environment variables restrictions and
safety checks, prefer absolute paths when executing tools like
/usr/bin/passwd
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
Michael Schwendt wrote:
>On Tue, 18 Nov 2008 08:36:56 -0800, Gordon Messmer wrote:
>
>
>
>>passwd-wrapper:
>>#!/bin/sh
>>
>># Validate that a username was given as an argument
>>[ -n "$1" ] || {
>> echo "Use: passwd-wrapper " >&2
>> exit 64
>>}
>>
>># Validate that the username wasn't "root"
>>[ "$1" != "root" ] || {
>> echo "Can't set the root user's password" >&2
>> exit 77
>>}
>>
>># Use -- to make sure that the "username" given wasn't just
>># a switch that passwd would interpret.
>># THIS ONLY WORKS ON GNU SYSTEMS.
>>passwd -- "$1"
>>
>>
>
>Don't let users run this via sudo unless you execute tools with
>absolute path --> /usr/bin/passwd
>
>
>
Hello,
Do you means there is some problem / security with this shell scripts ?
BUT, only some of special user who can running some of cmd via sudo...
eg: System Admin ( manager ) and Support Term...
Thank for your care...
Edward.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [sudo-users] How to disable ( deny ) user to change the password of root
On Tue, 18 Nov 2008 08:36:56 -0800, Gordon Messmer wrote:
> passwd-wrapper:
> #!/bin/sh
>
> # Validate that a username was given as an argument
> [ -n "$1" ] || {
> echo "Use: passwd-wrapper " >&2
> exit 64
> }
>
> # Validate that the username wasn't "root"
> [ "$1" != "root" ] || {
> echo "Can't set the root user's password" >&2
> exit 77
> }
>
> # Use -- to make sure that the "username" given wasn't just
> # a switch that passwd would interpret.
> # THIS ONLY WORKS ON GNU SYSTEMS.
> passwd -- "$1"
Don't let users run this via sudo unless you execute tools with
absolute path --> /usr/bin/passwd
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
