Jump to content

aioshin

Members
 View Profile  See their activity

  • Posts

    816

  • Joined

  • Last visited

 Content Type 

Posts posted by aioshin

  2. dhcp problem with Mandriva 2006 [solved]

    in Networking

    Posted · Edited by aioshin

    hardware for ws152 cannot be t7 check what the card mac address is.

     

    and check your bracketing and spacing not sure but the others are all the same not these two..

     

    actually, I just scrumbled those mac address since those are directly connected to internet, so there is nothing wrong with those.. but thanks for the reply anyway..

    .

    well, I found it, the culprit of my config.. almost a day I tried to look for the cause... and here it is

     

    Link

    The default value of the Siaddr field has changed

     

    The ISC guys have decided to change the default behaviour of the Siaddr field between release 3.0.2 and 3.0.3.

     

    Note that this change was considered to harmful by the ubuntu development team (its not nice to break user configurations with a minor version upgrade), it was reverted in ubuntu, so the following can be ignored by ubuntu users.

     

    Fortunately, there's a simple fix.

     

    The fix:

     

    In the dhcpd.conf file, you need to add a line like this:

     

    next-server 192.168.0.254;

     

     

    That entry should go near the top, so that it applies to ALL terminals. Make sure you put your server IP address in that entry..

     

     

     

    The reason for the breakage:

     

    In the DHCP reply offered by the server, there's a field called siaddr. This field is supposed to contain the IP address of the boot server. In versions of ISC dhcpd prior to 3.0.3, this field always defaulted to the value of the IP address of the dhcp server. As of ISC dhcpd version 3.0.3, it is now being zero filled.

     

    Here's the entry in the release notes that describe the change that was made:

     

    - The siaddr field was being improperly set to the server-identifier when

    responding to DHCP messages. RFC2131 clarified the siaddr field as

    meaning the 'next server in the bootstrap process', eg a tftp server.

    The siaddr field is now left zeroed unless next-server is configured.

     

     

    I've submitted a bug report to ISC, explaining that I think the field shouldn't default to zeros. We'll see if they accept it as a bug, and fix it for the next version. If not, then at least we have the easy fix of adding the 'next-server' entry to dhcpd.conf.

     

    Thanks to Anselm Martin Hoffmeister, for spending the time last weekend tracking down this issue.

     

    Jim McQuillan - Sept 9, 2005

     

    So on my config...for example on the host ws152 entry...

     

    host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}

    I inserted next-server 172.16.0.150; on it

    host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
next-server			172.16.0.150;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}

     

    which actually the same server that gaves those other thinclients a dhcp offer, while not using that particular entry...

    .

    .

    .

    :D

  4. dhcp problem with Mandriva 2006 [solved]

    in Networking

    Posted

    ok, here's the scenario:

     

    well, these is the result of my previous post about replacing Xandros with Mandriva.. now Im replacing it..and the problem:

     

    Configured 2006 as dhcp server.

    .

    I have several ThinClients PC and 2 DiskLess Desktop.. the thinclient boot directly from mandy 2006 via dhcp and fine, its working. Now I have here a remaining 2 Desktop acting as thinClients, Im using a floppy to boot to 2006 using Rom-O-Matic. I know there's no problem with the client since it already been booting fine on the Previous OS, Xandros. But now, on 2006, it just gave me a message :

     

    Searching for DHCP Server... NO IP address

    then how come that happened?, while the other had been able to connect to dhcp server.

    ok, here's my Config below and please help me, Im scratching my head now :wall:

    ddns-update-style			   none;
default-lease-time			  21600;
max-lease-time				  21600;
option subnet-mask			 255.255.255.0;
option broadcast-address	 172.16.0.255;
option routers					 172.16.0.1;
option domain-name-servers   2x.xx.xx.xx;
option domain-name		   "mydomain.com";		  # <--Fix this domain name
option root-path			 "172.16.0.150:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
subnet 172.16.0.0 netmask 255.255.255.0 {
use-host-decl-names	  on;
range	   172.16.0.150	172.16.0.180;
filename	"/lts/2.6.16.1-ltsp-2/pxelinux.0";
## If you want to use static IP address for your worksations, then un-comment
## the following section and modify to suit your network.
## Then, duplicate this section for each workstation that needs a static
## IP address.
		  }
