IP Routing with a subnet and internet

This is regarding 2 Computers with windows XP Pro with SP2 installed on both computers.
I been reading and looking for 2 weeks now, and with the 8 hrs I tried
today after work, I believe I am stuck! I need help Everyone!

I am basically trying to get PC1 to ping www.yahoo.com through this
connection layout:
PC1(NIC1) -> HUB -> PC2(NIC2) -> PC2(NIC3) -> cable modem -> www.yahoo.com


This is the setting I had so far. I cannot even get IPv4 to work.

-- PC1 (NIC1) --
IP address: 10.1.1.11
Subnet mask: 255.255.255.0
Default gateway: 10.1.1.1

-- PC2 (NIC2) --
IP address: 10.1.1.1
Subnet Mask: 255.255.255.0
Default gateway: empty

-- PC2 (NIC3) --
IP address: 192.168.1.148
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.1

-- cable modem --
IP address: 192.168.1.1

I already did the following 2 things as well on PC2:
1) changed the IPEnableRouter register to enable in windows XP
2) I even tried to add a IP route into window XP routing Table:
route -p add 192.0.0.0 mask 255.0.0.0 10.1.1.0 metric 2

Please help. Thanks

 

Hi gilee

Welcome to the BBS!

What in the world are you trying to do? Two different subnets?

Are these the only 2 computers on the LAN or are they on a larger network and you are just dealing with these 2?

Do the below on pc1

Drag mouse to highlight the ipconfig line below then rt click and copy

ipconfig /all > "%USERPROFILE% "\Desktop\pc1ipcfg.txt

Next

Start-Run
type
cmd
click OK to open CMD prompt

Left click in CMD prompt and rt click and paste then hit enter.
close cmd prompt.

There is now a pc1ipcfg.txt file on desktop. Open copy the contents and paste back to this thread.

Now do the exact same on pc2 with the below line and paste back here also.

ipconfig /all > "%USERPROFILE% "\Desktop\pc2ipcfg.txt

Mike

 

