forum.bitel.ru :: Просмотр темы

Option: (t=82,l=25) Agent Information Option
Option: (82) Agent Information Option
Length: 25
Value: 01060004044F0018020F000D31302E3137362E38322E3234...
Agent Circuit ID: 0004044F0018
Agent Remote ID: 000D31302E3137362E38322E323430

dhcp.82.key.option.code=1
dhcp.82.key.position=5

Option: (t=82,l=19) Agent Information Option
Option: (82) Agent Information Option
Length: 19
Value: 01110018044C31302E3137362E38322E313130
Agent Circuit ID: 0018044C31302E3137362E38322E313130

dhcp.82.key.option.code=1
dhcp.82.key.position=1

DEBUG 29.03.2010 16:44:51,427 pool-1-thread-12 processing request
DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 OP_BOOT_REQUEST
DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 agent information found!
DEBUG 29.03.2010 16:44:51,429 pool-1-thread-12 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 request.giaddr =10.176.82.110
DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 gateId = 11

Agent Circuit ID: 0018044C31302E3137362E38322E313130

DEBUG 05.04.2010 08:12:36,926 pool-1-thread-440 processing request
DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 OP_BOOT_REQUEST
DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 agent information found!
DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 05.04.2010 08:12:36,928 pool-1-thread-440 request.giaddr =10.35.2.110
DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 processing request
DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 OP_BOOT_REQUEST
DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 agent information found!
DEBUG 05.04.2010 08:12:44,928 pool-1-thread-440 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 05.04.2010 08:12:44,928 pool-1-thread-440 request.giaddr =10.35.2.110

08:12:36,926 DEBUG dhcp:200 - processing request
08:12:36,927 DEBUG dhcp:203 - OP_BOOT_REQUEST
08:12:36,927 DEBUG dhcp:244 - agent information found!
08:12:36,927 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
08:12:36,928 DEBUG dhcp:251 - request.giaddr =10.35.2.110
08:12:44,927 DEBUG dhcp:200 - processing request
08:12:44,927 DEBUG dhcp:203 - OP_BOOT_REQUEST
08:12:44,927 DEBUG dhcp:244 - agent information found!
08:12:44,928 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
08:12:44,928 DEBUG dhcp:251 - request.giaddr =10.35.2.110

processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor
#processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor
#Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1)

dhcp.82.key.option.code=1

#Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0).
#dhcp.82.key.position=2
#Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0).
#для Qtech
#dhcp.82.key.position=5

#для Zyxel
dhcp.82.key.position=1

admin.port=1868
dhcp.thread.count=10
dhcp.data.save.delay=3600
dhcp.data.save.period=3600
dhcp.server.identifier=10.176.74.151

Agent Circuit ID: 0018044C

DEBUG 05.04.2010 16:06:24,784 pool-1-thread-1 processing request
DEBUG 05.04.2010 16:06:24,785 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 05.04.2010 16:06:24,787 pool-1-thread-1 agent information found!
DEBUG 05.04.2010 16:06:24,788 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 05.04.2010 16:06:24,789 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 05.04.2010 16:06:32,773 pool-1-thread-1 processing request
DEBUG 05.04.2010 16:06:32,774 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 05.04.2010 16:06:32,775 pool-1-thread-1 agent information found!
DEBUG 05.04.2010 16:06:32,776 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 05.04.2010 16:06:32,776 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 05.04.2010 16:06:47,775 pool-1-thread-1 processing request
DEBUG 05.04.2010 16:06:47,776 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 05.04.2010 16:06:47,777 pool-1-thread-1 agent information found!
DEBUG 05.04.2010 16:06:47,777 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 05.04.2010 16:06:47,778 pool-1-thread-1 request.giaddr =10.35.2.110

16:06:24,784 DEBUG dhcp:200 - processing request
16:06:24,785 DEBUG dhcp:203 - OP_BOOT_REQUEST
16:06:24,787 DEBUG dhcp:244 - agent information found!
16:06:24,788 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
16:06:24,789 DEBUG dhcp:251 - request.giaddr =10.35.2.110
16:06:32,773 DEBUG dhcp:200 - processing request
16:06:32,774 DEBUG dhcp:203 - OP_BOOT_REQUEST
16:06:32,775 DEBUG dhcp:244 - agent information found!
16:06:32,776 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
16:06:32,776 DEBUG dhcp:251 - request.giaddr =10.35.2.110
16:06:47,775 DEBUG dhcp:200 - processing request
16:06:47,776 DEBUG dhcp:203 - OP_BOOT_REQUEST
16:06:47,777 DEBUG dhcp:244 - agent information found!
16:06:47,777 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
16:06:47,778 DEBUG dhcp:251 - request.giaddr =10.35.2.110
16:07:24,689 DEBUG dhcp:200 - processing request
16:07:24,690 DEBUG dhcp:203 - OP_BOOT_REQUEST
16:07:24,691 DEBUG dhcp:244 - agent information found!
16:07:24,691 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
16:07:24,692 DEBUG dhcp:251 - request.giaddr =10.35.2.110

processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor
#Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1)
dhcp.82.key.option.code=1
#Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0).
dhcp.82.key.position=1
admin.port=1868
dhcp.thread.count=10
dhcp.data.save.delay=3600
dhcp.data.save.period=3600
dhcp.server.identifier=10.176.74.151

processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor
#processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor
#Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1)
dhcp.82.key.option.code=1
#Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0).
#dhcp.82.key.position=2
#Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0).
dhcp.82.key.position=1
admin.port=1868
dhcp.thread.count=10
dhcp.data.save.delay=3600
dhcp.data.save.period=3600
dhcp.server.identifier=10.176.74.151

<?xml version="1.0" encoding="UTF-8"?>
<sync>
<gate id="11" host="10.35.2.110">
<param id="dhcp.option.121" value="190AB04A800A23FF011B511E3B000A23FF01"/>
<param id="dhcp.dns" value="10.176.74.131"/>
<param id="dhcp.subnetMask" value="255.240.0.0"/>
<param id="dhcp.ipAddressLeaseTime" value="86400"/>
<param id="dhcp.timeOffset" value="-18000"/>
<param id="dhcp.router" value="10.21.255.1"/>
</gate>
<port gateId="11" id="24" ip="0A 23 F2 6E"/>
</sync>

