Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[network1027]

Hi 

while I have no problem routing IPv6 or IPv4 with chained-up routers :

CPE----------Router1--------------Router2-----------Router3-----------PC1

just adding static IPv6 routes to the subnets,

the IPv4 connection fails if I insert a routing Windows OS :

CPE--------Router1---------------OS Router-----------Router3-----------PC1

the IPv6 connection works OK.

I think it may be a problem related to NAT. Can somebody explain this ? ( I'm too used to IPv6 and have my NAT skills fading away ).

I noticed on the DIR-626L, IPv4 routing only allows 'Wan' as an interface ( where IPv6 routing allows either Wan or Lan ). Is this related to this NAT problem ?

I guess you need a Windows Server to implement NAT on a Windows OS.
Still I have a hrd time understanding why my setup fails, just using ' Netsh int ipv6 set int x forward=enable ' on both OS Router interfaces + adding routes everywhere ?

Another question, can IPv4 NAT be disabled on a DIR626L ?

Thanks for any help 

[FurryNutz]

Link>Double NAT and How NAT Works.

IPv4 is the base foundation for most networking so I presume that IPv4 can't be disabled on these routers. Even when I did some Ipv6 years ago with Server 2003, IPv4 was still needed. Not sure when IPv4 can work will be designed to be disabled if IPv6 is all inclusive and becomes the primary foundation. 

Just curious why are you putting in a in between routes? Is this a Server class OS?

[PacketTracer]

Hi,

activation of IPv4 routing depends on Windows OS type: With a server OS you have to activate "Routing and RAS" service (which also allows to define NAT, if you want), while on Client OS (as far as I know) you have to do a registry hack to activate IPv4 routing:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

Set the DWORD entry "IPEnableRouter" to 1 (default is 0).

After a reboot "ipconfig /all" should show IP routing being enabled.

<EDIT>
But if you chose to configure OS Router for only being an IPv4 router without NAT and given that Router 1 and Router 3 do IPv4-NAT you would have to configure a static IPv4 route on Router 1 for the network between OS Router and Router 3. As this is not possible because you cannot select the LAN interface for the route (a "bug" I also know from my DIR-825) you have to configure OS Router for also doing IPv4 NAT because in this case (triple NAT) you don't have to configure IPv4 routes at all (except the next NAT (ISP for the last NAT) in outgoing direction beeing the default gateway for the previous NAT/PC1). So OS Router has to be a Windows Server or you have to use a third party NAT solution if OS Router is a Windows Client OS only.
</EDIT>

[network1027]

Link>Double NAT and How NAT Works.

IPv4 is the base foundation for most networking so I presume that IPv4 can't be disabled on these routers. Even when I did some Ipv6 years ago with Server 2003, IPv4 was still needed. Not sure when IPv4 can work will be designed to be disabled if IPv6 is all inclusive and becomes the primary foundation. 

Just curious why are you putting in a in between routes? Is this a Server class OS?

hi 

Thanks for the link about double NAT

Oh, my question was not about disabling IPv4 but about disabling NAT on the DIR626L, just out of curiosity ...

The Routing OS is a Windows Server 2008 R2. It's here because about what we are discussing with packettracer, understanding the DIR626L IPv6 FIrewall. But this task doesn't require a server OS, any windows would do this job fine. I only used it because it has several networks cards in.

The real reason I'm using WS2008R2 is I'm practicing my skills about IPv6/Windows Server and Windows Server network related functions : Firewall, Routing, DHCP, DNS, ...

[network1027]

Hi,

activation of IPv4 routing depends on Windows OS type: With a server OS you have to activate "Routing and RAS" service (which also allows to define NAT, if you want), while on Client OS (as far as I know) you have to do a registry hack to activate IPv4 routing:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

Set the DWORD entry "IPEnableRouter" to 1 (default is 0).

After a reboot "ipconfig /all" should show IP routing being enabled.

<EDIT>
But if you chose to configure OS Router for only being an IPv4 router without NAT and given that Router 1 and Router 3 do IPv4-NAT you would have to configure a static IPv4 route on Router 1 for the network between OS Router and Router 3. As this is not possible because you cannot select the LAN interface for the route (a "bug" I also know from my DIR-825) you have to configure OS Router for also doing IPv4 NAT because in this case (triple NAT) you don't have to configure IPv4 routes at all (except the next NAT (ISP for the last NAT) in outgoing direction beeing the default gateway for the previous NAT/PC1). So OS Router has to be a Windows Server or you have to use a third party NAT solution if OS Router is a Windows Client OS only.
</EDIT>

Hi Packettracer  

Oh, so if I get you right :

CPE------------Router1---------------OS Router-----------Router3-----------PC1
      192.168.1.0             192.168.2.0                192.168.3.0           192.168.4.0

IPv4 could function, if I could set Router 1 to have a route to subnet 192.168.3.0 using its LAN interface.
The thing would work . ( But unfortunately, no IPv4 Lan Routing on 626L/825L ).
Did I get it right ?

That was what I was kinda suspecting, as I couldn't figure out why my Routing OS would break the thing.

The other solution being to use RRAS with NAT, this I know.


Just two questions :

" HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

Set the DWORD entry "IPEnableRouter" to 1 (default is 0).

After a reboot "ipconfig /all" should show IP routing being enabled.

Does this do NAT too ?   Because if it doesn't, I've got an easier solution :
netsh int ipv4 set int [Idx1] forwarding=enable
netsh int ipv4 set int [Idx2] forwarding=enable

I re-tested it on a Windows 7 Home Premium, and it does the forwarding job OK. ( But no NAT )

Question 2 : Internet Connection Sharing on a Windows Client OS is doing what ? Bridging or NAT ?

Thanks for having helped me clear this thing out  

[PacketTracer]

Hello network1027,

Oh, so if I get you right :

CPE------------Router1---------------OS Router-----------Router3-----------PC1
      192.168.1.0             192.168.2.0                192.168.3.0           192.168.4.0

IPv4 could function, if I could set Router 1 to have a route to subnet 192.168.3.0 using its LAN interface.
The thing would work . ( But unfortunately, no IPv4 Lan Routing on 626L/825L ).
Did I get it right ?

That's what I meant, given OS router works as a pure IPv4 router w/o NAT sitting between the two NAT routers Router1 and Router3.

Does this do NAT too ?

No.

Because if it doesn't, I've got an easier solution :
netsh int ipv4 set int [Idx1] forwarding=enable
netsh int ipv4 set int [Idx2] forwarding=enable

Yes, triggered by your original question I have discovered this either. If this produces the desired result, of course this is the better solution. I'm surprised that netsh obviously offers almost the same set of interface commands for IPv4 as for IPv6. So far I have only worked with "netsh int ipv6" because most IPv4 configurations in Windows can be done with a GUI (in contrast to IPv6).

Question 2 : Internet Connection Sharing on a Windows Client OS is doing what ? Bridging or NAT ?

Not sure because I never tested ICS. But according to this the ICS server should operate as a NAT router (somewhere else I read that for ICS to work you have to use 192.168.0.0/24 inside your LAN, where ICS server uses 192.168.0.1 and runs a DHCP server to provide ICS clients with addresses within 192.168.0.2-254).

[FurryNutz]

I don't think there is any way of disabling NAT on these routers unless your turn them in to a wired AP and only connect the router via LAN to LAN.

Yes, I'm familiar with 2008 Server. It was what I used when I went to school of IPv6 years back. Good OS.

I actually used 2003 as a server at a place I worked for IPv6 support. I had a good time working with it.

Keep us posted and thank you for sharing the experiences and information.

hi 

Thanks for the link about double NAT

Oh, my question was not about disabling IPv4 but about disabling NAT on the DIR626L, just out of curiosity ...

The Routing OS is a Windows Server 2008 R2. It's here because about what we are discussing with packettracer, understanding the DIR626L IPv6 FIrewall. But this task doesn't require a server OS, any windows would do this job fine. I only used it because it has several networks cards in.

The real reason I'm using WS2008R2 is I'm practicing my skills about IPv6/Windows Server and Windows Server network related functions : Firewall, Routing, DHCP, DNS, ...