#
host ws151	  {
	hardware ethernet	   00:00:90:63:96:39;
	fixed-address		   172.16.0.151;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
#
host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}
#
host ws153	 {
	hardware ethernet	 00:07:55:B3:91:41;
	fixed-address		   172.16.0.153;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
#
host ws154
	 {
	hardware ethernet	   00:11:5B:2A:94:CE;
	fixed-address		 172.16.0.154;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
	  }
#
host ws155
			{
   hardware ethernet	   00:40:C3:74:84:0B;
  fixed-address		   172.16.0.155;
 filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
		 }
#
host ws156	 {
	hardware ethernet	   00:07:55:63:76:2C;
	fixed-address		   172.16.0.156;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
}

     

    hosts ws152 and ws155 are the ones that cannot see the dhcp server, Is there something wrong with the config?

    Even if I will comment on the entries of those hosts, so it will just be offered by dhcp with dynamic address, but still it wont be able to see the dhcp server...

    .

    Firewall supposedly is not an issue here since the other were able to connect to the dhcp server, and they are on the same network, :wall:

    .

    Ok, I tried to build another dhcp server (for testing), I have a running centos, installed dhcp-server there and copy and paste the entries of the said hosts on its dhcp.conf then restart those said hosts, you know what?, it was able to see that Dhcp server.. I really dont know what is the problem with 2006..

     

    any help here is very much appreciated..

     

    TIA!

  5. Samba Troubles

    in Networking

    Posted

    run as root in your konsole

     

    iptables -F

     

    and it will clear your iptables...

     

    have you tried to access that windows pc from your konqueror using?

     

    smb://xxx

     

    where xxx is the ip address of windows pc

  6. Running Mandriva on older hardware

    in Software

    Posted

    you can also disable the ff: if in particular you dont need them

    atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

    nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off

    nifd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

    ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

    partmon 0:off 1:off 2:off 3:on 4:on 5:on 6:off

    portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off

    rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off

  7. Samba Troubles

    in Networking

    Posted

    actually, you dont need samba to be started just to see your windows share from that linux box, as long as you have smbclient installed.

     

    try to check your log files while trying to access that certain windows shared folder...

     

    #tail -f /var/log/messages

     

     

    I'm sure, you'll be able to find some clue from there

  8. customizing kdm log-out theme or image [solved]

    in Art And Design

    Posted · Edited by aioshin

    thanks Ian for the reply, but there is no option that let you change that image via mcc.. anyway, found it.. the image is called shutdownkonq.png, so I just replace it with another image then use that same filename and that solves it...

     

    oh, here's the image I'm talking about

     

    shutdownkonq.jpg

     

    located at /usr/share/apps/ksmserver/pics/

  15. DWL-G510 rev.b1

    in Hardware

    Posted · Edited by aioshin

    $>iwconfig ath0

     

    $>iwconfig ath0 essid 'castle'

     

    $>iwconfig key open '************************'

     

    did you do those command above as root, since usually "$" is a user prompt...

    .

    also check if a firewall has been blobking outgoing connection, am not sure yet with the mvd 2006 firewall on how to check it, but try to do the command as root:

    #/sbin/iptables -F

    it will flush iptables entries which allow all connections possible.. just do that for checking your connectivity, afterall, you inside a local network, not directly connected to internet

  20. Where is amule?

    in Software

    Posted · Edited by aioshin

    try to check if amule really has been installed successfully..

    as root:

    rpm -qa | grep amule

    on my box, that query results

    rpm -qa | grep amule

    amule-2.0.3-3plf

    means that its been installed from plf repo.. so to make sure of your installation, install it via urpmi... go to easyurpmi page and try to add additional repositories..

  22. Which serial port is my modem on?

    in Hardware

    Posted

    it's supposed to but when I try to send the fax, it does nothing.

     

    you may have to check your log files to trace the problem...

    as root issue command

    tail -f /var/log/messages

    then try to send fax, also on the hylafax client, you can also find there log files to check...

    .

    and make sure hylafax is running. usually, hylafax server listens on port 4559, so you can just do the command as root

    netstat -anlp | grep fax

    to see if hfaxd listens to 4559, means that hylafax is running..

    if not then start it.. 

    /etc/init.d/hylafax start

  23. amaroK

    in Software

    Posted

    dependency problem might be the cause.. try to post the errors you see in your console... this might give us clue..

    .

    ok, the amarok you'd just downloaded from its website are intended for Mandriva 2006... so I just dont know if installing it is a good idea.. try to use easy urpmi and add the ff. repo source..

     

    main, contrib, update, plf free, and non-free

     

    then try to update amarok from that repositories.. though its not 1.4, 1.3 might be, but at least it will not break your system

×
×
  • Create New...