INFO 06.04.2010 10:02:21,393 main dhcp.server.identifier=10.176.74.151
INFO 06.04.2010 10:02:21,406 main Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)...
INFO 06.04.2010 10:02:21,413 main option_82=1
INFO 06.04.2010 10:02:21,416 main position_82=1
INFO 06.04.2010 10:02:21,417 main dhcp.data.save.delay=3600000
INFO 06.04.2010 10:02:21,418 main dhcp.data.save.period=3600000
INFO 06.04.2010 10:02:21,422 main Load data from file.
DEBUG 06.04.2010 10:02:21,796 main set gate 11 10.35.2.110
INFO 06.04.2010 10:02:21,800 main setGatePortIp: gateId = 11;port=24;adress=10.35.242.110
INFO 06.04.2010 10:02:21,804 main Processor init ok.
INFO 06.04.2010 10:02:21,822 main DHCPSocketListener on port=67 init ok.
INFO 06.04.2010 10:02:21,832 main AdminSocketListener on port=1868 init ok.
INFO 06.04.2010 10:02:21,833 Thread-7 AdminSocketListener listen.
DEBUG 06.04.2010 10:05:12,896 pool-1-thread-1 processing request
DEBUG 06.04.2010 10:05:12,897 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:05:12,898 pool-1-thread-1 agent information found!
DEBUG 06.04.2010 10:05:12,899 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:05:12,900 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:05:12,900 pool-1-thread-1 gateId = 11
DEBUG 06.04.2010 10:05:21,007 pool-1-thread-2 processing request
DEBUG 06.04.2010 10:05:21,008 pool-1-thread-2 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:05:21,008 pool-1-thread-2 agent information found!
DEBUG 06.04.2010 10:05:21,009 pool-1-thread-2 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:05:21,010 pool-1-thread-2 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:05:21,010 pool-1-thread-2 gateId = 11
DEBUG 06.04.2010 10:05:25,008 pool-1-thread-3 processing request
DEBUG 06.04.2010 10:05:25,008 pool-1-thread-3 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:05:25,009 pool-1-thread-3 agent information found!
DEBUG 06.04.2010 10:05:25,010 pool-1-thread-3 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:05:25,011 pool-1-thread-3 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:05:25,011 pool-1-thread-3 gateId = 11
DEBUG 06.04.2010 10:05:34,010 pool-1-thread-4 processing request
DEBUG 06.04.2010 10:05:34,011 pool-1-thread-4 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:05:34,012 pool-1-thread-4 agent information found!
DEBUG 06.04.2010 10:05:34,014 pool-1-thread-4 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:05:34,015 pool-1-thread-4 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:05:34,016 pool-1-thread-4 gateId = 11
DEBUG 06.04.2010 10:05:49,012 pool-1-thread-5 processing request
DEBUG 06.04.2010 10:05:49,012 pool-1-thread-5 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:05:49,013 pool-1-thread-5 agent information found!
DEBUG 06.04.2010 10:05:49,014 pool-1-thread-5 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:05:49,014 pool-1-thread-5 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:05:49,015 pool-1-thread-5 gateId = 11
DEBUG 06.04.2010 10:06:26,077 pool-1-thread-6 processing request
DEBUG 06.04.2010 10:06:26,078 pool-1-thread-6 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:06:26,079 pool-1-thread-6 agent information found!
DEBUG 06.04.2010 10:06:26,080 pool-1-thread-6 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:06:26,080 pool-1-thread-6 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:06:26,081 pool-1-thread-6 gateId = 11
DEBUG 06.04.2010 10:06:29,079 pool-1-thread-7 processing request
DEBUG 06.04.2010 10:06:29,080 pool-1-thread-7 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:06:29,080 pool-1-thread-7 agent information found!
DEBUG 06.04.2010 10:06:29,081 pool-1-thread-7 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:06:29,082 pool-1-thread-7 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:06:29,082 pool-1-thread-7 gateId = 11
DEBUG 06.04.2010 10:06:36,079 pool-1-thread-8 processing request
DEBUG 06.04.2010 10:06:36,081 pool-1-thread-8 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:06:36,082 pool-1-thread-8 agent information found!
DEBUG 06.04.2010 10:06:36,083 pool-1-thread-8 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:06:36,085 pool-1-thread-8 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:06:36,086 pool-1-thread-8 gateId = 11
DEBUG 06.04.2010 10:06:51,080 pool-1-thread-9 processing request
DEBUG 06.04.2010 10:06:51,081 pool-1-thread-9 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:06:51,081 pool-1-thread-9 agent information found!
DEBUG 06.04.2010 10:06:51,082 pool-1-thread-9 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:06:51,083 pool-1-thread-9 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:06:51,086 pool-1-thread-9 gateId = 11

10:02:21,393 INFO dhcp:271 - dhcp.server.identifier=10.176.74.151
10:02:21,406 INFO dhcp:39 - Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)...
10:02:21,413 INFO dhcp:172 - option_82=1
10:02:21,416 INFO dhcp:173 - position_82=1
10:02:21,417 INFO dhcp:175 - dhcp.data.save.delay=3600000
10:02:21,418 INFO dhcp:176 - dhcp.data.save.period=3600000
10:02:21,422 INFO dhcp:185 - Load data from file.
10:02:21,796 DEBUG dhcp:656 - set gate 11 10.35.2.110
10:02:21,800 INFO dhcp:705 - setGatePortIp: gateId = 11;port=24;adress=10.35.242.110
ok
10:02:21,804 INFO dhcp:52 - Processor init ok.
10:02:21,822 INFO dhcp:106 - DHCPSocketListener on port=67 init ok.
10:02:21,832 INFO dhcp:62 - AdminSocketListener on port=1868 init ok.
10:02:21,833 INFO dhcp:81 - AdminSocketListener listen.
10:05:12,896 DEBUG dhcp:200 - processing request
10:05:12,897 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:12,898 DEBUG dhcp:244 - agent information found!
10:05:12,899 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:12,900 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:12,900 DEBUG dhcp:264 - gateId = 11
Exception in thread "pool-1-thread-1" java.lang.NullPointerException
at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581)
at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576)
at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155)
at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98)
at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266)
at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
10:05:21,007 DEBUG dhcp:200 - processing request
10:05:21,008 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:21,008 DEBUG dhcp:244 - agent information found!
10:05:21,009 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:21,010 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:21,010 DEBUG dhcp:264 - gateId = 11
Exception in thread "pool-1-thread-2" java.lang.NullPointerException
at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581)
at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576)
at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155)
at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98)
at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266)
at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
10:05:25,008 DEBUG dhcp:200 - processing request
10:05:25,008 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:25,009 DEBUG dhcp:244 - agent information found!
10:05:25,010 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:25,011 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:25,011 DEBUG dhcp:264 - gateId = 11
Exception in thread "pool-1-thread-3" java.lang.NullPointerException
at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581)
at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576)
at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155)
at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98)
at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266)
at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
10:05:34,010 DEBUG dhcp:200 - processing request
10:05:34,011 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:34,012 DEBUG dhcp:244 - agent information found!
10:05:34,014 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:34,015 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:34,016 DEBUG dhcp:264 - gateId = 11
Exception in thread "pool-1-thread-4" java.lang.NullPointerException
at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581)
at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576)
at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155)
at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98)
at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266)
at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
10:05:49,012 DEBUG dhcp:200 - processing request
10:05:49,012 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:49,013 DEBUG dhcp:244 - agent information found!
10:05:49,014 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:49,014 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:49,015 DEBUG dhcp:264 - gateId = 11
Exception in thread "pool-1-thread-5" java.lang.NullPointerException
at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581)
at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576)
at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155)
at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98)
at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266)
at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
10:05:25,008 DEBUG dhcp:200 - processing request
10:05:25,008 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:05:25,009 DEBUG dhcp:244 - agent information found!
10:05:25,010 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:05:25,011 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:05:25,011 DEBUG dhcp:264 - gateId = 11

processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor
#processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor
#Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1)
dhcp.82.key.option.code=1
#Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0).
#dhcp.82.key.position=2
#Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0).
dhcp.82.key.position=5
admin.port=1868
dhcp.thread.count=10
dhcp.data.save.delay=3600
dhcp.data.save.period=3600
dhcp.server.identifier=10.176.74.151

INFO 06.04.2010 10:13:41,839 main dhcp.server.identifier=10.176.74.151
INFO 06.04.2010 10:13:41,852 main Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)...
INFO 06.04.2010 10:13:41,860 main option_82=1
INFO 06.04.2010 10:13:41,863 main position_82=5
INFO 06.04.2010 10:13:41,864 main dhcp.data.save.delay=3600000
INFO 06.04.2010 10:13:41,865 main dhcp.data.save.period=3600000
INFO 06.04.2010 10:13:41,868 main Load data from file.
DEBUG 06.04.2010 10:13:42,243 main set gate 11 10.35.2.110
INFO 06.04.2010 10:13:42,247 main setGatePortIp: gateId = 11;port=24;adress=10.35.242.110
INFO 06.04.2010 10:13:42,251 main Processor init ok.
INFO 06.04.2010 10:13:42,269 main DHCPSocketListener on port=67 init ok.
INFO 06.04.2010 10:13:42,280 main AdminSocketListener on port=1868 init ok.
INFO 06.04.2010 10:13:42,281 Thread-7 AdminSocketListener listen.
DEBUG 06.04.2010 10:14:35,555 pool-1-thread-1 processing request
DEBUG 06.04.2010 10:14:35,556 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:14:35,556 pool-1-thread-1 agent information found!
DEBUG 06.04.2010 10:14:35,557 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:14:35,558 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:14:35,559 pool-1-thread-1 gateId = 11
DEBUG 06.04.2010 10:14:35,561 pool-1-thread-1 port=24
DEBUG 06.04.2010 10:14:35,562 pool-1-thread-1 ip = 10.35.242.110
DEBUG 06.04.2010 10:14:35,563 pool-1-thread-1 DHCP_DISCOVER
DEBUG 06.04.2010 10:14:47,732 pool-1-thread-1 processing request
DEBUG 06.04.2010 10:14:47,733 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:14:47,733 pool-1-thread-1 agent information found!
DEBUG 06.04.2010 10:14:47,734 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:14:47,735 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:14:47,736 pool-1-thread-1 gateId = 11
DEBUG 06.04.2010 10:14:47,736 pool-1-thread-1 port=24
DEBUG 06.04.2010 10:14:47,737 pool-1-thread-1 ip = 10.35.242.110
DEBUG 06.04.2010 10:14:47,738 pool-1-thread-1 DHCP_DISCOVER
DEBUG 06.04.2010 10:14:47,772 pool-1-thread-1 processing request
DEBUG 06.04.2010 10:14:47,776 pool-1-thread-1 OP_BOOT_REQUEST
DEBUG 06.04.2010 10:14:47,777 pool-1-thread-1 agent information found!
DEBUG 06.04.2010 10:14:47,779 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER
DEBUG 06.04.2010 10:14:47,781 pool-1-thread-1 request.giaddr =10.35.2.110
DEBUG 06.04.2010 10:14:47,782 pool-1-thread-1 gateId = 11
DEBUG 06.04.2010 10:14:47,782 pool-1-thread-1 port=24
DEBUG 06.04.2010 10:14:47,783 pool-1-thread-1 ip = 10.35.242.110
DEBUG 06.04.2010 10:14:47,784 pool-1-thread-1 DHCP_REQUEST
DEBUG 06.04.2010 10:14:47,784 pool-1-thread-1 DHCP_ACK

10:13:41,839 INFO dhcp:271 - dhcp.server.identifier=10.176.74.151
10:13:41,852 INFO dhcp:39 - Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)...
10:13:41,860 INFO dhcp:172 - option_82=1
10:13:41,863 INFO dhcp:173 - position_82=5
10:13:41,864 INFO dhcp:175 - dhcp.data.save.delay=3600000
10:13:41,865 INFO dhcp:176 - dhcp.data.save.period=3600000
10:13:41,868 INFO dhcp:185 - Load data from file.
10:13:42,243 DEBUG dhcp:656 - set gate 11 10.35.2.110
10:13:42,247 INFO dhcp:705 - setGatePortIp: gateId = 11;port=24;adress=10.35.242.110
ok
10:13:42,251 INFO dhcp:52 - Processor init ok.
10:13:42,269 INFO dhcp:106 - DHCPSocketListener on port=67 init ok.
10:13:42,280 INFO dhcp:62 - AdminSocketListener on port=1868 init ok.
10:13:42,281 INFO dhcp:81 - AdminSocketListener listen.
10:14:35,555 DEBUG dhcp:200 - processing request
10:14:35,556 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:14:35,556 DEBUG dhcp:244 - agent information found!
10:14:35,557 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:14:35,558 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:14:35,559 DEBUG dhcp:264 - gateId = 11
10:14:35,561 DEBUG dhcp:333 - port=24
10:14:35,562 DEBUG dhcp:273 - ip = 10.35.242.110
10:14:35,563 DEBUG dhcp:281 - DHCP_DISCOVER
10:14:47,732 DEBUG dhcp:200 - processing request
10:14:47,733 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:14:47,733 DEBUG dhcp:244 - agent information found!
10:14:47,734 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:14:47,735 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:14:47,736 DEBUG dhcp:264 - gateId = 11
10:14:47,736 DEBUG dhcp:333 - port=24
10:14:47,737 DEBUG dhcp:273 - ip = 10.35.242.110
10:14:47,738 DEBUG dhcp:281 - DHCP_DISCOVER
10:14:47,772 DEBUG dhcp:200 - processing request
10:14:47,776 DEBUG dhcp:203 - OP_BOOT_REQUEST
10:14:47,777 DEBUG dhcp:244 - agent information found!
10:14:47,779 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER
10:14:47,781 DEBUG dhcp:251 - request.giaddr =10.35.2.110
10:14:47,782 DEBUG dhcp:264 - gateId = 11
10:14:47,782 DEBUG dhcp:333 - port=24
10:14:47,783 DEBUG dhcp:273 - ip = 10.35.242.110
10:14:47,784 DEBUG dhcp:288 - DHCP_REQUEST
10:14:47,784 DEBUG dhcp:310 - DHCP_ACK

Value: 01060004044C0018020F000D31302E3137362E38322E3234...

Agent Circuit ID: 0004044C0018

No. Time Source Destination Protocol Info
332 33.787444 10.35.2.110 10.176.74.151 DHCP DHCP Request - Transaction ID 0x5fe89b63

