- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Re: cloudguard interface _rename issue
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
			
				
					
						
							cloudguard interface _rename issue
						
					
					
				
			
		
	
		
	
	
	
	
	
	
	
	
			
					
				
		
	
Hi
We are deploying cloudguard R80.20 in Azure as per sk110194 and are noticing extra interfaces with '_rename' in them. Instead of eth0 and eth1 we see total of 4 interfaces
eth0
eth1
eth2_rename
eth3_rename
Output of ifconfig is
ifconfig -a | grep -v grep | grep HWaddr | awk '{print $1,$5}'
eth0 00:0D:3A:7E:82:B6                      state -on
eth1 00:0D:3A:7E:87:40                       state -on
eth2_rename 00:0D:3A:7E:87:40       state -on
eth3_rename 00:0D:3A:7E:82:B6       state -off
Has anyone came across this issue?
R80.10 does not have this issue.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI
We looked at sk86121 but its more for physical boxes as apposed to the cloudguard virtual applications.
Its seems the build has a missing script eth_hv_rename from /sbin/ folder. Although this doesn't entirely fix the issue. Hopefully CP will fix the build in the very near future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Most likely the additional interfaces are related to Azure accelerated networking feature.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI Constantin
It was an issue with the build script. There is a fix for it I can't remember the SK for it. Its been fixed in the latest build.
Cheers
 
					
				
				
			
		


 
					
				
		
 
		
			 
					
				
		
 
					
				 
		
		
		
		
		
	
			 
		
			 
					
				