loopbak : OK A --> O : OK A --> B : OK A --> C : OK A --> D : OK - C --> *All* : OK - B --> A : OK B --> O : OK B --> C(172.16.0.10) : OK B --> C(172.30.0.1) : Fail B --> D : Fail 1. The default router for B is A. 2. All the stations except A are Win2K/Win9X Any idea what I should do so that B can get to D? Best Regards Yehoram Ben-Yaacov [email]yben@boscom.com[/email] [allowsmilie] => 1 [showsignature] => 0 [ipaddress] => [iconid] => 0 [visible] => 1 [attach] => 0 [infraction] => 0 [reportthreadid] => 0 [isusenetpost] => 1 [msgid] => <4149929c.0309090414.6ac171e7@posting.google.com> [ref] => [htmlstate] => on_nl2br [postusername] => Yehoram B.Y. [ip] => yben@boscom.com [isdeleted] => 0 [usergroupid] => [membergroupids] => [displaygroupid] => [password] => [passworddate] => [email] => [styleid] => [parentemail] => [homepage] => [icq] => [aim] => [yahoo] => [msn] => [skype] => [showvbcode] => [showbirthday] => [usertitle] => [customtitle] => [joindate] => [daysprune] => [lastvisit] => [lastactivity] => [lastpost] => [lastpostid] => [posts] => [reputation] => [reputationlevelid] => [timezoneoffset] => [pmpopup] => [avatarid] => [avatarrevision] => [profilepicrevision] => [sigpicrevision] => [options] => [akvbghsfs_optionsfield] => [birthday] => [birthday_search] => [maxposts] => [startofweek] => [referrerid] => [languageid] => [emailstamp] => [threadedmode] => [autosubscribe] => [pmtotal] => [pmunread] => [salt] => [ipoints] => [infractions] => [warnings] => [infractiongroupids] => [infractiongroupid] => [adminoptions] => [profilevisits] => [friendcount] => [friendreqcount] => [vmunreadcount] => [vmmoderatedcount] => [socgroupinvitecount] => [socgroupreqcount] => [pcunreadcount] => [pcmoderatedcount] => [gmmoderatedcount] => [assetposthash] => [fbuserid] => [fbjoindate] => [fbname] => [logintype] => [fbaccesstoken] => [newrepcount] => [vbseo_likes_in] => [vbseo_likes_out] => [vbseo_likes_unread] => [temp] => [field1] => [field2] => [field3] => [field4] => [field5] => [subfolders] => [pmfolders] => [buddylist] => [ignorelist] => [signature] => [searchprefs] => [rank] => [icontitle] => [iconpath] => [avatarpath] => [hascustomavatar] => 0 [avatardateline] => [avwidth] => [avheight] => [edit_userid] => [edit_username] => [edit_dateline] => [edit_reason] => [hashistory] => [pagetext_html] => [hasimages] => [signatureparsed] => [sighasimages] => [sigpic] => [sigpicdateline] => [sigpicwidth] => [sigpicheight] => [postcount] => 5 [islastshown] => [isfirstshown] => [attachments] => [allattachments] => ) --> routing problem - Windows Networking
Professional Web Applications Themes

routing problem - Windows Networking

