streeter

Try to get back to the situation you were in to begin with. If you had a log in screen, presumably you WERE connected wirelessly, just not logged in to the hotels system... If this was the case, and you can get back there, don't touch any of the wireless stuff! You can confirm this at the command line with ifconfig as root - if you have an IP address for your wireless adapter, your wireless is working and you need to think about the login problem only. You may also want to try connecting to an open network to check too, if you can. Most common reasons for being dumped back to a login screen are either wrong user/pass or browser rejecting cookies. Just to be sure, try downloading Opera (assuming you've got an Internet connection...) Also, have you asked for an alternate username and password, just in case the one you have is not set up on the system - it does happen.

Have you got cookies turned on?

Why 2 routers? Would a hub or switch between the computers perhaps be more suitable, as PC1 is in effect a router if you are sharing its connection. What is your IP addressing scheme - if there is a router between the PCs, the IP addresses should be on different subnets (assuming you are actually routing, and the PCs are not just plugged into the switch ports on the router - then they should be in the same subnet.) Need the output of route -n too please, for both machines, as the gateway on PC2 should point to the router. Router gateway should point to PC1. Can you ping/browse a website by IP address? (66.249.93.99 should get you Google) Have you checked the Internet connection sharing howto?

/etc/modprobe.conf file: alias eth0 8139too if that doesn't work, I think there are further commands you can add in there, along the lines of remove 8139cp but there may be more to it than that - check the man pages /etc/modprobe.conf file: alias net-pf-10 off Any access point/ wireless modem router with a web interface should work. Wireless cards are another kettle of fish, but use the search facility in the forum for recommendations. I have used the following PCMCIA cards on Mandrake: (I don't run 2006 though...) Cisco 340 Buffalo WLI-PCM-L11G Belkin F5D7010xx (with ndiswrapper) and USB: Belkin F5D7050 (with ndiswrapper)

What module is being used now? I think we need to ensure the 8139too one is in use before we go any further, and IPv6 is disabled. Please confirm. Please also confirm you have checked/swapped the cables, you are not plugged in to an uplink port on the switch, or that the CD distro still works. I am also assuming you don't have another card you can try... Chris

You may have to install mii-tools (urpmi mii-tools). Not sure what processes you mean... To kill a process, type killall process_name (e.g. killall lisa - which I see has caused the problem you have described before - see the search tool)

This looks like one of those threads you wish you never replied to... :) The iptables command in the howto is to over-ride shorewall firewall when there is a proxy server running due to running the Internet connection sharing wizard - you don't have any of this, so an error is to be expected - ignore it. It's not causing your problem, but shouldn't the reslov.conf entry be 10.0.0.2 ? Your firewall is wide open, so no problem there. Try the suggestions in turn, and let us know how you get on. (ipv6 is still on - the inet6 addr: fe80::250:fcff:feb9:79e0/64 line in ifconfig doesn't need to be there) Make sure you are using the 8139too driver module. The output of mii-tools eth0 from both machines may help. Have fun!

The syslog thingy should show output from your system log, and is simply an easier way to view this output when you are troubleshooting. You will only get output if there has been something logged. For instance - I just ran out of paper in my printer, so the last entry is: It's just easier than typing tail /var/log/syslog all the time... Now, you have an IP address assigned to your NIC, and can ping it from itself - so far, so good, that means the NIC and networking is (probably) working OK. You say you have had the network working with a CD distro, so we can rule out cabling/connections. Just to be 100% sure though, swap the patch leads from the 2 PCs over, and check the pings again. Check the speed/duplex settings in the output of mii-tool eth0 on both computers - they should match. If not, they can be forced with something like mii-tool -F 100baseTx-FD eth0 I definitely think it is worth removing the 8139cp module before going any further. You may just need to edit the /etc/modprobe.conf file. Reboot afterwards, check it is gone with lsmod | grep 8139 The output from the route -n command and your firewall would be the next things to check. I know it is not easy copying output from commands with no networking, but it is very important we can see it - that's why it's there! Chris

You may also want to add alias net-pf-10 off to /etc/modules.conf, as this seems to have solved many problems in the past (turns off IPv6, the 'new' IP addressing scheme)

When you get problems like this, it is usually best to edit relevent files manually with a text editor (the purpose behind the howto!): Add to /etc/modules.conf: alias eth0 8139too Should force the module to load - make sure there are no other entries for eth0. Modules can be unloaded with rmmod if you need to, and added manually with modprobe, so try modprobe 8139too. You may get some output from this command if there is a problem - no output usually means success, but look in your logs. Hint - add this to the bottom of /etc/syslog.conf : *.* /dev/tty12 and you can view your system log in real time by pressing control-alt-F12. Control-alt-F7 (or some other F-key) to return to your window manager. If the module is loaded correctly, try (as root) ifconfig eth0 10.0.0.100 up Then see if you have an IP address... Good luck!

