D*n. Sorry for the direct email. Screwed up on the REPLY TO button. At 01/07/06 06:10, you wrote:
On Fri, 06 Jan 2006 20:35:58 -0600, you wrote:
At 01/05/06 06:42, Michael W Cocke wrote:
On Wed, 04 Jan 2006 22:05:00 -0600, you wrote:
Folks,
Many of you have seen my network traffic as I struggle to set up a small 2-subnet Samba-served LAN, and many of you have offered help in that endeavor, for which I thank you. Now, however, I'm confused.
[snip]
Eric, if I read your diagram correctly you're using the Linksys as your hub/switch? Did you know that while there are buggier pieces of equipment than a Linksys I cannot think of them offhand? Get rid of the trash and install a real firewall and a real switch and your problems will at least become consistant, if not go away.
Mike-
The Linksys sits on the edge of my LAN and fronts for it to the Internet. Everything that's happening on the LAN, including the on-again-off-again connection to my Samba server (which, by the way, is up today, but since I don't know why it's so unreliable, I don't consider this problem solved), is happening behind the Linksys.
Then I misread the diagram, sorry. Start from the top again please - You have a linux samba server - please post the smb.conf file. Also - are you using a wins server? I had some odd connection problems (don't recall the details, it was a while back) until I set one up - on the samba server, as it happens. You have windows workstations (Pro or home? Networks in XP home is severly broken.) that are connecting to the samba server intermittantly. Can you post the samba log from a session when the connect fails, and when the connect works?
Have I got the basics straight?
I think you've about got it, now. And my LAN is up today--two days in a row. I've done nothing, that I know of, to achieve this. And some clarifying data that, as my meager knowledge grows, may in fact be relevant. I say that the Linksys sits on the edge of my LAN and everything happens behind it, and that's the intent. However, all three NICs are on the SUSE Samba server, and because of the way YaST works, all three NICs have as their default gateway the Linksys. My understanding is that default GWs are addresses of last resort, so my claim that everything is happening behind the Linksys here stands (e.g., IP Forwarding is on, the stack knows where the interfaces are, etc), but I could be wrong. The smb.conf file (I've included only the global part, as the shares wouldn't seem relevant to this problem) and log excerpts are below. I have wins support = yes; and I have 2 instances of winbindd running. I have win2k Pro and XP Pro installed on the two devices. No "Home" versions for me. Thanks Eric Hines smb.conf [global]: [global] workgroup = ASTRA_ENT netbios name = LSERVER0 interfaces = 192.168.2.2/24, 192.168.3.1/24, lo bind interfaces only = Yes passdb backend = tdbsam pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*Password* %n\n *Re-enter*new*password* %n\n *Password*changed* username map = /etc/samba/smbusers unix password sync = Yes log level = 1 syslog = 0 log file = /var/log/samba/%m max log size = 50 smb ports = 139 name resolve order = wins bcast hosts time server = Yes printcap name = CUPS show add printer wizard = No add user script = /usr/sbin/useradd -m '%u' delete user script = /usr/sbin/userdel -r '%u' add group script = /usr/sbin/groupadd '%g' delete group script = /usr/sbin/groupdel '%g' add user to group script = /usr/sbin/usermod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u' shutdown script = /var/lib/samba/scripts/shutdown.sh abort shutdown script = /sbin/shutdown -c logon script = scripts\logon.bat logon path = \\%L\profiles\%U logon drive = X: logon home = \\%L\%U domain logons = Yes preferred master = Yes wins support = Yes ldap ssl = no utmp = Yes map acl inherit = Yes cups options = Raw veto files = /*.eml/*.nws/*.{*}/ veto oplock files = /*.doc/*.xls/*.mdb The log excerpts: ####log.nmbd: ###A day that failed: *** glibc detected *** double free or corruption (!prev): 0x081b2348 *** [2006/01/04 18:09:10, 0] nmbd/nmbd.c:main(724) Netbios nameserver version 3.0.22pre1-SVN-build-12170-SUSE started. Copyright Andrew Tridgell and the Samba Team 1992-2005 [2006/01/04 18:09:11, 0] nmbd/asyncdns.c:start_async_dns(151) started asyncdns process 6882 [2006/01/04 18:09:11, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/04 18:09:11, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/04 18:09:11, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet UNICAST_SUBNET [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup ASTRA_ENT, subnet UNICAST_SUBNET. [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 127.0.0.1 for domain master browser name ASTRA_ENT<1b> on workgroup ASTRA_ENT [2006/01/04 18:09:11, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet UNICAST_SUBNET [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet UNICAST_SUBNET ***** [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) become_domain_master_browser_bcast: Attempting to become domain master browser on workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) become_domain_master_browser_bcast: querying subnet 192.168.2.2 for domain master browser on workgroup ASTRA_ENT [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) become_domain_master_browser_bcast: Attempting to become domain master browser on workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/04 18:09:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) become_domain_master_browser_bcast: querying subnet 192.168.3.1 for domain master browser on workgroup ASTRA_ENT [2006/01/04 18:09:15, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/04 18:09:15, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/04 18:09:19, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** [2006/01/04 18:09:19, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet 192.168.3.1 ***** [2006/01/04 18:09:34, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server LSERVER0 is now a local master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** [2006/01/04 18:09:34, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server LSERVER0 is now a local master browser for workgroup ASTRA_ENT on subnet 192.168.3.1 ***** [2006/01/04 18:16:43, 0] nmbd/nmbd_incomingdgrams.c:process_local_master_announce(311) process_local_master_announce: Server MUSTELIDAE at IP 192.168.2.9 is announcing itself as a local master browser for workgroup ASTRA_ENT and we think we are master. Forcing election. [2006/01/04 18:16:43, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149) ***** Samba name server LSERVER0 has stopped being a local master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** [2006/01/04 18:17:00, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server LSERVER0 is now a local master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** ###A Day that succeeded: *** glibc detected *** double free or corruption (!prev): 0x081bbf18 *** [2006/01/07 06:27:19, 0] nmbd/nmbd.c:main(724) Netbios nameserver version 3.0.22pre1-SVN-build-12170-SUSE started. Copyright Andrew Tridgell and the Samba Team 1992-2005 [2006/01/07 06:27:20, 0] nmbd/asyncdns.c:start_async_dns(151) started asyncdns process 6736 [2006/01/07 06:27:20, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/07 06:27:20, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/07 06:27:20, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup ASTRA_ENT on subnet UNICAST_SUBNET [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup ASTRA_ENT, subnet UNICAST_SUBNET. [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 127.0.0.1 for domain master browser name ASTRA_ENT<1b> on workgroup ASTRA_ENT [2006/01/07 06:27:20, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet UNICAST_SUBNET [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet UNICAST_SUBNET ***** [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) become_domain_master_browser_bcast: Attempting to become domain master browser on workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) become_domain_master_browser_bcast: querying subnet 192.168.2.2 for domain master browser on workgroup ASTRA_ENT [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) become_domain_master_browser_bcast: Attempting to become domain master browser on workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/07 06:27:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) become_domain_master_browser_bcast: querying subnet 192.168.3.1 for domain master browser on workgroup ASTRA_ENT [2006/01/07 06:27:24, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet 192.168.2.2 [2006/01/07 06:27:24, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup ASTRA_ENT on subnet 192.168.3.1 [2006/01/07 06:27:28, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** [2006/01/07 06:27:28, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** Samba server LSERVER0 is now a domain master browser for workgroup ASTRA_ENT on subnet 192.168.3.1 ***** [2006/01/07 06:27:43, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server LSERVER0 is now a local master browser for workgroup ASTRA_ENT on subnet 192.168.2.2 ***** [2006/01/07 06:27:43, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server LSERVER0 is now a local master browser for workgroup ASTRA_ENT on subnet 192.168.3.1 ***** ####log.winbindd ###A day that failed [2006/01/04 22:37:53, 1] nsswitch/winbindd.c:main(976) winbindd version 3.0.22pre1-SVN-build-12170-SUSE started. Copyright The Samba Team 2000-2004 ###A day that succeeded: [2006/01/07 06:27:28, 1] nsswitch/winbindd.c:main(976) winbindd version 3.0.22pre1-SVN-build-12170-SUSE started. Copyright The Samba Team 2000-2004 ####winbindd ###A day that failed [2006/01/04 18:09:11, 0] nsswitch/winbindd_util.c:winbindd_param_init(782) winbindd: idmap uid range missing or invalid [2006/01/04 18:09:11, 0] nsswitch/winbindd_util.c:winbindd_param_init(783) winbindd: cannot continue, exiting. [2006/01/04 18:09:11, 1] nsswitch/winbindd.c:main(1009) Could not init idmap -- netlogon proxy only [2006/01/04 22:37:53, 0] nsswitch/winbindd_util.c:winbindd_param_init(782) winbindd: idmap uid range missing or invalid [2006/01/04 22:37:53, 0] nsswitch/winbindd_util.c:winbindd_param_init(783) winbindd: cannot continue, exiting. [2006/01/04 22:37:53, 1] nsswitch/winbindd.c:main(1009) Could not init idmap -- netlogon proxy only ###NOTE: the log.winbindd had a lot of this kind of entry, also at the end of Dec, but since 1 Jan, it's been as clean as indicated above. ###A day that succeeded [2006/01/07 06:27:28, 0] nsswitch/winbindd_util.c:winbindd_param_init(782) winbindd: idmap uid range missing or invalid [2006/01/07 06:27:28, 0] nsswitch/winbindd_util.c:winbindd_param_init(783) winbindd: cannot continue, exiting. [2006/01/07 06:27:28, 1] nsswitch/winbindd.c:main(1009) Could not init idmap -- netlogon proxy only There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell
On Sat, 2006-01-07 at 11:20 -0600, Eric Hines wrote:
D*n. Sorry for the direct email. Screwed up on the REPLY TO button.
<snip>
I think you've about got it, now. And my LAN is up today--two days in a row. I've done nothing, that I know of, to achieve this. And some clarifying data that, as my meager knowledge grows, may in fact be relevant. I say that the Linksys sits on the edge of my LAN and everything happens behind it, and that's the intent. However, all three NICs are on the SUSE Samba server, and because of the way YaST works, all three NICs have as their default gateway the Linksys. My understanding is that default GWs are addresses of last resort, so my claim that everything is happening behind the Linksys here stands (e.g., IP Forwarding is on, the stack knows where the interfaces are, etc), but I could be wrong. The smb.conf file (I've included only the global part, as the shares wouldn't seem relevant to this problem) and log excerpts are below.
I have wins support = yes; and I have 2 instances of winbindd running.
I have win2k Pro and XP Pro installed on the two devices. No "Home" versions for me.
Thanks
Eric Hines
<hugh snip> Eric, Since you are using your PC as a router with it (the PC) between two internal subnets and the internet the PC only needs to have a single default GW and IP forwarding turned on. The proper setup would have a separate hub/switch connected to each secondary NIC (or a crossover cable if only one PC is used) for network access. diagram: ISP modem | Linksys router | 192.168.1.1 (I may have the subnets mixed up but the theory is the | same) Also this is the default GW for the samba PC. | 192.168.1.2 | PC external NIC | samba PC |___________ | | | PC NIC #2 - internal network #1 192.168.100.x | PC NIC #3 - internal network #2 192.168.200.x Any PC's on internal #1 would set their default GW to the IP address if the NIC #2 on the samba PC. The same goes for PC's on internal #2 as they would have their default GW set to the IP of NIC #3 on the samba PC. I think most of your problems are one of routing not working as it should because the default GW's are not being properly setup or understood. If you want to talk via land line let me know in a private email. Not sure were you live, I'm in SW Florida. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
At 01/07/06 11:54, Ken Schneider wrote:
On Sat, 2006-01-07 at 11:20 -0600, Eric Hines wrote:
D*n. Sorry for the direct email. Screwed up on the REPLY TO button.
<snip>
I think you've about got it, now. And my LAN is up today--two days in a row. I've done nothing, that I know of, to achieve this. And some clarifying data that, as my meager knowledge grows, may in fact be relevant. I say that the Linksys sits on the edge of my LAN and everything happens behind it, and that's the intent. However, all three NICs are on the SUSE Samba server, and because of the way YaST works, all three NICs have as their default gateway the Linksys. My understanding is that default GWs are addresses of last resort, so my claim that everything is happening behind the Linksys here stands (e.g., IP Forwarding is on, the stack knows where the interfaces are, etc), but I could be wrong. The smb.conf file (I've included only the global part, as the shares wouldn't seem relevant to this problem) and log excerpts are below.
I have wins support = yes; and I have 2 instances of winbindd running.
I have win2k Pro and XP Pro installed on the two devices. No "Home" versions for me.
Thanks
Eric Hines
<hugh snip>
Eric,
Since you are using your PC as a router with it (the PC) between two internal subnets and the internet the PC only needs to have a single default GW and IP forwarding turned on. The proper setup would have a separate hub/switch connected to each secondary NIC (or a crossover cable if only one PC is used) for network access.
diagram:
ISP modem | Linksys router | 192.168.1.1 (I may have the subnets mixed up but the theory is the | same) Also this is the default GW for the samba PC. | 192.168.1.2 | PC external NIC | samba PC |___________ | | | PC NIC #2 - internal network #1 192.168.100.x | PC NIC #3 - internal network #2 192.168.200.x
Any PC's on internal #1 would set their default GW to the IP address if the NIC #2 on the samba PC. The same goes for PC's on internal #2 as they would have their default GW set to the IP of NIC #3 on the samba PC. I think most of your problems are one of routing not working as it should because the default GW's are not being properly setup or understood. If you want to talk via land line let me know in a private email. Not sure were you live, I'm in SW Florida.
If I understand you correctly, I think that is my set up, including with IP forwarding turned on. Below is my version of ASCII art, with more detail. I think it shows what you're talking about. .3.9 ---Laptop----Hub---------.3.1-----Samba (PDC/dns/dhcp)-----.2.2-------------Hub-----PC-----.2.9 (WinXP NIC (NIC on Samba | (NIC on Samba NIC (Win2k laptop) server) .1.2 server) PC) (NIC on Samba server) | Linksys router/switch .1.1 | ISP's Cable Modem | Internet The laptop NIC has .3.1 as its default gateway, the PC NIC has .2.2 as its default gateway, and the three NICs on the Samba server (.1.2, .2.2, and .3.1) all have, because of the way YaST does this, the Linksys as their default gateway. I think I'd like to have .2.2 and .3.1 each have .1.2 as their default gateway, but I don't know how to do that. The Hubs exist because of the physical layout of my office, not, unfortunately, through any special acumen on my part. However, each hub has only its computer and default gateway NIC plugged into it. I'm in a suburb of Dallas. I don't mind the telecon, but I think we may be at an accurate description of the LAN, now. Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell
On Saturday 07 January 2006 23:27, Eric Hines wrote:
If I understand you correctly, I think that is my set up, including with IP forwarding turned on. Below is my version of ASCII art, with more detail. I think it shows what you're talking about.
< ASCII art was munged>
The laptop NIC has .3.1 as its default gateway, the PC NIC has .2.2 as its default gateway, and the three NICs on the Samba server (.1.2, .2.2, and .3.1) all have, because of the way YaST does this, the Linksys as their default gateway. I think I'd like to have .2.2 and .3.1 each have .1.2 as their default gateway, but I don't know how to do that. The Hubs exist because of the physical layout of my office, not, unfortunately, through any special acumen on my part. However, each hub has only its computer and default gateway NIC plugged into it.
Do you really want these boxes to have ~.1.2 as their gateway? This, after all, if I have read your earlier diagram right, is the outgoing interface of the Samba PDC. I think you mean ~.1.1, your outgoing router. I think this can be done, if you set an explicit route to ~.1.1 on each box via which ever interface of the Samba PDC it is connected.
At 01/07/06 18:00, Vince Littler wrote:
On Saturday 07 January 2006 23:27, Eric Hines wrote:
If I understand you correctly, I think that is my set up, including with IP forwarding turned on. Below is my version of ASCII art, with more detail. I think it shows what you're talking about.
< ASCII art was munged>
The laptop NIC has .3.1 as its default gateway, the PC NIC has .2.2 as its default gateway, and the three NICs on the Samba server (.1.2, .2.2, and .3.1) all have, because of the way YaST does this, the Linksys as their default gateway. I think I'd like to have .2.2 and .3.1 each have .1.2 as their default gateway, but I don't know how to do that. The Hubs exist because of the physical layout of my office, not, unfortunately, through any special acumen on my part. However, each hub has only its computer and default gateway NIC plugged into it.
Do you really want these boxes to have ~.1.2 as their gateway? This, after all, if I have read your earlier diagram right, is the outgoing interface of the Samba PDC. I think you mean ~.1.1, your outgoing router.
Yes, the two subnets are supposed to have to go through the server box to get to the Internet, rather than having their own direct route. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell
On Sun, 2006-01-08 at 00:00 +0000, Vince Littler wrote:
On Saturday 07 January 2006 23:27, Eric Hines wrote:
If I understand you correctly, I think that is my set up, including with IP forwarding turned on. Below is my version of ASCII art, with more detail. I think it shows what you're talking about.
< ASCII art was munged>
The laptop NIC has .3.1 as its default gateway, the PC NIC has .2.2 as its default gateway, and the three NICs on the Samba server (.1.2, .2.2, and .3.1) all have, because of the way YaST does this, the Linksys as their default gateway. I think I'd like to have .2.2 and .3.1 each have .1.2 as their default gateway, but I don't know how to do that. The Hubs exist because of the physical layout of my office, not, unfortunately, through any special acumen on my part. However, each hub has only its computer and default gateway NIC plugged into it.
Do you really want these boxes to have ~.1.2 as their gateway? This, after all, if I have read your earlier diagram right, is the outgoing interface of the Samba PDC. I think you mean ~.1.1, your outgoing router.
I think this can be done, if you set an explicit route to ~.1.1 on each box via which ever interface of the Samba PDC it is connected.
Not correct, you need to set the default GW to the next router in the path to the internet, which in this case is the samba PC, for the subnet in use. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Sunday 08 January 2006 04:23, Ken Schneider wrote:
On Sun, 2006-01-08 at 00:00 +0000, Vince Littler wrote:
Do you really want these boxes to have ~.1.2 as their gateway? This, after all, if I have read your earlier diagram right, is the outgoing interface of the Samba PDC. I think you mean ~.1.1, your outgoing router.
I think this can be done, if you set an explicit route to ~.1.1 on each box via which ever interface of the Samba PDC it is connected.
Not correct, you need to set the default GW to the next router in the path to the internet, which in this case is the samba PC, for the subnet in use.
Agree. I was just trying to make more sense of the OP's proposal. And if it is do as I do rather than as I say, default gateway is on the same subnet as the box you are routing for. I have given the other config a quick try, and it seems to fall down on the way back from the second router. Probably it requires this router also to have a similar config, which it wont take, being a cheapy ADSL router.
On Sun, 2006-01-08 at 11:29 +0000, Vince Littler wrote:
On Sunday 08 January 2006 04:23, Ken Schneider wrote:
On Sun, 2006-01-08 at 00:00 +0000, Vince Littler wrote:
Do you really want these boxes to have ~.1.2 as their gateway? This, after all, if I have read your earlier diagram right, is the outgoing interface of the Samba PDC. I think you mean ~.1.1, your outgoing router.
I think this can be done, if you set an explicit route to ~.1.1 on each box via which ever interface of the Samba PDC it is connected.
Not correct, you need to set the default GW to the next router in the path to the internet, which in this case is the samba PC, for the subnet in use.
Agree. I was just trying to make more sense of the OP's proposal. And if it is do as I do rather than as I say, default gateway is on the same subnet as the box you are routing for.
I have given the other config a quick try, and it seems to fall down on the way back from the second router. Probably it requires this router also to have a similar config, which it wont take, being a cheapy ADSL router.
That also is not correct. Linksys routers will not route traffic when the subnet is not directly known (other then to try and send them out to the internet). They can only ask other routers if they know about a subnet (actually a host). In this case the samba PC/router is -between- the Linksys router and two subnets so it is the job of the samba PC/router to answer queries for those two subnets. If it does not then the Linksys router will send all packets that it doesn't have routing info for out it's default GW which would be the internet and all addresses in the 192.168.x.x range are not routable on the internet. That is why it "falls down" when the two subnets use the Linksys as a default GW, the PC's are trying to bypass the samba PC/router. Always use the nearest router as the defaut GW and let the router do it's job of routing the traffic. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (3)
-
Eric Hines -
Ken Schneider -
Vince Littler