I’m trying to set up the LAN side of my network. I’m on eth3 and have DHCP setup issuing 10.10.1.0 addresses. My client can get an address no problem. eth3 has address 10.10.1.1 which is my gateway.
My client cannot ping the gateway. Pinging 10.10.1.1 from my workstation times out. I have a Route that says 10.10.1.0 has a gateway of eth3.
Any suggestion on what I could be missing here?
10.10.1.0 is network, not gateway
Route gateway must be 10.10.1.1
It is impossible to say without more info. It could be a firewall on the unspecified router.
post your config as an export in a </> code block. Remove your S/N and any public ip addresses, but leave the private 10.10.1.x addresses.
This post has more info on how to export and upload, and the next post has a properly posted config
Are you sure you are not missing a /24 at the end of address in the /ip address entry for ether3?
Otherwise, post your redacted configuration as instructed by @Buckeye.
When I use /export is doesn’t seem to include the routes. How do I include my routes in the export?
Not necessarily.
ISP I use for my customer always as .254 as gateway address.
It only includes manually configured routes, not dynamic ones.
Terminal
/ip route print
copy and paste back here.
Ding, ding, ding, we have an answer. I added a route to include 10.10.1.0/24 to LAN3 and I can now ping. I’m wondering why I need both the DAC 10.10.1.0 LAN3 and the AS 10.10.1.0/24?
Check your IP address assignment.
If it has /24 as suggested by CGGXANNX, ROS will automatically create a route for everything going to 10.10.1.0/24 towards ether3.
And then you only keep that DAC entry (which is created automatically anyhow), no need for that static entry.
When you don't set a prefix length for the address entry under /ip address, then the prefix length is assumed to be /32.
Normally when you add an entry like this:
/ip address
add interface=intf address=a.b.c.d/n network=x.y.z.w
The interface intf will have the IP address a.b.c.d assigned AND under /ip route you'll see a dynamic connected route (with D and C flag) added with dst-address=x.y.z.w/n and gateway=intf.
So if you do this:
/ip address
add interface=bridge address=10.10.1.1 network=10.10.1.0
because you don't specify the prefix length /n it's implicit /32. As a result the interface bridge has the address 10.10.1.1 but the route added is only
/ip route
add dst-address=10.10.1.0/32 gateway=bridge distance=0 scope=10 target-scope=5
Which means the router only has the connected route to a single address, 10.10.1.0/32. That route entry cannot be used to reach a 10.10.1.15 host in LAN. To reach 10.10.1.15 the default route 0.0.0.0/0 will be used, which usually means going out to the internet. So when 10.10.1.15 pings 10.10.1.1, the ICMP reply packet is sent out towards WAN.
When you add /24
/ip address
add interface=bridge address=10.10.1.1/24 network=10.10.1.0
Because /n is /24, the added route is the correct one:
/ip route
add dst-address=10.10.1.0/24 gateway=bridge distance=0 scope=10 target-scope=5
And contacting 10.10.1.15 will use bridge as outgoing interface.