Hi All, details of my network: ======================== WindowsXP: first NIC(wireless) ->192.168.0.9 (static) second NIC ->192.168.1.5 (static) IPEnableRouter = 1 (yes) (not using bridge) Linux: IP 192.168.1.3 Windows2k: IP 192.168.0.102 (from DHCP from wireless router) connections: ====================================== Windows2k -> wireless router-> WindowsXP <- Linux ======================================== problem: I can ping from Win2k to WindowsXP both NICs, but I can't to Linux. I can ping from WindowsXP to Linux, so I thought if I add route 192.168.1.0 through 192.168.0.9 Gateway on XP it would work. But NOT. I don't get it why. Here is Windows 2k route map: =========================== Active Routes: Network Destination ...

  1. #1

    Default routing problem

    Hi All,
    details of my network:
    ========================
    WindowsXP:
    first NIC(wireless) ->192.168.0.9 (static)
    second NIC ->192.168.1.5 (static)
    IPEnableRouter = 1 (yes)
    (not using bridge)

    Linux:
    IP 192.168.1.3

    Windows2k:
    IP 192.168.0.102 (from DHCP from wireless router)

    connections:
    ======================================
    Windows2k -> wireless router-> WindowsXP <- Linux
    ========================================
    problem:
    I can ping from Win2k to WindowsXP both NICs, but I can't to Linux.
    I can ping from WindowsXP to Linux, so I thought if I add route
    192.168.1.0 through 192.168.0.9 Gateway on XP it would work. But NOT.
    I don't get it why.

    Here is Windows 2k route map:
    ===========================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102 1
    127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    192.168.0.0 255.255.255.0 192.168.0.102 192.168.0.102 1
    192.168.0.102 255.255.255.255 127.0.0.1 127.0.0.1 1
    192.168.0.255 255.255.255.255 192.168.0.102 192.168.0.102 1
    192.168.1.0 255.255.255.0 192.168.0.9 192.168.0.102 1
    224.0.0.0 224.0.0.0 192.168.0.102 192.168.0.102 1
    255.255.255.255 255.255.255.255 192.168.0.102 192.168.0.102 1
    Default Gateway: 192.168.0.1
    ================================================== =========================
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    192.168.1.0 255.255.255.0 192.168.0.9 1


    and here WindowsXP route map:
    ============================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    192.168.0.0 255.255.255.0 192.168.0.9 192.168.0.9 4
    192.168.0.9 255.255.255.255 127.0.0.1 127.0.0.1 4
    192.168.0.255 255.255.255.255 192.168.0.9 192.168.0.9 4
    192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 2
    192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 2
    192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 2
    224.0.0.0 240.0.0.0 192.168.0.9 192.168.0.9 4
    224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 2
    255.255.255.255 255.255.255.255 192.168.0.9 192.168.0.9 1
    255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
    ================================================== =========================
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    192.168.1.0 255.255.255.0 192.168.1.5 2

    any ideas?
    thanks



    cyborg Guest

  2. #2

    Default Re: routing problem

    In article <uBHNgJcRDHA.560TK2MSFTNGP10.phx.gbl>, "cyborg"
    <kc2ine> wrote:
    >Hi All,
    >details of my network:
    >========================
    >WindowsXP:
    >first NIC(wireless) ->192.168.0.9 (static)
    >second NIC ->192.168.1.5 (static)
    >IPEnableRouter = 1 (yes)
    >(not using bridge)
    >
    >Linux:
    >IP 192.168.1.3
    >
    >Windows2k:
    >IP 192.168.0.102 (from DHCP from wireless router)
    >
    >connections:
    >======================================
    >Windows2k -> wireless router-> WindowsXP <- Linux
    >========================================
    >problem:
    >I can ping from Win2k to WindowsXP both NICs, but I can't to Linux.
    >I can ping from WindowsXP to Linux, so I thought if I add route
    >192.168.1.0 through 192.168.0.9 Gateway on XP it would work. But NOT.
    >I don't get it why.
    >
    >Here is Windows 2k route map:
    >===========================
    >Active Routes:
    >Network Destination Netmask Gateway Interface Metric
    > 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102 1
    > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    > 192.168.0.0 255.255.255.0 192.168.0.102 192.168.0.102 1
    > 192.168.0.102 255.255.255.255 127.0.0.1 127.0.0.1 1
    > 192.168.0.255 255.255.255.255 192.168.0.102 192.168.0.102 1
    > 192.168.1.0 255.255.255.0 192.168.0.9 192.168.0.102 1
    > 224.0.0.0 224.0.0.0 192.168.0.102 192.168.0.102 1
    > 255.255.255.255 255.255.255.255 192.168.0.102 192.168.0.102 1
    >Default Gateway: 192.168.0.1
    >================================================= ==========================
    >Persistent Routes:
    > Network Address Netmask Gateway Address Metric
    > 192.168.1.0 255.255.255.0 192.168.0.9 1
    >
    >
    >and here WindowsXP route map:
    >============================
    >Active Routes:
    >Network Destination Netmask Gateway Interface Metric
    > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    > 192.168.0.0 255.255.255.0 192.168.0.9 192.168.0.9 4
    > 192.168.0.9 255.255.255.255 127.0.0.1 127.0.0.1 4
    > 192.168.0.255 255.255.255.255 192.168.0.9 192.168.0.9 4
    > 192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 2
    > 192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 2
    > 192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 2
    > 224.0.0.0 240.0.0.0 192.168.0.9 192.168.0.9 4
    > 224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 2
    > 255.255.255.255 255.255.255.255 192.168.0.9 192.168.0.9 1
    > 255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
    >================================================= ==========================
    >Persistent Routes:
    > Network Address Netmask Gateway Address Metric
    > 192.168.1.0 255.255.255.0 192.168.1.5 2
    >
    >any ideas?
    >thanks
    There should be no need for you to add a route to Windows XP. Since
    it has a NIC in each network, it knows how to reach each network.

    Pinging is a two-way communication: each computer (the source and the
    destination) needs a route to the other one.

    When you ping Linux (192.168.1.3) from Win2K (192.168.0.102), Win2K
    looks in its route table for a route to 192.168.1.x. It doesn't find
    one, so it sends the packets to the default gateway, which is the
    WinXP computer (192.168.0.1). XP, which has routes to both networks
    and has IP forwarding enabled, sends the packets to Linux.

    My guess is that Linux doesn't have a default gateway pointing back to
    WinXP. Without that, it doesn't know how to send packets to
    192.168.0.102, so it drops them. It's also possible that a firewall
    on Linux is blocking access.
    --
    Best Wishes,
    Steve Winograd, MS-MVP (Windows Networking)

    Please post any reply as a follow-up message in the news group
    for everyone to see. I'm sorry, but I don't answer questions
    addressed directly to me in E-mail or news groups.

    Microsoft Most Valuable Professional Program
    [url]http://mvp.support.microsoft.com[/url]
    Steve Winograd [MVP] Guest

  3. #3

    Default Re: routing problem

    (sorry Steve, I sent you email by mistake)

    Thats what I suspected, but I can ping to both NICs on WinXP from LINUX,
    but cannot ping 192.168.0.102 on Windows2k, which is weird if I can ping
    192.168.0.9 (1st NIC on XP)
    this is the same network, and from XP is no problem.

    here is the LINUX routing table
    =============================
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    192.168.0.0 192.168.1.5 255.255.255.255 UGH 0 0 0 eth0
    192.168.1.0 0.0.0.0 255.255.255.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 eth0


    thanks

    "Steve Winograd [MVP]" <winogradpobox.com> wrote in message
    news:93dngvk9fdj6qco0fmnphv999c4onq5lq34ax.com...
    > In article <uBHNgJcRDHA.560TK2MSFTNGP10.phx.gbl>, "cyborg"
    > <kc2ine> wrote:
    > >Hi All,
    > >details of my network:
    > >========================
    > >WindowsXP:
    > >first NIC(wireless) ->192.168.0.9 (static)
    > >second NIC ->192.168.1.5 (static)
    > >IPEnableRouter = 1 (yes)
    > >(not using bridge)
    > >
    > >Linux:
    > >IP 192.168.1.3
    > >
    > >Windows2k:
    > >IP 192.168.0.102 (from DHCP from wireless router)
    > >
    > >connections:
    > >======================================
    > >Windows2k -> wireless router-> WindowsXP <- Linux
    > >========================================
    > >problem:
    > >I can ping from Win2k to WindowsXP both NICs, but I can't to Linux.
    > >I can ping from WindowsXP to Linux, so I thought if I add route
    > >192.168.1.0 through 192.168.0.9 Gateway on XP it would work. But NOT.
    > >I don't get it why.
    > >
    > >Here is Windows 2k route map:
    > >===========================
    > >Active Routes:
    > >Network Destination Netmask Gateway Interface
    Metric
    > > 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102
    1
    > > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
    1
    > > 192.168.0.0 255.255.255.0 192.168.0.102 192.168.0.102
    1
    > > 192.168.0.102 255.255.255.255 127.0.0.1 127.0.0.1
    1
    > > 192.168.0.255 255.255.255.255 192.168.0.102 192.168.0.102
    1
    > > 192.168.1.0 255.255.255.0 192.168.0.9 192.168.0.102
    1
    > > 224.0.0.0 224.0.0.0 192.168.0.102 192.168.0.102
    1
    > > 255.255.255.255 255.255.255.255 192.168.0.102 192.168.0.102
    1
    > >Default Gateway: 192.168.0.1
    >
    >================================================= ==========================
    > >Persistent Routes:
    > > Network Address Netmask Gateway Address Metric
    > > 192.168.1.0 255.255.255.0 192.168.0.9 1
    > >
    > >
    > >and here WindowsXP route map:
    > >============================
    > >Active Routes:
    > >Network Destination Netmask Gateway Interface
    Metric
    > > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    > > 192.168.0.0 255.255.255.0 192.168.0.9 192.168.0.9 4
    > > 192.168.0.9 255.255.255.255 127.0.0.1 127.0.0.1 4
    > > 192.168.0.255 255.255.255.255 192.168.0.9 192.168.0.9 4
    > > 192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 2
    > > 192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 2
    > > 192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 2
    > > 224.0.0.0 240.0.0.0 192.168.0.9 192.168.0.9 4
    > > 224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 2
    > > 255.255.255.255 255.255.255.255 192.168.0.9 192.168.0.9 1
    > > 255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
    >
    >================================================= ==========================
    > >Persistent Routes:
    > > Network Address Netmask Gateway Address Metric
    > > 192.168.1.0 255.255.255.0 192.168.1.5 2
    > >
    > >any ideas?
    > >thanks
    >
    > There should be no need for you to add a route to Windows XP. Since
    > it has a NIC in each network, it knows how to reach each network.
    >
    > Pinging is a two-way communication: each computer (the source and the
    > destination) needs a route to the other one.
    >
    > When you ping Linux (192.168.1.3) from Win2K (192.168.0.102), Win2K
    > looks in its route table for a route to 192.168.1.x. It doesn't find
    > one, so it sends the packets to the default gateway, which is the
    > WinXP computer (192.168.0.1). XP, which has routes to both networks
    > and has IP forwarding enabled, sends the packets to Linux.
    >
    > My guess is that Linux doesn't have a default gateway pointing back to
    > WinXP. Without that, it doesn't know how to send packets to
    > 192.168.0.102, so it drops them. It's also possible that a firewall
    > on Linux is blocking access.
    > --
    > Best Wishes,
    > Steve Winograd, MS-MVP (Windows Networking)
    >
    > Please post any reply as a follow-up message in the news group
    > for everyone to see. I'm sorry, but I don't answer questions
    > addressed directly to me in E-mail or news groups.
    >
    > Microsoft Most Valuable Professional Program
    > [url]http://mvp.support.microsoft.com[/url]

    cyborg Guest

  4. #4

    Default Re: routing problem

    I got it , its working. All I need was add route on unix.

    "Steve Winograd [MVP]" <winogradpobox.com> wrote in message
    news:93dngvk9fdj6qco0fmnphv999c4onq5lq34ax.com...
    > In article <uBHNgJcRDHA.560TK2MSFTNGP10.phx.gbl>, "cyborg"
    > <kc2ine> wrote:
    > >Hi All,
    > >details of my network:
    > >========================
    > >WindowsXP:
    > >first NIC(wireless) ->192.168.0.9 (static)
    > >second NIC ->192.168.1.5 (static)
    > >IPEnableRouter = 1 (yes)
    > >(not using bridge)
    > >
    > >Linux:
    > >IP 192.168.1.3
    > >
    > >Windows2k:
    > >IP 192.168.0.102 (from DHCP from wireless router)
    > >
    > >connections:
    > >======================================
    > >Windows2k -> wireless router-> WindowsXP <- Linux
    > >========================================
    > >problem:
    > >I can ping from Win2k to WindowsXP both NICs, but I can't to Linux.
    > >I can ping from WindowsXP to Linux, so I thought if I add route
    > >192.168.1.0 through 192.168.0.9 Gateway on XP it would work. But NOT.
    > >I don't get it why.
    > >
    > >Here is Windows 2k route map:
    > >===========================
    > >Active Routes:
    > >Network Destination Netmask Gateway Interface
    Metric
    > > 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102
    1
    > > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
    1
    > > 192.168.0.0 255.255.255.0 192.168.0.102 192.168.0.102
    1
    > > 192.168.0.102 255.255.255.255 127.0.0.1 127.0.0.1
    1
    > > 192.168.0.255 255.255.255.255 192.168.0.102 192.168.0.102
    1
    > > 192.168.1.0 255.255.255.0 192.168.0.9 192.168.0.102
    1
    > > 224.0.0.0 224.0.0.0 192.168.0.102 192.168.0.102
    1
    > > 255.255.255.255 255.255.255.255 192.168.0.102 192.168.0.102
    1
    > >Default Gateway: 192.168.0.1
    >
    >================================================= ==========================
    > >Persistent Routes:
    > > Network Address Netmask Gateway Address Metric
    > > 192.168.1.0 255.255.255.0 192.168.0.9 1
    > >
    > >
    > >and here WindowsXP route map:
    > >============================
    > >Active Routes:
    > >Network Destination Netmask Gateway Interface
    Metric
    > > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    > > 192.168.0.0 255.255.255.0 192.168.0.9 192.168.0.9 4
    > > 192.168.0.9 255.255.255.255 127.0.0.1 127.0.0.1 4
    > > 192.168.0.255 255.255.255.255 192.168.0.9 192.168.0.9 4
    > > 192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 2
    > > 192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 2
    > > 192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 2
    > > 224.0.0.0 240.0.0.0 192.168.0.9 192.168.0.9 4
    > > 224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 2
    > > 255.255.255.255 255.255.255.255 192.168.0.9 192.168.0.9 1
    > > 255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
    >
    >================================================= ==========================
    > >Persistent Routes:
    > > Network Address Netmask Gateway Address Metric
    > > 192.168.1.0 255.255.255.0 192.168.1.5 2
    > >
    > >any ideas?
    > >thanks
    >
    > There should be no need for you to add a route to Windows XP. Since
    > it has a NIC in each network, it knows how to reach each network.
    >
    > Pinging is a two-way communication: each computer (the source and the
    > destination) needs a route to the other one.
    >
    > When you ping Linux (192.168.1.3) from Win2K (192.168.0.102), Win2K
    > looks in its route table for a route to 192.168.1.x. It doesn't find
    > one, so it sends the packets to the default gateway, which is the
    > WinXP computer (192.168.0.1). XP, which has routes to both networks
    > and has IP forwarding enabled, sends the packets to Linux.
    >
    > My guess is that Linux doesn't have a default gateway pointing back to
    > WinXP. Without that, it doesn't know how to send packets to
    > 192.168.0.102, so it drops them. It's also possible that a firewall
    > on Linux is blocking access.
    > --
    > Best Wishes,
    > Steve Winograd, MS-MVP (Windows Networking)
    >
    > Please post any reply as a follow-up message in the news group
    > for everyone to see. I'm sorry, but I don't answer questions
    > addressed directly to me in E-mail or news groups.
    >
    > Microsoft Most Valuable Professional Program
    > [url]http://mvp.support.microsoft.com[/url]

    cyborg Guest

  5. #5

    Default Routing problem

    Hi,

    I'm trying to use Linux as a small router but it is probably not my day :)
    this is the configuration I have:

    +------+
    | O |
    +------+
    |172.17.2.3
    |
    |
    |172.17.2.30 Masquerade t this interface
    +--------------+
    | A - Linux |
    +--------------+
    |172.16.0.1
    |
    |
    +------+172.16.0.2 | 172.16.0.10+------+172.30.0.1 172.30.0.10+------+
    | B |--------------------------| C |--------------------------| D |
    +------+ 255.255.0.0 +------+ 255.255.0.0 +------+

    interface I have:
    eth0 Link encap:Ethernet HWaddr 00:E0:72:A0:03:1F
    inet addr:172.17.2.30 Bcast:172.17.255.255 Mask:255.255.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:821 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:75201 (73.4 kiB) TX bytes:1306 (1.2 kiB)
    Base address:0x8500

    eth1 Link encap:Ethernet HWaddr 00:E0:72:A0:03:10
    inet addr:172.16.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:58 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:9209 (8.9 kiB) TX bytes:0 (0.0 iB)
    Base address:0x8400

    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:283 errors:0 dropped:0 overruns:0 frame:0
    TX packets:283 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:82004 (80.0 kiB) TX bytes:82004 (80.0 kiB)


    this is the perliminary routing table I had:
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt Iface
    172.16.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth1
    172.17.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth0
    0.0.0.0 172.17.1.10 0.0.0.0 UG 40 0 0 eth0

    I add the next route:
    route add -net 172.30.0.0 netmask 255.255.0.0 gw 172.16.0.10

    so now I have the next routing table:
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt Iface
    172.30.0.0 172.16.0.10 255.255.0.0 UG 40 0 0 eth1
    172.16.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth1
    172.17.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth0
    0.0.0.0 172.17.1.10 0.0.0.0 UG 40 0 0 eth0


    Connection test using ping:
    A --> loopbak : OK
    A --> O : OK
    A --> B : OK
    A --> C : OK
    A --> D : OK
    -
    C --> *All* : OK
    -
    B --> A : OK
    B --> O : OK
    B --> C(172.16.0.10) : OK
    B --> C(172.30.0.1) : Fail
    B --> D : Fail

    1. The default router for B is A.
    2. All the stations except A are Win2K/Win9X


    Any idea what I should do so that B can get to D?

    Best Regards

    Yehoram Ben-Yaacov
    [email]ybenboscom.com[/email]
    Yehoram B.Y. Guest

  6. #6

    Default Re: Routing problem

    On 9 Sep 2003 05:14:39 -0700, Yehoram B.Y.
    <ybenboscom.com> wrote:
    >
    >
    > Any idea what I should do so that B can get to D?
    >
    route add -net 172.30.0.0 netmask 255.255.0.0 gw 172.16.0.10
    on B.


    --
    Commander Spiral Pyjama Pseudo-Rhinocerous Feline Thingamajig Bill Mar
    (the First)
    Ozy and Millie Name Generator [url]http://heifong.phase.org/omname.php[/url]
    Bill Marcum Guest

Similar Threads

  1. Complicated Routing problem
    By Andy Holyer in forum Linux / Unix Administration
    Replies: 12
    Last Post: September 13th, 03:11 PM
  2. Routing
    By Dave McDuell in forum Windows Server
    Replies: 1
    Last Post: June 28th, 07:24 PM
  3. Help on routing
    By Martin Jeppesen in forum Linux / Unix Administration
    Replies: 0
    Last Post: October 15th, 02:24 AM
  4. MDK 9.1: Is it a routing problem?
    By Michael Badt in forum Linux Setup, Configuration & Administration
    Replies: 0
    Last Post: September 14th, 07:07 PM
  5. Problem with PCI-IRQ routing
    By Pigeon in forum Debian
    Replies: 0
    Last Post: August 4th, 01:30 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139