[opensuse] Networking Issue (Revisited)
Hello folks! A long time ago I installed a home/office network based on a SUSE (~9.x) server with several Win clients. The server was also connected to the Internet via an ADSL modem (configured as a modem, not a router) - and everything has worked fine through all the SUSE updates through to the current 10.3. The SUSE firewall was also configured and ran as expected. I had the supreme temerity to install a new half-way decent work-station/server. The 10.3 re-install went like clockwork except for one problem: 1. The Win clients all communicate happily with the server via SAMBA. 2. The server itself talks to the Internet via the ADSL modem. I cannot get the client Win systems talking to the Internet (as they did before) through the server i.e. I'm missing something in the network setup. Here are a few details: (For the time being I have firewalling disabled so as not to complicate things.) 1. The ADSL modem is connected to server on eth0, which is set to take an IP address etc dynamically via modem's DHCP server. That works (otherwise you wouldn't be seeing this). 2. The new server is connected to the LAN via eth1 to a hub. 3. THE Server IP is set to 192.168.1.100 on eth1. 4. IP forwarding enabled. 5. The DHCPD daemon is installed to serve client machines and works fine. They define 192.168.1.100 as their gateway. Here is netstat: (The vmnet items are from VMware and may be ignored.) danny:~ # netstat -n -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 213.8.255.155 0.0.0.0 255.255.255.255 UH 0 0 0 dsl0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.16.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1 192.168.216.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 dsl0 and here is ifconfig (with the vmnet items removed): danny:~ # ifconfig dsl0 Link encap:Point-to-Point Protocol inet addr:84.228.69.233 P-t-P:213.8.255.155 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:5802 errors:0 dropped:0 overruns:0 frame:0 TX packets:10089 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6522877 (6.2 Mb) TX bytes:999040 (975.6 Kb) eth0 Link encap:Ethernet HWaddr 00:1C:C0:53:F6:53 inet addr:10.0.0.2 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9570 errors:0 dropped:0 overruns:0 frame:0 TX packets:15750 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:10908964 (10.4 Mb) TX bytes:1856712 (1.7 Mb) Base address:0x40c0 Memory:e3100000-e3120000 eth1 Link encap:Ethernet HWaddr 00:C1:26:0E:CA:46 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7644 errors:0 dropped:0 overruns:0 frame:0 TX packets:228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:603541 (589.3 Kb) TX bytes:31004 (30.2 Kb) Interrupt:17 Base address:0x6000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:408 errors:0 dropped:0 overruns:0 frame:0 TX packets:408 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20856 (20.3 Kb) TX bytes:20856 (20.3 Kb) The dsl0 IP address, 84.228.69.233 is my (dynamic) local address supplied by the ISP. The eth0 IP address, 10.0.0.2 is allocated by the ADSL modem's own DHCP server and "looks right" based on previous experience. I have gone through the usual panaceas of rebooting the server, and then the clients - to no avail. So what am I missing? Any takers? Thanks, Daniel
Hey Daniel, Question: What is the gateway of stations? The same ip on eth0? If you have a interface with same network of stations, please put the eth0 address to the stations gateways. And better: use tcpdump to look incoming packets from local network. A simple way to check this is: tcpdump -i eth0 After change the gateway of stations, use the command above and paste here: Cheers. On Sat, May 10, 2008 at 7:05 PM, Daniel Feiglin <dilogsys@inter.net.il> wrote:
Hello folks!
A long time ago I installed a home/office network based on a SUSE (~9.x) server with several Win clients. The server was also connected to the Internet via an ADSL modem (configured as a modem, not a router) - and everything has worked fine through all the SUSE updates through to the current 10.3. The SUSE firewall was also configured and ran as expected.
I had the supreme temerity to install a new half-way decent work-station/server. The 10.3 re-install went like clockwork except for one problem:
1. The Win clients all communicate happily with the server via SAMBA. 2. The server itself talks to the Internet via the ADSL modem.
I cannot get the client Win systems talking to the Internet (as they did before) through the server i.e. I'm missing something in the network setup.
Here are a few details: (For the time being I have firewalling disabled so as not to complicate things.)
1. The ADSL modem is connected to server on eth0, which is set to take an IP address etc dynamically via modem's DHCP server. That works (otherwise you wouldn't be seeing this). 2. The new server is connected to the LAN via eth1 to a hub. 3. THE Server IP is set to 192.168.1.100 on eth1. 4. IP forwarding enabled. 5. The DHCPD daemon is installed to serve client machines and works fine. They define 192.168.1.100 as their gateway.
Here is netstat: (The vmnet items are from VMware and may be ignored.) danny:~ # netstat -n -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 213.8.255.155 0.0.0.0 255.255.255.255 UH 0 0 0 dsl0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.16.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1 192.168.216.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 dsl0
and here is ifconfig (with the vmnet items removed): danny:~ # ifconfig dsl0 Link encap:Point-to-Point Protocol inet addr:84.228.69.233 P-t-P:213.8.255.155 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:5802 errors:0 dropped:0 overruns:0 frame:0 TX packets:10089 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6522877 (6.2 Mb) TX bytes:999040 (975.6 Kb)
eth0 Link encap:Ethernet HWaddr 00:1C:C0:53:F6:53 inet addr:10.0.0.2 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9570 errors:0 dropped:0 overruns:0 frame:0 TX packets:15750 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:10908964 (10.4 Mb) TX bytes:1856712 (1.7 Mb) Base address:0x40c0 Memory:e3100000-e3120000
eth1 Link encap:Ethernet HWaddr 00:C1:26:0E:CA:46 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7644 errors:0 dropped:0 overruns:0 frame:0 TX packets:228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:603541 (589.3 Kb) TX bytes:31004 (30.2 Kb) Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:408 errors:0 dropped:0 overruns:0 frame:0 TX packets:408 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20856 (20.3 Kb) TX bytes:20856 (20.3 Kb)
The dsl0 IP address, 84.228.69.233 is my (dynamic) local address supplied by the ISP.
The eth0 IP address, 10.0.0.2 is allocated by the ADSL modem's own DHCP server and "looks right" based on previous experience.
I have gone through the usual panaceas of rebooting the server, and then the clients - to no avail.
So what am I missing?
Any takers?
Thanks,
Daniel
-- /\ Gabriel Stein gabrielstein@gmail.com MSN: gabrielstein@hotmail.com Administrador de Redes - Network Administrator Linux User #223750 +55 51 9357 3886 Porto Alegre - RS - Brasil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Gabriel Stein wrote:
Hey Daniel,
Question: What is the gateway of stations? The LAN gateway is the eth1 address, i.e. 192.168.1.100. I have not actually explicitly defined it as such (e.g. through yast|Nestwork Serices|Routing|Default Gateway), and it doesn't seem to make any difference.
The same ip on eth0? eth0 get its IP address from the modem DHCP server. The ISP's gateway IP address appears on the dsl0 interface in the netstat table. I have no control of these things. If you have a interface with same network of stations, please put the eth0 address to the stations gateways.
And better: use tcpdump to look incoming packets from local network. A simple way to check this is: tcpdump -i eth0
I switched off all but one client, with IP address 192.168.1.200. I also shut down the local browser. With nothing doing (except for a bit of mail now and again), eth0 was quiet. I have apache running on my server. When I asked the client to go to http://192,168.1.100/ it did so correctly, but there was a flurry of activity on eth0 - that should not happen. That by the way is WITH yast|Nestwork Serices|Routing|Default Gateway now set to 192.168.1.100. I then attempted to access a website (known to be responding) from the client - and again I got a flurry of activity on eth0, of packets from 192.168.1.200 - the client. So stuff is getting out - maybe too much. Question: What filter for tcpdump should I use to push out just to see relevant stuff in both directions?
After change the gateway of stations, use the command above and paste here:
Cheers.
On Sat, May 10, 2008 at 7:05 PM, Daniel Feiglin <dilogsys@inter.net.il> wrote:
Hello folks!
A long time ago I installed a home/office network based on a SUSE (~9.x) server with several Win clients. The server was also connected to the Internet via an ADSL modem (configured as a modem, not a router) - and everything has worked fine through all the SUSE updates through to the current 10.3. The SUSE firewall was also configured and ran as expected.
I had the supreme temerity to install a new half-way decent work-station/server. The 10.3 re-install went like clockwork except for one problem:
1. The Win clients all communicate happily with the server via SAMBA. 2. The server itself talks to the Internet via the ADSL modem.
I cannot get the client Win systems talking to the Internet (as they did before) through the server i.e. I'm missing something in the network setup.
Here are a few details: (For the time being I have firewalling disabled so as not to complicate things.)
1. The ADSL modem is connected to server on eth0, which is set to take an IP address etc dynamically via modem's DHCP server. That works (otherwise you wouldn't be seeing this). 2. The new server is connected to the LAN via eth1 to a hub. 3. THE Server IP is set to 192.168.1.100 on eth1. 4. IP forwarding enabled. 5. The DHCPD daemon is installed to serve client machines and works fine. They define 192.168.1.100 as their gateway.
Here is netstat: (The vmnet items are from VMware and may be ignored.) danny:~ # netstat -n -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 213.8.255.155 0.0.0.0 255.255.255.255 UH 0 0 0 dsl0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.16.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1 192.168.216.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 dsl0
and here is ifconfig (with the vmnet items removed): danny:~ # ifconfig dsl0 Link encap:Point-to-Point Protocol inet addr:84.228.69.233 P-t-P:213.8.255.155 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:5802 errors:0 dropped:0 overruns:0 frame:0 TX packets:10089 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6522877 (6.2 Mb) TX bytes:999040 (975.6 Kb)
eth0 Link encap:Ethernet HWaddr 00:1C:C0:53:F6:53 inet addr:10.0.0.2 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9570 errors:0 dropped:0 overruns:0 frame:0 TX packets:15750 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:10908964 (10.4 Mb) TX bytes:1856712 (1.7 Mb) Base address:0x40c0 Memory:e3100000-e3120000
eth1 Link encap:Ethernet HWaddr 00:C1:26:0E:CA:46 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7644 errors:0 dropped:0 overruns:0 frame:0 TX packets:228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:603541 (589.3 Kb) TX bytes:31004 (30.2 Kb) Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:408 errors:0 dropped:0 overruns:0 frame:0 TX packets:408 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20856 (20.3 Kb) TX bytes:20856 (20.3 Kb)
The dsl0 IP address, 84.228.69.233 is my (dynamic) local address supplied by the ISP.
The eth0 IP address, 10.0.0.2 is allocated by the ADSL modem's own DHCP server and "looks right" based on previous experience.
I have gone through the usual panaceas of rebooting the server, and then the clients - to no avail.
So what am I missing?
Any takers?
Thanks,
Daniel
On 05/11/2008 06:05 AM, Daniel Feiglin wrote:
1. The Win clients all communicate happily with the server via SAMBA. 2. The server itself talks to the Internet via the ADSL modem.
I cannot get the client Win systems talking to the Internet (as they did before) through the server i.e. I'm missing something in the network setup.
You need to run the firewall, and you need to turn on masquerading, and you need to define which NIC is in which zone, i.e. eth0 in external, eth1 in internal. The client machines need NATed to be able to reach the internet, which is accomplished by the masquerade feature on the firewall.
Here are a few details: (For the time being I have firewalling disabled so as not to complicate things.)
1. The ADSL modem is connected to server on eth0, which is set to take an IP address etc dynamically via modem's DHCP server. That works (otherwise you wouldn't be seeing this). 2. The new server is connected to the LAN via eth1 to a hub. 3. THE Server IP is set to 192.168.1.100 on eth1. 4. IP forwarding enabled.
You also need masquerading turned on in the firewall.
5. The DHCPD daemon is installed to serve client machines and works fine. They define 192.168.1.100 as their gateway.
Hope that helps. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
On 05/11/2008 06:05 AM, Daniel Feiglin wrote:
1. The Win clients all communicate happily with the server via SAMBA. 2. The server itself talks to the Internet via the ADSL modem.
I cannot get the client Win systems talking to the Internet (as they did before) through the server i.e. I'm missing something in the network setup.
You need to run the firewall, and you need to turn on masquerading, and you need to define which NIC is in which zone, i.e. eth0 in external, eth1 in internal. The client machines need NATed to be able to reach the internet, which is accomplished by the masquerade feature on the firewall.
Here are a few details: (For the time being I have firewalling disabled so as not to complicate things.)
1. The ADSL modem is connected to server on eth0, which is set to take an IP address etc dynamically via modem's DHCP server. That works (otherwise you wouldn't be seeing this). 2. The new server is connected to the LAN via eth1 to a hub. 3. THE Server IP is set to 192.168.1.100 on eth1. 4. IP forwarding enabled.
You also need masquerading turned on in the firewall.
5. The DHCPD daemon is installed to serve client machines and works fine. They define 192.168.1.100 as their gateway.
Hope that helps.
That did it! Thanks.
participants (3)
-
Daniel Feiglin -
Gabriel Stein -
Joe Morris