Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Ifconfig.me
212 views
Skip to first unread message
Jocelyn Kahler
Jan 18, 2024, 2:16:16 AM1/18/24
to
ifconfig.me is a website, so when you curl it you are getting an external website telling you what it sees as you IP address. this information is not available inside the JVM (or really the computer) you need to request your ipaddress from something outside of your network to see your public ip address.
note that this (updated) example will simulate exactly what cURL sends to the ifconfig.me site, so you will get the expected response. If you don't send a User-Agent that looks like cURL then ifconfig.me will just send you the full HTML document that it sends to a web browser
ifconfig.me
DOWNLOAD https://t.co/tp1HZrKEWC
about 4 days ago, ifconfig.me stopped working for me, and I also got locked out of an allow-listed db I was in, as if the db no longer recognized my IP. I added my ipv6 to the db and it started working again. But ifconfig still returns nothing. This leads me to suspect my router firmware (spectrum) updated and put me behind a proxy of some kind ? Any other ideas on what may have happened ?
It is important not to let theoretical risks cloud your judgement. When you navigate to a particular web site, there is so much going on behind the scenes that what you type into the address bar is virtually irrelevant. The risk from going to feee.fr is not virtually zero, it is absolute zero. The risk from ifconfig.me is even lower.
ifconfig.me is a web service that displays information about your connection, including IP address, hostname and User Agent string. Helpfully it provides a simplified interface that can be easily queried to get this information from the command line.
From my home network on a (MacOS Venture 13.4): curl works but curl ifconfig.me or curl not working.When connecting to other networks both work fine. Is there any way to debug the issue? why it's not working in the latter case?
It is very simple and it just curl at ifconfig.me to get the current IP and then make a DNS query for your DDNS Record, if they matches the check is OK, otherwise is CRITICAL.
You can find it at GitHub - GianlucaUlivi/CheckMK-DDNS-Check: A custom CheckMK plugin to verify your current Public IP against a DNS Record, useful for checking the correct update of a DDNS Service and Record.
Now, I would like to make a script to email my public ip when it changes, but when running ifconfig command or ip address I can't find it. Only when doing things like curl ifconfig.me I am able to retrieve it. Do you have any idea why ?
I'm quite experienced with VLANs, switches, routing and iptables.
However I have some trouble assigning a SSID to a specific VLAN on OpenWRT. I use CPE210 and today is my first day with OpenWRT.
So I've created an interface "TEST" in VLAN19 and assigned it to "LAN" on Firewall-Tab.
grafik964152 7.86 KB
VLAN19 fully works with TP-Link stock firmware on this switchport. The switchport ist configured to be without VLAN-Tag in normal LAN and allows vlan 19 tagged.
For testing purposes I had also selected DHCP-Client on eht0.19 and I got an IP-Adress in VLAN19. I also could do a curl --interface eth0.19 ifconfig.me and got the outbound IP-Adress of VLAN19.
f448fe82f3
note that this (updated) example will simulate exactly what cURL sends to the ifconfig.me site, so you will get the expected response. If you don't send a User-Agent that looks like cURL then ifconfig.me will just send you the full HTML document that it sends to a web browser
ifconfig.me
DOWNLOAD https://t.co/tp1HZrKEWC
about 4 days ago, ifconfig.me stopped working for me, and I also got locked out of an allow-listed db I was in, as if the db no longer recognized my IP. I added my ipv6 to the db and it started working again. But ifconfig still returns nothing. This leads me to suspect my router firmware (spectrum) updated and put me behind a proxy of some kind ? Any other ideas on what may have happened ?
It is important not to let theoretical risks cloud your judgement. When you navigate to a particular web site, there is so much going on behind the scenes that what you type into the address bar is virtually irrelevant. The risk from going to feee.fr is not virtually zero, it is absolute zero. The risk from ifconfig.me is even lower.
ifconfig.me is a web service that displays information about your connection, including IP address, hostname and User Agent string. Helpfully it provides a simplified interface that can be easily queried to get this information from the command line.
From my home network on a (MacOS Venture 13.4): curl works but curl ifconfig.me or curl not working.When connecting to other networks both work fine. Is there any way to debug the issue? why it's not working in the latter case?
It is very simple and it just curl at ifconfig.me to get the current IP and then make a DNS query for your DDNS Record, if they matches the check is OK, otherwise is CRITICAL.
You can find it at GitHub - GianlucaUlivi/CheckMK-DDNS-Check: A custom CheckMK plugin to verify your current Public IP against a DNS Record, useful for checking the correct update of a DDNS Service and Record.
Now, I would like to make a script to email my public ip when it changes, but when running ifconfig command or ip address I can't find it. Only when doing things like curl ifconfig.me I am able to retrieve it. Do you have any idea why ?
I'm quite experienced with VLANs, switches, routing and iptables.
However I have some trouble assigning a SSID to a specific VLAN on OpenWRT. I use CPE210 and today is my first day with OpenWRT.
So I've created an interface "TEST" in VLAN19 and assigned it to "LAN" on Firewall-Tab.
grafik964152 7.86 KB
VLAN19 fully works with TP-Link stock firmware on this switchport. The switchport ist configured to be without VLAN-Tag in normal LAN and allows vlan 19 tagged.
For testing purposes I had also selected DHCP-Client on eht0.19 and I got an IP-Adress in VLAN19. I also could do a curl --interface eth0.19 ifconfig.me and got the outbound IP-Adress of VLAN19.
f448fe82f3
0 new messages