On Sun, 8 Feb 2004, Remco Barendse wrote:
>
> Everything has been working fine but all of a sudden a client on the
> linksys could not connect.
>
> The LAN card that the linksys is connected to is using ips in the
> 10.2.x.x range, the linksys gets an ip like 10.2.0.10.
>
Are you saying that the linksys doesn''t have a fixed address?
> The linksys hands out ip addresses in the 192.168.x.x range and I think
> this is causing the problem. This is a snippet from the log:
>
> Feb 8 22:03:16 raveon nmbd[23217]: [2004/02/08 22:03:16, 0]
> nmbd/nmbd_packets.c:send_netbios_packet(172)
>
> Feb 8 22:03:16 raveon nmbd[23217]: send_netbios_packet: send_packet()
> to IP 192.168.1.103 port 137 failed
>
> Feb 8 22:03:16 raveon nmbd[23217]: [2004/02/08 22:03:16, 0]
> nmbd/nmbd_namequery.c:query_name_from_wins_server(297)
>
> Feb 8 22:03:16 raveon nmbd[23217]: query_name_from_wins_server: Failed
> to send packet trying to query name SABINE<03>
>
> I haven''t got a clue however why this has been working for over a
year and
> all of a sudden it stopped working?
>
> Ideas anyone?
>
Your Linux router needs to know how to route to 192.168.0.0/16 so you
presumabely have a route defined to that network through the Linksys. If
the Linksys gets an address other than the gateway address in that route,
then your Linux box can''t route to the 192.168.0.0/16 network.
If this is your situation, I would set up your DHCP server such that the
Linksys always gets the same IP address.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net