Hello, I kinda figure people might ask why in the world I am doing what I am trying to do here.
It is a VERY long story, but let me give you a short summary of it so you understand why.
This is a setup I am trying to do for my Thesis for master Degree, and I have to setup the network in this form so I can continue further into my project and complete my degree. So in a big picture, I am setting up an entire local network with two computers. PC1 and PC2. They both are collected with a HUB (I pick HUB before I intentionally don't want any intelligents/smartness to it) PC1 has only 1 NIC which connects to the HUB. PC2 has 2 NIC, one to the HUB and one to the cable modem (to the internet). What I am trying to do is, on PC1, I tries to ping a website on the WWW using IPv6. So PC1 NIC1 ping PC2 NIC2 thought the hub, then the ping will get routed to PC2 NIC3 to the WWW ..on and on...

I tried over 2 weeks reading and reasearching but still no luck in this problem. So please help.

Here are the information for PC1 and PC2. I hope this will helps. They are obtained by ipconfig /all > "%USERPROFILE% "\Desktop\pc1ipcfg.txt for both PC1 and PC2.

======= PC1 (tester1) ========
Windows IP Configuration
Host Name . . . . . . . . . . . . : tester1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/100 VE Desktop Connection
Physical Address. . . . . . . . . : 00-02-55-7F-E7-7D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::202:55ff:fe7f:e77d%4
Default Gateway . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 0A-01-01-0B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.11%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled


======= PC2 (tester2) ========
Windows IP Configuration
Host Name . . . . . . . . . . . . : tester2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-C0-CA-19-A3-28
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.148
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2c0:caff:fe19:a328%4
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Saturday, August 30, 2008 8:27:34 PM
Lease Expires . . . . . . . . . . : Sunday, August 31, 2008 8:27:34 PM

Ethernet adapter Local Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/100 VE Desktop Connection
Physical Address. . . . . . . . . : 00-02-55-3F-4E-F4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::202:55ff:fe3f:4ef4%5
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-01-94
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.148%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 0A-01-01-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.1%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled

 

Geeze

Ok so lets see what does work

On tester1

ping tester2 > "%USERPROFILE% "\Desktop\t1pingt2.txt
ping 192.168.1.148 >> "%USERPROFILE% "\Desktop\t1pingt2.txt
ping 192.168.1.1 >> "%USERPROFILE% "\Desktop\t1pingt2.txt
ping yahoo.com >> "%USERPROFILE% "\Desktop\t1pingt2.txt


On tester2

ping tester1 > "%USERPROFILE% "\Desktop\t2pingt1.txt
ping 10.1.1.11 >> "%USERPROFILE% "\Desktop\t2pingt1.txt
ping 10.1.1.1 >> "%USERPROFILE% "\Desktop\t2pingt1.txt
ping yahoo.com >> "%USERPROFILE% "\Desktop\t2pingt1.txt

Get me the above info, you can paste all 4 lines at once if you want.

Mike

 

Hi gilee

My last post showed you the error of your ways huh?

But just confirm it here so we can close this thread!

Mike

 

Hi gilee

My last post showed you the error of your ways huh?

But just confirm it here so we can close this thread!

Mike

 

no solution yet!

hi mike sorry for late reply! I went down to nyc for a wedding so I don't the system with me!! I will get the info and post it here tonight again ! thx again!

 

Sorry for the wait Mike.

Hi mike, here are the results from both PC1(tester1) & PC2(tester2)
Obtained by typing in the following into CMD:
ping tester2 > "%USERPROFILE% "\Desktop\t1pingt2.txt
ping 192.168.1.148 >> "%USERPROFILE% "\Desktop\t1pingt2.txt
ping 192.168.1.1 >> "%USERPROFILE% "\Desktop\t1pingt2.txt
ping yahoo.com >> "%USERPROFILE% "\Desktop\t1pingt2.txt

=========== Ping From Tester1 ============
Pinging tester2 [10.1.1.1] with 32 bytes of data:
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Ping statistics for 10.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.148 with 32 bytes of data:
Reply from 192.168.1.148: bytes=32 time<1ms TTL=128
Reply from 192.168.1.148: bytes=32 time<1ms TTL=128
Reply from 192.168.1.148: bytes=32 time<1ms TTL=128
Reply from 192.168.1.148: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping request could not find host www.yahoo.com. Please check the name and try again.


=========== Ping From Tester2============
Pinging tester1 [10.1.1.11] with 32 bytes of data:
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Ping statistics for 10.1.1.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 10.1.1.11 with 32 bytes of data:
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
Ping statistics for 10.1.1.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 10.1.1.1 with 32 bytes of data:
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Reply from 10.1.1.1: bytes=32 time<1ms TTL=128
Ping statistics for 10.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging www.yahoo-ht3.akadns.net [69.147.76.15] with 32 bytes of data:
Reply from 69.147.76.15: bytes=32 time=20ms TTL=50
Reply from 69.147.76.15: bytes=32 time=18ms TTL=50
Reply from 69.147.76.15: bytes=32 time=18ms TTL=50
Reply from 69.147.76.15: bytes=32 time=17ms TTL=50
Ping statistics for 69.147.76.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 20ms, Average = 18ms

Let me know if you need any other information from me.
Thanks again for your help.
I Greatly appreciated!

 

I think the problem is that the cable modem/router doesn't know where to forward packets that are destined for the 10.1.1.0 network. Therefore, when it receives ping requests from that network, it can't reply. Also when response come back from the internet, it cannot forward those.

You need to add a static route to the router (it's labelled as a modem, but in this network it is acting as a router) at 192.168.1.1. That static route should be something like this:

Destination Address: 10.1.1.0
Mask: 255.255.255.0
Gateway: 192.168.1.148
Interface: 192.168.1.1

You may also have to modify your NAT, but see if it works without any modification.

 

My routing table on PC2.

Hello ReggieB,
I am not sure what you mean by adding a direct route to the router?
Do you mean adding a route into the route table on PC2? or you mean directly on to the cable modem (router) that my PC2 connects to that provide me internet access?

As post #1, I already did the following to PC2 route table (added 3 Persistent Routes to the route table).
I did it by: route -p add 192.0.0.0 mask 255.0.0.0 10.1.1.0 metric 2
I even added 3 other route just incase I missed something.

Edit: Sorry, the table looks horrible, but since the forum strips out all the spaces, I have to replace them with underscores. Hope they help

Here are the print out of my: route print (on PC2/tester2)
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 c0 ca 19 a3 28 ...... Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
0x3 ...00 02 55 3f 4e f4 ...... Intel® PRO/100 VE Desktop Connection - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination________Netmask_______Gateway_____ Interface_____Metric
_________0.0.0.0___________0.0.0.0______192.168.1.1__ 192.168.1.148 ____20
________ 10.0.0.0_________255.0.0.0_____192.168.1.0__ 192.168.1.148 ____2
________ 10.1.1.0_____255.255.255.0_______ 10.1.1.1________10.1.1.1 ____20
________ 10.1.1.1___255.255.255.255_______127.0.0.1______ 127.0.0.1 ____20
__ 10.255.255.255___255.255.255.255_______ 10.1.1.1________10.1.1.1 ____20
_______127.0.0.0_________255.0.0.0________127.0.0.1______ 127.0.0.1 ____1
_______192.0.0.0_________255.0.0.0________ 10.1.1.0________10.1.1.1 ____2
_______192.0.0.0_________255.0.0.0________ 10.1.1.4________10.1.1.1 ____2
_____192.168.1.0_____255.255.255.0____192.168.1.148__ 192.168.1.148 ____20
___192.168.1.148___255.255.255.255________127.0.0.1______ 127.0.0.1 ____20
___192.168.1.255___255.255.255.255____192.168.1.148__ 192.168.1.148 ____20
_______224.0.0.0_________240.0.0.0________ 10.1.1.1________10.1.1.1 ____20
_______224.0.0.0_________240.0.0.0____192.168.1.148__ 192.168.1.148 ____20
_255.255.255.255___255.255.255.255________ 10.1.1.1________10.1.1.1 ____1
_255.255.255.255___255.255.255.255____192.168.1.148__ 192.168.1.148 ____1
Default Gateway:_______ 192.168.1.1
===========================================================================
Persistent Routes:
__Network Address______Netmask__Gateway Address__Metric
______192.0.0.0________255.0.0.0________ 10.1.1.0______ 2
______ 10.0.0.0________255.0.0.0______192.168.1.0______ 2
______192.0.0.0________255.0.0.0________ 10.1.1.4______ 2

 

Trying another way to solve my problem!

Hi guys,
I just thought of using another point of view (different angle) in attacking my problem.
How about I do it this way.
Same configuration of having 2 computers. PC1 (with 1 NIC) & PC2 (with 2 NICs)
Same configuration of PC1(NIC1) <-> HUB <-> PC2 (NIC2) -- PC2 (NIC3) <-> internet
Both PC has windows XP installed with SP2 updated and both PC has Microsoft TCP/IP version 6 installed.

Now I set PC1 NIC1 to "Obtain an IP address automatically" from Internet Protocol (TCP/IP) Properties
I set PC2 NIC2 to "Obtain an IP address automatically" also
Then I set PC2 NIC3 to Internet Connection Sharing Enabled.

Now when I tries to PING from tester1(PC1) to tester2(PC2), it works fine and so does other PING like (from tester1)
PING tester2 (successful)
PING 192.168.1.1 (successful)
PING 192.168.1.148 (successful)
PING www.yahoo.com (successful)

But the reason I chose not to use Internet Connection Sharing features and go for manual IP routing because I cannot get IPv6 to work.
I am trying to capture IPv6 packets (echo) using wireshark on PC1 when I ping www.yahoo.com.
But instead the wireshark on PC1 (tester1) only capture IPv4 packets, so this is clearly show that PC1 used IPv4 to send the PING to PC2 and route to www.yahoo.com for PING.

Can anyone help for providing what setting I can do to PING in IPv6?
Thank you very much!

 

You need to go into the configuration of the modem/router at 192.168.1.1 and add the static route there. What its make and model?

You don't need to add static routes to PC2. It is directly connected to both private networks so will get the right paths automatically. The only extra route it needs is to the outside world - the 0.0.0.0 path. That's your default gateway, so simply setting that on PC2 does all the routing that PC needs.

So I'd suggest you remove those static routes you added to PC2.

 

The router is my housemate's. and it is very old so last month he mentioned about the DDWRT and I flashed it to the latest DD-WRT Router Firmware.

So you saying I do not have to do route add from the PC2 machine?
So instead, I should do the route add in the PC1 machine ... ? am I getting correctly? So how should I set the route in the PC1? can you tell me what I should type? route -p add ??? mask 255.255.255.0 ???

Also i am confused, you mentioned about "simply setting the default gateway on PC2 does all the routing" ???

Can you please provide more details.
Thanks alot!

 

NO! You have to program your mate's router!!

Open up a browser on PC2 and enter http://192.168.1.1 and then enter the admin username and password. I assume you have those if you've updated the router's firmware. Have a browse around the routers config pages, there will be a section where you can add static routes. If you can't find it please tell us the make and model of router and we'll look up a manual for the setting.

You have three subnets in your configuation: between PC1 and PC2 there is 10.1.1.0, between the router and PC2 there is 192.168.1.0, and there is the internet beyond the router which is 0.0.0.0.

Part of the process of connecting a network card to a network is to tell it what subnet it is joining. This is automatically done for you when you apply an IP address to the network card.

PC2 has two network cards, one on each of the subnets: 10.1.1.0 and 192.168.1.0. In setting up those cards you have automatically told PC2 all it needs to know as to how to connect to any PC on those to subnets. The card drivers will automatically add all the routing information required for the subnets it is directly attached to.

So that only leave 0.0.0.0 for PC2 to worry about. 0.0.0.0 is the default route. It is where all packets that do not match any of the other routing rules, is sent. It is in effect almost always the internet. Specifying a Default Gateway in you IP settings tells the system all the information it needs for it to determine and set up the default router.

In summary:
Applying an IP address to the network card on 192.168.1.0 sets up all the routing information for that subnet.
Applying an IP address to the network card on 10.1.1.0 sets up all the routing information for that subnet.
Apply a Default gateway tells the system the path to the 0.0.0.0 network.

So router to all three subnets is sorted for PC2.

In your network, PC2 is by far the simplest PC to set up.

 

Thanks for the details Reggie, I will try that out tonight.
Also I found an interesting site, http://www.berkom.blazing.de/tools/ping.cgi
From there, I am able to ping any website, but I tries to use wireshark to capture the packets when I hit PING on the website, and I didn't capture any ICMPv6 packets, so I guess all the pinging was done from the server side?

 

still no good, I need more clarifications

I found this static routing table in my router and it is the following:
The bold one is what I added into the router after I read the previous post.
Routing Table Entry List
Destination LAN NET__Subnet Mask____Gateway______Interface
_____192.168.1.0____255.255.255.0___0.0.0.0______LAN & WLAN
_____10.1.1.0_______255.255.255.0___0.0.0.0______LAN & WLAN
_____76.15.116.0____255.255.252.0___0.0.0.0______WAN
_____169.254.0.0____255.255.0.0_____0.0.0.0______LAN & WLAN
_____0.0.0.0________0.0.0.0_________76.15.116.1__WAN

After adding the above route to the routing table in the router (which the PC2 NIC connect to) I still have no luck getting PC1 to ping www.yahoo.com.
I removed all the previous route add to both PC1 and PC2 already as well.

 

Gateway!

 

Sorry for the frustration... No good.

Hi reggie,
Thanks for being patient and helping me.
I really don't understand what I did wrong ... lacking some info still?
I just went into the router and added the correct static routing in the advanced Routing to:
Metric 2
Destination LAN NET 10.1.1.0
Subnet Mask 255.255.255.0
Gateway 192.168.1.148
Interface LAN/WLAN (I cannot change this specifically to 192.168.1.1)

After saving, I tried the PINGING on PC1 (tester1)
PING 10.1.1.1 (works)
PING 192.168.1.148 (works)
PING 192.168.1.1 (timed out)
PING 69.147.76.15 (yahoo.com timed out)

Since now on the router I added a static route that route the traffic from my PC2 NIC (192.168.1.148) to the other subnet (PC1 & PC2 connection) So the outside world (internet) should be able to connect to my PC1 correct?
I am just wondering do I need to set up any route on PC1 or PC2 using route add command?? As of now, I removed all Persistent Routes from both PC.

Thanks again!
I greatly appreciated your help!

 

With the gateway set as 0.0.0.0 you were effectively saying that the way to the 10.1.1.0 subnet was via the internet. You needed to set the gateway to 192.168.1.148 to tell the router that it needed to send packets to the 10.1.1.0 via 192.168.1.148.

The only static route you need on a PC, is on PC1 if you want PC1 to be able to directly communicate with nodes on the 192.168.1.0 network. If that is the case you'll need to add a route to PC1. This command run on PC1 will do that for you:

Code:

route ADD 192.168.1.0 MASK 255.255.255.0 10.1.1.1

The first address and the mask tell the system the range of IP addresses accessible via the given route (192.168.1.0 to 192.168.1.255). The final IP address defines the gateway, which tell the system where to route traffic destined for the 192.168.1.0/255.255.255.0 IP address space.

 

Gateway 192.168.1.148...

As you said, "you need to set the gateway to 192.168.1.148 to tell router that it needs to send packets to the 10.1.1.0 via 192.168.1.148 "

But as I stated, I added the following route right into my router.
Routing to:
Metric 2
Destination LAN NET 10.1.1.0
Subnet Mask 255.255.255.0
Gateway 192.168.1.148
Interface LAN/WLAN (I cannot change this specifically to 192.168.1.1)

So I already added it into the router, but still no good.

I will try about adding the other route into PC1 and see if that helps.