LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   internet sharing lost after update Suse 9.2 (http://www.linuxquestions.org/questions/linux-networking-3/internet-sharing-lost-after-update-suse-9-2-a-299510/)

newtuxuser 03-09-2005 04:26 AM

internet sharing lost after update Suse 9.2
 
Good morning,

I have an (old) Mandrake 9.2 pc which connects through an ADSL router (192.168.100.100) to the internet.
This machine has always shared the internet over it's second NIC (eth1 - static 192.168.100.50) with the Suse 9.2 pc.

The Mandrake get's it's IP from the router through dhcp on it's eth0.

After updating Suse 9.2 (with Yast) two weeks ago I can now only use http (surf with Mozilla).
FTP, receiving/sending email, streaming music (mplayer plugin), the d4x downloader and You (yast update) do not work anymore.

Fish works as usual so I can still connect to the Mandrake pc.

The Suse machine has static IP 192.168.100.51 on eth0

How can I put everything ( ? manually) back to normal.


newtuxuser

Fraudulent 03-10-2005 02:17 AM

Re: internet sharing lost after update Suse 9.2
 
Answer inline


Quote:

Originally posted by newtuxuser
Good morning,

I have an (old) Mandrake 9.2 pc which connects through an ADSL router (192.168.100.100) to the internet.
This machine has always shared the internet over it's second NIC (eth1 - static 192.168.100.50) with the Suse 9.2 pc.

The Mandrake get's it's IP from the router through dhcp on it's eth0.

After updating Suse 9.2 (with Yast) two weeks ago I can now only use http (surf with Mozilla).
FTP, receiving/sending email, streaming music (mplayer plugin), the d4x downloader and You (yast update) do not work anymore.

Fish works as usual so I can still connect to the Mandrake pc.

The Suse machine has static IP 192.168.100.51 on eth0

How can I put everything ( ? manually) back to normal.


newtuxuser

This sounds to me like a firewall problem.
Have I got your network figured out correctly?

Code:

[suse]---[mandrake]----[router]--(internet)
or is it
Code:

              [suse]
                l
[mandrake]---[router]---(internet)

If you CAN still surf then the connections fine. I would check out firewall settings on the suse box since that is what has changed.
/m

newtuxuser 03-10-2005 03:41 AM

Thanks for wanting to help me out

The first setup is correct

Suse (childrens Pc) is connected to the Mandrake (my pc) which connects through the adsl router to the internet

I dropped the firewalls on both machines for testing but this makes no difference

The proxy setting on the suse is http://192.168.100.50:80

Is there a command to see why only http works ?

This is very strange - I've been using both distro's since Suse 6.4 and never experienced any problems.

Fraudulent 03-11-2005 04:18 AM

Is the mandrake serving as a http-proxy? If that is the case:
This smells like a routing problem. You should set up mandrake to masquerade (NAT) instead.
HTTP is working because the proxy (mandrake?) will do the surfing for you and return the pages. Maybe your old suse was setup to use mandrake as a proxy for everything?

The other stuff (ftp etc..) is obviously not using the proxy. If Mandrake is not translating addresses, your router will have no way of knowing how to pass reply packets back to your suse box. If you do use translation on mandrake, the router will simply pass the packets to mandrake which in turn will forward the packets to suse.
If you set up ethereal and sniff the packets on your mandrake box you should see suse packets going out to the router but no return packets is coming back.

I realize this stuff is difficult to grasp without knowing a fair bit of TCP/IP. Let me know if you need futher explanation.

newtuxuser 03-11-2005 04:27 PM

how do i make NAT work ?

if been through the Mandrake control center but didn't find it

newtuxuser 03-14-2005 05:35 AM

You were right - it was a routing problem which I could fix.

Thanks a lot for your help !!!!!!!!

Fraudulent 03-14-2005 05:46 AM

Quote:

Originally posted by newtuxuser
You were right - it was a routing problem which I could fix.

Thanks a lot for your help !!!!!!!!

Well you actually fixed it yourself, so pat yourself on the back and have an extra beer.


All times are GMT -5. The time now is 05:38 AM.