streeter
Members-
Posts
333 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by streeter
-
Probably the easiest thing, as you have only just installed the system, would be a re-install - choose upgrade when prompted.
-
Glad it works! Q1: Normally it is simple - just use the wizard, but if you make a mistake, have an out of the ordinary set up or run the wrong wizard (say, internet connection sharing), Mandrakes wizards will mess up big time. Q2: DNS is a system for looking up numerical IP addresses from the human readable ones you type in (like www.google.com). The config file for this is /etc/resolv.conf. You just need a line (put it at the top) saying nameserver xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is your ISPs nameserver address. You can get this from their website or another PC - a Windows one will do. The phrases to look for are DNS, domain name server, nameserver or any combination... If you are really stuck, use my ISPs until you find out yours - 195.20.224.165 (belongs to 1&1 - putting your ISPs server in here will be a little quicker) Chris
-
Glad I checked before posting this - I was typing loads of stuff (mostly rubbish) - you fixed it! You don't need iptables installed to have a firewall - iptables is just a 'front end' to the kernel netfilter code and is worth installing to use for troubleshooting. You may have something else setting up a firewall, most likely shorewall. masonjd >>I hope no one minds... Of course not - the more the merrier!! Chris
-
Please post contents of /etc/resolv.conf
-
>> Should I change it too poor since I have a firewall? Not really - best to have multi-level security. The security levels do not refer directly to the firewall - they do quite a few other things, like checking file permissions and running checks - have a look here for more info: Msec Can you also connect to the interface itself? i.e. "telnet 192.168.0.1 25" or whatever address you are using, rather than 127.0.0.1 My guess is you have a firewall on this machine blocking input - post the output of "iptables -nvL". If you get an error, "urpmi iptables" to install it. For testing only, I have a short howto disable a firewall at Disable your firewall Or you could just open port 25 with iptables -I INPUT 1 -i eth0 -p tcp --dport 25 -j ACCEPT But be warned this will be the first rule in the chain - you may want to put other rules before it. Chris
-
If rebooting's not an option, run the same command with the -D switch instead of -A or -I. You can also do it by number: "iptables -t nat -D PREROUTING 1" for instance. See man iptables and the netfilter howtos - if you are setting up or altering an internet facing firewall manually (or at all for that matter) you really ought to read up on iptables/netfilter. Chris
-
Don't know about Suse, so probably can't help - anybody else? You could try echo 1 > /proc/sys/net/ipv4/ip_forward - does the same thing (may already be set - have a look). Chris
-
You appear to have 2 network cards defined - please post the output of lsmod | grep natsemi lsmod | grep 8239too This will tell us if the drivers are being loaded. Then have a look at my howto at : My howto Also look at the sticky post at the top of the networking forum Chris
-
Haven't tried this MoBo, but find it pretty unlikely that it won't work with mdk - more likely to be our old friend a 'wizard problem'. Have a look at the sticky post at the top of the networking forum and take it from there. Let us know how you get on. Post output from ifconfig if still having probs. Chris
-
This is forwarding all http traffic coming in on eth0 to your webserver - I assume you want this to be eth1... So the rule needs to be iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j DNAT --to 192.168.117.156 You could also use eth+ for all ethernet interfaces You will also need to enable forwarding with net.ipv4.ip_forward=1 in /etc/sysctl.conf Chris
-
"urpmi telnet-client" to install
-
No need to compile - sasl is included in the mdk postfix rpm. I have this working, but cannot really remember what I did (!!). I do however maintain a file I keep setup notes of all sorts in, so this extract may help, particularly the URL: #To enable relaying through isp (allow auth): echo auth.smtp.myisp.co.uk user:pass >> /etc/postfix/isp_auth (I made this filename up) #To hash passwd list do: postmap hash:/etc/postfix/isp_auth /etc/postfix/main.cf: (see /usr/share/doc/postfix/samples/sample-auth.cf) smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/isp_auth smtp_sasl_security_options = (blank. allows any auth. including plain text) See http://postfix.state-of-mind.de/patrick.koetter/smtpauth/ error message after upgrade from 9.1 - 10.0: (Authentication failed: cannot SASL authenticate to server auth.smtp.myisp.co.uk[xxx.xxx.xxx.xxx]: no mechanism available) Reinstalling cyrix-sasl fixed it
-
I will add that to the howto Chris
-
>>Yes, it is running Sorry - reading too quickly!! Have you a line in /etc/postfix/main/cf that says inet_interfaces = all ? This sets the ports to listen to. Can you ping the postfix machine? Can you telnet from the postfix machine itself to port 25? Chris
-
Sorry - clarification: (I just did this now to make sure it works!!) BACK UP /usr and /home and anything else important, like /etc perhaps. Hit esc on the lilo boot screen and type linux 1 <<enter>> to go to run level 1 Type diskdrake at the prompt Use diskdrake to resize /home and then make and format the new partition - set /usr as it's mountpoint - you will be prompted to move or hide the files - choose move. /usr will be copied across to the new partition. Say yes to the question about modifying fstab. Type reboot, and all should be well... Chris
-
Your onboard card SHOULD work with a standard MDK 2.6 kernel - try Typing "lsmod | grep rhine" - do you get any output? If you do, the driver module is loaded. If not try "modprobe via-rhine" - what output do you get? Make sure you have "alias eth0 via-rhine" in your /etc/modprobe.conf file Then look at the 'sticky' post at the top of the networking forum for how to set up a manual connection. You will find a link to this URL: http://web.onetel.net.uk/~showerail/simple_net_setup.html which will hopefully help - let me know... Chris
-
I have never had any problems with diskdrake, but usual backup warnings apply... As I cannot see what else you have on your disk (in between hda1 and 6), I would suggest shrinking the home partition by say 15GB and then mounting this 15GB as the /usr filesystem. You will obviously need to mount the new partition as a temporary filesystem to copy the existing /usr files across before altering fstab. Chris
-
So is postfix running? "service postfix status" should give you "master (pid xxx) is running..." If not, try "service postfix start" or use drakxservices. If you still cannot telnet to port 25, you need to edit the configuration - it would help us if you told us exactly what you are trying to achieve and how far you have got... If you use webmin to set postfix up, you probably don't have to do a lot of configuration. Chris
-
The service postfix should be running - check with drakxservices. How far have you got, and what are you trying to achieve, i.e. do you wish to run an internet visible server, or just outbound for your private network? Can you telnet to your smtp server - "telnet <IP_ADDRESS> 25" from your LAN? You will need to open up port 25 on your firewall, and also set postfix up to listen on any required interface - the "inet_interfaces = " directive in the main.cf file. Webmin is quite good for setting the server up. Chris
-
I like kpackage - gives a list of all files and their paths
-
>>When I do a iptable -L , I get a listing of my active rules as far as I know? To see the nat table, you need to specify it with: iptables -nvL -t nat You may also need to insert the rule into the PREROUTING table, rather than adding it to the end - use "-I PREROUTING <position>" instead of "-A PREROUTING", otherwise another rule may 'catch' the packets first. Should be OK to do this 'on top' of shorewall, providing it is done after shorewall has run, though to keep things tidy it is best to edit the shorewall files. Chris
-
AHA!! That would explain a lot :) I should have looked the card up... >>.. and there WAS NO /etc/modprobe.conf For the record, the equivalent files were called modules and modules.conf Chris
-
Several ways, but I like putting commands at the end of /etc/rc.d/rc.local - this script gets executed after all the other links in (if you are booting to a graphical desktop) rc.5. Probably the easiest way. You could also put the commands in a separate script in the /etc/rc.d/init.d folder if you like, then make a symlink to it from /etc/rc.d/rc.5. Or you could start it later, when KDE loads Chris
-
Have a look at the sticky post at the top of the networking forum - there are a couple of links to a generic manual set up (including where to put your default route) Read in conjunction with steve Scrimshaw's excellent advice. Also tells you the information we need for a diagnosis. Chris
-
Still erring on the side of replacement, but if you can ping the card from itself, it may be worth installing iptables in case it is a firewall issue (unlikely, unless you have added/removed any rules). You can then disable any firewall by following the instructions in the sticky post link and try to ping the network again. If it now works, you will have to change the firewall rules. If it doesn't - best get a new card. Chris