netbox ipam python module doesnot work

[lasag-2511]

Hi all,

Anyone uses automatic scan of networks and importing ip address to netbox using python? I am trying some python script to scan and add ip addresses to netbox. But the python module netbox.ipam.create_ip_address - doesnot work anymore. Any suggestions would be appreciated.

[candlerb]

the python module netbox.ipam.create_ip_address

And what module is that exactly? It's not part of Netbox, that's for sure:

$ cd /opt/netbox
$ find . -name '*create_ip_address*'
$ grep -R create_ip_address .
$ 

Is this some code you've written yourself, or some third-party library you're using? Is it a component of this "python script to scan and add ip addresses to netbox"? Is it some random script you found on the Internet? Very likely it's broken, or worked with an old version of Netbox but not a new one.

doesnot work anymore

http://www.catb.org/~esr/faqs/smart-questions.html#idm368
http://www.catb.org/~esr/faqs/smart-questions.html#beprecise

You need to be more specific: show the code you're running that "does not work", explain what you think it should be doing, and explain what it does instead (including showing the full, complete error message and/or backtrace, if any, copy-pasted verbatim)

Netbox supports many different forms of external integration, so you also need to be clear what you're using (e.g. the REST API directly, the REST API via some front-end library like pynetbox, the GraphQL API, the Django ORM directly, the Django ORM from a Custom Script or Plugin, etc)

Include information about the versions of all key software you are using, including most importantly Netbox itself, and Python.

[lasag-2511]

https://pypi.org/project/python-netbox/ - This is the link for the module overview.
I notice you're not checking any return value from netbox.ipam.create_ip_address, maybe you are supposed to? And how do you know that create_ip_address is even being called? - No this is not yet even called, because netbox.ipam.update_ip(str(ipaddress),status="active") -- this works

[candlerb]

I notice you've raised a similar report here: jagter/python-netbox#61

If you just say "your library doesn't work", apart from being disrespectful, it doesn't give any starting point for helping to narrow down the problem. Maybe your own code is using the library in an improper way (regardless of whether it used to work with an older version of something). In any case, you also haven't identified whether it was an older version of Netbox or an older version of this library where it worked the way you expected.

If you want someone to help you, you need to be specific. Show the minimal amount of standalone code needed to reproduce the problem in a concrete fashion. And you are more likely to get a helpful response if you've done your own troubleshooting. Even demonstrating that it works with Netbox 3.4 but not 3.5 (for example) would be very helpful to the person maintaining this code.

If it turns out that the code isn't being maintained, there are other options, and pynetbox is being actively maintained.

[markkuleinio]

pynetbox is being actively maintained.

Are you sure about that? There haven't been new commits from maintainers for months, and contributions don't get reviewed or merged. Also, there is a new netbox-python project started, but it hasn't got much progress either.

I personally have mentally prepared myself for forking pynetbox for the customer I'm mostly working with when/if I need features that are not supported in current 7.0.1. That won't be ideal, so I don't know yet.

[candlerb]

@markkuleinio wrote:

pynetbox is being actively maintained.

Are you sure about that?

No! 😛 All I mean is, it hasn't broken for my use case with Netbox 3.5.

I note that pynetbox and the new netbox-python are both under "netbox-community" which gives them some sort of semi-official status, whereas jagter/python-netbox is completely independent.

[markkuleinio]

I'm pleased to see that today there has been lots of maintainer activity in pynetbox so it's suddenly looking totally different than last week.

[lasag-2511]

yes i rasied there as well in the last week but no replies was received. hence i am asking here.I was using the version v3.2.5 before it worked, but now doesnot work. So i upgraded the netbox and tried to use the same code there and realized that the module is broken. you can find the code here if you would like to test
https://gitlab.com/Sasha0986/netbox/-/blob/master/updateipv2.py

N

[candlerb]

This is my last reply.

The same output I have posted on the above quotes with tcpdump and code with out scanner

I asked that you show the first part of the HTTP exchange - you have not.

Can i use netbox-python modules or pynetbox for scanning and adding ipaddress to netbox?

Scanning, and adding IP addresses to Netbox, are two completely separate and independent activities.

[lasag-2511]

This is my last reply.

sorry i have missed the first part of tcpdump.

I asked that you show the first part of the HTTP exchange - you have not. -- Its a get request

tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on lo, link-type EN10MB (Ethernet), snapshot length 262144 bytes
09:47:02.355002 IP 127.0.0.1.59938 > 127.0.0.1.8001: Flags [S], seq 248780666, win 65495, options [mss 65495,sackOK,TS val 2717264347 ecr 0,nop,wscale 7], length 0
E..<..@.@..*.........".A...z.........0.........
..).........
09:47:02.355027 IP 127.0.0.1.8001 > 127.0.0.1.59938: Flags [S.], seq 4021659945, ack 248780667, win 65483, options [mss 65495,sackOK,TS val 2717264347 ecr 2717264347,nop,wscale 7], length 0
E..<..@.@.<..........A."...)...{.....0.........
..)...).....
09:47:02.355050 IP 127.0.0.1.59938 > 127.0.0.1.8001: Flags [.], ack 1, win 512, options [nop,nop,TS val 2717264347 ecr 2717264347], length 0
E..4..@.@..1.........".A...{...*.....(.....
..)...).
09:47:02.355141 IP 127.0.0.1.59938 > 127.0.0.1.8001: Flags [P.], seq 1:322, ack 1, win 512, options [nop,nop,TS val 2717264347 ecr 2717264347], length 321
E..u..@.@............".A...{...*.....i.....
..)...).GET /api/ipam/ip-addresses/ HTTP/1.0
X-Forwarded-Host: 192.168.200.24
X-Real-IP: ::ffff:192.168.200.1
X-Forwarded-Proto: https
Host: localhost:8001
Connection: close
User-Agent: python-requests/2.30.0
Accept-Encoding: gzip, deflate
Accept: application/json
Authorization: Token a98b952b558f0436a2b6e14402bc214ea3ff2497

[markkuleinio]

netbox.ipam.create_ip_address() is not sending GET request:

https://github.com/jagter/python-netbox/blob/master/netbox/ipam.py#L54-L62

[lasag-2511]

So it should be post even post doesnot work

[lasag-2511]

any suggestions would be appreciated.
{"count":0,"next":null,"previous":null,"results":[]}' - for me it looks like this part is not working at all with API requests