Frame 332 (373 bytes on wire, 373 bytes captured)
Arrival Time: Apr 6, 2010 10:50:03.173687000
[Time delta from previous captured frame: 0.002777000 seconds]
[Time delta from previous displayed frame: 33.787444000 seconds]
[Time since reference or first frame: 33.787444000 seconds]
Frame Number: 332
Frame Length: 373 bytes
Capture Length: 373 bytes
[Frame is marked: False]
[Protocols in frame: eth:vlan:ip:udp:bootp]
[Coloring Rule Name: UDP]
[Coloring Rule String: udp]
Ethernet II, Src: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a), Dst: AsustekC_10:da:4f (00:13:d4:10:da:4f)
Destination: AsustekC_10:da:4f (00:13:d4:10:da:4f)
Address: AsustekC_10:da:4f (00:13:d4:10:da:4f)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
Source: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a)
Address: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
Type: 802.1Q Virtual LAN (0x8100)
802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 102
000. .... .... .... = Priority: 0
...0 .... .... .... = CFI: 0
.... 0000 0110 0110 = ID: 102
Type: IP (0x0800)
Internet Protocol, Src: 10.35.2.110 (10.35.2.110), Dst: 10.176.74.151 (10.176.74.151)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 355
Identification: 0x805e (32862)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 254
Protocol: UDP (0x11)
Header checksum: 0xd953 [correct]
Source: 10.35.2.110 (10.35.2.110)
Destination: 10.176.74.151 (10.176.74.151)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
Message type: Boot Request (1)
Hardware type: Ethernet
Hardware address length: 6
Hops: 1
Transaction ID: 0x5fe89b63
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
Client IP address: 10.35.242.110 (10.35.242.110)
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Relay agent IP address: 10.35.2.110 (10.35.2.110)
Client MAC address: ArimaCom_0f:d4:b9 (00:03:25:0f:d4:b9)
Server host name not given
Boot file name not given
Option: (t=53,l=1) DHCP Message Type = DHCP Request
Option: (53) DHCP Message Type
Length: 1
Value: 03
Option: (t=61,l=7) Client identifier
Option: (61) Client identifier
Length: 7
Value: 010003250FD4B9
Hardware type: Ethernet
Client MAC address: ArimaCom_0f:d4:b9 (00:03:25:0f:d4:b9)
Option: (t=12,l=15) Host Name = "microsof-682ebb"
Option: (12) Host Name
Length: 15
Value: 6D6963726F736F662D363832656262
Option: (t=81,l=19) Client Fully Qualified Domain Name
Option: (81) Client Fully Qualified Domain Name
Length: 19
Value: 0000006D6963726F736F662D3638326562622E
Flags: 0x00
0000 .... = Reserved flags: 0x00
.... 0... = Server DDNS: Some server updates
.... .0.. = Encoding: ASCII encoding
.... ..0. = Server overrides: No override
.... ...0 = Server: Client
A-RR result: 0
PTR-RR result: 0
Client name: microsof-682ebb.
Option: (t=60,l=8) Vendor class identifier = "MSFT 5.0"
Option: (60) Vendor class identifier
Length: 8
Value: 4D53465420352E30
Option: (t=55,l=11) Parameter Request List
Option: (55) Parameter Request List
Length: 11
Value: 010F03062C2E2F1F21F92B
1 = Subnet Mask
15 = Domain Name
3 = Router
6 = Domain Name Server
44 = NetBIOS over TCP/IP Name Server
46 = NetBIOS over TCP/IP Node Type
47 = NetBIOS over TCP/IP Scope
31 = Perform Router Discover
33 = Static Route
249 = Classless Static Route (Microsoft)
43 = Vendor-Specific Information
Option: (t=43,l=3) Vendor-Specific Information
Option: (43) Vendor-Specific Information
Length: 3
Value: DC0100
Option: (t=82,l=6) Agent Information Option
Option: (82) Agent Information Option
Length: 6
Value: 01040018044C
Agent Circuit ID: 0018044C
End Option

Автор:	mrustik [ 29 мар 2010, 16:51 ]
Заголовок сообщения:	DHCP Op.82 Circuit ID
есть свич, у которого снифер выдает параметры Op.82 2-3 байты влан, 5 - порт Код: Option: (t=82,l=25) Agent Information Option Option: (82) Agent Information Option Length: 25 Value: 01060004044F0018020F000D31302E3137362E38322E3234... Agent Circuit ID: 0004044F0018 Agent Remote ID: 000D31302E3137362E38322E323430 В настройках DHCP сервера стоит Код: dhcp.82.key.option.code=1 dhcp.82.key.position=5 Выдает адрес нормально, проблем нет. Но есть свич у которого параметры Op.82 не стандартные, 1 - порт, 2-3 влан Код: Option: (t=82,l=19) Agent Information Option Option: (82) Agent Information Option Length: 19 Value: 01110018044C31302E3137362E38322E313130 Agent Circuit ID: 0018044C31302E3137362E38322E313130 В настройках DHCP сервера ставлю Код: dhcp.82.key.option.code=1 dhcp.82.key.position=1 Но сервер в логах выдает Код: DEBUG 29.03.2010 16:44:51,427 pool-1-thread-12 processing request DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 OP_BOOT_REQUEST DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 agent information found! DEBUG 29.03.2010 16:44:51,429 pool-1-thread-12 DHCP_REQUEST or DHCP_DISCOVER DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 request.giaddr =10.176.82.110 DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 gateId = 11 и номер порта не находит. Как правильно прописать настройки?