OK - so all we need to do is set up the notebook. Although the card works in other OS's, there may be a problem with this distro or the setup. As I said before, follow the howto for the client set up (Assigning static IP addresses in the pinned post). It is vital to have all the IP addresses in the same group as each other. There is a simple test routine at the end of the post : On the desktop, type ifconfig eth0 into a terminal as root. This will give you the IP address of the desktop, say 10.0.0.2. Do the same on the notebook - make sure you have an IP address and it is in the same group as the desktop, but with a different number at the end. If there is no IP address, the config, card or driver module is at fault. If you have an IP address, try pinging your notebook NIC from the notebook - that's right, ping the notebook from itself (type "ping -c3 10.0.0.2" or whatever your IP address is) This will either give a positive result (look for 3 packets transmitted, 3 received in the output) or negative (3 packets transmitted, 0 received in the output). If OK - Try pinging the desktop If OK - Try pinging the router If OK - Try browsing - if you cannot reach say, www.google.com, try typing http://216.239.59.99 (IP address of google) into your browser address bar. (If you cannot reach a site by name, but can get it by IP address, you have a name resolver (DNS) problem - the dns server should probably be set to the IP address of the router. This is in /etc/resolv.conf) If you get errors, post all the IP addresses, any error messages and the results of all the tests above. There is a list of things to post at the bottom of the howto - you may need to copy them to a floppy or USB key to post them. We need as much info as possible. Chris

In the factory default state, the router will normally have a LAN side IP address of (usually) 192.168.0.1 or 192.168.1.1, but check the manual. It will normally have a built in DHCP server which is enabled and set to issue IP addresses and configuration to computers on demand. If you have set up any software on your PCs to use other IP address ranges, and don't want to change the configs, you will obviouslyneed to change the IP address of the router - in order to do this you will have to temporarily change the IP address of one of your PCs to an address in the same range as the router and use a web browser to log in to it at 192.168.0.1 (or 192.168.1.1). To change a PC IP address, type (as root) ifconfig eth0 192.168.0.2 up The IP address may be different - check the manual. Netgear routers usually have it printed on a label, together with the default password and username underneath the device. The howto at client setup goes through how your files should look - this is the howto you should be following. File sharing etc. through the switch will work just fine - you will need to set up file sharing with Samba, NFS or whatever you intend to use. The howto above actually assumes you have been 'fiddling' with the configuration, so yes, it should work! Could you clarify the actual problem for us? i.e. is the router connected to the net and working, what make/model of router/modem have you got, can you connect with Windows? etc... You may want to reset the router if you have altered any of the firewall or security settings in it, just to make sure. Chris

Hi Arne You are correct - the connection sharing howto is written for sharing a dial-up modem connection - i.e. one computer is connected directly to the net and is sharing its connection. With a router and switch, the router is the device doing the connecting and sharing. So you need to set up all the computers connected through the switch as clients. Your setup is the easiest to implement - it often 'just works' ! Chris

Haven't ever tried to get Linux to talk to a Mac, and this is not exactly what you are asking, but I have sucessfully networked Win98 with OSX. The key is to have a user set up on the Windows box with EXACTLY the same username and password as on the Mac. The username to use is the short name on the Mac. Failing this, you could perhaps set up an FTP server on the Linux box, or maybe even get an external drive... Remember, you should store a backup off site (fire, flood, theft...)

Your gateway address is the IP address of the device you are connecting to the Internet with, i.e. the LAN facing side of your router/modem. The dynamic gateway your ISP refers to will be picked up automatically by your router/modem - you don't need to worry about this. Often (but not always) 192.168.1.1 unless you have changed it. Look in your documentation. If you need more help, or this is not relevent to your set up, please give a few more details - your PC IP address, what devices you have on the LAN with their make/model and how it is all connected. Good luck!

Just been playing around with a Belkin F5D7050 802,11g USB adaptor - reasonably easy to get going with ndiswrapper. Haven't tested it for a great deal of time, but seems reliable enough connecting to both my home WLAN and the local towns wireless network. Chris

Welcome to Linux (and this board) ! See the sticky howto: https://mandrivausers.org/index.php?showtopic=16737

