Routing 169.254 Networks
-
Thanks! It was very kind of you to post the steps and screenshots.
It is working and I can finally connect to my printer now!I really appreciate for your help :)
-
Yeah never know when the next guy will have the same question ;)
Glad you got is sorted - but its still BORKED!!! dude.. Your IT guys need to rethink how they have their printer setup.. That is just nonsense to have to have users create route statements, etc.
-
To be fair, I don't think they will do anything about it though. Regardless the network is borked or not, they won't modify the network settings for the one single guy who wants more security with a PF box. Especially when other (Windows) users doesn't have any issues.
Funny thing is, the printer seems automatically change its IP every few days, I guess I have to live with it and use IP Aliases..ha!
-
APIPA (169.254.x.x) is what is used when device is set for dhcp and it gets no dhcp, so yeah it could change whenever it tries to get dhcp again, or when its rebooted for sure, etc..
You would think they could take the time to actually just set a rfc1918 IP on the freaking thing - so its always the same IP..
You sure they even understand what its doing?
-
I am not sure. But if the printer gets a RFC1918 IP (e.g. 192.168.x.x), I think it requires more configurations for my colleagues' Windows PCs, which means they (the IT guys) need to do more things, which means it is better to leave the network configuration to status quo. I don't think they really care if the network is f*'d up or not, as long as it works...
-
No it would require the same sort of shit nonsense with a route statement..
But it wouldn't be freaking changing as the wind blows.
-
Hmm... I will try to talk to the IT guys later if possible.
In the meantime I think I probably will need to stick to current configurations.
Thanks again for your help. You really did save the day! -
Sorry for bumping up the old post.
After upgrading to 2.4.5, I cannot reach the printer anymore.It seems that I can ping it on the pfsense box, but not on the NAT IP on LAN.
When pinging 192.168.200.1 (Printer is at 169.254.169.100, VIP of my box is 169.254.100.100/16) from 192.168.1.4:
It seems that there is no response:
I have confirmed that no_apipa_block is set to true, and
pfctl -srshows no blockage for packets in 169.254.0.0/16
Any ideas what is going on?
Thanks
-
@hopkins Got similar issue for users upgraded to 2.4.5, not sure if it helps to diagnostic the issue:
https://www.reddit.com/r/PFSENSE/comments/fq8t8f/245_breaks_apipanat_rules_for_me/ -
And clearly that redmine was rejected..
-
@hopkins said in Routing 169.254 Networks:
shows no blockage for packets in 169.254.0.0/16
To talk to something on another vlan that is using apipa, that device would have to have a gateway.. Or you would have to nat to it, etc.