Автор:	mrustik [ 29 мар 2010, 17:18 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Если ставить 2 байт (dhcp.82.key.position=1), то у первого свича находит порт 4, что верно. Не может быть, что у второго свича, строка Код: Agent Circuit ID: 0018044C31302E3137362E38322E313130 слишком длинная, поэтому сервер и не воспринимает ее. Если так, можно ли это исправить?

Автор:	mrustik [ 31 мар 2010, 09:15 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Уважаемые разработчики, у вас есть ответ или как?

Автор:	mrustik [ 01 апр 2010, 18:24 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Есть еще более существенное различие, нет в запросе поля Agent Remote ID, может это иметь значение для DHCP сервера ?

Автор:	stark [ 02 апр 2010, 17:06 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
версия биллинга какая ? вы используете DHCPRelayProcessor или DHCPVlanRelayProcessor ?

forum.bitel.ru http://forum.bitel.ru/

DHCP Op.82 Circuit ID http://forum.bitel.ru/viewtopic.php?f=7&t=3767	Страница 1 из 1

Автор:	stark [ 02 апр 2010, 17:07 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
mrustik писал(а): Если ставить 2 байт (dhcp.82.key.position=1), то у первого свича находит порт 4, что верно. Не может быть, что у второго свича, строка Код: Agent Circuit ID: 0018044C31302E3137362E38322E313130 слишком длинная, поэтому сервер и не воспринимает ее. нет

Автор:	stark [ 02 апр 2010, 17:10 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
mrustik писал(а): Код: DEBUG 29.03.2010 16:44:51,427 pool-1-thread-12 processing request DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 OP_BOOT_REQUEST DEBUG 29.03.2010 16:44:51,428 pool-1-thread-12 agent information found! DEBUG 29.03.2010 16:44:51,429 pool-1-thread-12 DHCP_REQUEST or DHCP_DISCOVER DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 request.giaddr =10.176.82.110 DEBUG 29.03.2010 16:44:51,430 pool-1-thread-12 gateId = 11 он должен еще выводить информацию по поске порта . "port=xxxx" . Там точно нет никаких ошибок в логах? настройки у вас правильные

Автор:	mrustik [ 05 апр 2010, 08:20 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Версия 4.6 сборка 666 от 19.02.2010 16:48:52 ipn вер. 4.6 сборка 244 от 22.03.2010 17:23:48 BGDHCP_IPN_4.6_142.zip Использую processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor Ошибок нет, настройки правильные. С одним свичем работает нормально, все выдает, но с другим нет. В логах dhcp.log пишет Код: DEBUG 05.04.2010 08:12:36,926 pool-1-thread-440 processing request DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 OP_BOOT_REQUEST DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 agent information found! DEBUG 05.04.2010 08:12:36,927 pool-1-thread-440 DHCP_REQUEST or DHCP_DISCOVER DEBUG 05.04.2010 08:12:36,928 pool-1-thread-440 request.giaddr =10.35.2.110 DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 processing request DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 OP_BOOT_REQUEST DEBUG 05.04.2010 08:12:44,927 pool-1-thread-440 agent information found! DEBUG 05.04.2010 08:12:44,928 pool-1-thread-440 DHCP_REQUEST or DHCP_DISCOVER DEBUG 05.04.2010 08:12:44,928 pool-1-thread-440 request.giaddr =10.35.2.110 в dhcp.out Код: 08:12:36,926 DEBUG dhcp:200 - processing request 08:12:36,927 DEBUG dhcp:203 - OP_BOOT_REQUEST 08:12:36,927 DEBUG dhcp:244 - agent information found! 08:12:36,927 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 08:12:36,928 DEBUG dhcp:251 - request.giaddr =10.35.2.110 08:12:44,927 DEBUG dhcp:200 - processing request 08:12:44,927 DEBUG dhcp:203 - OP_BOOT_REQUEST 08:12:44,927 DEBUG dhcp:244 - agent information found! 08:12:44,928 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 08:12:44,928 DEBUG dhcp:251 - request.giaddr =10.35.2.110 Настройки Код: processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor #processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor #Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1) dhcp.82.key.option.code=1 #Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0). #dhcp.82.key.position=2 #Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0). #для Qtech #dhcp.82.key.position=5 #для Zyxel dhcp.82.key.position=1 admin.port=1868 dhcp.thread.count=10 dhcp.data.save.delay=3600 dhcp.data.save.period=3600 dhcp.server.identifier=10.176.74.151

Автор:	mrustik [ 05 апр 2010, 08:31 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Можно ли выводить дополнительную информацию по работе сервера, например строку Agent Circuit ID, которую получает сервер.

Автор:	mrustik [ 05 апр 2010, 16:14 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Сейчас на сервер приходит Код: Agent Circuit ID: 0018044C как в доке сказано, Цитата: #Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0). поставил dhcp.82.key.position=1, но результат тотже Код: DEBUG 05.04.2010 16:06:24,784 pool-1-thread-1 processing request DEBUG 05.04.2010 16:06:24,785 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 05.04.2010 16:06:24,787 pool-1-thread-1 agent information found! DEBUG 05.04.2010 16:06:24,788 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 05.04.2010 16:06:24,789 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 05.04.2010 16:06:32,773 pool-1-thread-1 processing request DEBUG 05.04.2010 16:06:32,774 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 05.04.2010 16:06:32,775 pool-1-thread-1 agent information found! DEBUG 05.04.2010 16:06:32,776 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 05.04.2010 16:06:32,776 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 05.04.2010 16:06:47,775 pool-1-thread-1 processing request DEBUG 05.04.2010 16:06:47,776 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 05.04.2010 16:06:47,777 pool-1-thread-1 agent information found! DEBUG 05.04.2010 16:06:47,777 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 05.04.2010 16:06:47,778 pool-1-thread-1 request.giaddr =10.35.2.110 Код: 16:06:24,784 DEBUG dhcp:200 - processing request 16:06:24,785 DEBUG dhcp:203 - OP_BOOT_REQUEST 16:06:24,787 DEBUG dhcp:244 - agent information found! 16:06:24,788 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 16:06:24,789 DEBUG dhcp:251 - request.giaddr =10.35.2.110 16:06:32,773 DEBUG dhcp:200 - processing request 16:06:32,774 DEBUG dhcp:203 - OP_BOOT_REQUEST 16:06:32,775 DEBUG dhcp:244 - agent information found! 16:06:32,776 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 16:06:32,776 DEBUG dhcp:251 - request.giaddr =10.35.2.110 16:06:47,775 DEBUG dhcp:200 - processing request 16:06:47,776 DEBUG dhcp:203 - OP_BOOT_REQUEST 16:06:47,777 DEBUG dhcp:244 - agent information found! 16:06:47,777 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 16:06:47,778 DEBUG dhcp:251 - request.giaddr =10.35.2.110 16:07:24,689 DEBUG dhcp:200 - processing request 16:07:24,690 DEBUG dhcp:203 - OP_BOOT_REQUEST 16:07:24,691 DEBUG dhcp:244 - agent information found! 16:07:24,691 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 16:07:24,692 DEBUG dhcp:251 - request.giaddr =10.35.2.110 не ищет номер порта. конфигурация Код: processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor #Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1) dhcp.82.key.option.code=1 #Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0). dhcp.82.key.position=1 admin.port=1868 dhcp.thread.count=10 dhcp.data.save.delay=3600 dhcp.data.save.period=3600 dhcp.server.identifier=10.176.74.151

Автор:	mrustik [ 05 апр 2010, 16:42 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
и вообще значение Option 82 Код: Value: 01040018044C 1 позиция 4 байта и получаем субопцию 1 Код: 0018044C , где 18 - номер порта (24), 044С влан 1100 Где засада

Автор:	stark [ 05 апр 2010, 19:38 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
дайте запросный пакет полностью . как в это теме дали : viewtopic.php?f=7&t=1703 возможно ошибка как-то связана с теми изменениями

Автор:	stark [ 05 апр 2010, 19:43 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
switch какой ?

Автор:	mrustik [ 06 апр 2010, 10:12 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
шлюз - модифицированный зухель У меня есть 2 свича Zyxel 2024A и Qtech 2900. С одинаковыми настройками, Qtech адрес получает,а Zyxel нет. Настройки для Zyxel dhcp.properties: Код: processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor #processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor #Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1) dhcp.82.key.option.code=1 #Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0). #dhcp.82.key.position=2 #Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0). dhcp.82.key.position=1 admin.port=1868 dhcp.thread.count=10 dhcp.data.save.delay=3600 dhcp.data.save.period=3600 dhcp.server.identifier=10.176.74.151 dhcp.data Код: <?xml version="1.0" encoding="UTF-8"?> <sync> <gate id="11" host="10.35.2.110"> <param id="dhcp.option.121" value="190AB04A800A23FF011B511E3B000A23FF01"/> <param id="dhcp.dns" value="10.176.74.131"/> <param id="dhcp.subnetMask" value="255.240.0.0"/> <param id="dhcp.ipAddressLeaseTime" value="86400"/> <param id="dhcp.timeOffset" value="-18000"/> <param id="dhcp.router" value="10.21.255.1"/> </gate> <port gateId="11" id="24" ip="0A 23 F2 6E"/> </sync> dhcp.log Код: INFO 06.04.2010 10:02:21,393 main dhcp.server.identifier=10.176.74.151 INFO 06.04.2010 10:02:21,406 main Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)... INFO 06.04.2010 10:02:21,413 main option_82=1 INFO 06.04.2010 10:02:21,416 main position_82=1 INFO 06.04.2010 10:02:21,417 main dhcp.data.save.delay=3600000 INFO 06.04.2010 10:02:21,418 main dhcp.data.save.period=3600000 INFO 06.04.2010 10:02:21,422 main Load data from file. DEBUG 06.04.2010 10:02:21,796 main set gate 11 10.35.2.110 INFO 06.04.2010 10:02:21,800 main setGatePortIp: gateId = 11;port=24;adress=10.35.242.110 INFO 06.04.2010 10:02:21,804 main Processor init ok. INFO 06.04.2010 10:02:21,822 main DHCPSocketListener on port=67 init ok. INFO 06.04.2010 10:02:21,832 main AdminSocketListener on port=1868 init ok. INFO 06.04.2010 10:02:21,833 Thread-7 AdminSocketListener listen. DEBUG 06.04.2010 10:05:12,896 pool-1-thread-1 processing request DEBUG 06.04.2010 10:05:12,897 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 06.04.2010 10:05:12,898 pool-1-thread-1 agent information found! DEBUG 06.04.2010 10:05:12,899 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:05:12,900 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:05:12,900 pool-1-thread-1 gateId = 11 DEBUG 06.04.2010 10:05:21,007 pool-1-thread-2 processing request DEBUG 06.04.2010 10:05:21,008 pool-1-thread-2 OP_BOOT_REQUEST DEBUG 06.04.2010 10:05:21,008 pool-1-thread-2 agent information found! DEBUG 06.04.2010 10:05:21,009 pool-1-thread-2 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:05:21,010 pool-1-thread-2 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:05:21,010 pool-1-thread-2 gateId = 11 DEBUG 06.04.2010 10:05:25,008 pool-1-thread-3 processing request DEBUG 06.04.2010 10:05:25,008 pool-1-thread-3 OP_BOOT_REQUEST DEBUG 06.04.2010 10:05:25,009 pool-1-thread-3 agent information found! DEBUG 06.04.2010 10:05:25,010 pool-1-thread-3 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:05:25,011 pool-1-thread-3 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:05:25,011 pool-1-thread-3 gateId = 11 DEBUG 06.04.2010 10:05:34,010 pool-1-thread-4 processing request DEBUG 06.04.2010 10:05:34,011 pool-1-thread-4 OP_BOOT_REQUEST DEBUG 06.04.2010 10:05:34,012 pool-1-thread-4 agent information found! DEBUG 06.04.2010 10:05:34,014 pool-1-thread-4 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:05:34,015 pool-1-thread-4 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:05:34,016 pool-1-thread-4 gateId = 11 DEBUG 06.04.2010 10:05:49,012 pool-1-thread-5 processing request DEBUG 06.04.2010 10:05:49,012 pool-1-thread-5 OP_BOOT_REQUEST DEBUG 06.04.2010 10:05:49,013 pool-1-thread-5 agent information found! DEBUG 06.04.2010 10:05:49,014 pool-1-thread-5 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:05:49,014 pool-1-thread-5 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:05:49,015 pool-1-thread-5 gateId = 11 DEBUG 06.04.2010 10:06:26,077 pool-1-thread-6 processing request DEBUG 06.04.2010 10:06:26,078 pool-1-thread-6 OP_BOOT_REQUEST DEBUG 06.04.2010 10:06:26,079 pool-1-thread-6 agent information found! DEBUG 06.04.2010 10:06:26,080 pool-1-thread-6 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:06:26,080 pool-1-thread-6 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:06:26,081 pool-1-thread-6 gateId = 11 DEBUG 06.04.2010 10:06:29,079 pool-1-thread-7 processing request DEBUG 06.04.2010 10:06:29,080 pool-1-thread-7 OP_BOOT_REQUEST DEBUG 06.04.2010 10:06:29,080 pool-1-thread-7 agent information found! DEBUG 06.04.2010 10:06:29,081 pool-1-thread-7 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:06:29,082 pool-1-thread-7 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:06:29,082 pool-1-thread-7 gateId = 11 DEBUG 06.04.2010 10:06:36,079 pool-1-thread-8 processing request DEBUG 06.04.2010 10:06:36,081 pool-1-thread-8 OP_BOOT_REQUEST DEBUG 06.04.2010 10:06:36,082 pool-1-thread-8 agent information found! DEBUG 06.04.2010 10:06:36,083 pool-1-thread-8 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:06:36,085 pool-1-thread-8 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:06:36,086 pool-1-thread-8 gateId = 11 DEBUG 06.04.2010 10:06:51,080 pool-1-thread-9 processing request DEBUG 06.04.2010 10:06:51,081 pool-1-thread-9 OP_BOOT_REQUEST DEBUG 06.04.2010 10:06:51,081 pool-1-thread-9 agent information found! DEBUG 06.04.2010 10:06:51,082 pool-1-thread-9 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:06:51,083 pool-1-thread-9 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:06:51,086 pool-1-thread-9 gateId = 11 dhcp.out Код: 10:02:21,393 INFO dhcp:271 - dhcp.server.identifier=10.176.74.151 10:02:21,406 INFO dhcp:39 - Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)... 10:02:21,413 INFO dhcp:172 - option_82=1 10:02:21,416 INFO dhcp:173 - position_82=1 10:02:21,417 INFO dhcp:175 - dhcp.data.save.delay=3600000 10:02:21,418 INFO dhcp:176 - dhcp.data.save.period=3600000 10:02:21,422 INFO dhcp:185 - Load data from file. 10:02:21,796 DEBUG dhcp:656 - set gate 11 10.35.2.110 10:02:21,800 INFO dhcp:705 - setGatePortIp: gateId = 11;port=24;adress=10.35.242.110 ok 10:02:21,804 INFO dhcp:52 - Processor init ok. 10:02:21,822 INFO dhcp:106 - DHCPSocketListener on port=67 init ok. 10:02:21,832 INFO dhcp:62 - AdminSocketListener on port=1868 init ok. 10:02:21,833 INFO dhcp:81 - AdminSocketListener listen. 10:05:12,896 DEBUG dhcp:200 - processing request 10:05:12,897 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:12,898 DEBUG dhcp:244 - agent information found! 10:05:12,899 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:12,900 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:12,900 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-1" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 10:05:21,007 DEBUG dhcp:200 - processing request 10:05:21,008 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:21,008 DEBUG dhcp:244 - agent information found! 10:05:21,009 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:21,010 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:21,010 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-2" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 10:05:25,008 DEBUG dhcp:200 - processing request 10:05:25,008 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:25,009 DEBUG dhcp:244 - agent information found! 10:05:25,010 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:25,011 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:25,011 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-3" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 10:05:34,010 DEBUG dhcp:200 - processing request 10:05:34,011 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:34,012 DEBUG dhcp:244 - agent information found! 10:05:34,014 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:34,015 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:34,016 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-4" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 10:05:49,012 DEBUG dhcp:200 - processing request 10:05:49,012 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:49,013 DEBUG dhcp:244 - agent information found! 10:05:49,014 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:49,014 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:49,015 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-5" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 10:05:25,008 DEBUG dhcp:200 - processing request 10:05:25,008 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:05:25,009 DEBUG dhcp:244 - agent information found! 10:05:25,010 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:05:25,011 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:05:25,011 DEBUG dhcp:264 - gateId = 11 пакет Op.82 Код: Value: 01040018044C

Страница 1 из 1	Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/

Автор:	mrustik [ 06 апр 2010, 10:21 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Все тоже самое, но для Qtech dhcp.properties Код: processor.class=bitel.billing.server.ext.dhcp.DHCPRelayProcessor #processor.class=bitel.billing.server.ext.dhcp.DHCPVlanRelayProcessor #Номер субопции в Option 82, в которой хранится vlan клиента(нумерация с 1) dhcp.82.key.option.code=1 #Позиция(номер байта) внутри субопции, в которой хранится vlan клиента(нумерация с 0). #dhcp.82.key.position=2 #Позиция(номер байта) внутри субопции, в которой хранится порт клиента(нумерация с 0). dhcp.82.key.position=5 admin.port=1868 dhcp.thread.count=10 dhcp.data.save.delay=3600 dhcp.data.save.period=3600 dhcp.server.identifier=10.176.74.151 dhcp.data Код: <?xml version="1.0" encoding="UTF-8"?> <sync> <gate id="11" host="10.35.2.110"> <param id="dhcp.option.121" value="190AB04A800A23FF011B511E3B000A23FF01"/> <param id="dhcp.dns" value="10.176.74.131"/> <param id="dhcp.subnetMask" value="255.240.0.0"/> <param id="dhcp.ipAddressLeaseTime" value="86400"/> <param id="dhcp.timeOffset" value="-18000"/> <param id="dhcp.router" value="10.21.255.1"/> </gate> <port gateId="11" id="24" ip="0A 23 F2 6E"/> </sync> dhcp.log Код: INFO 06.04.2010 10:13:41,839 main dhcp.server.identifier=10.176.74.151 INFO 06.04.2010 10:13:41,852 main Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)... INFO 06.04.2010 10:13:41,860 main option_82=1 INFO 06.04.2010 10:13:41,863 main position_82=5 INFO 06.04.2010 10:13:41,864 main dhcp.data.save.delay=3600000 INFO 06.04.2010 10:13:41,865 main dhcp.data.save.period=3600000 INFO 06.04.2010 10:13:41,868 main Load data from file. DEBUG 06.04.2010 10:13:42,243 main set gate 11 10.35.2.110 INFO 06.04.2010 10:13:42,247 main setGatePortIp: gateId = 11;port=24;adress=10.35.242.110 INFO 06.04.2010 10:13:42,251 main Processor init ok. INFO 06.04.2010 10:13:42,269 main DHCPSocketListener on port=67 init ok. INFO 06.04.2010 10:13:42,280 main AdminSocketListener on port=1868 init ok. INFO 06.04.2010 10:13:42,281 Thread-7 AdminSocketListener listen. DEBUG 06.04.2010 10:14:35,555 pool-1-thread-1 processing request DEBUG 06.04.2010 10:14:35,556 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 06.04.2010 10:14:35,556 pool-1-thread-1 agent information found! DEBUG 06.04.2010 10:14:35,557 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:14:35,558 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:14:35,559 pool-1-thread-1 gateId = 11 DEBUG 06.04.2010 10:14:35,561 pool-1-thread-1 port=24 DEBUG 06.04.2010 10:14:35,562 pool-1-thread-1 ip = 10.35.242.110 DEBUG 06.04.2010 10:14:35,563 pool-1-thread-1 DHCP_DISCOVER DEBUG 06.04.2010 10:14:47,732 pool-1-thread-1 processing request DEBUG 06.04.2010 10:14:47,733 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 06.04.2010 10:14:47,733 pool-1-thread-1 agent information found! DEBUG 06.04.2010 10:14:47,734 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:14:47,735 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:14:47,736 pool-1-thread-1 gateId = 11 DEBUG 06.04.2010 10:14:47,736 pool-1-thread-1 port=24 DEBUG 06.04.2010 10:14:47,737 pool-1-thread-1 ip = 10.35.242.110 DEBUG 06.04.2010 10:14:47,738 pool-1-thread-1 DHCP_DISCOVER DEBUG 06.04.2010 10:14:47,772 pool-1-thread-1 processing request DEBUG 06.04.2010 10:14:47,776 pool-1-thread-1 OP_BOOT_REQUEST DEBUG 06.04.2010 10:14:47,777 pool-1-thread-1 agent information found! DEBUG 06.04.2010 10:14:47,779 pool-1-thread-1 DHCP_REQUEST or DHCP_DISCOVER DEBUG 06.04.2010 10:14:47,781 pool-1-thread-1 request.giaddr =10.35.2.110 DEBUG 06.04.2010 10:14:47,782 pool-1-thread-1 gateId = 11 DEBUG 06.04.2010 10:14:47,782 pool-1-thread-1 port=24 DEBUG 06.04.2010 10:14:47,783 pool-1-thread-1 ip = 10.35.242.110 DEBUG 06.04.2010 10:14:47,784 pool-1-thread-1 DHCP_REQUEST DEBUG 06.04.2010 10:14:47,784 pool-1-thread-1 DHCP_ACK dhcp.out Код: 10:13:41,839 INFO dhcp:271 - dhcp.server.identifier=10.176.74.151 10:13:41,852 INFO dhcp:39 - Starting BGDhcpIPN (BGBilling DHCP server/gate for IPN)... 10:13:41,860 INFO dhcp:172 - option_82=1 10:13:41,863 INFO dhcp:173 - position_82=5 10:13:41,864 INFO dhcp:175 - dhcp.data.save.delay=3600000 10:13:41,865 INFO dhcp:176 - dhcp.data.save.period=3600000 10:13:41,868 INFO dhcp:185 - Load data from file. 10:13:42,243 DEBUG dhcp:656 - set gate 11 10.35.2.110 10:13:42,247 INFO dhcp:705 - setGatePortIp: gateId = 11;port=24;adress=10.35.242.110 ok 10:13:42,251 INFO dhcp:52 - Processor init ok. 10:13:42,269 INFO dhcp:106 - DHCPSocketListener on port=67 init ok. 10:13:42,280 INFO dhcp:62 - AdminSocketListener on port=1868 init ok. 10:13:42,281 INFO dhcp:81 - AdminSocketListener listen. 10:14:35,555 DEBUG dhcp:200 - processing request 10:14:35,556 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:14:35,556 DEBUG dhcp:244 - agent information found! 10:14:35,557 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:14:35,558 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:14:35,559 DEBUG dhcp:264 - gateId = 11 10:14:35,561 DEBUG dhcp:333 - port=24 10:14:35,562 DEBUG dhcp:273 - ip = 10.35.242.110 10:14:35,563 DEBUG dhcp:281 - DHCP_DISCOVER 10:14:47,732 DEBUG dhcp:200 - processing request 10:14:47,733 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:14:47,733 DEBUG dhcp:244 - agent information found! 10:14:47,734 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:14:47,735 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:14:47,736 DEBUG dhcp:264 - gateId = 11 10:14:47,736 DEBUG dhcp:333 - port=24 10:14:47,737 DEBUG dhcp:273 - ip = 10.35.242.110 10:14:47,738 DEBUG dhcp:281 - DHCP_DISCOVER 10:14:47,772 DEBUG dhcp:200 - processing request 10:14:47,776 DEBUG dhcp:203 - OP_BOOT_REQUEST 10:14:47,777 DEBUG dhcp:244 - agent information found! 10:14:47,779 DEBUG dhcp:247 - DHCP_REQUEST or DHCP_DISCOVER 10:14:47,781 DEBUG dhcp:251 - request.giaddr =10.35.2.110 10:14:47,782 DEBUG dhcp:264 - gateId = 11 10:14:47,782 DEBUG dhcp:333 - port=24 10:14:47,783 DEBUG dhcp:273 - ip = 10.35.242.110 10:14:47,784 DEBUG dhcp:288 - DHCP_REQUEST 10:14:47,784 DEBUG dhcp:310 - DHCP_ACK пакет Op.82 Код: Value: 01060004044C0018020F000D31302E3137362E38322E3234... Код: Agent Circuit ID: 0004044C0018 Единственное различие dhcp.82.key.position=5 для Qtech и dhcp.82.key.position=1 для Zyxel

Автор:	mrustik [ 06 апр 2010, 11:03 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Вот сам пакет запроса Zyxel Код: No. Time Source Destination Protocol Info 332 33.787444 10.35.2.110 10.176.74.151 DHCP DHCP Request - Transaction ID 0x5fe89b63 Frame 332 (373 bytes on wire, 373 bytes captured) Arrival Time: Apr 6, 2010 10:50:03.173687000 [Time delta from previous captured frame: 0.002777000 seconds] [Time delta from previous displayed frame: 33.787444000 seconds] [Time since reference or first frame: 33.787444000 seconds] Frame Number: 332 Frame Length: 373 bytes Capture Length: 373 bytes [Frame is marked: False] [Protocols in frame: eth:vlan:ip:udp:bootp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a), Dst: AsustekC_10:da:4f (00:13:d4:10:da:4f) Destination: AsustekC_10:da:4f (00:13:d4:10:da:4f) Address: AsustekC_10:da:4f (00:13:d4:10:da:4f) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) Source: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a) Address: Cisco_5e:9f:4a (00:1e:49:5e:9f:4a) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) Type: 802.1Q Virtual LAN (0x8100) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 102 000. .... .... .... = Priority: 0 ...0 .... .... .... = CFI: 0 .... 0000 0110 0110 = ID: 102 Type: IP (0x0800) Internet Protocol, Src: 10.35.2.110 (10.35.2.110), Dst: 10.176.74.151 (10.176.74.151) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 355 Identification: 0x805e (32862) Flags: 0x00 0... = Reserved bit: Not set .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 254 Protocol: UDP (0x11) Header checksum: 0xd953 [correct] Source: 10.35.2.110 (10.35.2.110) Destination: 10.176.74.151 (10.176.74.151) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Message type: Boot Request (1) Hardware type: Ethernet Hardware address length: 6 Hops: 1 Transaction ID: 0x5fe89b63 Seconds elapsed: 0 Bootp flags: 0x0000 (Unicast) Client IP address: 10.35.242.110 (10.35.242.110) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 10.35.2.110 (10.35.2.110) Client MAC address: ArimaCom_0f:d4:b9 (00:03:25:0f:d4:b9) Server host name not given Boot file name not given Option: (t=53,l=1) DHCP Message Type = DHCP Request Option: (53) DHCP Message Type Length: 1 Value: 03 Option: (t=61,l=7) Client identifier Option: (61) Client identifier Length: 7 Value: 010003250FD4B9 Hardware type: Ethernet Client MAC address: ArimaCom_0f:d4:b9 (00:03:25:0f:d4:b9) Option: (t=12,l=15) Host Name = "microsof-682ebb" Option: (12) Host Name Length: 15 Value: 6D6963726F736F662D363832656262 Option: (t=81,l=19) Client Fully Qualified Domain Name Option: (81) Client Fully Qualified Domain Name Length: 19 Value: 0000006D6963726F736F662D3638326562622E Flags: 0x00 0000 .... = Reserved flags: 0x00 .... 0... = Server DDNS: Some server updates .... .0.. = Encoding: ASCII encoding .... ..0. = Server overrides: No override .... ...0 = Server: Client A-RR result: 0 PTR-RR result: 0 Client name: microsof-682ebb. Option: (t=60,l=8) Vendor class identifier = "MSFT 5.0" Option: (60) Vendor class identifier Length: 8 Value: 4D53465420352E30 Option: (t=55,l=11) Parameter Request List Option: (55) Parameter Request List Length: 11 Value: 010F03062C2E2F1F21F92B 1 = Subnet Mask 15 = Domain Name 3 = Router 6 = Domain Name Server 44 = NetBIOS over TCP/IP Name Server 46 = NetBIOS over TCP/IP Node Type 47 = NetBIOS over TCP/IP Scope 31 = Perform Router Discover 33 = Static Route 249 = Classless Static Route (Microsoft) 43 = Vendor-Specific Information Option: (t=43,l=3) Vendor-Specific Information Option: (43) Vendor-Specific Information Length: 3 Value: DC0100 Option: (t=82,l=6) Agent Information Option Option: (82) Agent Information Option Length: 6 Value: 01040018044C Agent Circuit ID: 0018044C End Option

Автор:	mrustik [ 06 апр 2010, 11:04 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Судя по ответам приведенной ссылки должно работать, но не работает.

Автор:	stark [ 07 апр 2010, 15:22 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
mrustik писал(а): 10:05:12,900 DEBUG dhcp:264 - gateId = 11 Exception in thread "pool-1-thread-1" java.lang.NullPointerException at bitel.billing.server.ext.dhcp.DHCPPacket.findOption(DHCPPacket.java:581) at bitel.billing.server.ext.dhcp.DHCPPacket.access$2(DHCPPacket.java:576) at bitel.billing.server.ext.dhcp.DHCPPacket$DHCPSubOption.getSubOption(DHCPPacket.java:155) at bitel.billing.server.ext.dhcp.DHCPProcessor.getDHCPClientIdentifier(DHCPProcessor.java:98) at bitel.billing.server.ext.dhcp.DHCPRelayProcessor.processRequest(DHCPRelayProcessor.java:266) at bitel.billing.server.ext.dhcp.DHCPRequestThread.run(DHCPRequestThread.java:21) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Вот с этого и надо было начинать. я же спрашивал есть ли увас ошибки в логах

Автор:	stark [ 07 апр 2010, 15:26 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
stark писал(а): mrustik писал(а): Есть еще более существенное различие, нет в запросе поля Agent Remote ID, может это иметь значение для DHCP сервера ? нет я ошибся , оказывается имеет.. Попробую это исправить

Автор:	stark [ 07 апр 2010, 15:46 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
покажите пакет от Qtech

Автор:	stark [ 07 апр 2010, 17:23 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
все . там ошибка была . исправлено . Обновление dhcp выложено .

Автор:	mrustik [ 08 апр 2010, 09:43 ]
Заголовок сообщения:	Re: DHCP Op.82 Circuit ID
Спасибо, все заработало.