I have vncserver running on my server, which does not run a graphical desktop (no monitor, so why bother) Cannot remember how I set it up :) urpmi tightvnc-server There is a file /etc/rc.d/init.d/vncserver and also /etc/sysconfig/vncservers, which contains the following line: VNCSERVERS="1:chris" chris is my username, 1 is the screen number. It is run at boot from a symlink in /etc/rc.d/rc3.d May have a closer look if I have time as I could do with documenting it in case of disaster... Chris Edit: Ok - curiosity got the better of me - I just set it up on my test machine... took all of 5 minutes. 1) Install tightvnc-server with urpmi tightvnc-server 2) Edit /etc/sysconfig/vncservers as above ( VNCSERVERS="1:chris" ) 3) As the named user, type vncpasswd and follow the prompts 4) Edit symlinks in/etc/rc.d/rcx.d (it added K35vncserver on mine - change to S99vncserver or some other high number that loads after networking, firewall etc..) 5) Reboot or start the service with ' service vncserver start ' That's it - worked for me! Log on from a remote machine by using <ip address>:1 as the hostname.

Don't know about the suspending prob, but these NICs should be on different networks, for instance 192.168.1.x and 192.168.2.x. I suspect restarting the network sets the routing table so that 'it works'. Set up 2 separate networks and you will probably find the problem disappears... Chris

Can you reach, say www.cisco.com? If not, can you reach it by typing 198.133.219.25 in to the browser address bar? Can you ping the Cisco site (or any other website for that matter) from XP? Again, by name and then IP address. Chris

That looks OK - what is the problem? We will need a description of your network (what machines, what are their IP addresses, how do you connect to the Internet, have you a firewall etc...) Also the output of ' route -n ' and ' cat /etc/resolv.conf ' may be helpful. Chris

Virtual interfaces don't show up in the routing table, but it all looks OK to me, assuming nothing else has changed (are both the IP addresses shown in ifconfig?) Wonder why route resolved the ip address in the default route line of your routing table, but not the first line... these addresses should be the same. You should use route -n to view the table - it shows the addresses without doing a DNS lookup. If the virtual interfaces work, but the 'real' one doesn't, perhaps it might be worth trying 2 virtual ones? ie eth0:1 and eth0:2 - worth a try :) You should be able to set the virtual interfaces up at boot by making new files in /etc/sysconfig/network-scripts. Copy the ifcfg-eth0 file, edit it and rename to ifcfg-eth0:1 etc... Chris

Try turning off shorewall - a lot of those rules are unnecessary for a simple network... Below is a cut down, basic firewall which can be put in a file in /etc/rc.d/init.d. Call it tables or something and put symlinks in /etc/rc3.d and rc5.d to run it at boot. It is very basic (doesn't do protection from DOS attacks etc, but we are on dial up here so being practical, that's not really a problem). It gives pretty good protection and will be easy to troubleshoot. See how you get on... #flush the tables iptables -F iptables -t nat -F iptables -X common iptables -N common # Create new chain called common #Default policies iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT ACCEPT iptables -A INPUT -i ppp+ -m state --state ESTABLISHED,RELATED -j ACCEPT # allow established packets in ppp0 iptables -A INPUT -i ppp+ -j DROP # drop all other packets coming in to ppp0 iptables -A INPUT -j common iptables -A FORWARD -j common iptables -A common -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A common -s 127.0.0.1 -j ACCEPT iptables -A common -s 192.168.100.0/24 -j ACCEPT iptables -A common -j LOG --log-prefix "Chain common" iptables -A common -j DROP #Log, then Dump the rest iptables -t nat -A POSTROUTING -o ppp+ -s 192.168.100.0/24 -d 0/0 -j MASQUERADE

Chain loc_dnat (1 references) pkts bytes target prot opt in out source destination 0 0 REDIRECT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 redir ports 3128 0 0 REDIRECT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 redir ports 3128 Haven't got time at the minute to follow the chains through, but this is redirecting all HTTP traffic through Squid, which is presumeably not working properly... Try adding this rule: iptables -t nat -D PREROUTING -i eth0 -j loc_dnat Should work - deletes the path to the redirection rule. Chris

Ouch - long firewall list... When you try to access the Internet from the laptop, the packets follow this route through your rules and get dropped: Chain FORWARD (policy DROP 0 packets, 0 bytes) 26 1928 srcfilt all -- * * 0.0.0.0/0 0.0.0.0/0 Chain srcfilt (2 references) 29 2180 s2 all -- * * 192.168.100.0/24 0.0.0.0/0 Chain s2 (1 references) 26 1928 f2to0 all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2to0 (1 references) 26 1928 logdrop all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logdrop (8 references) 29 2072 logdrop2 all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 1/sec burst 10 Chain logdrop2 (1 references) 29 2072 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 7 level 4 prefix `DROPPED ' 29 2072 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 So, try typing this as root: iptables -I FORWARD 1 -s 192.168.100.0/24 -j ACCEPT and let us know what happens! (it Inserts a rule to allow anything from your LAN at the top of the FORWARD table) Your firewall ruleset really does not need to be that long - there are a lot of redundant entries in there... Chris